Hi,
Thanks in advance for any help with this one -- it's quite a show-stopping issue for me at the moment.
Yesterday, Adept did 3 automatic updates which had something to do with "volume". I didn't read them properly and thought at the time that it was to do with audio (hence quite harmless), but when I rebooted shortly after I discovered that the encrypted root partition of my SATA disk wouldn't mount (it uses the standard LVM encryption option from the Kubuntu installer). The mental cogs then started to turn, and D.P. Gumby suggested that "volume" probably referred to the other kind of volume. I've tried to find out exactly what these packages were, and the best I can come up with is these:
libvolume-id-dev
libvolume-id0
volumeid
and I know that, in the update, one of them was removed; but I don't know where to check to see whether these are, actually, the packages that were updated. Obviously I can't just check the logs at this stage.
OK, here's what happens at boot, when I remove the "quiet" option in the grub boot script:
Loading essential drivers... ok
Running /scripts/init-premount ok
Mounting root file system...
Running scripts/local-top ok
Waiting for root file system...
...and it continues to wait for about 200 seconds before dropping into the BusyBox.
This is the kernel line from grub: /vmlinuz-2.6.22-14-generic root=/dev/mapper/kubuntu-root ro quiet splash
I noticed that /dev/mapper/kubuntu-root doesn't exist, so I changed the grub boot script to root=/dev/sda5 (my encrypted partition), and this merely had the rather predictable effect of doing nothing except dropping me into BusyBox (though without the 200 seconds wait). For any other device (/dev/sda, /dev/sda1, /dev/sda2) it still waits 200 seconds but then drops into BusyBox. For reference, here's /proc/partitions:
8 0 78150744 sda
8 1 248976 sda1
8 2 1 sda2
8 5 77899153 sda5
sda1 is /boot, and sda5 is /. sda2 is presumably some sort of wrapper for the encrypted volume sda5.
I can't see anything in /proc/kmsg that would indicate it was trying to mount an encrypted volume (no "cryptsetup" or /dev/mapper/cryptoroot), and I see no reference to anything containing the word "crypt" in /lib or in /conf/modules or in any of the scripts in /scripts.
This is way over my head, so can anyone here offer any help as to how I might mount the filesystem and what I should do to make it boot properly in future? Thanks in advance...
Thanks in advance for any help with this one -- it's quite a show-stopping issue for me at the moment.
Yesterday, Adept did 3 automatic updates which had something to do with "volume". I didn't read them properly and thought at the time that it was to do with audio (hence quite harmless), but when I rebooted shortly after I discovered that the encrypted root partition of my SATA disk wouldn't mount (it uses the standard LVM encryption option from the Kubuntu installer). The mental cogs then started to turn, and D.P. Gumby suggested that "volume" probably referred to the other kind of volume. I've tried to find out exactly what these packages were, and the best I can come up with is these:
libvolume-id-dev
libvolume-id0
volumeid
and I know that, in the update, one of them was removed; but I don't know where to check to see whether these are, actually, the packages that were updated. Obviously I can't just check the logs at this stage.
OK, here's what happens at boot, when I remove the "quiet" option in the grub boot script:
Loading essential drivers... ok
Running /scripts/init-premount ok
Mounting root file system...
Running scripts/local-top ok
Waiting for root file system...
...and it continues to wait for about 200 seconds before dropping into the BusyBox.
This is the kernel line from grub: /vmlinuz-2.6.22-14-generic root=/dev/mapper/kubuntu-root ro quiet splash
I noticed that /dev/mapper/kubuntu-root doesn't exist, so I changed the grub boot script to root=/dev/sda5 (my encrypted partition), and this merely had the rather predictable effect of doing nothing except dropping me into BusyBox (though without the 200 seconds wait). For any other device (/dev/sda, /dev/sda1, /dev/sda2) it still waits 200 seconds but then drops into BusyBox. For reference, here's /proc/partitions:
8 0 78150744 sda
8 1 248976 sda1
8 2 1 sda2
8 5 77899153 sda5
sda1 is /boot, and sda5 is /. sda2 is presumably some sort of wrapper for the encrypted volume sda5.
I can't see anything in /proc/kmsg that would indicate it was trying to mount an encrypted volume (no "cryptsetup" or /dev/mapper/cryptoroot), and I see no reference to anything containing the word "crypt" in /lib or in /conf/modules or in any of the scripts in /scripts.
This is way over my head, so can anyone here offer any help as to how I might mount the filesystem and what I should do to make it boot properly in future? Thanks in advance...
Comment