Description of problem: System panics when trying to boot. It has encrypted partitions. Version-Release number of selected component (if applicable): kernel-2.6.18-118.el5 How reproducible: always Steps to Reproduce: 1. Install latest RHEL5.3 build with the following disk layout: Partition Size Mount point FS type Format /dev/cciss/c0d0p1 250 M none vfat NO /dev/cciss/c0d0p2 400 M none vfat NO /dev/cciss/c0d0p3 100 M /boot/efi vfat YES /dev/cciss/c0d0p4 132 G / ext3 YES, Encrypted Actual results: Install completes and system panics on boot Expected results: System prompts for LUKS pass phrase and boots properly Additional info: Main difference between the system in question and another system that doesn't exhibit the issue is the use of hardware RAID controller (see disk names).
* kernel 2.6.18-118.el5, no disk encryption - boots to run level 3 * kernel 2.6.18-118.el5, use disk encryption: sh-3.2# blkid /dev/cciss/c0d0p4 /dev/cciss/c0d0p4: LABEL="/" UUID="df8568f1-bf9c-4556-b343-cf3425142d5c" SEC_TYPE="ext2" TYPE="ext3" ^^ this is the encrypted device sh-3.2# cat /boot/efi/efi/redhat/elilo.conf prompt timeout=20 default=linux relocatable image=vmlinuz-2.6.18-118.el5 label=linux initrd=initrd-2.6.18-118.el5.img read-only append="root=LABEL=/1" ^^ label seems incorrect sh-3.2# cat /etc/crypttab luks-3017a657-fd05-4557-bc4f-6620015c08f0 UUID=3017a657-fd05-4557-bc4f-6620015c08f0 none sh-3.2# cat /etc/fstab /dev/mapper/luks-3017a657-fd05-4557-bc4f-6620015c08f0 / ext3 defaults 1 1 /dev/cciss/c0d0p3 /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 after boot I got: Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc:Kernel panic - not syncing: Attempted to kill init! No such file or directory setu * try to tell kernel / is on LUKS device (panic again): image=vmlinuz-2.6.18-118.el5 label=linux-luks-label initrd=initrd-2.6.18-118.el5.img read-only append="root=/dev/mapper/luks-3017a657-fd05-4557-bc4f-6620015c08f0" Loading dm-log.ko module Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Waiting for driver initialization. Kernel panic - not syncing: Attempted to kill init! Scanning and con * Install kernel 2.6.18-120 from brew in rescue mode (elilo.conf entry is automatically generated) - panic again: image=vmlinuz-2.6.18-120.el5 label=2.6.18-120.el5 initrd=initrd-2.6.18-120.el5.img read-only append="root=/dev/mapper/luks-3017a657-fd05-4557-bc4f-6620015c08f0" Scanning and configuring dmraid supported devices Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root'Kernel panic - not syncing: Attempted to kill init! Setting up oth er filesystems.
info from rescue mode: blkid: /dev/mapper/luks-3017a657-fd05-4557-bc4f-6620015c08f0: LABEL="/1" UUID="9af4863a-7599-4dcc-94f1-f0ed8a9e8a6c" TYPE="ext3" /dev/cciss/c0d0p1: LABEL="EFIPART" UUID="A476-2271" TYPE="vfat" /dev/cciss/c0d0p2: LABEL="HPPART" UUID="8479-1D43" TYPE="vfat" /dev/cciss/c0d0p3: SEC_TYPE="msdos" LABEL="/boot/efi" UUID="48FD-93AE" TYPE="vfat" /dev/cciss/c0d0p4: LABEL="/" UUID="df8568f1-bf9c-4556-b343-cf3425142d5c" SEC_TYPE="ext2" TYPE="ext3" LUKS device has the label "/1" which was in elilo.conf right after install. Not sure why it has a different UUID than the ID in the name though. CC'ing dlehman to answer this.
Created attachment 320994 [details] anaconda.log just in case we need it
To install use update image at http://dlehman.fedorapeople.org/updates-464769.img because of bug #464769
Tried also append="root=LABEL=/1" with -120 kernel. Same result - panic At this time I'm thinking it's anaconda issue which manifests in the kernel not finding the root file system upon boot.
FYI: Haven't tested on other arches than ia64 exclusively but from what I know nobody from RTT has seen such behavior so far.
What do you see on the console when the system panics? Surely there are some messages of some sort.
The problem is mkinitrd doesn't know how to handle encrypted CCISS devices.
Created attachment 321086 [details] handle luks on cciss
Requesting approval for Snapshot 1 since fix is available.
updated summary to reflect real cause of problem
Fixed in mkinitrd-5.1.19.6-39.
*** Bug 469131 has been marked as a duplicate of this bug. ***
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0237.html