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

DISCUSSION Gerhard Wiesinger 6 participants 19 messages May 27, 2015 – Jun 15, 2015 16 messages not in the archive

lore

Share & tools

lore

Gerhard Wiesinger

author

2015-05-27 11:28 UTC #0 lore raw

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

+ cat /proc/mdstat
Personalities :
unused devices: <none>

A message that is not in the archive (sent off-list or not yet received): [email protected]

Harald Hoyer

2015-05-27 11:56 UTC #2 lore raw

Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:

Quoted 116 lines

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).

Quoted 7 lines

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

A message that is not in the archive (sent off-list or not yet received): [email protected]

Gerhard Wiesinger

author

2015-05-27 12:09 UTC #4 lore raw

Quoted 131 lines · Harald Hoyer

Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
Quoted 116 lines
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).
Quoted 7 lines
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

Quoted 5 lines

... whatever is needed to boot your system.
# dracut --print-cmdline
should tell you what kernel cmdline parameters are needed

Thank you for the fast reply.

# comment: 3 separate lines!!!!! (maybe a problem)
dracut --print-cmdline
rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09
rd.lvm.lv=VolGroup00/root
rd.lvm.lv=VolGroup00/swap
rd.md.uuid=51e8e983:8786b868:dbc38735:7e1a9534
rd.md.uuid=56e9bde4:5cd1630d:188c22a5:4c1c8c37 resume=/dev/mapper/VolGroup00-swap root=/dev/mapper/VolGroup00-root rootflags=rw,relatime,data=ordered rootfstype=ext4

dracut --force 4.0.4-301.fc22.x86_64

Still no correct entry in /etc/grub2.cfg
linux16 /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

Looks like a bug to me.

Thank you.

Ciao,
Gerhard

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andrei Borzenkov

2015-05-27 12:13 UTC #6 lore raw

Quoted 177 lines · Gerhard Wiesinger

Quoted 156 lines · Harald Hoyer
Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
Quoted 137 lines
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).
Quoted 9 lines
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
Quoted 5 lines
... whatever is needed to boot your system.
# dracut --print-cmdline
should tell you what kernel cmdline parameters are needed
Thank you for the fast reply.
# comment: 3 separate lines!!!!! (maybe a problem) dracut --print-cmdline
rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09
rd.lvm.lv=VolGroup00/root
rd.lvm.lv=VolGroup00/swap rd.md.uuid=51e8e983:8786b868:dbc38735:7e1a9534
rd.md.uuid=56e9bde4:5cd1630d:188c22a5:4c1c8c37 resume=/dev/mapper/VolGroup00-swap root=/dev/mapper/VolGroup00-root rootflags=rw,relatime,data=ordered rootfstype=ext4

Quoted 3 lines

dracut --force 4.0.4-301.fc22.x86_64
Still no correct entry in /etc/grub2.cfg

I would be very surprised if dracut made any changes to grub.cfg. As I understand it, you either build host-specific dracut that will include this emulated command line or you have to add lines manually to your boot loader configuration.

Quoted 15 lines

linux16 /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
Looks like a bug to me.
Thank you.
Ciao,
Gerhard
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): CAA91j0UysOKJG6LpuvCdrh3jcRMdj9+=XaD-R+Shw7WFZSvbUw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org

Harald Hoyer

2015-05-27 12:25 UTC #8 lore raw

Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:

Quoted 178 lines · Gerhard Wiesinger

Quoted 177 lines · Harald Hoyer
Quoted 156 lines
Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
Quoted 137 lines
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).
Quoted 9 lines
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
Quoted 5 lines
... whatever is needed to boot your system.
# dracut --print-cmdline
should tell you what kernel cmdline parameters are needed
Thank you for the fast reply.
# comment: 3 separate lines!!!!! (maybe a problem) dracut --print-cmdline
rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09
rd.lvm.lv=VolGroup00/root
rd.lvm.lv=VolGroup00/swap rd.md.uuid=51e8e983:8786b868:dbc38735:7e1a9534
rd.md.uuid=56e9bde4:5cd1630d:188c22a5:4c1c8c37 resume=/dev/mapper/VolGroup00-swap root=/dev/mapper/VolGroup00-root rootflags=rw,relatime,data=ordered rootfstype=ext4

Quoted 14 lines

Quoted 3 lines
dracut --force 4.0.4-301.fc22.x86_64
Still no correct entry in /etc/grub2.cfg
I would be very surprised if dracut made any changes to grub.cfg. As I understand it, you either build host-specific dracut that will include this emulated command line or you have to add lines manually to your boot loader configuration.
Quoted 5 lines
linux16 /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
Looks like a bug to me.

You have to add the options manually to the grub conf and all in the same line.

dracut does not modify your grub configuration.

A message that is not in the archive (sent off-list or not yet received): [email protected]

Gerhard Wiesinger

author

2015-05-27 12:39 UTC #10 lore raw

Quoted 183 lines · Harald Hoyer

Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
Quoted 182 lines · Gerhard Wiesinger
Quoted 173 lines · Harald Hoyer
Quoted 153 lines
Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
Quoted 136 lines
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).
Quoted 9 lines
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
Quoted 5 lines
... whatever is needed to boot your system.
# dracut --print-cmdline
should tell you what kernel cmdline parameters are needed
Thank you for the fast reply.
# comment: 3 separate lines!!!!! (maybe a problem) dracut --print-cmdline
rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09
rd.lvm.lv=VolGroup00/root
rd.lvm.lv=VolGroup00/swap rd.md.uuid=51e8e983:8786b868:dbc38735:7e1a9534
rd.md.uuid=56e9bde4:5cd1630d:188c22a5:4c1c8c37 resume=/dev/mapper/VolGroup00-swap root=/dev/mapper/VolGroup00-root rootflags=rw,relatime,data=ordered rootfstype=ext4
Quoted 3 lines
dracut --force 4.0.4-301.fc22.x86_64
Still no correct entry in /etc/grub2.cfg
I would be very surprised if dracut made any changes to grub.cfg. As I understand it, you either build host-specific dracut that will include this emulated command line or you have to add lines manually to your boot loader configuration.

