From your BootInfo Script, I can see that GRUB2 resides erroneously on /sda1, your Windows boot partition. I'm not much into Windows anymore, but from what I know there are tools on the Windows CD that allow restoration of bootsectors. You need to boot from the Windows CD and start the repair mode. On the command line, you can try
bootrec.exe /fixboot
to restore your Windows partition boot sector.
Then, however, you won't be able to boot Ubuntu, because there will be no more GRUB2. GRUB2 should have been installed in the MBR of /sda which is not so in your case. This means you will either have to reinstall GRUB (using a Ubuntu live CD) there, or you may find it less time consuming to reinstall Ubuntu as a whole. The latter should not be a great thing if you only installed it recently for testing. In any case, take note that you should not install Grub2 on your Windows boot sector again.
As @mook765 mentions in comments, I think you can use PARTUUID, but just without quotes.
PARTUUID=5678-03 /boot [...]
Also, failing that, I think you can use the /dev/disk/by-partuuid/* symlinks that udev creates.
You may also want to use 'UUID', not 'PARTUUID'. Here's an example of the boot section of my fstab (this is the default of Ubuntu):
# /boot was on /dev/sda1 during installation
UUID=4e8a17a6-87ca-403b-9a1a-896d553e518c /boot ext3 defaults 0 2
UUID=7A56-4947 /boot/efi vfat defaults 0 1
To get the UUID of a block device:
sudo blkid /dev/sda1
/dev/sda1: LABEL="ubuntu-boot" UUID="4e8a17a6-87ca-403b-9a1a-896d553e518c" TYPE="ext3" PARTLABEL="ubuntu-boot" PARTUUID="57e3d2de-492b-4875-b110-76325e2401ec"
Just for example on another machine, you'll notice that each filesystem on the disk has a different UUID:
root@bierstadt:~# lsblk -o name,UUID /dev/sda
NAME UUID
sda
├─sda1 8D99-B7B6
├─sda2 147da7cf-c356-4ff9-a6fa-8fb555290b25
└─sda3 1dd7ce7d-6de9-40e0-bd3f-5550ae40a588
└─sda3_crypt mAdSjw-3B31-Z7Im-WbCk-QmIP-b01M-5mFckC
├─ubuntu--vg-root 1b3d8c0f-2241-48c1-a272-39f8e683ccc9
└─ubuntu--vg-swap_1 fd34789c-c65f-4253-a810-8183988e9760
Note the UUID comes with the filesystem. So, if you have cloned the partition, the UUID will come with it. You should probably change it if you want to mount it, or refer to it distinctly:
From this blog:
Since it is not possible to mount two file systems with the same UUID,
extra care need to be taken when LVM snapshots (or cloned disks) are
used in an environment: mounting might fail due to duplicate UUIDs.
[...]
One way to deal with this is by the way to change the UUID during
creation or afterwards, another way is to mount with the nouuid
option.
To change:
# tune2fs -U new_uuid /dev/sdaX
References
Best Answer
I solved the problem of slow booting. When I saw the boot messages it showed me that a startup process is running my dev mapper. I checked the
/etc/fstaband there was a swapfile indicating/swapfilebut I checked usingfree -mthat I didn't have a swap set up. So I set up a swap but still the problem remained unchanged. The actual problem was that there was an unexisting drive listed on the/etc/crypttabwhich was causing the issue. I commented out the line and now it boots fine.So if you have starup job slow boot issue, please do check:
sudo swapon -s#and a space at the starting of the line./etc/crypttab. If there is, comment it out.