Boot stalls waiting for Luks encrypted external disk after upgrade to Lucid from Karmic

[jcat]

After upgrading from Karmic to Lucid, I rebooted to complete the upgrade.
However, early in the boot process, it displays a message like "Waiting for /data (SD)", and never proceeds any further.

I believe the system was attempting to fsck the drive, but the drive was not attached at the time attached.

fstab entry:
LABEL=DATA /data ext4 relatime 0 2

If I choose to boot without splash, the process halts after displaying a message:
Init: Unreadable other main process (896) terminated with status 4

I did not have the drive to attach, so the only fix was to remove it from fstab after booting off a live CD.

Whenever I add the entry back into fstab, the boot process halts at the same point again. That configuration was fine under Karmic.

Packages are fully up to date as of now.

If I need to provide more info, please let me know.

Cheers,
jcat

[jcat (jcat)]

If someone has the power to change "upfrade" to "upgrade", please do it :)

[rwhitehurst (ubuntu-launchpad-ghyspran)]

I get a similar problem, except with separate encrypted /home and swap partitions. System hangs after prompting for passwords for the partitions or if system set to use keyfiles saved in /etc. If splash and quiet are removed from the boot line, the system drops to a recovery shell, displaying "General error mounting partitions". In /dev/mapper are sda3_crypt (swap partition), sda3_crypt_unformatted (?), sda6_crypt (home partition), and sda6_crypt_unformatted (?). None of these are mounted, but manually mounting works fine. Commenting out the relevant lines in /etc/fstab allows the system to boot, but /home must be manually mounted before login.

[Valentin (vsurrel)]

Exactly same symptoms here, mounting encrypted luks partition fails (hangs) during boot, dropping in recevery shell hitting "Enter".

Manual mount before login (CTRL-ALT-F2 to text-login, luksOpen and then mount /home) works correctly

[Valentin (vsurrel)]

I forgot to say that it fails after upgrade and after full re-install of Lucid Beta1. (trying to mount existing encrypted /home)

[Jeremy Foshee (jeremyfoshee)]

Hi jcat,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 541857

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Valentin (vsurrel)]

Works for me in 10.04 release.

[Jeremy Foshee (jeremyfoshee)]

jcat, can you verify Valentin's findings above?

Thanks!

~JFo

[jcat (jcat)]

Hi,

I believe our disk problems are actually slightly different.

My system won't boot if I have the entry in fstab, but without the external encrypted disk attached.
If I remove the entry from fstab, the system will then boot without the disk.

In addition, after testing again, I also realised that boot fails with the disk attached as well!
If I remove the entry from fstab, the system boots with or without the disk.

This config was fine with Karmic. I was able to leave the entry in fstab, and boot with or without the drive.

I updated the packages on this system today, added the entry back into fstab, then tried to boot without the disk attached again.
The problem is still present, it fails to boot in the same way as before.

I'll attach screen shots of the boot with and without the disk, with the entry in fstab.

Cheers,
jcat

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[jcat (jcat)]

So no one wants to fix it then..?

I started this bug report, and my original problem remains. I'm glad that someone else's issue was fixed, but that was not the subject of this bug.

I supplied info when requested. Indeed, the last comments on this bug were from me.
My original problem remains.

This doesn't really make me feel like raising any further bugs, even for the good of the project, as the response I received on this one has been poor.
Indeed, now it's closed due to lack of activity. If further information was required from me, then it should have been requested, I'm not psychic.

Cheers,
jcat

[kenorb (kenorb)]

The same problem after upgrade.
This workaround works: http://ubuntuforums.org/showthread.php?t=1138779
I agree, this should be fixed permanently!!!
I already spent 2 days to do upgrade, because every time there are some different kind of problems which I have to look on Google.