Quoted 8 lines

Quoted 5 lines
Quoted 5 lines
linux16 /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
Looks like a bug to me.
You have to add the options manually to the grub conf and all in the same line.
dracut does not modify your grub configuration.

OK, I thought it was modifying it, at least in the past.

Added it manually and it worked well.

What's still strange:

Last lines after startup, luks-md0 has already been started as the root fs is there .... Starting Cryptography Setup for luks-md0...
Starting Authorization Manager...

Fedora release 22 (Twenty Two)
Kernel 4.0.4-301.fc22.x86_64 on an x86_64 (ttyS0)

# Rebooting, why is a passphrase necessary here?
reboot
Please enter passphrase for disk luks-md0!

Possible bug here?

Ciao,
Gerhard

A message that is not in the archive (sent off-list or not yet received): [email protected]

Harald Hoyer

2015-05-27 12:43 UTC #12 lore raw

Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:

Quoted 208 lines · Harald Hoyer

Quoted 185 lines
Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
Quoted 184 lines · Gerhard Wiesinger
Quoted 175 lines · Harald Hoyer
Quoted 155 lines
Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
Quoted 138 lines
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).
Quoted 9 lines
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
Quoted 5 lines
... whatever is needed to boot your system.
# dracut --print-cmdline
should tell you what kernel cmdline parameters are needed
Thank you for the fast reply.
# comment: 3 separate lines!!!!! (maybe a problem) dracut --print-cmdline
rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09
rd.lvm.lv=VolGroup00/root
rd.lvm.lv=VolGroup00/swap rd.md.uuid=51e8e983:8786b868:dbc38735:7e1a9534
rd.md.uuid=56e9bde4:5cd1630d:188c22a5:4c1c8c37 resume=/dev/mapper/VolGroup00-swap root=/dev/mapper/VolGroup00-root rootflags=rw,relatime,data=ordered rootfstype=ext4
Quoted 3 lines
dracut --force 4.0.4-301.fc22.x86_64
Still no correct entry in /etc/grub2.cfg
I would be very surprised if dracut made any changes to grub.cfg. As I understand it, you either build host-specific dracut that will include this emulated command line or you have to add lines manually to your boot loader configuration.
Quoted 8 lines
Quoted 5 lines
Quoted 5 lines
linux16 /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
Looks like a bug to me.
You have to add the options manually to the grub conf and all in the same line.
dracut does not modify your grub configuration.
OK, I thought it was modifying it, at least in the past.
Added it manually and it worked well.
What's still strange:
Last lines after startup, luks-md0 has already been started as the root fs is there ....
Starting Cryptography Setup for luks-md0...
Starting Authorization Manager...
Fedora release 22 (Twenty Two)
Kernel 4.0.4-301.fc22.x86_64 on an x86_64 (ttyS0)

Quoted 9 lines

# Rebooting, why is a passphrase necessary here?
reboot
Please enter passphrase for disk luks-md0!
Possible bug here?
Ciao,
Gerhard

Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?

What is your /etc/crypttab ?

A message that is not in the archive (sent off-list or not yet received): [email protected]

Gerhard Wiesinger

author

2015-05-27 13:03 UTC #14 lore raw

Quoted 211 lines · Harald Hoyer

Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
Quoted 210 lines · Harald Hoyer
Quoted 183 lines
Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
Quoted 182 lines · Gerhard Wiesinger
Quoted 173 lines · Harald Hoyer
Quoted 154 lines
Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
Quoted 138 lines
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).
Quoted 9 lines
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
Quoted 5 lines
... whatever is needed to boot your system.
# dracut --print-cmdline
should tell you what kernel cmdline parameters are needed
Thank you for the fast reply.
# comment: 3 separate lines!!!!! (maybe a problem) dracut --print-cmdline
rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09
rd.lvm.lv=VolGroup00/root
rd.lvm.lv=VolGroup00/swap rd.md.uuid=51e8e983:8786b868:dbc38735:7e1a9534
rd.md.uuid=56e9bde4:5cd1630d:188c22a5:4c1c8c37 resume=/dev/mapper/VolGroup00-swap root=/dev/mapper/VolGroup00-root rootflags=rw,relatime,data=ordered rootfstype=ext4
Quoted 3 lines
dracut --force 4.0.4-301.fc22.x86_64
Still no correct entry in /etc/grub2.cfg
I would be very surprised if dracut made any changes to grub.cfg. As I understand it, you either build host-specific dracut that will include this emulated command line or you have to add lines manually to your boot loader configuration.
Quoted 8 lines
Quoted 5 lines
Quoted 5 lines
linux16 /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
Looks like a bug to me.
You have to add the options manually to the grub conf and all in the same line.
dracut does not modify your grub configuration.
OK, I thought it was modifying it, at least in the past.
Added it manually and it worked well.
What's still strange:
Last lines after startup, luks-md0 has already been started as the root fs is there ....
Starting Cryptography Setup for luks-md0...
Starting Authorization Manager...
Fedora release 22 (Twenty Two)
Kernel 4.0.4-301.fc22.x86_64 on an x86_64 (ttyS0)
# Rebooting, why is a passphrase necessary here?
reboot
Please enter passphrase for disk luks-md0!

Quoted 6 lines

Quoted 5 lines
Possible bug here?
Ciao,
Gerhard
Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?

Yes, of course. :-)

Quoted 2 lines

What is your /etc/crypttab ?

cat /etc/crypttab

luks-md0                /dev/md0        none
luks-md1                /dev/md1        /etc/crypto-key-md1

BTW: Why did it work in previous versions without the long command line and predefined "hint" parameters?

Ciao,
Gerhard

