Re: Update FC22 - doesn't find root fs and doesn't boot

Harald Hoyer
2015-05-27T11:56:22Z

Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
> Hello,
>
> After upgrading one machine it does't boot anymore. Booting the old kernel
> works well.
>
> It is a RAID, LUKS, LVM setup. Find relevant details below.
>
> So it looks RAID assembling doesn't work any more.
>
> Any ideas?
>
> Thank you.
>
> Ciao,
> Gerhard
>
> blkid
> /dev/sda1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37" TYPE="linux_raid_member"
> PARTUUID="5ec6792c-01"
> /dev/sdb1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37" TYPE="linux_raid_member"
> PARTUUID="1c7cffaf-01"
> /dev/sdc1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37" TYPE="linux_raid_member"
> PARTUUID="0079dfc3-01"
> /dev/sdd1: UUID="eb295015-e20b-e133-15db-5c9130487300" TYPE="linux_raid_member"
> PARTUUID="fadeaffe-01"
> /dev/sde1: UUID="eb295015-e20b-e133-15db-5c9130487300" TYPE="linux_raid_member"
> PARTUUID="539b5814-01"
> /dev/sdf1: UUID="eb295015-e20b-e133-15db-5c9130487300" TYPE="linux_raid_member"
> PARTUUID="badeaffe-01"
> /dev/sdh1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534" TYPE="linux_raid_member"
> PARTUUID="15631562-01"
> /dev/sdg1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534" TYPE="linux_raid_member"
> PARTUUID="162f0d0b-01"
>
>
> blkid -o udev
> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
> ID_FS_TYPE=linux_raid_member
> ID_FS_PARTUUID=5ec6792c-01
>
> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
> ID_FS_TYPE=linux_raid_member
> ID_FS_PARTUUID=1c7cffaf-01
>
> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
> ID_FS_TYPE=linux_raid_member
> ID_FS_PARTUUID=0079dfc3-01
>
> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
> ID_FS_TYPE=linux_raid_member
> ID_FS_PARTUUID=fadeaffe-01
>
> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
> ID_FS_TYPE=linux_raid_member
> ID_FS_PARTUUID=539b5814-01
>
> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
> ID_FS_TYPE=linux_raid_member
> ID_FS_PARTUUID=badeaffe-01
>
> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
> ID_FS_TYPE=linux_raid_member
> ID_FS_PARTUUID=15631562-01
>
> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
> ID_FS_TYPE=linux_raid_member
> ID_FS_PARTUUID=162f0d0b-01
>
> [ 2.479836] myhost systemd[1]: Device
> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0.device appeared twice
> with different sysfs paths /sys
> /devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.0/host8/target
> 8:0:0/8:0:0:0/block/sdg
> [ 2.500826] myhost systemd[1]: Device
> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0\x2dpart1.device
> appeared twice with different sysfs p
> aths
> /sys/devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.
> 0/host8/target8:0:0/8:0:0:0/block/sdg/sdg1
> [ 2.632754] myhost kernel: Switched to clocksource tsc
> [ 91.162986] myhost systemd[1]: Job dev-md0.device/start timed out.
> [ 91.163138] myhost systemd[1]: Timed out waiting for device dev-md0.device.
> [ 91.163251] myhost systemd[1]: Dependency failed for Cryptography Setup for
> luks-md0.
> [ 91.163360] myhost systemd[1]: Dependency failed for
> dev-mapper-luks\x2dmd0.device.
> [ 91.163474] myhost systemd[1]: Job dev-mapper-luks\x2dmd0.device/start
> failed with result 'dependency'.
> [ 91.163586] myhost systemd[1]: Dependency failed for Encrypted Volumes.
> [ 91.163694] myhost systemd[1]: Job cryptsetup.target/start failed with
> result 'dependency'.
> [ 91.163801] myhost systemd[1]: Job
> systemd-cryptsetup@luks\x2dmd0.service/start failed with result 'dependency'.
> [ 91.163910] myhost systemd[1]: Job dev-md0.device/start failed with result
> 'timeout'.
> [ 91.164021] myhost systemd[1]: Reached target System Initialization.
> [ 91.164129] myhost systemd[1]: Starting System Initialization.
> [ 91.164236] myhost systemd[1]: Reached target Basic System.
> [ 91.164346] myhost systemd[1]: Starting Basic System.
> [ 185.740238] myhost dracut-initqueue[340]: Warning: Could not boot.
> [ 185.741266] myhost systemd[1]: Received SIGRTMIN+20 from PID 341 (plymouthd).
> [ 185.841257] myhost dracut-initqueue[340]: Warning: /dev/VolGroup00/root does
> not exist
> [ 185.841403] myhost systemd[1]: Starting Dracut Emergency Shell...
> [ 185.859366] myhost systemd[1]: Received SIGRTMIN+21 from PID 341 (plymouthd).
>
> dracut:/# cat "/run/initramfs/rdsosreport.txt"
> + cat /lib/dracut/dracut-041-10.fc22.1
> dracut-041-10.fc22.1
> + cat /proc/cmdline
> BOOT_IMAGE=/vmlinuz-4.0.4-301.fc22.x86_64 root=/dev/VolGroup00/root ro quiet
> console=ttyS0,115200n8 rd_NO_PLYMOUTH SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-
> 8 KEYTABLE=de-latin1

your kernel cmdline seems to be missing the raid configuration

rd.md.uuid=56e9bde4-5cd1-630d-188c-22a54c1c8c37
rd.md.uuid=eb295015-e20b-e133-15db-5c9130487300
rd.md.uuid=51e8e983-8786-b868-dbc3-87357e1a9534

... whatever is needed to boot your system.

# dracut --print-cmdline

should tell you what kernel cmdline parameters are needed