I've used the Debian installer (Sarge) for installing a system onto an
SSD, using this layout:
/dev/sda5 luks, -> sda5_crypt with "/"
After the installation finished, I realized that I should have aligned
the partition boundaries. So I booted into GRML, backed up the file
systems with tar, created a new partition table + filesystems
manually, mounted, extracted the tars. Mounted in correct nesting plus
/proc /sys /dev and chroot'ed inside, "grub-setup -d /boot/grub
Now, the difficult part is figuring out all the locations where the
system is using UUIDs (d'oh!), and maybe other information that has
changed by me recreating the partition table.
I've updated /etc/fstab and /etc/crypttab and ran update-grub from
within the chroot (while running GRML). Now grub doesn't complain/warn
anymore about not finding devices, but after the kernel loads, the
boot process still says:
[ .... ] ... BAR 6: no parent found for of device [0xfffe000-0xffffffff]
Loading, please wait...
cryptsetup: lvm is not available
cryptsetup: evms_activate is not available
then it hangs indefinitely (minutes, giving up), but hitting ctl-c is
giving me the initrd shell. I can "cryptsetup luksOpen /dev/sda5
sda5_crypt" and ctl-d to continue the boot (actually it then tries to
open sda5 again, failing, then continues). But I don't see why it
hangs above, and whether the messages before the hang are relevant.
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com
Archive: CAEjYwfVCRHfYaX-Rx0Z6jcSP=yobWbiCMa1xjRJHZV3xAvSN6Q@mail.gmail.com ">http://lists.debian.org/CAEjYwfVCRHfYaX-Rx0Z6jcSP=yobWbiCMa1xjRJHZV3xAvSN6Q@mail.gmail.com