A message that is not in the archive (sent off-list or not yet received): [email protected]

Harald Hoyer

2015-05-27 13:07 UTC #16 lore raw

Am 27.05.2015 um 15:03 schrieb Gerhard Wiesinger:

Quoted 229 lines · Harald Hoyer

Quoted 215 lines
Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
Quoted 214 lines · Harald Hoyer
Quoted 190 lines
Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
Quoted 189 lines
Quoted 175 lines · Gerhard Wiesinger
Quoted 156 lines · Harald Hoyer
Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
Quoted 140 lines
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).
Quoted 9 lines
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
Quoted 5 lines
... whatever is needed to boot your system.
# dracut --print-cmdline
should tell you what kernel cmdline parameters are needed
Thank you for the fast reply.
# comment: 3 separate lines!!!!! (maybe a problem) dracut --print-cmdline
rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09
rd.lvm.lv=VolGroup00/root
rd.lvm.lv=VolGroup00/swap rd.md.uuid=51e8e983:8786b868:dbc38735:7e1a9534
rd.md.uuid=56e9bde4:5cd1630d:188c22a5:4c1c8c37 resume=/dev/mapper/VolGroup00-swap root=/dev/mapper/VolGroup00-root rootflags=rw,relatime,data=ordered rootfstype=ext4
Quoted 3 lines
dracut --force 4.0.4-301.fc22.x86_64
Still no correct entry in /etc/grub2.cfg
I would be very surprised if dracut made any changes to grub.cfg. As I understand it, you either build host-specific dracut that will include this emulated command line or you have to add lines manually to your boot loader configuration.
Quoted 4 lines
linux16 /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
Quoted 5 lines
Quoted 1 line
Quoted 1 line
Looks like a bug to me.
You have to add the options manually to the grub conf and all in the same line.
dracut does not modify your grub configuration.
OK, I thought it was modifying it, at least in the past.
Added it manually and it worked well.
What's still strange:
Last lines after startup, luks-md0 has already been started as the root fs is there ....
Starting Cryptography Setup for luks-md0...
Starting Authorization Manager...
Fedora release 22 (Twenty Two)
Kernel 4.0.4-301.fc22.x86_64 on an x86_64 (ttyS0)
# Rebooting, why is a passphrase necessary here?
reboot
Please enter passphrase for disk luks-md0!
Quoted 6 lines
Quoted 5 lines
Possible bug here?
Ciao,
Gerhard
Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?
Yes, of course. :-)
Quoted 2 lines
What is your /etc/crypttab ?
cat /etc/crypttab

Quoted 9 lines

luks-md0                /dev/md0        none
luks-md1                /dev/md1        /etc/crypto-key-md1
BTW: Why did it work in previous versions without the long command line and predefined "hint" parameters?
Ciao,
Gerhard

Oh... please, please do not use kernel names like "md0" ... better use UUID=

A message that is not in the archive (sent off-list or not yet received): [email protected]

Gerhard Wiesinger

author

2015-05-27 13:21 UTC #18 lore raw

Quoted 229 lines · Harald Hoyer

Am 27.05.2015 um 15:03 schrieb Gerhard Wiesinger:
Quoted 228 lines · Harald Hoyer
Quoted 214 lines
Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
Quoted 213 lines · Harald Hoyer
Quoted 189 lines
Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
Quoted 188 lines
Quoted 170 lines · Gerhard Wiesinger
Quoted 156 lines · Harald Hoyer
Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
Quoted 140 lines
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).
Quoted 9 lines
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
Quoted 5 lines
... whatever is needed to boot your system.
# dracut --print-cmdline
should tell you what kernel cmdline parameters are needed
Thank you for the fast reply.
# comment: 3 separate lines!!!!! (maybe a problem) dracut --print-cmdline
    rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09
rd.lvm.lv=VolGroup00/root
    rd.lvm.lv=VolGroup00/swap
    rd.md.uuid=51e8e983:8786b868:dbc38735:7e1a9534
Quoted 7 lines
rd.md.uuid=56e9bde4:5cd1630d:188c22a5:4c1c8c37 resume=/dev/mapper/VolGroup00-swap root=/dev/mapper/VolGroup00-root rootflags=rw,relatime,data=ordered rootfstype=ext4
dracut --force 4.0.4-301.fc22.x86_64
Still no correct entry in /etc/grub2.cfg
I would be very surprised if dracut made any changes to grub.cfg. As I understand it, you either build host-specific dracut that will include this emulated command line or you have to add lines manually to your boot loader configuration.
Quoted 4 lines
linux16 /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
Quoted 5 lines
Quoted 1 line
Quoted 1 line
Looks like a bug to me.
You have to add the options manually to the grub conf and all in the same line.
dracut does not modify your grub configuration.
OK, I thought it was modifying it, at least in the past.
Added it manually and it worked well.
What's still strange:
Last lines after startup, luks-md0 has already been started as the root fs is there ....
Starting Cryptography Setup for luks-md0...
Starting Authorization Manager...
Fedora release 22 (Twenty Two)
Kernel 4.0.4-301.fc22.x86_64 on an x86_64 (ttyS0)
# Rebooting, why is a passphrase necessary here?
reboot
Please enter passphrase for disk luks-md0!
Quoted 6 lines
Quoted 5 lines
Possible bug here?
Ciao,
Gerhard
Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?
Yes, of course. :-)
Quoted 1 line
What is your /etc/crypttab ?
cat /etc/crypttab
luks-md0                /dev/md0        none
luks-md1                /dev/md1        /etc/crypto-key-md1

Quoted 7 lines

Quoted 6 lines
BTW: Why did it work in previous versions without the long command line and predefined "hint" parameters?
Ciao,
Gerhard
Oh... please, please do not use kernel names like "md0" ... better use UUID=

changed it, but didn't help. This machine was updated since around FC5. :-)

