here's your problem:
=================== blkid:
/dev/sda3: UUID="f18a769e-4f52-49ad-a38e-bab773834ad8" TYPE="crypto_LUKS"
mount: unknown filesystem type 'crypto_LUKS'
mount /dev/sda3 : Error code 32
mount -r /dev/sda3 /mnt/boot-sav/sda3
mount: unknown filesystem type 'crypto_LUKS'
mount -r /dev/sda3 : Error code 32
ermm...
at this point, you'll probably need to load up a live cd, and mount your lukscrypt partition there, with the decryption key.
you're going to need to use /dev/mapper for mounting sda3 in your fstab/mount commands.
At this point, I suspect, you're going to need to boot to a live Ubuntu CD, chroot
the Ubuntu environment, mount all the partitions on all the drives, and run grub-update. This process should both recover the boot for Windows and Linux to the grub menu.
Try the following:
- Boot the Ubuntu LiveDVD
- Select the option Try Ubuntu
Then try the following:
sudo su -
mount /dev/sda3 /mnt
cryptsetup luksOpen /dev/sda3/ crypthome
mount /dev/mapper/crypthome /mnt
At this point, you'll have mounted your encrypted LUKS partition to /mnt
on the LiveDVD.
I would advise saving everything from /mnt/home
to external storage before continuing. Worst case, if this becomes too painful, you can start over and at least save any docs/pics/desktop/junk/etc you may have been working on.
Now we're going to attempt to fix things... through a chroot
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
chroot /mnt /bin/bash
At this stage you'll be in your PC's native OS in a chroot environment, but we're far from clear of your problem: we're going to need to review things, so your input from here forward will greatly help.
copy things that will help us diagnose, your pc should have internet access as well, if not you can place the following things on external storage and paste individually to http://paste.ubuntu.com/ passing the links back to this help topic.
/etc/fstab
/dev/mapper/*
- Please update on your progress and pain points. At the moment, it's hard to decypher just what went wrong
- you're running full disk encryption and the mount point for dev/mapper doesn't appear to be properly set up, so boot is failing...