Ubuntu
cryptsetup package

regression: /home on dm-crypt+LVM fails to mount during boot (due to failed fsck)

Bug #421876 reported by Luka Renko
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
Fix Released
Undecided
Unassigned
lvm2 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: cryptsetup

SW: Kubuntu Karmic up-to-date
HW: ThinkPad X200s

I am opening new bug report as my old bug 418901 was marked as duplicate.

I have done a fresh install of Kubuntu Karmic on my laptop. I have used same/similar disk layout as I use on Jaunty:
- /boot on regular partition (/dev/sda1)
- / on LVM volume on regular physical partition (/dev/sda3)
- /home on LVM volume on top of dm-crypt physical volume (/dev/sda2)

Karmic boot fails almost in 100% (I think boot succeeded once or twice), because fsck fails finding UUID of my /home partition (see attached /var/log/fsck/checkfs). I can easily workaround the problem by issuing "mount -a" (which successfully mounts /home) and "exit" the shell and then the boot sequence continues properly.

I have attached "fdisk -l /dev/sda" and "vgdisplay -v" output. If anything more is needed, please let me know.

ProblemType: Bug
Architecture: amd64
Date: Mon Aug 31 12:55:54 2009
DistroRelease: Ubuntu 9.10
Package: cryptsetup 2:1.0.6+20090405.svn49-1ubuntu1
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-8.28-generic
SourcePackage: cryptsetup
Uname: Linux 2.6.31-8-generic x86_64

Revision history for this message
Luka Renko (lure) wrote :
Revision history for this message
Luka Renko (lure) wrote :

Content of /var/log/fsck/checkfs file indicating root cause of the problem:

Log of fsck -C3 -R -A -a
Mon Aug 31 12:32:12 2009

fsck from util-linux-ng 2.16
boot: recovering journal
boot: clean, 188/62248 files, 89730/248976 blocks (check in 2 mounts)
fsck.ext4: Unable to resolve 'UUID=47bcbd50-5ae6-47c5-88b9-463e577f7ade'
/dev/mapper/plain-misc: recovering journal
/dev/mapper/plain-misc: clean, 5658/2621440 files, 9378933/10485760 blocks
fsck died with exit status 8

Mon Aug 31 12:32:13 2009
----------------

Note: I suspect this is some timing issue in the boot sequence (udev or upstart related), as the fsck seems to be run before LVM is properly set-up on top of dm-crypt device.

Revision history for this message
Luka Renko (lure) wrote :
Revision history for this message
Luka Renko (lure) wrote :

As you can see, UUID of the file system that fails is the one for /home

Revision history for this message
Luka Renko (lure) wrote :

Attached is the photo of the shell prompt where my boot ends as it is unable to fsck /home. "mount -a" helps and mounts /home properly.

Revision history for this message
Luka Renko (lure) wrote :

I would also like to note that other LVM-only filesystem (/misc) does not get mounted sometime, but I am not sure if this is just side-effect of /home failure (depends on timing of mount commands executed and when

I am adding lvm2 task, as it seems dm-crypt gets properly setup, but LVM does not get started on top of it, so it may be bug in LVM udev config.

tags: added: regression-release
Revision history for this message
Luka Renko (lure) wrote :

This bug is now fixed for me by recent changes/switch to upstart job - see bug 430496 for details.

Changed in cryptsetup (Ubuntu):
status: New → Fix Released
Changed in lvm2 (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.