Booting:
[FAILED] Failed to start Cryptography Setup for luks-md0.
See "systemctl status 'systemd-cryptsetup@luks\x2dmd0.service'" for details. [DEPEND] Dependency failed for Encrypted Volumes.
...
[FAILED] Failed to start Cryptography Setup for luks-md0.
See "systemctl status 'systemd-cryptsetup@luks\x2dmd0.service'" for details. [DEPEND] Dependency failed for Encrypted Volumes.
...
Starting Cryptography Setup for luks-md0...
Starting Authorization Manager...

Fedora release 22 (Twenty Two)

cat /etc/crypttab
luks-md0 UUID="0c66fc77-a8a0-49e6-b96c-55e886a91f09" none
luks-md1 UUID="aaa6ec1e-e54f-4864-a793-cc95d5fa59d2" /etc/crypto-key-md1

Ciao,
Gerhard

A message that is not in the archive (sent off-list or not yet received): [email protected]

Harald Hoyer

2015-05-27 13:27 UTC #20 lore raw

Am 27.05.2015 um 15:21 schrieb Gerhard Wiesinger:

Quoted 257 lines · Harald Hoyer

Quoted 233 lines
Am 27.05.2015 um 15:03 schrieb Gerhard Wiesinger:
Quoted 232 lines · Harald Hoyer
Quoted 218 lines
Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
Quoted 217 lines · Harald Hoyer
Quoted 193 lines
Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
Quoted 192 lines
Quoted 174 lines · Gerhard Wiesinger
Quoted 160 lines · Harald Hoyer
Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
Quoted 144 lines
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).
Quoted 9 lines
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
Quoted 5 lines
... whatever is needed to boot your system.
# dracut --print-cmdline
should tell you what kernel cmdline parameters are needed
Thank you for the fast reply.
# comment: 3 separate lines!!!!! (maybe a problem) dracut --print-cmdline
    rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09
rd.lvm.lv=VolGroup00/root
    rd.lvm.lv=VolGroup00/swap
    rd.md.uuid=51e8e983:8786b868:dbc38735:7e1a9534
Quoted 7 lines
rd.md.uuid=56e9bde4:5cd1630d:188c22a5:4c1c8c37 resume=/dev/mapper/VolGroup00-swap root=/dev/mapper/VolGroup00-root rootflags=rw,relatime,data=ordered rootfstype=ext4
dracut --force 4.0.4-301.fc22.x86_64
Still no correct entry in /etc/grub2.cfg
I would be very surprised if dracut made any changes to grub.cfg. As I understand it, you either build host-specific dracut that will include this emulated command line or you have to add lines manually to your boot loader configuration.
Quoted 4 lines
linux16 /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
Quoted 5 lines
Quoted 1 line
Quoted 1 line
Looks like a bug to me.
You have to add the options manually to the grub conf and all in the same line.
dracut does not modify your grub configuration.
OK, I thought it was modifying it, at least in the past.
Added it manually and it worked well.
What's still strange:
Last lines after startup, luks-md0 has already been started as the root fs is there ....
Starting Cryptography Setup for luks-md0...
Starting Authorization Manager...
Fedora release 22 (Twenty Two)
Kernel 4.0.4-301.fc22.x86_64 on an x86_64 (ttyS0)
# Rebooting, why is a passphrase necessary here?
reboot
Please enter passphrase for disk luks-md0!
Quoted 6 lines
Quoted 5 lines
Possible bug here?
Ciao,
Gerhard
Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?
Yes, of course. :-)
Quoted 1 line
What is your /etc/crypttab ?
cat /etc/crypttab
luks-md0                /dev/md0        none
luks-md1                /dev/md1        /etc/crypto-key-md1
Quoted 7 lines
Quoted 6 lines
BTW: Why did it work in previous versions without the long command line and predefined "hint" parameters?
Ciao,
Gerhard
Oh... please, please do not use kernel names like "md0" ... better use UUID=
changed it, but didn't help. This machine was updated since around FC5. :-)
Booting:
[FAILED] Failed to start Cryptography Setup for luks-md0.
See "systemctl status 'systemd-cryptsetup@luks\x2dmd0.service'" for details. [DEPEND] Dependency failed for Encrypted Volumes.
...
[FAILED] Failed to start Cryptography Setup for luks-md0.
See "systemctl status 'systemd-cryptsetup@luks\x2dmd0.service'" for details. [DEPEND] Dependency failed for Encrypted Volumes.
...
Starting Cryptography Setup for luks-md0...
Starting Authorization Manager...

Quoted 9 lines

Fedora release 22 (Twenty Two)
cat /etc/crypttab
luks-md0 UUID="0c66fc77-a8a0-49e6-b96c-55e886a91f09" none
luks-md1 UUID="aaa6ec1e-e54f-4864-a793-cc95d5fa59d2" /etc/crypto-key-md1
Ciao,
Gerhard

Does "dracut -f" help to get the update crypttab in the initramfs?

A message that is not in the archive (sent off-list or not yet received): [email protected]

Gerhard Wiesinger

author

2015-05-27 13:33 UTC #22 lore raw

Quoted 259 lines · Harald Hoyer

Am 27.05.2015 um 15:21 schrieb Gerhard Wiesinger:
Quoted 258 lines · Harald Hoyer
Quoted 233 lines
Am 27.05.2015 um 15:03 schrieb Gerhard Wiesinger:
Quoted 232 lines · Harald Hoyer
Quoted 218 lines
Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
Quoted 217 lines · Harald Hoyer
Quoted 193 lines
Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
Quoted 192 lines
Quoted 174 lines · Gerhard Wiesinger
Quoted 160 lines · Harald Hoyer
Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
Quoted 144 lines
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).
Quoted 9 lines
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
Quoted 5 lines
... whatever is needed to boot your system.
# dracut --print-cmdline
should tell you what kernel cmdline parameters are needed
Thank you for the fast reply.
# comment: 3 separate lines!!!!! (maybe a problem) dracut --print-cmdline
     rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09
