Red Hat Bugzilla – Bug 464900
Boot sequence fails with encrypted /home on native partition
Last modified: 2008-10-01 10:09:05 EDT
Description of problem: The boot sequence fails when /home is on separate physical partition and is encrypted. Version-Release number of selected component (if applicable): initscripts-8.45.20-1 How reproducible: Always Steps to Reproduce: 1. Install the system. Disk layout is: /dev/sda1 vfat /boot/efi (on ia64 or /boot otherwise) /dev/sda2 ext3 / not ecnrypted /dev/sdb1 ext3 /home encrypted 2. Reboot after install Actual results: System failed to boot Expected results: System boots and asks the user for a pass phrase late in the init process Additional info: The console message is: Loading default keymap (us): [ OK ] Setting hostname localhost.localdomain: [ OK ] Starting disk encryption: Command failed: Error opening device: No such file or directory [FAILED] No devices found Setting up Logical Volume Management: [ OK ] Checking filesystems Checking all file systems. [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda2 /: clean, 17798/35848192 files, 1353630/35818076 blocks [/sbin/fsck.ext3 (1) -- /home] fsck.ext3 -a LABEL=/home fsck.ext3: Unable to resolve 'LABEL=/home' [FAILED] *** An error occurred during the file system check. *** Dropping you to a shell; the system will reboot *** when you leave the shell. *** Warning -- SELinux is active *** Disabling security enforcement for system recovery. *** Run 'setenforce 1' to reenable. Give root password for maintenance (or type Control-D to continue):
More info after typin gin the root password: (Repair filesystem) 1 # cat /etc/crypttab luks-fd15a4e9-8921-4683-937c-7f6d95f6a352 UUID=fd15a4e9-8921-4683-937c-7f6d95f6a352 none (Repair filesystem) 2 # cat /etc/fstab LABEL=/ / ext3 defaults 1 1 LABEL=/home /home ext3 defaults 1 2 /dev/sda1 /boot/efi vfat defaults 0 0 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 (Repair filesystem) 7 # dumpe2fs /dev/sdb1 dumpe2fs 1.39 (29-May-2006) dumpe2fs: Bad magic number in super-block while trying to open /dev/sdb1 Couldn't find valid filesystem superblock.
*** This bug has been marked as a duplicate of bug 464787 ***