rd.lvm.lv=VolGroup00/root
     rd.lvm.lv=VolGroup00/swap
     rd.md.uuid=51e8e983:8786b868:dbc38735:7e1a9534
Quoted 7 lines
rd.md.uuid=56e9bde4:5cd1630d:188c22a5:4c1c8c37 resume=/dev/mapper/VolGroup00-swap root=/dev/mapper/VolGroup00-root rootflags=rw,relatime,data=ordered rootfstype=ext4
dracut --force 4.0.4-301.fc22.x86_64
Still no correct entry in /etc/grub2.cfg
I would be very surprised if dracut made any changes to grub.cfg. As I understand it, you either build host-specific dracut that will include this emulated command line or you have to add lines manually to your boot loader configuration.
Quoted 4 lines
linux16 /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
Quoted 5 lines
Quoted 1 line
Quoted 1 line
Looks like a bug to me.
You have to add the options manually to the grub conf and all in the same line.
dracut does not modify your grub configuration.
OK, I thought it was modifying it, at least in the past.
Added it manually and it worked well.
What's still strange:
Last lines after startup, luks-md0 has already been started as the root fs is there ....
Starting Cryptography Setup for luks-md0...
Starting Authorization Manager...
Fedora release 22 (Twenty Two)
Kernel 4.0.4-301.fc22.x86_64 on an x86_64 (ttyS0)
# Rebooting, why is a passphrase necessary here?
reboot
Please enter passphrase for disk luks-md0!
Quoted 6 lines
Quoted 5 lines
Possible bug here?
Ciao,
Gerhard
Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?
Yes, of course. :-)
Quoted 1 line
What is your /etc/crypttab ?
cat /etc/crypttab
luks-md0                /dev/md0        none
luks-md1                /dev/md1        /etc/crypto-key-md1
Quoted 7 lines
Quoted 6 lines
BTW: Why did it work in previous versions without the long command line and predefined "hint" parameters?
Ciao,
Gerhard
Oh... please, please do not use kernel names like "md0" ... better use UUID=
changed it, but didn't help. This machine was updated since around FC5. :-)
Booting:
[FAILED] Failed to start Cryptography Setup for luks-md0.
See "systemctl status 'systemd-cryptsetup@luks\x2dmd0.service'" for details. [DEPEND] Dependency failed for Encrypted Volumes.
...
[FAILED] Failed to start Cryptography Setup for luks-md0.
See "systemctl status 'systemd-cryptsetup@luks\x2dmd0.service'" for details. [DEPEND] Dependency failed for Encrypted Volumes.
...
Starting Cryptography Setup for luks-md0...
Starting Authorization Manager...
Fedora release 22 (Twenty Two)

Quoted 9 lines

Quoted 7 lines
cat /etc/crypttab
luks-md0 UUID="0c66fc77-a8a0-49e6-b96c-55e886a91f09" none
luks-md1 UUID="aaa6ec1e-e54f-4864-a793-cc95d5fa59d2" /etc/crypto-key-md1
Ciao,
Gerhard
Does "dracut -f" help to get the update crypttab in the initramfs?

No, still the same.

Ciao,
Gerhard

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andrew Udvare

2015-05-27 17:21 UTC #24 lore raw

Try by specifying luks in your /etc/crypttab (I do this just in case):

name UUID=... the-key-file/path luks

If you have 2 separate physical disks that must be decrypted before detection of a partition (like with LVM), then you must have both in the crypttab in the initramfs image. This was a problem for me with 2 physical disks, both separately encrypted, for creating a volume group.

The issue is that depending on your configuration, the crypttab generator in the crypt module may not see your 2 or more physical disks comprising the root partition (it will only see the first). So I had to hack mine, which is to comment out or remove the conditionals:

module-setup.sh 2015-04-15 02:28:08.381183319 -0700 renamed from module-setup.sh.old 2015-01-31 03:54:52.000000000 -0800 +0 -2

@@ -73,13 +73,14 @@
                 _dev="/dev/disk/by-uuid/${_dev#UUID=}"
 
             for _hdev in "${!host_fs_types[@]}"; do
-                [[ ${host_fs_types[$_hdev]} == "crypto_LUKS" ]] || continue
-                if [[ $_hdev -ef $_dev ]] || [[ /dev/block/$_hdev -ef

$_dev ]]; then
+ #[[ ${host_fs_types[$_hdev]} == "crypto_LUKS" ]] || continue
+ #if [[ $_hdev -ef $_dev ]] || [[ /dev/block/$_hdev
-ef $_dev ]]; then

                     echo "$_mapper $_dev $_rest"
                     break

- fi
+ #fi
done
done < /etc/crypttab > $initdir/etc/crypttab
+ cat $initdir/etc/crypttab
mark_hostonly /etc/crypttab
fi

This is at /usr/lib64/dracut/modules.d/90crypt/module-setup.sh

This way you are forcing every encrypted partition into /etc/crypttab in the initramfs image (where before it will not always match your disks's copy). You may not actually want this, because you only want a minimal image but if your key is the same for everything and every disk is encrypted then it will not make a big difference. I would take out of the key file and use none in the all /etc/crypttab for testing. You will then have to type your password twice. This prompt may be hard to see in all the output from systemd but sometimes you can just press Return and it will appear clean.

Quoted 331 lines · Gerhard Wiesinger

Quoted 310 lines · Harald Hoyer
Am 27.05.2015 um 15:21 schrieb Gerhard Wiesinger:
Quoted 308 lines · Harald Hoyer
Quoted 280 lines
Am 27.05.2015 um 15:03 schrieb Gerhard Wiesinger:
Quoted 278 lines · Harald Hoyer
Quoted 256 lines
Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
Quoted 254 lines · Harald Hoyer
Quoted 225 lines
Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
Quoted 223 lines
Quoted 197 lines · Gerhard Wiesinger
Quoted 181 lines · Harald Hoyer
Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
Quoted 162 lines
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).
Quoted 10 lines
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
Quoted 5 lines
... whatever is needed to boot your system.
# dracut --print-cmdline
should tell you what kernel cmdline parameters are needed
Thank you for the fast reply.
# comment: 3 separate lines!!!!! (maybe a problem) dracut --print-cmdline
     rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09
rd.lvm.lv=VolGroup00/root
     rd.lvm.lv=VolGroup00/swap
     rd.md.uuid=51e8e983:8786b868:dbc38735:7e1a9534
Quoted 8 lines
rd.md.uuid=56e9bde4:5cd1630d:188c22a5:4c1c8c37 resume=/dev/mapper/VolGroup00-swap root=/dev/mapper/VolGroup00-root rootflags=rw,relatime,data=ordered rootfstype=ext4
dracut --force 4.0.4-301.fc22.x86_64
Still no correct entry in /etc/grub2.cfg
I would be very surprised if dracut made any changes to grub.cfg. As I
understand it, you either build host-specific dracut that will include
this emulated command line or you have to add lines manually to your
boot loader configuration.
Quoted 5 lines
linux16 /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
Quoted 7 lines
Quoted 1 line
Quoted 1 line
Looks like a bug to me.
You have to add the options manually to the grub conf and all in the same
line.
dracut does not modify your grub configuration.
OK, I thought it was modifying it, at least in the past.
Added it manually and it worked well.
What's still strange:
Last lines after startup, luks-md0 has already been started as the root fs is
there ....
Starting Cryptography Setup for luks-md0...
Starting Authorization Manager...
Fedora release 22 (Twenty Two)
Kernel 4.0.4-301.fc22.x86_64 on an x86_64 (ttyS0)
# Rebooting, why is a passphrase necessary here?
reboot
Please enter passphrase for disk luks-md0!
Quoted 7 lines
Quoted 5 lines
Possible bug here?
Ciao,
Gerhard
Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?
Yes, of course. :-)
Quoted 1 line
What is your /etc/crypttab ?
cat /etc/crypttab
luks-md0                /dev/md0        none
luks-md1                /dev/md1        /etc/crypto-key-md1
BTW: Why did it work in previous versions without the long command line and
predefined "hint" parameters?
Quoted 5 lines
Quoted 3 lines
Ciao,
Gerhard
Oh... please, please do not use kernel names like "md0" ... better use UUID=
changed it, but didn't help. This machine was updated since around FC5. :-)
Booting:
[FAILED] Failed to start Cryptography Setup for luks-md0. See "systemctl status 'systemd-cryptsetup@luks\x2dmd0.service'" for details.
[DEPEND] Dependency failed for Encrypted Volumes.
...
[FAILED] Failed to start Cryptography Setup for luks-md0. See "systemctl status 'systemd-cryptsetup@luks\x2dmd0.service'" for details.
[DEPEND] Dependency failed for Encrypted Volumes.
...
Starting Cryptography Setup for luks-md0... Starting Authorization Manager...
Fedora release 22 (Twenty Two)
Quoted 9 lines
Quoted 7 lines
cat /etc/crypttab
luks-md0 UUID="0c66fc77-a8a0-49e6-b96c-55e886a91f09" none
luks-md1 UUID="aaa6ec1e-e54f-4864-a793-cc95d5fa59d2" /etc/crypto-key-md1
Ciao,
Gerhard
Does "dracut -f" help to get the update crypttab in the initramfs?
No, still the same.
Ciao,
Gerhard
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

Gerhard Wiesinger

author

2015-05-28 12:19 UTC #25 lore raw

In reply to a message not in the archive

Quoted 259 lines · Harald Hoyer

Am 27.05.2015 um 15:21 schrieb Gerhard Wiesinger:
Quoted 258 lines · Harald Hoyer
Quoted 233 lines
Am 27.05.2015 um 15:03 schrieb Gerhard Wiesinger:
Quoted 232 lines · Harald Hoyer
Quoted 218 lines
Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
Quoted 217 lines · Harald Hoyer
Quoted 193 lines
Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
Quoted 192 lines
Quoted 174 lines · Gerhard Wiesinger
Quoted 160 lines · Harald Hoyer
Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
Quoted 144 lines
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).
Quoted 9 lines
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
Quoted 5 lines
... whatever is needed to boot your system.
# dracut --print-cmdline
should tell you what kernel cmdline parameters are needed
Thank you for the fast reply.
# comment: 3 separate lines!!!!! (maybe a problem) dracut --print-cmdline
     rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09
rd.lvm.lv=VolGroup00/root
     rd.lvm.lv=VolGroup00/swap
     rd.md.uuid=51e8e983:8786b868:dbc38735:7e1a9534
Quoted 7 lines
rd.md.uuid=56e9bde4:5cd1630d:188c22a5:4c1c8c37 resume=/dev/mapper/VolGroup00-swap root=/dev/mapper/VolGroup00-root rootflags=rw,relatime,data=ordered rootfstype=ext4
dracut --force 4.0.4-301.fc22.x86_64
Still no correct entry in /etc/grub2.cfg
I would be very surprised if dracut made any changes to grub.cfg. As I understand it, you either build host-specific dracut that will include this emulated command line or you have to add lines manually to your boot loader configuration.
Quoted 4 lines
linux16 /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
Quoted 5 lines
Quoted 1 line
Quoted 1 line
Looks like a bug to me.
You have to add the options manually to the grub conf and all in the same line.
dracut does not modify your grub configuration.
OK, I thought it was modifying it, at least in the past.
Added it manually and it worked well.
What's still strange:
Last lines after startup, luks-md0 has already been started as the root fs is there ....
Starting Cryptography Setup for luks-md0...
Starting Authorization Manager...
Fedora release 22 (Twenty Two)
Kernel 4.0.4-301.fc22.x86_64 on an x86_64 (ttyS0)
# Rebooting, why is a passphrase necessary here?
reboot
Please enter passphrase for disk luks-md0!
Quoted 6 lines
Quoted 5 lines
Possible bug here?
Ciao,
Gerhard
Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?
Yes, of course. :-)
Quoted 1 line
What is your /etc/crypttab ?
cat /etc/crypttab
luks-md0                /dev/md0        none
luks-md1                /dev/md1        /etc/crypto-key-md1
Quoted 7 lines
Quoted 6 lines
BTW: Why did it work in previous versions without the long command line and predefined "hint" parameters?
Ciao,
Gerhard
Oh... please, please do not use kernel names like "md0" ... better use UUID=
changed it, but didn't help. This machine was updated since around FC5. :-)
Booting:
[FAILED] Failed to start Cryptography Setup for luks-md0.
See "systemctl status 'systemd-cryptsetup@luks\x2dmd0.service'" for details. [DEPEND] Dependency failed for Encrypted Volumes.
...
[FAILED] Failed to start Cryptography Setup for luks-md0.
See "systemctl status 'systemd-cryptsetup@luks\x2dmd0.service'" for details. [DEPEND] Dependency failed for Encrypted Volumes.
...
Starting Cryptography Setup for luks-md0...
Starting Authorization Manager...
Fedora release 22 (Twenty Two)

Quoted 10 lines

Quoted 7 lines
cat /etc/crypttab
luks-md0 UUID="0c66fc77-a8a0-49e6-b96c-55e886a91f09" none
luks-md1 UUID="aaa6ec1e-e54f-4864-a793-cc95d5fa59d2" /etc/crypto-key-md1
Ciao,
Gerhard
Does "dracut -f" help to get the update crypttab in the initramfs?

Removing quotes from the UUID helped.

Thank you.

Ciao,
Gerhard

--
http://www.wiesinger.com/

A message that is not in the archive (sent off-list or not yet received): [email protected]

poma

2015-05-31 07:51 UTC #27 lore raw

Quoted 271 lines · Gerhard Wiesinger

Quoted 259 lines · Harald Hoyer
Am 27.05.2015 um 15:21 schrieb Gerhard Wiesinger:
Quoted 258 lines · Harald Hoyer
Quoted 233 lines
Am 27.05.2015 um 15:03 schrieb Gerhard Wiesinger:
Quoted 232 lines · Harald Hoyer
Quoted 218 lines
Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
Quoted 217 lines · Harald Hoyer
Quoted 193 lines
Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
Quoted 192 lines
Quoted 174 lines · Gerhard Wiesinger
Quoted 160 lines · Harald Hoyer
Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
Quoted 144 lines
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).
Quoted 9 lines
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
Quoted 5 lines
... whatever is needed to boot your system.
# dracut --print-cmdline
should tell you what kernel cmdline parameters are needed
Thank you for the fast reply.
# comment: 3 separate lines!!!!! (maybe a problem) dracut --print-cmdline
     rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09
rd.lvm.lv=VolGroup00/root
     rd.lvm.lv=VolGroup00/swap
     rd.md.uuid=51e8e983:8786b868:dbc38735:7e1a9534
Quoted 7 lines
rd.md.uuid=56e9bde4:5cd1630d:188c22a5:4c1c8c37 resume=/dev/mapper/VolGroup00-swap root=/dev/mapper/VolGroup00-root rootflags=rw,relatime,data=ordered rootfstype=ext4
dracut --force 4.0.4-301.fc22.x86_64
Still no correct entry in /etc/grub2.cfg
I would be very surprised if dracut made any changes to grub.cfg. As I understand it, you either build host-specific dracut that will include this emulated command line or you have to add lines manually to your boot loader configuration.
Quoted 4 lines
linux16 /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
Quoted 5 lines
Quoted 1 line
Quoted 1 line
Looks like a bug to me.
You have to add the options manually to the grub conf and all in the same line.
dracut does not modify your grub configuration.
OK, I thought it was modifying it, at least in the past.
Added it manually and it worked well.
What's still strange:
Last lines after startup, luks-md0 has already been started as the root fs is there ....
Starting Cryptography Setup for luks-md0...
Starting Authorization Manager...
Fedora release 22 (Twenty Two)
Kernel 4.0.4-301.fc22.x86_64 on an x86_64 (ttyS0)
# Rebooting, why is a passphrase necessary here?
reboot
Please enter passphrase for disk luks-md0!
Quoted 6 lines
Quoted 5 lines
Possible bug here?
Ciao,
Gerhard
Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?
Yes, of course. :-)
Quoted 1 line
What is your /etc/crypttab ?
cat /etc/crypttab
luks-md0                /dev/md0        none
luks-md1                /dev/md1        /etc/crypto-key-md1
Quoted 7 lines
Quoted 6 lines
BTW: Why did it work in previous versions without the long command line and predefined "hint" parameters?
Ciao,
Gerhard
Oh... please, please do not use kernel names like "md0" ... better use UUID=
changed it, but didn't help. This machine was updated since around FC5. :-)
Booting:
[FAILED] Failed to start Cryptography Setup for luks-md0.
See "systemctl status 'systemd-cryptsetup@luks\x2dmd0.service'" for details. [DEPEND] Dependency failed for Encrypted Volumes.
...
[FAILED] Failed to start Cryptography Setup for luks-md0.
See "systemctl status 'systemd-cryptsetup@luks\x2dmd0.service'" for details. [DEPEND] Dependency failed for Encrypted Volumes.
...
Starting Cryptography Setup for luks-md0...
Starting Authorization Manager...
Fedora release 22 (Twenty Two)
Quoted 10 lines
Quoted 7 lines
cat /etc/crypttab
luks-md0 UUID="0c66fc77-a8a0-49e6-b96c-55e886a91f09" none
luks-md1 UUID="aaa6ec1e-e54f-4864-a793-cc95d5fa59d2" /etc/crypto-key-md1
Ciao,
Gerhard
Does "dracut -f" help to get the update crypttab in the initramfs?

Quoted 7 lines

Removing quotes from the UUID helped.
Thank you.
Ciao,
Gerhard

Without even mention these UUIDs spaghetti.

$ grep ^kernel /etc/dracut.conf.d/custom.conf
kernel_cmdline="rd.auto=1"

# lsinitrd -f

$ lsinitrd -f etc/cmdline.d/01-default.conf
rd.auto=1

This is -not- necessary for MD/RAID setups on Fedora 21:

$ rpm -q dracut
dracut-038-39.git20150518.fc21.x86_64

But it has become -mandatory- on MD/RAID setups on Fedora 22 and Fedora 23:

$ rpm -q dracut
dracut-041-10.fc22.1.x86_64

$ rpm -q dracut
dracut-041-10.git20150219.fc23.x86_64

And already we have fought for this user's side simplification, but it seems developers are very persistent when they do not need to be.

Bruno Wolff III

2015-05-31 18:08 UTC #28 lore raw

Quoted 1 line

And already we have fought for this user's side simplification, but it seems developers are very persistent when they do not need to be.

In the past changes with this effect were reverted. This time they were not. This generally just affects people upgrading, as anaconda has been adding the needed stuff on the kernel command line for a while now.

You can also hostonly_cmdline=yes to the dracut config or set hostonly=no if you are willing to have a larger initramfs file. The latter will also help if you switch out hardware.

I am not sure why hostonly_cmdline=yes is not the default when hostonly=yes. That would seem to be a better default.

Signature · 4 lines

test mailing list
[email protected]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

A message that is not in the archive (sent off-list or not yet received): [email protected]

poma

2015-06-11 09:06 UTC #30 lore raw

Quoted 6 lines · Bruno Wolff III

Quoted 1 line
And already we have fought for this user's side simplification, but it seems developers are very persistent when they do not need to be.
In the past changes with this effect were reverted. This time they were not. This generally just affects people upgrading, as anaconda has been adding the needed stuff on the kernel command line for a while now.

Quoted 7 lines

You can also hostonly_cmdline=yes to the dracut config or set hostonly=no if you are willing to have a larger initramfs file. The latter will also help if you switch out hardware.
I am not sure why hostonly_cmdline=yes is not the default when hostonly=yes. That would seem to be a better default.

dracut.conf.d/fedora.conf.example
+hostonly_cmdline="no"

http://pkgs.fedoraproject.org/cgit/dracut.git/commit/0001-fedora.conf-do-not-store-cmdline-in-image-by-default.patch?id=43a1228
http://git.kernel.org/cgit/boot/dracut/dracut.git/commit/dracut.conf.d/fedora.conf.example?id=38e2177

no explanation why this was done

A message that is not in the archive (sent off-list or not yet received): [email protected]

Harald Hoyer

2015-06-15 09:42 UTC #32 lore raw

Quoted 16 lines · poma

Quoted 6 lines · Bruno Wolff III
Quoted 1 line
And already we have fought for this user's side simplification, but it seems developers are very persistent when they do not need to be.
In the past changes with this effect were reverted. This time they were not. This generally just affects people upgrading, as anaconda has been adding the needed stuff on the kernel command line for a while now.
Quoted 7 lines
You can also hostonly_cmdline=yes to the dracut config or set hostonly=no if you are willing to have a larger initramfs file. The latter will also help if you switch out hardware.
I am not sure why hostonly_cmdline=yes is not the default when hostonly=yes. That would seem to be a better default.

Quoted 7 lines

dracut.conf.d/fedora.conf.example
+hostonly_cmdline="no"
http://pkgs.fedoraproject.org/cgit/dracut.git/commit/0001-fedora.conf-do-not-store-cmdline-in-image-by-default.patch?id=43a1228
http://git.kernel.org/cgit/boot/dracut/dracut.git/commit/dracut.conf.d/fedora.conf.example?id=38e2177
no explanation why this was done

Basically it's because compiled in arguments are hard to override and people could not boot after they changed disk configuration.

I guess, s.th. like "rd.cmdline=clean rd.auto" or "rd.helpIwanttobootnow" is the better solution.

A message that is not in the archive (sent off-list or not yet received): [email protected]

poma

2015-06-15 10:37 UTC #34 lore raw

Quoted 23 lines · Harald Hoyer

Quoted 22 lines · poma
Quoted 6 lines · Bruno Wolff III
Quoted 1 line
And already we have fought for this user's side simplification, but it seems developers are very persistent when they do not need to be.
In the past changes with this effect were reverted. This time they were not. This generally just affects people upgrading, as anaconda has been adding the needed stuff on the kernel command line for a while now.
Quoted 7 lines
You can also hostonly_cmdline=yes to the dracut config or set hostonly=no if you are willing to have a larger initramfs file. The latter will also help if you switch out hardware.
I am not sure why hostonly_cmdline=yes is not the default when hostonly=yes. That would seem to be a better default.
dracut.conf.d/fedora.conf.example
+hostonly_cmdline="no"
http://pkgs.fedoraproject.org/cgit/dracut.git/commit/0001-fedora.conf-do-not-store-cmdline-in-image-by-default.patch?id=43a1228
http://git.kernel.org/cgit/boot/dracut/dracut.git/commit/dracut.conf.d/fedora.conf.example?id=38e2177

Quoted 9 lines

Quoted 1 line
no explanation why this was done
Basically it's because compiled in arguments are hard to override and people could not boot after they changed disk configuration.
I guess, s.th. like "rd.cmdline=clean rd.auto" or "rd.helpIwanttobootnow" is the better solution.

rd.OhLordwontyoubuymeaMercedesBenzMyfriendsalldrivePorschesImustmakeamends