* Update FC22 - doesn't find root fs and doesn't boot
@ 2015-05-27 11:28 Gerhard Wiesinger
[not found] ` <5565AA58.6000409-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
0 siblings, 1 reply; 19+ messages in thread
From: Gerhard Wiesinger @ 2015-05-27 11:28 UTC (permalink / raw)
To: initramfs-u79uwXL29TY76Z2rM5mHXA
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>
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <5565AA58.6000409-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
@ 2015-05-27 11:56 ` Harald Hoyer
[not found] ` <5565B0E6.3050204-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
0 siblings, 1 reply; 19+ messages in thread
From: Harald Hoyer @ 2015-05-27 11:56 UTC (permalink / raw)
To: Gerhard Wiesinger, initramfs-u79uwXL29TY76Z2rM5mHXA
Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
> Hello,
>
> After upgrading one machine it does't boot anymore. Booting the old kernel
> works well.
>
> It is a RAID, LUKS, LVM setup. Find relevant details below.
>
> So it looks RAID assembling doesn't work any more.
>
> Any ideas?
>
> Thank you.
>
> Ciao,
> Gerhard
>
> blkid
> /dev/sda1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37" TYPE="linux_raid_member"
> PARTUUID="5ec6792c-01"
> /dev/sdb1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37" TYPE="linux_raid_member"
> PARTUUID="1c7cffaf-01"
> /dev/sdc1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37" TYPE="linux_raid_member"
> PARTUUID="0079dfc3-01"
> /dev/sdd1: UUID="eb295015-e20b-e133-15db-5c9130487300" TYPE="linux_raid_member"
> PARTUUID="fadeaffe-01"
> /dev/sde1: UUID="eb295015-e20b-e133-15db-5c9130487300" TYPE="linux_raid_member"
> PARTUUID="539b5814-01"
> /dev/sdf1: UUID="eb295015-e20b-e133-15db-5c9130487300" TYPE="linux_raid_member"
> PARTUUID="badeaffe-01"
> /dev/sdh1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534" TYPE="linux_raid_member"
> PARTUUID="15631562-01"
> /dev/sdg1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534" TYPE="linux_raid_member"
> PARTUUID="162f0d0b-01"
>
>
> blkid -o udev
> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
> ID_FS_TYPE=linux_raid_member
> ID_FS_PARTUUID=5ec6792c-01
>
> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
> ID_FS_TYPE=linux_raid_member
> ID_FS_PARTUUID=1c7cffaf-01
>
> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
> ID_FS_TYPE=linux_raid_member
> ID_FS_PARTUUID=0079dfc3-01
>
> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
> ID_FS_TYPE=linux_raid_member
> ID_FS_PARTUUID=fadeaffe-01
>
> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
> ID_FS_TYPE=linux_raid_member
> ID_FS_PARTUUID=539b5814-01
>
> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
> ID_FS_TYPE=linux_raid_member
> ID_FS_PARTUUID=badeaffe-01
>
> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
> ID_FS_TYPE=linux_raid_member
> ID_FS_PARTUUID=15631562-01
>
> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
> ID_FS_TYPE=linux_raid_member
> ID_FS_PARTUUID=162f0d0b-01
>
> [ 2.479836] myhost systemd[1]: Device
> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0.device appeared twice
> with different sysfs paths /sys
> /devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.0/host8/target
> 8:0:0/8:0:0:0/block/sdg
> [ 2.500826] myhost systemd[1]: Device
> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0\x2dpart1.device
> appeared twice with different sysfs p
> aths
> /sys/devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.
> 0/host8/target8:0:0/8:0:0:0/block/sdg/sdg1
> [ 2.632754] myhost kernel: Switched to clocksource tsc
> [ 91.162986] myhost systemd[1]: Job dev-md0.device/start timed out.
> [ 91.163138] myhost systemd[1]: Timed out waiting for device dev-md0.device.
> [ 91.163251] myhost systemd[1]: Dependency failed for Cryptography Setup for
> luks-md0.
> [ 91.163360] myhost systemd[1]: Dependency failed for
> dev-mapper-luks\x2dmd0.device.
> [ 91.163474] myhost systemd[1]: Job dev-mapper-luks\x2dmd0.device/start
> failed with result 'dependency'.
> [ 91.163586] myhost systemd[1]: Dependency failed for Encrypted Volumes.
> [ 91.163694] myhost systemd[1]: Job cryptsetup.target/start failed with
> result 'dependency'.
> [ 91.163801] myhost systemd[1]: Job
> systemd-cryptsetup@luks\x2dmd0.service/start failed with result 'dependency'.
> [ 91.163910] myhost systemd[1]: Job dev-md0.device/start failed with result
> 'timeout'.
> [ 91.164021] myhost systemd[1]: Reached target System Initialization.
> [ 91.164129] myhost systemd[1]: Starting System Initialization.
> [ 91.164236] myhost systemd[1]: Reached target Basic System.
> [ 91.164346] myhost systemd[1]: Starting Basic System.
> [ 185.740238] myhost dracut-initqueue[340]: Warning: Could not boot.
> [ 185.741266] myhost systemd[1]: Received SIGRTMIN+20 from PID 341 (plymouthd).
> [ 185.841257] myhost dracut-initqueue[340]: Warning: /dev/VolGroup00/root does
> not exist
> [ 185.841403] myhost systemd[1]: Starting Dracut Emergency Shell...
> [ 185.859366] myhost systemd[1]: Received SIGRTMIN+21 from PID 341 (plymouthd).
>
> dracut:/# cat "/run/initramfs/rdsosreport.txt"
> + cat /lib/dracut/dracut-041-10.fc22.1
> dracut-041-10.fc22.1
> + cat /proc/cmdline
> BOOT_IMAGE=/vmlinuz-4.0.4-301.fc22.x86_64 root=/dev/VolGroup00/root ro quiet
> console=ttyS0,115200n8 rd_NO_PLYMOUTH SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-
> 8 KEYTABLE=de-latin1
your kernel cmdline seems to be missing the raid configuration
rd.md.uuid=56e9bde4-5cd1-630d-188c-22a54c1c8c37
rd.md.uuid=eb295015-e20b-e133-15db-5c9130487300
rd.md.uuid=51e8e983-8786-b868-dbc3-87357e1a9534
... whatever is needed to boot your system.
# dracut --print-cmdline
should tell you what kernel cmdline parameters are needed
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <5565B0E6.3050204-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
@ 2015-05-27 12:09 ` Gerhard Wiesinger
[not found] ` <5565B3E6.4010806-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
0 siblings, 1 reply; 19+ messages in thread
From: Gerhard Wiesinger @ 2015-05-27 12:09 UTC (permalink / raw)
To: Harald Hoyer, initramfs-u79uwXL29TY76Z2rM5mHXA
On 27.05.2015 13:56, Harald Hoyer wrote:
> Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
>> Hello,
>>
>> After upgrading one machine it does't boot anymore. Booting the old kernel
>> works well.
>>
>> It is a RAID, LUKS, LVM setup. Find relevant details below.
>>
>> So it looks RAID assembling doesn't work any more.
>>
>> Any ideas?
>>
>> Thank you.
>>
>> Ciao,
>> Gerhard
>>
>> blkid
>> /dev/sda1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37" TYPE="linux_raid_member"
>> PARTUUID="5ec6792c-01"
>> /dev/sdb1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37" TYPE="linux_raid_member"
>> PARTUUID="1c7cffaf-01"
>> /dev/sdc1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37" TYPE="linux_raid_member"
>> PARTUUID="0079dfc3-01"
>> /dev/sdd1: UUID="eb295015-e20b-e133-15db-5c9130487300" TYPE="linux_raid_member"
>> PARTUUID="fadeaffe-01"
>> /dev/sde1: UUID="eb295015-e20b-e133-15db-5c9130487300" TYPE="linux_raid_member"
>> PARTUUID="539b5814-01"
>> /dev/sdf1: UUID="eb295015-e20b-e133-15db-5c9130487300" TYPE="linux_raid_member"
>> PARTUUID="badeaffe-01"
>> /dev/sdh1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534" TYPE="linux_raid_member"
>> PARTUUID="15631562-01"
>> /dev/sdg1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534" TYPE="linux_raid_member"
>> PARTUUID="162f0d0b-01"
>>
>>
>> blkid -o udev
>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>> ID_FS_TYPE=linux_raid_member
>> ID_FS_PARTUUID=5ec6792c-01
>>
>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>> ID_FS_TYPE=linux_raid_member
>> ID_FS_PARTUUID=1c7cffaf-01
>>
>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>> ID_FS_TYPE=linux_raid_member
>> ID_FS_PARTUUID=0079dfc3-01
>>
>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>> ID_FS_TYPE=linux_raid_member
>> ID_FS_PARTUUID=fadeaffe-01
>>
>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>> ID_FS_TYPE=linux_raid_member
>> ID_FS_PARTUUID=539b5814-01
>>
>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>> ID_FS_TYPE=linux_raid_member
>> ID_FS_PARTUUID=badeaffe-01
>>
>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>> ID_FS_TYPE=linux_raid_member
>> ID_FS_PARTUUID=15631562-01
>>
>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>> ID_FS_TYPE=linux_raid_member
>> ID_FS_PARTUUID=162f0d0b-01
>>
>> [ 2.479836] myhost systemd[1]: Device
>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0.device appeared twice
>> with different sysfs paths /sys
>> /devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.0/host8/target
>> 8:0:0/8:0:0:0/block/sdg
>> [ 2.500826] myhost systemd[1]: Device
>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0\x2dpart1.device
>> appeared twice with different sysfs p
>> aths
>> /sys/devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.
>> 0/host8/target8:0:0/8:0:0:0/block/sdg/sdg1
>> [ 2.632754] myhost kernel: Switched to clocksource tsc
>> [ 91.162986] myhost systemd[1]: Job dev-md0.device/start timed out.
>> [ 91.163138] myhost systemd[1]: Timed out waiting for device dev-md0.device.
>> [ 91.163251] myhost systemd[1]: Dependency failed for Cryptography Setup for
>> luks-md0.
>> [ 91.163360] myhost systemd[1]: Dependency failed for
>> dev-mapper-luks\x2dmd0.device.
>> [ 91.163474] myhost systemd[1]: Job dev-mapper-luks\x2dmd0.device/start
>> failed with result 'dependency'.
>> [ 91.163586] myhost systemd[1]: Dependency failed for Encrypted Volumes.
>> [ 91.163694] myhost systemd[1]: Job cryptsetup.target/start failed with
>> result 'dependency'.
>> [ 91.163801] myhost systemd[1]: Job
>> systemd-cryptsetup@luks\x2dmd0.service/start failed with result 'dependency'.
>> [ 91.163910] myhost systemd[1]: Job dev-md0.device/start failed with result
>> 'timeout'.
>> [ 91.164021] myhost systemd[1]: Reached target System Initialization.
>> [ 91.164129] myhost systemd[1]: Starting System Initialization.
>> [ 91.164236] myhost systemd[1]: Reached target Basic System.
>> [ 91.164346] myhost systemd[1]: Starting Basic System.
>> [ 185.740238] myhost dracut-initqueue[340]: Warning: Could not boot.
>> [ 185.741266] myhost systemd[1]: Received SIGRTMIN+20 from PID 341 (plymouthd).
>> [ 185.841257] myhost dracut-initqueue[340]: Warning: /dev/VolGroup00/root does
>> not exist
>> [ 185.841403] myhost systemd[1]: Starting Dracut Emergency Shell...
>> [ 185.859366] myhost systemd[1]: Received SIGRTMIN+21 from PID 341 (plymouthd).
>>
>> dracut:/# cat "/run/initramfs/rdsosreport.txt"
>> + cat /lib/dracut/dracut-041-10.fc22.1
>> dracut-041-10.fc22.1
>> + cat /proc/cmdline
>> BOOT_IMAGE=/vmlinuz-4.0.4-301.fc22.x86_64 root=/dev/VolGroup00/root ro quiet
>> console=ttyS0,115200n8 rd_NO_PLYMOUTH SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-
>> 8 KEYTABLE=de-latin1
>
> your kernel cmdline seems to be missing the raid configuration
>
> rd.md.uuid=56e9bde4-5cd1-630d-188c-22a54c1c8c37
> rd.md.uuid=eb295015-e20b-e133-15db-5c9130487300
> rd.md.uuid=51e8e983-8786-b868-dbc3-87357e1a9534
>
> ... whatever is needed to boot your system.
>
> # dracut --print-cmdline
>
> should tell you what kernel cmdline parameters are needed
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
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <5565B3E6.4010806-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
@ 2015-05-27 12:13 ` Andrei Borzenkov
[not found] ` <CAA91j0UysOKJG6LpuvCdrh3jcRMdj9+=XaD-R+Shw7WFZSvbUw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
0 siblings, 1 reply; 19+ messages in thread
From: Andrei Borzenkov @ 2015-05-27 12:13 UTC (permalink / raw)
To: Gerhard Wiesinger; +Cc: Harald Hoyer, initramfs
On Wed, May 27, 2015 at 3:09 PM, Gerhard Wiesinger <lists-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org> wrote:
> On 27.05.2015 13:56, Harald Hoyer wrote:
>>
>> Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
>>>
>>> Hello,
>>>
>>> After upgrading one machine it does't boot anymore. Booting the old
>>> kernel
>>> works well.
>>>
>>> It is a RAID, LUKS, LVM setup. Find relevant details below.
>>>
>>> So it looks RAID assembling doesn't work any more.
>>>
>>> Any ideas?
>>>
>>> Thank you.
>>>
>>> Ciao,
>>> Gerhard
>>>
>>> blkid
>>> /dev/sda1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>> TYPE="linux_raid_member"
>>> PARTUUID="5ec6792c-01"
>>> /dev/sdb1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>> TYPE="linux_raid_member"
>>> PARTUUID="1c7cffaf-01"
>>> /dev/sdc1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>> TYPE="linux_raid_member"
>>> PARTUUID="0079dfc3-01"
>>> /dev/sdd1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>> TYPE="linux_raid_member"
>>> PARTUUID="fadeaffe-01"
>>> /dev/sde1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>> TYPE="linux_raid_member"
>>> PARTUUID="539b5814-01"
>>> /dev/sdf1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>> TYPE="linux_raid_member"
>>> PARTUUID="badeaffe-01"
>>> /dev/sdh1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>> TYPE="linux_raid_member"
>>> PARTUUID="15631562-01"
>>> /dev/sdg1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>> TYPE="linux_raid_member"
>>> PARTUUID="162f0d0b-01"
>>>
>>>
>>> blkid -o udev
>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>> ID_FS_TYPE=linux_raid_member
>>> ID_FS_PARTUUID=5ec6792c-01
>>>
>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>> ID_FS_TYPE=linux_raid_member
>>> ID_FS_PARTUUID=1c7cffaf-01
>>>
>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>> ID_FS_TYPE=linux_raid_member
>>> ID_FS_PARTUUID=0079dfc3-01
>>>
>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>> ID_FS_TYPE=linux_raid_member
>>> ID_FS_PARTUUID=fadeaffe-01
>>>
>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>> ID_FS_TYPE=linux_raid_member
>>> ID_FS_PARTUUID=539b5814-01
>>>
>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>> ID_FS_TYPE=linux_raid_member
>>> ID_FS_PARTUUID=badeaffe-01
>>>
>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>> ID_FS_TYPE=linux_raid_member
>>> ID_FS_PARTUUID=15631562-01
>>>
>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>> ID_FS_TYPE=linux_raid_member
>>> ID_FS_PARTUUID=162f0d0b-01
>>>
>>> [ 2.479836] myhost systemd[1]: Device
>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0.device appeared
>>> twice
>>> with different sysfs paths /sys
>>>
>>> /devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.0/host8/target
>>> 8:0:0/8:0:0:0/block/sdg
>>> [ 2.500826] myhost systemd[1]: Device
>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0\x2dpart1.device
>>> appeared twice with different sysfs p
>>> aths
>>>
>>> /sys/devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.
>>> 0/host8/target8:0:0/8:0:0:0/block/sdg/sdg1
>>> [ 2.632754] myhost kernel: Switched to clocksource tsc
>>> [ 91.162986] myhost systemd[1]: Job dev-md0.device/start timed out.
>>> [ 91.163138] myhost systemd[1]: Timed out waiting for device
>>> dev-md0.device.
>>> [ 91.163251] myhost systemd[1]: Dependency failed for Cryptography
>>> Setup for
>>> luks-md0.
>>> [ 91.163360] myhost systemd[1]: Dependency failed for
>>> dev-mapper-luks\x2dmd0.device.
>>> [ 91.163474] myhost systemd[1]: Job dev-mapper-luks\x2dmd0.device/start
>>> failed with result 'dependency'.
>>> [ 91.163586] myhost systemd[1]: Dependency failed for Encrypted
>>> Volumes.
>>> [ 91.163694] myhost systemd[1]: Job cryptsetup.target/start failed with
>>> result 'dependency'.
>>> [ 91.163801] myhost systemd[1]: Job
>>> systemd-cryptsetup@luks\x2dmd0.service/start failed with result
>>> 'dependency'.
>>> [ 91.163910] myhost systemd[1]: Job dev-md0.device/start failed with
>>> result
>>> 'timeout'.
>>> [ 91.164021] myhost systemd[1]: Reached target System Initialization.
>>> [ 91.164129] myhost systemd[1]: Starting System Initialization.
>>> [ 91.164236] myhost systemd[1]: Reached target Basic System.
>>> [ 91.164346] myhost systemd[1]: Starting Basic System.
>>> [ 185.740238] myhost dracut-initqueue[340]: Warning: Could not boot.
>>> [ 185.741266] myhost systemd[1]: Received SIGRTMIN+20 from PID 341
>>> (plymouthd).
>>> [ 185.841257] myhost dracut-initqueue[340]: Warning:
>>> /dev/VolGroup00/root does
>>> not exist
>>> [ 185.841403] myhost systemd[1]: Starting Dracut Emergency Shell...
>>> [ 185.859366] myhost systemd[1]: Received SIGRTMIN+21 from PID 341
>>> (plymouthd).
>>>
>>> dracut:/# cat "/run/initramfs/rdsosreport.txt"
>>> + cat /lib/dracut/dracut-041-10.fc22.1
>>> dracut-041-10.fc22.1
>>> + cat /proc/cmdline
>>> BOOT_IMAGE=/vmlinuz-4.0.4-301.fc22.x86_64 root=/dev/VolGroup00/root ro
>>> quiet
>>> console=ttyS0,115200n8 rd_NO_PLYMOUTH SYSFONT=latarcyrheb-sun16
>>> LANG=en_US.UTF-
>>> 8 KEYTABLE=de-latin1
>>
>>
>> your kernel cmdline seems to be missing the raid configuration
>>
>> rd.md.uuid=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>> rd.md.uuid=eb295015-e20b-e133-15db-5c9130487300
>> rd.md.uuid=51e8e983-8786-b868-dbc3-87357e1a9534
>>
>> ... whatever is needed to boot your system.
>>
>> # dracut --print-cmdline
>>
>> should tell you what kernel cmdline parameters are needed
>
>
>
> 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
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.
> 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 majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <CAA91j0UysOKJG6LpuvCdrh3jcRMdj9+=XaD-R+Shw7WFZSvbUw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2015-05-27 12:25 ` Harald Hoyer
[not found] ` <5565B7BF.4010604-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
0 siblings, 1 reply; 19+ messages in thread
From: Harald Hoyer @ 2015-05-27 12:25 UTC (permalink / raw)
To: Andrei Borzenkov, Gerhard Wiesinger; +Cc: initramfs
Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
> On Wed, May 27, 2015 at 3:09 PM, Gerhard Wiesinger <lists-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org> wrote:
>> On 27.05.2015 13:56, Harald Hoyer wrote:
>>>
>>> Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
>>>>
>>>> Hello,
>>>>
>>>> After upgrading one machine it does't boot anymore. Booting the old
>>>> kernel
>>>> works well.
>>>>
>>>> It is a RAID, LUKS, LVM setup. Find relevant details below.
>>>>
>>>> So it looks RAID assembling doesn't work any more.
>>>>
>>>> Any ideas?
>>>>
>>>> Thank you.
>>>>
>>>> Ciao,
>>>> Gerhard
>>>>
>>>> blkid
>>>> /dev/sda1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>> TYPE="linux_raid_member"
>>>> PARTUUID="5ec6792c-01"
>>>> /dev/sdb1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>> TYPE="linux_raid_member"
>>>> PARTUUID="1c7cffaf-01"
>>>> /dev/sdc1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>> TYPE="linux_raid_member"
>>>> PARTUUID="0079dfc3-01"
>>>> /dev/sdd1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>> TYPE="linux_raid_member"
>>>> PARTUUID="fadeaffe-01"
>>>> /dev/sde1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>> TYPE="linux_raid_member"
>>>> PARTUUID="539b5814-01"
>>>> /dev/sdf1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>> TYPE="linux_raid_member"
>>>> PARTUUID="badeaffe-01"
>>>> /dev/sdh1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>> TYPE="linux_raid_member"
>>>> PARTUUID="15631562-01"
>>>> /dev/sdg1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>> TYPE="linux_raid_member"
>>>> PARTUUID="162f0d0b-01"
>>>>
>>>>
>>>> blkid -o udev
>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>> ID_FS_TYPE=linux_raid_member
>>>> ID_FS_PARTUUID=5ec6792c-01
>>>>
>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>> ID_FS_TYPE=linux_raid_member
>>>> ID_FS_PARTUUID=1c7cffaf-01
>>>>
>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>> ID_FS_TYPE=linux_raid_member
>>>> ID_FS_PARTUUID=0079dfc3-01
>>>>
>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>> ID_FS_TYPE=linux_raid_member
>>>> ID_FS_PARTUUID=fadeaffe-01
>>>>
>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>> ID_FS_TYPE=linux_raid_member
>>>> ID_FS_PARTUUID=539b5814-01
>>>>
>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>> ID_FS_TYPE=linux_raid_member
>>>> ID_FS_PARTUUID=badeaffe-01
>>>>
>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>> ID_FS_TYPE=linux_raid_member
>>>> ID_FS_PARTUUID=15631562-01
>>>>
>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>> ID_FS_TYPE=linux_raid_member
>>>> ID_FS_PARTUUID=162f0d0b-01
>>>>
>>>> [ 2.479836] myhost systemd[1]: Device
>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0.device appeared
>>>> twice
>>>> with different sysfs paths /sys
>>>>
>>>> /devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.0/host8/target
>>>> 8:0:0/8:0:0:0/block/sdg
>>>> [ 2.500826] myhost systemd[1]: Device
>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0\x2dpart1.device
>>>> appeared twice with different sysfs p
>>>> aths
>>>>
>>>> /sys/devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.
>>>> 0/host8/target8:0:0/8:0:0:0/block/sdg/sdg1
>>>> [ 2.632754] myhost kernel: Switched to clocksource tsc
>>>> [ 91.162986] myhost systemd[1]: Job dev-md0.device/start timed out.
>>>> [ 91.163138] myhost systemd[1]: Timed out waiting for device
>>>> dev-md0.device.
>>>> [ 91.163251] myhost systemd[1]: Dependency failed for Cryptography
>>>> Setup for
>>>> luks-md0.
>>>> [ 91.163360] myhost systemd[1]: Dependency failed for
>>>> dev-mapper-luks\x2dmd0.device.
>>>> [ 91.163474] myhost systemd[1]: Job dev-mapper-luks\x2dmd0.device/start
>>>> failed with result 'dependency'.
>>>> [ 91.163586] myhost systemd[1]: Dependency failed for Encrypted
>>>> Volumes.
>>>> [ 91.163694] myhost systemd[1]: Job cryptsetup.target/start failed with
>>>> result 'dependency'.
>>>> [ 91.163801] myhost systemd[1]: Job
>>>> systemd-cryptsetup@luks\x2dmd0.service/start failed with result
>>>> 'dependency'.
>>>> [ 91.163910] myhost systemd[1]: Job dev-md0.device/start failed with
>>>> result
>>>> 'timeout'.
>>>> [ 91.164021] myhost systemd[1]: Reached target System Initialization.
>>>> [ 91.164129] myhost systemd[1]: Starting System Initialization.
>>>> [ 91.164236] myhost systemd[1]: Reached target Basic System.
>>>> [ 91.164346] myhost systemd[1]: Starting Basic System.
>>>> [ 185.740238] myhost dracut-initqueue[340]: Warning: Could not boot.
>>>> [ 185.741266] myhost systemd[1]: Received SIGRTMIN+20 from PID 341
>>>> (plymouthd).
>>>> [ 185.841257] myhost dracut-initqueue[340]: Warning:
>>>> /dev/VolGroup00/root does
>>>> not exist
>>>> [ 185.841403] myhost systemd[1]: Starting Dracut Emergency Shell...
>>>> [ 185.859366] myhost systemd[1]: Received SIGRTMIN+21 from PID 341
>>>> (plymouthd).
>>>>
>>>> dracut:/# cat "/run/initramfs/rdsosreport.txt"
>>>> + cat /lib/dracut/dracut-041-10.fc22.1
>>>> dracut-041-10.fc22.1
>>>> + cat /proc/cmdline
>>>> BOOT_IMAGE=/vmlinuz-4.0.4-301.fc22.x86_64 root=/dev/VolGroup00/root ro
>>>> quiet
>>>> console=ttyS0,115200n8 rd_NO_PLYMOUTH SYSFONT=latarcyrheb-sun16
>>>> LANG=en_US.UTF-
>>>> 8 KEYTABLE=de-latin1
>>>
>>>
>>> your kernel cmdline seems to be missing the raid configuration
>>>
>>> rd.md.uuid=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>> rd.md.uuid=eb295015-e20b-e133-15db-5c9130487300
>>> rd.md.uuid=51e8e983-8786-b868-dbc3-87357e1a9534
>>>
>>> ... whatever is needed to boot your system.
>>>
>>> # dracut --print-cmdline
>>>
>>> should tell you what kernel cmdline parameters are needed
>>
>>
>>
>> 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
>
> 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.
>
>> 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.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <5565B7BF.4010604-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
@ 2015-05-27 12:39 ` Gerhard Wiesinger
[not found] ` <5565BAEA.6080202-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
0 siblings, 1 reply; 19+ messages in thread
From: Gerhard Wiesinger @ 2015-05-27 12:39 UTC (permalink / raw)
To: Harald Hoyer, Andrei Borzenkov; +Cc: initramfs
On 27.05.2015 14:25, Harald Hoyer wrote:
> Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
>> On Wed, May 27, 2015 at 3:09 PM, Gerhard Wiesinger <lists-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org> wrote:
>>> On 27.05.2015 13:56, Harald Hoyer wrote:
>>>> Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
>>>>> Hello,
>>>>>
>>>>> After upgrading one machine it does't boot anymore. Booting the old
>>>>> kernel
>>>>> works well.
>>>>>
>>>>> It is a RAID, LUKS, LVM setup. Find relevant details below.
>>>>>
>>>>> So it looks RAID assembling doesn't work any more.
>>>>>
>>>>> Any ideas?
>>>>>
>>>>> Thank you.
>>>>>
>>>>> Ciao,
>>>>> Gerhard
>>>>>
>>>>> blkid
>>>>> /dev/sda1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>> TYPE="linux_raid_member"
>>>>> PARTUUID="5ec6792c-01"
>>>>> /dev/sdb1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>> TYPE="linux_raid_member"
>>>>> PARTUUID="1c7cffaf-01"
>>>>> /dev/sdc1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>> TYPE="linux_raid_member"
>>>>> PARTUUID="0079dfc3-01"
>>>>> /dev/sdd1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>> TYPE="linux_raid_member"
>>>>> PARTUUID="fadeaffe-01"
>>>>> /dev/sde1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>> TYPE="linux_raid_member"
>>>>> PARTUUID="539b5814-01"
>>>>> /dev/sdf1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>> TYPE="linux_raid_member"
>>>>> PARTUUID="badeaffe-01"
>>>>> /dev/sdh1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>> TYPE="linux_raid_member"
>>>>> PARTUUID="15631562-01"
>>>>> /dev/sdg1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>> TYPE="linux_raid_member"
>>>>> PARTUUID="162f0d0b-01"
>>>>>
>>>>>
>>>>> blkid -o udev
>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>> ID_FS_TYPE=linux_raid_member
>>>>> ID_FS_PARTUUID=5ec6792c-01
>>>>>
>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>> ID_FS_TYPE=linux_raid_member
>>>>> ID_FS_PARTUUID=1c7cffaf-01
>>>>>
>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>> ID_FS_TYPE=linux_raid_member
>>>>> ID_FS_PARTUUID=0079dfc3-01
>>>>>
>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>> ID_FS_TYPE=linux_raid_member
>>>>> ID_FS_PARTUUID=fadeaffe-01
>>>>>
>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>> ID_FS_TYPE=linux_raid_member
>>>>> ID_FS_PARTUUID=539b5814-01
>>>>>
>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>> ID_FS_TYPE=linux_raid_member
>>>>> ID_FS_PARTUUID=badeaffe-01
>>>>>
>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>> ID_FS_TYPE=linux_raid_member
>>>>> ID_FS_PARTUUID=15631562-01
>>>>>
>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>> ID_FS_TYPE=linux_raid_member
>>>>> ID_FS_PARTUUID=162f0d0b-01
>>>>>
>>>>> [ 2.479836] myhost systemd[1]: Device
>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0.device appeared
>>>>> twice
>>>>> with different sysfs paths /sys
>>>>>
>>>>> /devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.0/host8/target
>>>>> 8:0:0/8:0:0:0/block/sdg
>>>>> [ 2.500826] myhost systemd[1]: Device
>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0\x2dpart1.device
>>>>> appeared twice with different sysfs p
>>>>> aths
>>>>>
>>>>> /sys/devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.
>>>>> 0/host8/target8:0:0/8:0:0:0/block/sdg/sdg1
>>>>> [ 2.632754] myhost kernel: Switched to clocksource tsc
>>>>> [ 91.162986] myhost systemd[1]: Job dev-md0.device/start timed out.
>>>>> [ 91.163138] myhost systemd[1]: Timed out waiting for device
>>>>> dev-md0.device.
>>>>> [ 91.163251] myhost systemd[1]: Dependency failed for Cryptography
>>>>> Setup for
>>>>> luks-md0.
>>>>> [ 91.163360] myhost systemd[1]: Dependency failed for
>>>>> dev-mapper-luks\x2dmd0.device.
>>>>> [ 91.163474] myhost systemd[1]: Job dev-mapper-luks\x2dmd0.device/start
>>>>> failed with result 'dependency'.
>>>>> [ 91.163586] myhost systemd[1]: Dependency failed for Encrypted
>>>>> Volumes.
>>>>> [ 91.163694] myhost systemd[1]: Job cryptsetup.target/start failed with
>>>>> result 'dependency'.
>>>>> [ 91.163801] myhost systemd[1]: Job
>>>>> systemd-cryptsetup@luks\x2dmd0.service/start failed with result
>>>>> 'dependency'.
>>>>> [ 91.163910] myhost systemd[1]: Job dev-md0.device/start failed with
>>>>> result
>>>>> 'timeout'.
>>>>> [ 91.164021] myhost systemd[1]: Reached target System Initialization.
>>>>> [ 91.164129] myhost systemd[1]: Starting System Initialization.
>>>>> [ 91.164236] myhost systemd[1]: Reached target Basic System.
>>>>> [ 91.164346] myhost systemd[1]: Starting Basic System.
>>>>> [ 185.740238] myhost dracut-initqueue[340]: Warning: Could not boot.
>>>>> [ 185.741266] myhost systemd[1]: Received SIGRTMIN+20 from PID 341
>>>>> (plymouthd).
>>>>> [ 185.841257] myhost dracut-initqueue[340]: Warning:
>>>>> /dev/VolGroup00/root does
>>>>> not exist
>>>>> [ 185.841403] myhost systemd[1]: Starting Dracut Emergency Shell...
>>>>> [ 185.859366] myhost systemd[1]: Received SIGRTMIN+21 from PID 341
>>>>> (plymouthd).
>>>>>
>>>>> dracut:/# cat "/run/initramfs/rdsosreport.txt"
>>>>> + cat /lib/dracut/dracut-041-10.fc22.1
>>>>> dracut-041-10.fc22.1
>>>>> + cat /proc/cmdline
>>>>> BOOT_IMAGE=/vmlinuz-4.0.4-301.fc22.x86_64 root=/dev/VolGroup00/root ro
>>>>> quiet
>>>>> console=ttyS0,115200n8 rd_NO_PLYMOUTH SYSFONT=latarcyrheb-sun16
>>>>> LANG=en_US.UTF-
>>>>> 8 KEYTABLE=de-latin1
>>>>
>>>> your kernel cmdline seems to be missing the raid configuration
>>>>
>>>> rd.md.uuid=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>> rd.md.uuid=eb295015-e20b-e133-15db-5c9130487300
>>>> rd.md.uuid=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>
>>>> ... whatever is needed to boot your system.
>>>>
>>>> # dracut --print-cmdline
>>>>
>>>> should tell you what kernel cmdline parameters are needed
>>>
>>>
>>> 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
>> 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.
>>
>>> 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
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <5565BAEA.6080202-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
@ 2015-05-27 12:43 ` Harald Hoyer
[not found] ` <5565BBF8.1050509-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
0 siblings, 1 reply; 19+ messages in thread
From: Harald Hoyer @ 2015-05-27 12:43 UTC (permalink / raw)
To: Gerhard Wiesinger, Andrei Borzenkov; +Cc: initramfs
Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
> On 27.05.2015 14:25, Harald Hoyer wrote:
>> Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
>>> On Wed, May 27, 2015 at 3:09 PM, Gerhard Wiesinger <lists-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org> wrote:
>>>> On 27.05.2015 13:56, Harald Hoyer wrote:
>>>>> Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
>>>>>> Hello,
>>>>>>
>>>>>> After upgrading one machine it does't boot anymore. Booting the old
>>>>>> kernel
>>>>>> works well.
>>>>>>
>>>>>> It is a RAID, LUKS, LVM setup. Find relevant details below.
>>>>>>
>>>>>> So it looks RAID assembling doesn't work any more.
>>>>>>
>>>>>> Any ideas?
>>>>>>
>>>>>> Thank you.
>>>>>>
>>>>>> Ciao,
>>>>>> Gerhard
>>>>>>
>>>>>> blkid
>>>>>> /dev/sda1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>> TYPE="linux_raid_member"
>>>>>> PARTUUID="5ec6792c-01"
>>>>>> /dev/sdb1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>> TYPE="linux_raid_member"
>>>>>> PARTUUID="1c7cffaf-01"
>>>>>> /dev/sdc1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>> TYPE="linux_raid_member"
>>>>>> PARTUUID="0079dfc3-01"
>>>>>> /dev/sdd1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>> TYPE="linux_raid_member"
>>>>>> PARTUUID="fadeaffe-01"
>>>>>> /dev/sde1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>> TYPE="linux_raid_member"
>>>>>> PARTUUID="539b5814-01"
>>>>>> /dev/sdf1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>> TYPE="linux_raid_member"
>>>>>> PARTUUID="badeaffe-01"
>>>>>> /dev/sdh1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>> TYPE="linux_raid_member"
>>>>>> PARTUUID="15631562-01"
>>>>>> /dev/sdg1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>> TYPE="linux_raid_member"
>>>>>> PARTUUID="162f0d0b-01"
>>>>>>
>>>>>>
>>>>>> blkid -o udev
>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>> ID_FS_PARTUUID=5ec6792c-01
>>>>>>
>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>> ID_FS_PARTUUID=1c7cffaf-01
>>>>>>
>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>> ID_FS_PARTUUID=0079dfc3-01
>>>>>>
>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>> ID_FS_PARTUUID=fadeaffe-01
>>>>>>
>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>> ID_FS_PARTUUID=539b5814-01
>>>>>>
>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>> ID_FS_PARTUUID=badeaffe-01
>>>>>>
>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>> ID_FS_PARTUUID=15631562-01
>>>>>>
>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>> ID_FS_PARTUUID=162f0d0b-01
>>>>>>
>>>>>> [ 2.479836] myhost systemd[1]: Device
>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0.device appeared
>>>>>> twice
>>>>>> with different sysfs paths /sys
>>>>>>
>>>>>> /devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
>>>>>>
>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.0/host8/target
>>>>>> 8:0:0/8:0:0:0/block/sdg
>>>>>> [ 2.500826] myhost systemd[1]: Device
>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0\x2dpart1.device
>>>>>> appeared twice with different sysfs p
>>>>>> aths
>>>>>>
>>>>>> /sys/devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
>>>>>>
>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.
>>>>>> 0/host8/target8:0:0/8:0:0:0/block/sdg/sdg1
>>>>>> [ 2.632754] myhost kernel: Switched to clocksource tsc
>>>>>> [ 91.162986] myhost systemd[1]: Job dev-md0.device/start timed out.
>>>>>> [ 91.163138] myhost systemd[1]: Timed out waiting for device
>>>>>> dev-md0.device.
>>>>>> [ 91.163251] myhost systemd[1]: Dependency failed for Cryptography
>>>>>> Setup for
>>>>>> luks-md0.
>>>>>> [ 91.163360] myhost systemd[1]: Dependency failed for
>>>>>> dev-mapper-luks\x2dmd0.device.
>>>>>> [ 91.163474] myhost systemd[1]: Job dev-mapper-luks\x2dmd0.device/start
>>>>>> failed with result 'dependency'.
>>>>>> [ 91.163586] myhost systemd[1]: Dependency failed for Encrypted
>>>>>> Volumes.
>>>>>> [ 91.163694] myhost systemd[1]: Job cryptsetup.target/start failed with
>>>>>> result 'dependency'.
>>>>>> [ 91.163801] myhost systemd[1]: Job
>>>>>> systemd-cryptsetup@luks\x2dmd0.service/start failed with result
>>>>>> 'dependency'.
>>>>>> [ 91.163910] myhost systemd[1]: Job dev-md0.device/start failed with
>>>>>> result
>>>>>> 'timeout'.
>>>>>> [ 91.164021] myhost systemd[1]: Reached target System Initialization.
>>>>>> [ 91.164129] myhost systemd[1]: Starting System Initialization.
>>>>>> [ 91.164236] myhost systemd[1]: Reached target Basic System.
>>>>>> [ 91.164346] myhost systemd[1]: Starting Basic System.
>>>>>> [ 185.740238] myhost dracut-initqueue[340]: Warning: Could not boot.
>>>>>> [ 185.741266] myhost systemd[1]: Received SIGRTMIN+20 from PID 341
>>>>>> (plymouthd).
>>>>>> [ 185.841257] myhost dracut-initqueue[340]: Warning:
>>>>>> /dev/VolGroup00/root does
>>>>>> not exist
>>>>>> [ 185.841403] myhost systemd[1]: Starting Dracut Emergency Shell...
>>>>>> [ 185.859366] myhost systemd[1]: Received SIGRTMIN+21 from PID 341
>>>>>> (plymouthd).
>>>>>>
>>>>>> dracut:/# cat "/run/initramfs/rdsosreport.txt"
>>>>>> + cat /lib/dracut/dracut-041-10.fc22.1
>>>>>> dracut-041-10.fc22.1
>>>>>> + cat /proc/cmdline
>>>>>> BOOT_IMAGE=/vmlinuz-4.0.4-301.fc22.x86_64 root=/dev/VolGroup00/root ro
>>>>>> quiet
>>>>>> console=ttyS0,115200n8 rd_NO_PLYMOUTH SYSFONT=latarcyrheb-sun16
>>>>>> LANG=en_US.UTF-
>>>>>> 8 KEYTABLE=de-latin1
>>>>>
>>>>> your kernel cmdline seems to be missing the raid configuration
>>>>>
>>>>> rd.md.uuid=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>> rd.md.uuid=eb295015-e20b-e133-15db-5c9130487300
>>>>> rd.md.uuid=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>
>>>>> ... whatever is needed to boot your system.
>>>>>
>>>>> # dracut --print-cmdline
>>>>>
>>>>> should tell you what kernel cmdline parameters are needed
>>>>
>>>>
>>>> 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
>>> 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.
>>>
>>>> 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
>
Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?
What is your /etc/crypttab ?
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <5565BBF8.1050509-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
@ 2015-05-27 13:03 ` Gerhard Wiesinger
[not found] ` <5565C0AC.2070106-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
0 siblings, 1 reply; 19+ messages in thread
From: Gerhard Wiesinger @ 2015-05-27 13:03 UTC (permalink / raw)
To: Harald Hoyer, Andrei Borzenkov; +Cc: initramfs
On 27.05.2015 14:43, Harald Hoyer wrote:
> Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
>> On 27.05.2015 14:25, Harald Hoyer wrote:
>>> Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
>>>> On Wed, May 27, 2015 at 3:09 PM, Gerhard Wiesinger <lists-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org> wrote:
>>>>> On 27.05.2015 13:56, Harald Hoyer wrote:
>>>>>> Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
>>>>>>> Hello,
>>>>>>>
>>>>>>> After upgrading one machine it does't boot anymore. Booting the old
>>>>>>> kernel
>>>>>>> works well.
>>>>>>>
>>>>>>> It is a RAID, LUKS, LVM setup. Find relevant details below.
>>>>>>>
>>>>>>> So it looks RAID assembling doesn't work any more.
>>>>>>>
>>>>>>> Any ideas?
>>>>>>>
>>>>>>> Thank you.
>>>>>>>
>>>>>>> Ciao,
>>>>>>> Gerhard
>>>>>>>
>>>>>>> blkid
>>>>>>> /dev/sda1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>> TYPE="linux_raid_member"
>>>>>>> PARTUUID="5ec6792c-01"
>>>>>>> /dev/sdb1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>> TYPE="linux_raid_member"
>>>>>>> PARTUUID="1c7cffaf-01"
>>>>>>> /dev/sdc1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>> TYPE="linux_raid_member"
>>>>>>> PARTUUID="0079dfc3-01"
>>>>>>> /dev/sdd1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>> TYPE="linux_raid_member"
>>>>>>> PARTUUID="fadeaffe-01"
>>>>>>> /dev/sde1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>> TYPE="linux_raid_member"
>>>>>>> PARTUUID="539b5814-01"
>>>>>>> /dev/sdf1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>> TYPE="linux_raid_member"
>>>>>>> PARTUUID="badeaffe-01"
>>>>>>> /dev/sdh1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>>> TYPE="linux_raid_member"
>>>>>>> PARTUUID="15631562-01"
>>>>>>> /dev/sdg1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>>> TYPE="linux_raid_member"
>>>>>>> PARTUUID="162f0d0b-01"
>>>>>>>
>>>>>>>
>>>>>>> blkid -o udev
>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>> ID_FS_PARTUUID=5ec6792c-01
>>>>>>>
>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>> ID_FS_PARTUUID=1c7cffaf-01
>>>>>>>
>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>> ID_FS_PARTUUID=0079dfc3-01
>>>>>>>
>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>> ID_FS_PARTUUID=fadeaffe-01
>>>>>>>
>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>> ID_FS_PARTUUID=539b5814-01
>>>>>>>
>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>> ID_FS_PARTUUID=badeaffe-01
>>>>>>>
>>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>> ID_FS_PARTUUID=15631562-01
>>>>>>>
>>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>> ID_FS_PARTUUID=162f0d0b-01
>>>>>>>
>>>>>>> [ 2.479836] myhost systemd[1]: Device
>>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0.device appeared
>>>>>>> twice
>>>>>>> with different sysfs paths /sys
>>>>>>>
>>>>>>> /devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
>>>>>>>
>>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.0/host8/target
>>>>>>> 8:0:0/8:0:0:0/block/sdg
>>>>>>> [ 2.500826] myhost systemd[1]: Device
>>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0\x2dpart1.device
>>>>>>> appeared twice with different sysfs p
>>>>>>> aths
>>>>>>>
>>>>>>> /sys/devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
>>>>>>>
>>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.
>>>>>>> 0/host8/target8:0:0/8:0:0:0/block/sdg/sdg1
>>>>>>> [ 2.632754] myhost kernel: Switched to clocksource tsc
>>>>>>> [ 91.162986] myhost systemd[1]: Job dev-md0.device/start timed out.
>>>>>>> [ 91.163138] myhost systemd[1]: Timed out waiting for device
>>>>>>> dev-md0.device.
>>>>>>> [ 91.163251] myhost systemd[1]: Dependency failed for Cryptography
>>>>>>> Setup for
>>>>>>> luks-md0.
>>>>>>> [ 91.163360] myhost systemd[1]: Dependency failed for
>>>>>>> dev-mapper-luks\x2dmd0.device.
>>>>>>> [ 91.163474] myhost systemd[1]: Job dev-mapper-luks\x2dmd0.device/start
>>>>>>> failed with result 'dependency'.
>>>>>>> [ 91.163586] myhost systemd[1]: Dependency failed for Encrypted
>>>>>>> Volumes.
>>>>>>> [ 91.163694] myhost systemd[1]: Job cryptsetup.target/start failed with
>>>>>>> result 'dependency'.
>>>>>>> [ 91.163801] myhost systemd[1]: Job
>>>>>>> systemd-cryptsetup@luks\x2dmd0.service/start failed with result
>>>>>>> 'dependency'.
>>>>>>> [ 91.163910] myhost systemd[1]: Job dev-md0.device/start failed with
>>>>>>> result
>>>>>>> 'timeout'.
>>>>>>> [ 91.164021] myhost systemd[1]: Reached target System Initialization.
>>>>>>> [ 91.164129] myhost systemd[1]: Starting System Initialization.
>>>>>>> [ 91.164236] myhost systemd[1]: Reached target Basic System.
>>>>>>> [ 91.164346] myhost systemd[1]: Starting Basic System.
>>>>>>> [ 185.740238] myhost dracut-initqueue[340]: Warning: Could not boot.
>>>>>>> [ 185.741266] myhost systemd[1]: Received SIGRTMIN+20 from PID 341
>>>>>>> (plymouthd).
>>>>>>> [ 185.841257] myhost dracut-initqueue[340]: Warning:
>>>>>>> /dev/VolGroup00/root does
>>>>>>> not exist
>>>>>>> [ 185.841403] myhost systemd[1]: Starting Dracut Emergency Shell...
>>>>>>> [ 185.859366] myhost systemd[1]: Received SIGRTMIN+21 from PID 341
>>>>>>> (plymouthd).
>>>>>>>
>>>>>>> dracut:/# cat "/run/initramfs/rdsosreport.txt"
>>>>>>> + cat /lib/dracut/dracut-041-10.fc22.1
>>>>>>> dracut-041-10.fc22.1
>>>>>>> + cat /proc/cmdline
>>>>>>> BOOT_IMAGE=/vmlinuz-4.0.4-301.fc22.x86_64 root=/dev/VolGroup00/root ro
>>>>>>> quiet
>>>>>>> console=ttyS0,115200n8 rd_NO_PLYMOUTH SYSFONT=latarcyrheb-sun16
>>>>>>> LANG=en_US.UTF-
>>>>>>> 8 KEYTABLE=de-latin1
>>>>>> your kernel cmdline seems to be missing the raid configuration
>>>>>>
>>>>>> rd.md.uuid=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>> rd.md.uuid=eb295015-e20b-e133-15db-5c9130487300
>>>>>> rd.md.uuid=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>
>>>>>> ... whatever is needed to boot your system.
>>>>>>
>>>>>> # dracut --print-cmdline
>>>>>>
>>>>>> should tell you what kernel cmdline parameters are needed
>>>>>
>>>>> 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
>>>> 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.
>>>>
>>>>> 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
>>
> Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?
Yes, of course. :-)
>
> 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
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <5565C0AC.2070106-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
@ 2015-05-27 13:07 ` Harald Hoyer
[not found] ` <5565C182.30709-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
0 siblings, 1 reply; 19+ messages in thread
From: Harald Hoyer @ 2015-05-27 13:07 UTC (permalink / raw)
To: Gerhard Wiesinger, Andrei Borzenkov; +Cc: initramfs
Am 27.05.2015 um 15:03 schrieb Gerhard Wiesinger:
> On 27.05.2015 14:43, Harald Hoyer wrote:
>> Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
>>> On 27.05.2015 14:25, Harald Hoyer wrote:
>>>> Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
>>>>> On Wed, May 27, 2015 at 3:09 PM, Gerhard Wiesinger <lists-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
>>>>> wrote:
>>>>>> On 27.05.2015 13:56, Harald Hoyer wrote:
>>>>>>> Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> After upgrading one machine it does't boot anymore. Booting the old
>>>>>>>> kernel
>>>>>>>> works well.
>>>>>>>>
>>>>>>>> It is a RAID, LUKS, LVM setup. Find relevant details below.
>>>>>>>>
>>>>>>>> So it looks RAID assembling doesn't work any more.
>>>>>>>>
>>>>>>>> Any ideas?
>>>>>>>>
>>>>>>>> Thank you.
>>>>>>>>
>>>>>>>> Ciao,
>>>>>>>> Gerhard
>>>>>>>>
>>>>>>>> blkid
>>>>>>>> /dev/sda1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>> TYPE="linux_raid_member"
>>>>>>>> PARTUUID="5ec6792c-01"
>>>>>>>> /dev/sdb1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>> TYPE="linux_raid_member"
>>>>>>>> PARTUUID="1c7cffaf-01"
>>>>>>>> /dev/sdc1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>> TYPE="linux_raid_member"
>>>>>>>> PARTUUID="0079dfc3-01"
>>>>>>>> /dev/sdd1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>> TYPE="linux_raid_member"
>>>>>>>> PARTUUID="fadeaffe-01"
>>>>>>>> /dev/sde1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>> TYPE="linux_raid_member"
>>>>>>>> PARTUUID="539b5814-01"
>>>>>>>> /dev/sdf1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>> TYPE="linux_raid_member"
>>>>>>>> PARTUUID="badeaffe-01"
>>>>>>>> /dev/sdh1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>>>> TYPE="linux_raid_member"
>>>>>>>> PARTUUID="15631562-01"
>>>>>>>> /dev/sdg1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>>>> TYPE="linux_raid_member"
>>>>>>>> PARTUUID="162f0d0b-01"
>>>>>>>>
>>>>>>>>
>>>>>>>> blkid -o udev
>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>> ID_FS_PARTUUID=5ec6792c-01
>>>>>>>>
>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>> ID_FS_PARTUUID=1c7cffaf-01
>>>>>>>>
>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>> ID_FS_PARTUUID=0079dfc3-01
>>>>>>>>
>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>> ID_FS_PARTUUID=fadeaffe-01
>>>>>>>>
>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>> ID_FS_PARTUUID=539b5814-01
>>>>>>>>
>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>> ID_FS_PARTUUID=badeaffe-01
>>>>>>>>
>>>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>> ID_FS_PARTUUID=15631562-01
>>>>>>>>
>>>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>> ID_FS_PARTUUID=162f0d0b-01
>>>>>>>>
>>>>>>>> [ 2.479836] myhost systemd[1]: Device
>>>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0.device appeared
>>>>>>>> twice
>>>>>>>> with different sysfs paths /sys
>>>>>>>>
>>>>>>>> /devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
>>>>>>>>
>>>>>>>>
>>>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.0/host8/target
>>>>>>>> 8:0:0/8:0:0:0/block/sdg
>>>>>>>> [ 2.500826] myhost systemd[1]: Device
>>>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0\x2dpart1.device
>>>>>>>> appeared twice with different sysfs p
>>>>>>>> aths
>>>>>>>>
>>>>>>>> /sys/devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
>>>>>>>>
>>>>>>>>
>>>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.
>>>>>>>> 0/host8/target8:0:0/8:0:0:0/block/sdg/sdg1
>>>>>>>> [ 2.632754] myhost kernel: Switched to clocksource tsc
>>>>>>>> [ 91.162986] myhost systemd[1]: Job dev-md0.device/start timed out.
>>>>>>>> [ 91.163138] myhost systemd[1]: Timed out waiting for device
>>>>>>>> dev-md0.device.
>>>>>>>> [ 91.163251] myhost systemd[1]: Dependency failed for Cryptography
>>>>>>>> Setup for
>>>>>>>> luks-md0.
>>>>>>>> [ 91.163360] myhost systemd[1]: Dependency failed for
>>>>>>>> dev-mapper-luks\x2dmd0.device.
>>>>>>>> [ 91.163474] myhost systemd[1]: Job dev-mapper-luks\x2dmd0.device/start
>>>>>>>> failed with result 'dependency'.
>>>>>>>> [ 91.163586] myhost systemd[1]: Dependency failed for Encrypted
>>>>>>>> Volumes.
>>>>>>>> [ 91.163694] myhost systemd[1]: Job cryptsetup.target/start failed with
>>>>>>>> result 'dependency'.
>>>>>>>> [ 91.163801] myhost systemd[1]: Job
>>>>>>>> systemd-cryptsetup@luks\x2dmd0.service/start failed with result
>>>>>>>> 'dependency'.
>>>>>>>> [ 91.163910] myhost systemd[1]: Job dev-md0.device/start failed with
>>>>>>>> result
>>>>>>>> 'timeout'.
>>>>>>>> [ 91.164021] myhost systemd[1]: Reached target System Initialization.
>>>>>>>> [ 91.164129] myhost systemd[1]: Starting System Initialization.
>>>>>>>> [ 91.164236] myhost systemd[1]: Reached target Basic System.
>>>>>>>> [ 91.164346] myhost systemd[1]: Starting Basic System.
>>>>>>>> [ 185.740238] myhost dracut-initqueue[340]: Warning: Could not boot.
>>>>>>>> [ 185.741266] myhost systemd[1]: Received SIGRTMIN+20 from PID 341
>>>>>>>> (plymouthd).
>>>>>>>> [ 185.841257] myhost dracut-initqueue[340]: Warning:
>>>>>>>> /dev/VolGroup00/root does
>>>>>>>> not exist
>>>>>>>> [ 185.841403] myhost systemd[1]: Starting Dracut Emergency Shell...
>>>>>>>> [ 185.859366] myhost systemd[1]: Received SIGRTMIN+21 from PID 341
>>>>>>>> (plymouthd).
>>>>>>>>
>>>>>>>> dracut:/# cat "/run/initramfs/rdsosreport.txt"
>>>>>>>> + cat /lib/dracut/dracut-041-10.fc22.1
>>>>>>>> dracut-041-10.fc22.1
>>>>>>>> + cat /proc/cmdline
>>>>>>>> BOOT_IMAGE=/vmlinuz-4.0.4-301.fc22.x86_64 root=/dev/VolGroup00/root ro
>>>>>>>> quiet
>>>>>>>> console=ttyS0,115200n8 rd_NO_PLYMOUTH SYSFONT=latarcyrheb-sun16
>>>>>>>> LANG=en_US.UTF-
>>>>>>>> 8 KEYTABLE=de-latin1
>>>>>>> your kernel cmdline seems to be missing the raid configuration
>>>>>>>
>>>>>>> rd.md.uuid=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>> rd.md.uuid=eb295015-e20b-e133-15db-5c9130487300
>>>>>>> rd.md.uuid=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>
>>>>>>> ... whatever is needed to boot your system.
>>>>>>>
>>>>>>> # dracut --print-cmdline
>>>>>>>
>>>>>>> should tell you what kernel cmdline parameters are needed
>>>>>>
>>>>>> 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
>>>>> 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.
>>>>>
>>>>>> 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
>>>
>> Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?
>
> Yes, of course. :-)
>
>>
>> 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
>
Oh... please, please do not use kernel names like "md0" ... better use UUID=
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <5565C182.30709-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
@ 2015-05-27 13:21 ` Gerhard Wiesinger
[not found] ` <5565C4E7.6010301-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
0 siblings, 1 reply; 19+ messages in thread
From: Gerhard Wiesinger @ 2015-05-27 13:21 UTC (permalink / raw)
To: Harald Hoyer, Andrei Borzenkov; +Cc: initramfs
On 27.05.2015 15:07, Harald Hoyer wrote:
> Am 27.05.2015 um 15:03 schrieb Gerhard Wiesinger:
>> On 27.05.2015 14:43, Harald Hoyer wrote:
>>> Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
>>>> On 27.05.2015 14:25, Harald Hoyer wrote:
>>>>> Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
>>>>>> On Wed, May 27, 2015 at 3:09 PM, Gerhard Wiesinger <lists-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
>>>>>> wrote:
>>>>>>> On 27.05.2015 13:56, Harald Hoyer wrote:
>>>>>>>> Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> After upgrading one machine it does't boot anymore. Booting the old
>>>>>>>>> kernel
>>>>>>>>> works well.
>>>>>>>>>
>>>>>>>>> It is a RAID, LUKS, LVM setup. Find relevant details below.
>>>>>>>>>
>>>>>>>>> So it looks RAID assembling doesn't work any more.
>>>>>>>>>
>>>>>>>>> Any ideas?
>>>>>>>>>
>>>>>>>>> Thank you.
>>>>>>>>>
>>>>>>>>> Ciao,
>>>>>>>>> Gerhard
>>>>>>>>>
>>>>>>>>> blkid
>>>>>>>>> /dev/sda1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>> PARTUUID="5ec6792c-01"
>>>>>>>>> /dev/sdb1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>> PARTUUID="1c7cffaf-01"
>>>>>>>>> /dev/sdc1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>> PARTUUID="0079dfc3-01"
>>>>>>>>> /dev/sdd1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>> PARTUUID="fadeaffe-01"
>>>>>>>>> /dev/sde1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>> PARTUUID="539b5814-01"
>>>>>>>>> /dev/sdf1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>> PARTUUID="badeaffe-01"
>>>>>>>>> /dev/sdh1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>> PARTUUID="15631562-01"
>>>>>>>>> /dev/sdg1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>> PARTUUID="162f0d0b-01"
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> blkid -o udev
>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>> ID_FS_PARTUUID=5ec6792c-01
>>>>>>>>>
>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>> ID_FS_PARTUUID=1c7cffaf-01
>>>>>>>>>
>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>> ID_FS_PARTUUID=0079dfc3-01
>>>>>>>>>
>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>> ID_FS_PARTUUID=fadeaffe-01
>>>>>>>>>
>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>> ID_FS_PARTUUID=539b5814-01
>>>>>>>>>
>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>> ID_FS_PARTUUID=badeaffe-01
>>>>>>>>>
>>>>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>> ID_FS_PARTUUID=15631562-01
>>>>>>>>>
>>>>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>> ID_FS_PARTUUID=162f0d0b-01
>>>>>>>>>
>>>>>>>>> [ 2.479836] myhost systemd[1]: Device
>>>>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0.device appeared
>>>>>>>>> twice
>>>>>>>>> with different sysfs paths /sys
>>>>>>>>>
>>>>>>>>> /devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.0/host8/target
>>>>>>>>> 8:0:0/8:0:0:0/block/sdg
>>>>>>>>> [ 2.500826] myhost systemd[1]: Device
>>>>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0\x2dpart1.device
>>>>>>>>> appeared twice with different sysfs p
>>>>>>>>> aths
>>>>>>>>>
>>>>>>>>> /sys/devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.
>>>>>>>>> 0/host8/target8:0:0/8:0:0:0/block/sdg/sdg1
>>>>>>>>> [ 2.632754] myhost kernel: Switched to clocksource tsc
>>>>>>>>> [ 91.162986] myhost systemd[1]: Job dev-md0.device/start timed out.
>>>>>>>>> [ 91.163138] myhost systemd[1]: Timed out waiting for device
>>>>>>>>> dev-md0.device.
>>>>>>>>> [ 91.163251] myhost systemd[1]: Dependency failed for Cryptography
>>>>>>>>> Setup for
>>>>>>>>> luks-md0.
>>>>>>>>> [ 91.163360] myhost systemd[1]: Dependency failed for
>>>>>>>>> dev-mapper-luks\x2dmd0.device.
>>>>>>>>> [ 91.163474] myhost systemd[1]: Job dev-mapper-luks\x2dmd0.device/start
>>>>>>>>> failed with result 'dependency'.
>>>>>>>>> [ 91.163586] myhost systemd[1]: Dependency failed for Encrypted
>>>>>>>>> Volumes.
>>>>>>>>> [ 91.163694] myhost systemd[1]: Job cryptsetup.target/start failed with
>>>>>>>>> result 'dependency'.
>>>>>>>>> [ 91.163801] myhost systemd[1]: Job
>>>>>>>>> systemd-cryptsetup@luks\x2dmd0.service/start failed with result
>>>>>>>>> 'dependency'.
>>>>>>>>> [ 91.163910] myhost systemd[1]: Job dev-md0.device/start failed with
>>>>>>>>> result
>>>>>>>>> 'timeout'.
>>>>>>>>> [ 91.164021] myhost systemd[1]: Reached target System Initialization.
>>>>>>>>> [ 91.164129] myhost systemd[1]: Starting System Initialization.
>>>>>>>>> [ 91.164236] myhost systemd[1]: Reached target Basic System.
>>>>>>>>> [ 91.164346] myhost systemd[1]: Starting Basic System.
>>>>>>>>> [ 185.740238] myhost dracut-initqueue[340]: Warning: Could not boot.
>>>>>>>>> [ 185.741266] myhost systemd[1]: Received SIGRTMIN+20 from PID 341
>>>>>>>>> (plymouthd).
>>>>>>>>> [ 185.841257] myhost dracut-initqueue[340]: Warning:
>>>>>>>>> /dev/VolGroup00/root does
>>>>>>>>> not exist
>>>>>>>>> [ 185.841403] myhost systemd[1]: Starting Dracut Emergency Shell...
>>>>>>>>> [ 185.859366] myhost systemd[1]: Received SIGRTMIN+21 from PID 341
>>>>>>>>> (plymouthd).
>>>>>>>>>
>>>>>>>>> dracut:/# cat "/run/initramfs/rdsosreport.txt"
>>>>>>>>> + cat /lib/dracut/dracut-041-10.fc22.1
>>>>>>>>> dracut-041-10.fc22.1
>>>>>>>>> + cat /proc/cmdline
>>>>>>>>> BOOT_IMAGE=/vmlinuz-4.0.4-301.fc22.x86_64 root=/dev/VolGroup00/root ro
>>>>>>>>> quiet
>>>>>>>>> console=ttyS0,115200n8 rd_NO_PLYMOUTH SYSFONT=latarcyrheb-sun16
>>>>>>>>> LANG=en_US.UTF-
>>>>>>>>> 8 KEYTABLE=de-latin1
>>>>>>>> your kernel cmdline seems to be missing the raid configuration
>>>>>>>>
>>>>>>>> rd.md.uuid=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>> rd.md.uuid=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>> rd.md.uuid=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>
>>>>>>>> ... whatever is needed to boot your system.
>>>>>>>>
>>>>>>>> # dracut --print-cmdline
>>>>>>>>
>>>>>>>> should tell you what kernel cmdline parameters are needed
>>>>>>> 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
>>>>>> 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.
>>>>>>
>>>>>>> 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
>>>>
>>> Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?
>> Yes, of course. :-)
>>
>>> 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
>>
> 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
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <5565C4E7.6010301-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
@ 2015-05-27 13:27 ` Harald Hoyer
[not found] ` <5565C654.3000101-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
0 siblings, 1 reply; 19+ messages in thread
From: Harald Hoyer @ 2015-05-27 13:27 UTC (permalink / raw)
To: Gerhard Wiesinger, Andrei Borzenkov; +Cc: initramfs
Am 27.05.2015 um 15:21 schrieb Gerhard Wiesinger:
> On 27.05.2015 15:07, Harald Hoyer wrote:
>> Am 27.05.2015 um 15:03 schrieb Gerhard Wiesinger:
>>> On 27.05.2015 14:43, Harald Hoyer wrote:
>>>> Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
>>>>> On 27.05.2015 14:25, Harald Hoyer wrote:
>>>>>> Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
>>>>>>> On Wed, May 27, 2015 at 3:09 PM, Gerhard Wiesinger <lists-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
>>>>>>> wrote:
>>>>>>>> On 27.05.2015 13:56, Harald Hoyer wrote:
>>>>>>>>> Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> After upgrading one machine it does't boot anymore. Booting the old
>>>>>>>>>> kernel
>>>>>>>>>> works well.
>>>>>>>>>>
>>>>>>>>>> It is a RAID, LUKS, LVM setup. Find relevant details below.
>>>>>>>>>>
>>>>>>>>>> So it looks RAID assembling doesn't work any more.
>>>>>>>>>>
>>>>>>>>>> Any ideas?
>>>>>>>>>>
>>>>>>>>>> Thank you.
>>>>>>>>>>
>>>>>>>>>> Ciao,
>>>>>>>>>> Gerhard
>>>>>>>>>>
>>>>>>>>>> blkid
>>>>>>>>>> /dev/sda1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>> PARTUUID="5ec6792c-01"
>>>>>>>>>> /dev/sdb1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>> PARTUUID="1c7cffaf-01"
>>>>>>>>>> /dev/sdc1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>> PARTUUID="0079dfc3-01"
>>>>>>>>>> /dev/sdd1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>> PARTUUID="fadeaffe-01"
>>>>>>>>>> /dev/sde1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>> PARTUUID="539b5814-01"
>>>>>>>>>> /dev/sdf1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>> PARTUUID="badeaffe-01"
>>>>>>>>>> /dev/sdh1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>> PARTUUID="15631562-01"
>>>>>>>>>> /dev/sdg1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>> PARTUUID="162f0d0b-01"
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> blkid -o udev
>>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>> ID_FS_PARTUUID=5ec6792c-01
>>>>>>>>>>
>>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>> ID_FS_PARTUUID=1c7cffaf-01
>>>>>>>>>>
>>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>> ID_FS_PARTUUID=0079dfc3-01
>>>>>>>>>>
>>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>> ID_FS_PARTUUID=fadeaffe-01
>>>>>>>>>>
>>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>> ID_FS_PARTUUID=539b5814-01
>>>>>>>>>>
>>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>> ID_FS_PARTUUID=badeaffe-01
>>>>>>>>>>
>>>>>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>> ID_FS_PARTUUID=15631562-01
>>>>>>>>>>
>>>>>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>> ID_FS_PARTUUID=162f0d0b-01
>>>>>>>>>>
>>>>>>>>>> [ 2.479836] myhost systemd[1]: Device
>>>>>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0.device appeared
>>>>>>>>>> twice
>>>>>>>>>> with different sysfs paths /sys
>>>>>>>>>>
>>>>>>>>>> /devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.0/host8/target
>>>>>>>>>> 8:0:0/8:0:0:0/block/sdg
>>>>>>>>>> [ 2.500826] myhost systemd[1]: Device
>>>>>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0\x2dpart1.device
>>>>>>>>>> appeared twice with different sysfs p
>>>>>>>>>> aths
>>>>>>>>>>
>>>>>>>>>> /sys/devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.
>>>>>>>>>> 0/host8/target8:0:0/8:0:0:0/block/sdg/sdg1
>>>>>>>>>> [ 2.632754] myhost kernel: Switched to clocksource tsc
>>>>>>>>>> [ 91.162986] myhost systemd[1]: Job dev-md0.device/start timed out.
>>>>>>>>>> [ 91.163138] myhost systemd[1]: Timed out waiting for device
>>>>>>>>>> dev-md0.device.
>>>>>>>>>> [ 91.163251] myhost systemd[1]: Dependency failed for Cryptography
>>>>>>>>>> Setup for
>>>>>>>>>> luks-md0.
>>>>>>>>>> [ 91.163360] myhost systemd[1]: Dependency failed for
>>>>>>>>>> dev-mapper-luks\x2dmd0.device.
>>>>>>>>>> [ 91.163474] myhost systemd[1]: Job
>>>>>>>>>> dev-mapper-luks\x2dmd0.device/start
>>>>>>>>>> failed with result 'dependency'.
>>>>>>>>>> [ 91.163586] myhost systemd[1]: Dependency failed for Encrypted
>>>>>>>>>> Volumes.
>>>>>>>>>> [ 91.163694] myhost systemd[1]: Job cryptsetup.target/start failed
>>>>>>>>>> with
>>>>>>>>>> result 'dependency'.
>>>>>>>>>> [ 91.163801] myhost systemd[1]: Job
>>>>>>>>>> systemd-cryptsetup@luks\x2dmd0.service/start failed with result
>>>>>>>>>> 'dependency'.
>>>>>>>>>> [ 91.163910] myhost systemd[1]: Job dev-md0.device/start failed with
>>>>>>>>>> result
>>>>>>>>>> 'timeout'.
>>>>>>>>>> [ 91.164021] myhost systemd[1]: Reached target System Initialization.
>>>>>>>>>> [ 91.164129] myhost systemd[1]: Starting System Initialization.
>>>>>>>>>> [ 91.164236] myhost systemd[1]: Reached target Basic System.
>>>>>>>>>> [ 91.164346] myhost systemd[1]: Starting Basic System.
>>>>>>>>>> [ 185.740238] myhost dracut-initqueue[340]: Warning: Could not boot.
>>>>>>>>>> [ 185.741266] myhost systemd[1]: Received SIGRTMIN+20 from PID 341
>>>>>>>>>> (plymouthd).
>>>>>>>>>> [ 185.841257] myhost dracut-initqueue[340]: Warning:
>>>>>>>>>> /dev/VolGroup00/root does
>>>>>>>>>> not exist
>>>>>>>>>> [ 185.841403] myhost systemd[1]: Starting Dracut Emergency Shell...
>>>>>>>>>> [ 185.859366] myhost systemd[1]: Received SIGRTMIN+21 from PID 341
>>>>>>>>>> (plymouthd).
>>>>>>>>>>
>>>>>>>>>> dracut:/# cat "/run/initramfs/rdsosreport.txt"
>>>>>>>>>> + cat /lib/dracut/dracut-041-10.fc22.1
>>>>>>>>>> dracut-041-10.fc22.1
>>>>>>>>>> + cat /proc/cmdline
>>>>>>>>>> BOOT_IMAGE=/vmlinuz-4.0.4-301.fc22.x86_64 root=/dev/VolGroup00/root ro
>>>>>>>>>> quiet
>>>>>>>>>> console=ttyS0,115200n8 rd_NO_PLYMOUTH SYSFONT=latarcyrheb-sun16
>>>>>>>>>> LANG=en_US.UTF-
>>>>>>>>>> 8 KEYTABLE=de-latin1
>>>>>>>>> your kernel cmdline seems to be missing the raid configuration
>>>>>>>>>
>>>>>>>>> rd.md.uuid=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>> rd.md.uuid=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>> rd.md.uuid=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>
>>>>>>>>> ... whatever is needed to boot your system.
>>>>>>>>>
>>>>>>>>> # dracut --print-cmdline
>>>>>>>>>
>>>>>>>>> should tell you what kernel cmdline parameters are needed
>>>>>>>> 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
>>>>>>> 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.
>>>>>>>
>>>>>>>> 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
>>>>>
>>>> Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?
>>> Yes, of course. :-)
>>>
>>>> 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
>>>
>> 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
>
Does "dracut -f" help to get the update crypttab in the initramfs?
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <5565C654.3000101-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
@ 2015-05-27 13:33 ` Gerhard Wiesinger
[not found] ` <5565C7AF.70009-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
2015-05-28 12:19 ` Gerhard Wiesinger
1 sibling, 1 reply; 19+ messages in thread
From: Gerhard Wiesinger @ 2015-05-27 13:33 UTC (permalink / raw)
To: Harald Hoyer, Andrei Borzenkov; +Cc: initramfs
On 27.05.2015 15:27, Harald Hoyer wrote:
> Am 27.05.2015 um 15:21 schrieb Gerhard Wiesinger:
>> On 27.05.2015 15:07, Harald Hoyer wrote:
>>> Am 27.05.2015 um 15:03 schrieb Gerhard Wiesinger:
>>>> On 27.05.2015 14:43, Harald Hoyer wrote:
>>>>> Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
>>>>>> On 27.05.2015 14:25, Harald Hoyer wrote:
>>>>>>> Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
>>>>>>>> On Wed, May 27, 2015 at 3:09 PM, Gerhard Wiesinger <lists-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
>>>>>>>> wrote:
>>>>>>>>> On 27.05.2015 13:56, Harald Hoyer wrote:
>>>>>>>>>> Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
>>>>>>>>>>> Hello,
>>>>>>>>>>>
>>>>>>>>>>> After upgrading one machine it does't boot anymore. Booting the old
>>>>>>>>>>> kernel
>>>>>>>>>>> works well.
>>>>>>>>>>>
>>>>>>>>>>> It is a RAID, LUKS, LVM setup. Find relevant details below.
>>>>>>>>>>>
>>>>>>>>>>> So it looks RAID assembling doesn't work any more.
>>>>>>>>>>>
>>>>>>>>>>> Any ideas?
>>>>>>>>>>>
>>>>>>>>>>> Thank you.
>>>>>>>>>>>
>>>>>>>>>>> Ciao,
>>>>>>>>>>> Gerhard
>>>>>>>>>>>
>>>>>>>>>>> blkid
>>>>>>>>>>> /dev/sda1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>> PARTUUID="5ec6792c-01"
>>>>>>>>>>> /dev/sdb1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>> PARTUUID="1c7cffaf-01"
>>>>>>>>>>> /dev/sdc1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>> PARTUUID="0079dfc3-01"
>>>>>>>>>>> /dev/sdd1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>> PARTUUID="fadeaffe-01"
>>>>>>>>>>> /dev/sde1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>> PARTUUID="539b5814-01"
>>>>>>>>>>> /dev/sdf1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>> PARTUUID="badeaffe-01"
>>>>>>>>>>> /dev/sdh1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>> PARTUUID="15631562-01"
>>>>>>>>>>> /dev/sdg1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>> PARTUUID="162f0d0b-01"
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> blkid -o udev
>>>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>> ID_FS_PARTUUID=5ec6792c-01
>>>>>>>>>>>
>>>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>> ID_FS_PARTUUID=1c7cffaf-01
>>>>>>>>>>>
>>>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>> ID_FS_PARTUUID=0079dfc3-01
>>>>>>>>>>>
>>>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>> ID_FS_PARTUUID=fadeaffe-01
>>>>>>>>>>>
>>>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>> ID_FS_PARTUUID=539b5814-01
>>>>>>>>>>>
>>>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>> ID_FS_PARTUUID=badeaffe-01
>>>>>>>>>>>
>>>>>>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>> ID_FS_PARTUUID=15631562-01
>>>>>>>>>>>
>>>>>>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>> ID_FS_PARTUUID=162f0d0b-01
>>>>>>>>>>>
>>>>>>>>>>> [ 2.479836] myhost systemd[1]: Device
>>>>>>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0.device appeared
>>>>>>>>>>> twice
>>>>>>>>>>> with different sysfs paths /sys
>>>>>>>>>>>
>>>>>>>>>>> /devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.0/host8/target
>>>>>>>>>>> 8:0:0/8:0:0:0/block/sdg
>>>>>>>>>>> [ 2.500826] myhost systemd[1]: Device
>>>>>>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0\x2dpart1.device
>>>>>>>>>>> appeared twice with different sysfs p
>>>>>>>>>>> aths
>>>>>>>>>>>
>>>>>>>>>>> /sys/devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.
>>>>>>>>>>> 0/host8/target8:0:0/8:0:0:0/block/sdg/sdg1
>>>>>>>>>>> [ 2.632754] myhost kernel: Switched to clocksource tsc
>>>>>>>>>>> [ 91.162986] myhost systemd[1]: Job dev-md0.device/start timed out.
>>>>>>>>>>> [ 91.163138] myhost systemd[1]: Timed out waiting for device
>>>>>>>>>>> dev-md0.device.
>>>>>>>>>>> [ 91.163251] myhost systemd[1]: Dependency failed for Cryptography
>>>>>>>>>>> Setup for
>>>>>>>>>>> luks-md0.
>>>>>>>>>>> [ 91.163360] myhost systemd[1]: Dependency failed for
>>>>>>>>>>> dev-mapper-luks\x2dmd0.device.
>>>>>>>>>>> [ 91.163474] myhost systemd[1]: Job
>>>>>>>>>>> dev-mapper-luks\x2dmd0.device/start
>>>>>>>>>>> failed with result 'dependency'.
>>>>>>>>>>> [ 91.163586] myhost systemd[1]: Dependency failed for Encrypted
>>>>>>>>>>> Volumes.
>>>>>>>>>>> [ 91.163694] myhost systemd[1]: Job cryptsetup.target/start failed
>>>>>>>>>>> with
>>>>>>>>>>> result 'dependency'.
>>>>>>>>>>> [ 91.163801] myhost systemd[1]: Job
>>>>>>>>>>> systemd-cryptsetup@luks\x2dmd0.service/start failed with result
>>>>>>>>>>> 'dependency'.
>>>>>>>>>>> [ 91.163910] myhost systemd[1]: Job dev-md0.device/start failed with
>>>>>>>>>>> result
>>>>>>>>>>> 'timeout'.
>>>>>>>>>>> [ 91.164021] myhost systemd[1]: Reached target System Initialization.
>>>>>>>>>>> [ 91.164129] myhost systemd[1]: Starting System Initialization.
>>>>>>>>>>> [ 91.164236] myhost systemd[1]: Reached target Basic System.
>>>>>>>>>>> [ 91.164346] myhost systemd[1]: Starting Basic System.
>>>>>>>>>>> [ 185.740238] myhost dracut-initqueue[340]: Warning: Could not boot.
>>>>>>>>>>> [ 185.741266] myhost systemd[1]: Received SIGRTMIN+20 from PID 341
>>>>>>>>>>> (plymouthd).
>>>>>>>>>>> [ 185.841257] myhost dracut-initqueue[340]: Warning:
>>>>>>>>>>> /dev/VolGroup00/root does
>>>>>>>>>>> not exist
>>>>>>>>>>> [ 185.841403] myhost systemd[1]: Starting Dracut Emergency Shell...
>>>>>>>>>>> [ 185.859366] myhost systemd[1]: Received SIGRTMIN+21 from PID 341
>>>>>>>>>>> (plymouthd).
>>>>>>>>>>>
>>>>>>>>>>> dracut:/# cat "/run/initramfs/rdsosreport.txt"
>>>>>>>>>>> + cat /lib/dracut/dracut-041-10.fc22.1
>>>>>>>>>>> dracut-041-10.fc22.1
>>>>>>>>>>> + cat /proc/cmdline
>>>>>>>>>>> BOOT_IMAGE=/vmlinuz-4.0.4-301.fc22.x86_64 root=/dev/VolGroup00/root ro
>>>>>>>>>>> quiet
>>>>>>>>>>> console=ttyS0,115200n8 rd_NO_PLYMOUTH SYSFONT=latarcyrheb-sun16
>>>>>>>>>>> LANG=en_US.UTF-
>>>>>>>>>>> 8 KEYTABLE=de-latin1
>>>>>>>>>> your kernel cmdline seems to be missing the raid configuration
>>>>>>>>>>
>>>>>>>>>> rd.md.uuid=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>> rd.md.uuid=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>> rd.md.uuid=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>
>>>>>>>>>> ... whatever is needed to boot your system.
>>>>>>>>>>
>>>>>>>>>> # dracut --print-cmdline
>>>>>>>>>>
>>>>>>>>>> should tell you what kernel cmdline parameters are needed
>>>>>>>>> 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
>>>>>>>> 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.
>>>>>>>>
>>>>>>>>> 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
>>>>>>
>>>>> Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?
>>>> Yes, of course. :-)
>>>>
>>>>> 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
>>>>
>>> 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
>>
> Does "dracut -f" help to get the update crypttab in the initramfs?
>
No, still the same.
Ciao,
Gerhard
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <5565C7AF.70009-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
@ 2015-05-27 17:21 ` Andrew Udvare
0 siblings, 0 replies; 19+ messages in thread
From: Andrew Udvare @ 2015-05-27 17:21 UTC (permalink / raw)
To: Gerhard Wiesinger; +Cc: Harald Hoyer, Andrei Borzenkov, initramfs
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.old 2015-01-31 03:54:52.000000000 -0800
+++ module-setup.sh 2015-04-15 02:28:08.381183319 -0700
@@ -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.
On 27 May 2015 at 06:33, Gerhard Wiesinger <lists-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org> wrote:
> On 27.05.2015 15:27, Harald Hoyer wrote:
>>
>> Am 27.05.2015 um 15:21 schrieb Gerhard Wiesinger:
>>>
>>> On 27.05.2015 15:07, Harald Hoyer wrote:
>>>>
>>>> Am 27.05.2015 um 15:03 schrieb Gerhard Wiesinger:
>>>>>
>>>>> On 27.05.2015 14:43, Harald Hoyer wrote:
>>>>>>
>>>>>> Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
>>>>>>>
>>>>>>> On 27.05.2015 14:25, Harald Hoyer wrote:
>>>>>>>>
>>>>>>>> Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
>>>>>>>>>
>>>>>>>>> On Wed, May 27, 2015 at 3:09 PM, Gerhard Wiesinger
>>>>>>>>> <lists-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> On 27.05.2015 13:56, Harald Hoyer wrote:
>>>>>>>>>>>
>>>>>>>>>>> Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
>>>>>>>>>>>>
>>>>>>>>>>>> Hello,
>>>>>>>>>>>>
>>>>>>>>>>>> After upgrading one machine it does't boot anymore. Booting the
>>>>>>>>>>>> old
>>>>>>>>>>>> kernel
>>>>>>>>>>>> works well.
>>>>>>>>>>>>
>>>>>>>>>>>> It is a RAID, LUKS, LVM setup. Find relevant details below.
>>>>>>>>>>>>
>>>>>>>>>>>> So it looks RAID assembling doesn't work any more.
>>>>>>>>>>>>
>>>>>>>>>>>> Any ideas?
>>>>>>>>>>>>
>>>>>>>>>>>> Thank you.
>>>>>>>>>>>>
>>>>>>>>>>>> Ciao,
>>>>>>>>>>>> Gerhard
>>>>>>>>>>>>
>>>>>>>>>>>> blkid
>>>>>>>>>>>> /dev/sda1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>>> PARTUUID="5ec6792c-01"
>>>>>>>>>>>> /dev/sdb1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>>> PARTUUID="1c7cffaf-01"
>>>>>>>>>>>> /dev/sdc1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>>> PARTUUID="0079dfc3-01"
>>>>>>>>>>>> /dev/sdd1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>>> PARTUUID="fadeaffe-01"
>>>>>>>>>>>> /dev/sde1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>>> PARTUUID="539b5814-01"
>>>>>>>>>>>> /dev/sdf1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>>> PARTUUID="badeaffe-01"
>>>>>>>>>>>> /dev/sdh1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>>> PARTUUID="15631562-01"
>>>>>>>>>>>> /dev/sdg1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>>> PARTUUID="162f0d0b-01"
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> blkid -o udev
>>>>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>>> ID_FS_PARTUUID=5ec6792c-01
>>>>>>>>>>>>
>>>>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>>> ID_FS_PARTUUID=1c7cffaf-01
>>>>>>>>>>>>
>>>>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>>> ID_FS_PARTUUID=0079dfc3-01
>>>>>>>>>>>>
>>>>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>>> ID_FS_PARTUUID=fadeaffe-01
>>>>>>>>>>>>
>>>>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>>> ID_FS_PARTUUID=539b5814-01
>>>>>>>>>>>>
>>>>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>>> ID_FS_PARTUUID=badeaffe-01
>>>>>>>>>>>>
>>>>>>>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>>> ID_FS_PARTUUID=15631562-01
>>>>>>>>>>>>
>>>>>>>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>>> ID_FS_PARTUUID=162f0d0b-01
>>>>>>>>>>>>
>>>>>>>>>>>> [ 2.479836] myhost systemd[1]: Device
>>>>>>>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0.device
>>>>>>>>>>>> appeared
>>>>>>>>>>>> twice
>>>>>>>>>>>> with different sysfs paths /sys
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> /devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> and
>>>>>>>>>>>> /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.0/host8/target
>>>>>>>>>>>> 8:0:0/8:0:0:0/block/sdg
>>>>>>>>>>>> [ 2.500826] myhost systemd[1]: Device
>>>>>>>>>>>>
>>>>>>>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0\x2dpart1.device
>>>>>>>>>>>> appeared twice with different sysfs p
>>>>>>>>>>>> aths
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> /sys/devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.
>>>>>>>>>>>> 0/host8/target8:0:0/8:0:0:0/block/sdg/sdg1
>>>>>>>>>>>> [ 2.632754] myhost kernel: Switched to clocksource tsc
>>>>>>>>>>>> [ 91.162986] myhost systemd[1]: Job dev-md0.device/start timed
>>>>>>>>>>>> out.
>>>>>>>>>>>> [ 91.163138] myhost systemd[1]: Timed out waiting for device
>>>>>>>>>>>> dev-md0.device.
>>>>>>>>>>>> [ 91.163251] myhost systemd[1]: Dependency failed for
>>>>>>>>>>>> Cryptography
>>>>>>>>>>>> Setup for
>>>>>>>>>>>> luks-md0.
>>>>>>>>>>>> [ 91.163360] myhost systemd[1]: Dependency failed for
>>>>>>>>>>>> dev-mapper-luks\x2dmd0.device.
>>>>>>>>>>>> [ 91.163474] myhost systemd[1]: Job
>>>>>>>>>>>> dev-mapper-luks\x2dmd0.device/start
>>>>>>>>>>>> failed with result 'dependency'.
>>>>>>>>>>>> [ 91.163586] myhost systemd[1]: Dependency failed for
>>>>>>>>>>>> Encrypted
>>>>>>>>>>>> Volumes.
>>>>>>>>>>>> [ 91.163694] myhost systemd[1]: Job cryptsetup.target/start
>>>>>>>>>>>> failed
>>>>>>>>>>>> with
>>>>>>>>>>>> result 'dependency'.
>>>>>>>>>>>> [ 91.163801] myhost systemd[1]: Job
>>>>>>>>>>>> systemd-cryptsetup@luks\x2dmd0.service/start failed with result
>>>>>>>>>>>> 'dependency'.
>>>>>>>>>>>> [ 91.163910] myhost systemd[1]: Job dev-md0.device/start
>>>>>>>>>>>> failed with
>>>>>>>>>>>> result
>>>>>>>>>>>> 'timeout'.
>>>>>>>>>>>> [ 91.164021] myhost systemd[1]: Reached target System
>>>>>>>>>>>> Initialization.
>>>>>>>>>>>> [ 91.164129] myhost systemd[1]: Starting System
>>>>>>>>>>>> Initialization.
>>>>>>>>>>>> [ 91.164236] myhost systemd[1]: Reached target Basic System.
>>>>>>>>>>>> [ 91.164346] myhost systemd[1]: Starting Basic System.
>>>>>>>>>>>> [ 185.740238] myhost dracut-initqueue[340]: Warning: Could not
>>>>>>>>>>>> boot.
>>>>>>>>>>>> [ 185.741266] myhost systemd[1]: Received SIGRTMIN+20 from PID
>>>>>>>>>>>> 341
>>>>>>>>>>>> (plymouthd).
>>>>>>>>>>>> [ 185.841257] myhost dracut-initqueue[340]: Warning:
>>>>>>>>>>>> /dev/VolGroup00/root does
>>>>>>>>>>>> not exist
>>>>>>>>>>>> [ 185.841403] myhost systemd[1]: Starting Dracut Emergency
>>>>>>>>>>>> Shell...
>>>>>>>>>>>> [ 185.859366] myhost systemd[1]: Received SIGRTMIN+21 from PID
>>>>>>>>>>>> 341
>>>>>>>>>>>> (plymouthd).
>>>>>>>>>>>>
>>>>>>>>>>>> dracut:/# cat "/run/initramfs/rdsosreport.txt"
>>>>>>>>>>>> + cat /lib/dracut/dracut-041-10.fc22.1
>>>>>>>>>>>> dracut-041-10.fc22.1
>>>>>>>>>>>> + cat /proc/cmdline
>>>>>>>>>>>> BOOT_IMAGE=/vmlinuz-4.0.4-301.fc22.x86_64
>>>>>>>>>>>> root=/dev/VolGroup00/root ro
>>>>>>>>>>>> quiet
>>>>>>>>>>>> console=ttyS0,115200n8 rd_NO_PLYMOUTH SYSFONT=latarcyrheb-sun16
>>>>>>>>>>>> LANG=en_US.UTF-
>>>>>>>>>>>> 8 KEYTABLE=de-latin1
>>>>>>>>>>>
>>>>>>>>>>> your kernel cmdline seems to be missing the raid configuration
>>>>>>>>>>>
>>>>>>>>>>> rd.md.uuid=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>> rd.md.uuid=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>> rd.md.uuid=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>>
>>>>>>>>>>> ... whatever is needed to boot your system.
>>>>>>>>>>>
>>>>>>>>>>> # dracut --print-cmdline
>>>>>>>>>>>
>>>>>>>>>>> should tell you what kernel cmdline parameters are needed
>>>>>>>>>>
>>>>>>>>>> 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
>>>>>>>>>
>>>>>>>>> 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.
>>>>>>>>>
>>>>>>>>>> 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
>>>>>>>
>>>>>> Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09
>>>>>> " also?
>>>>>
>>>>> Yes, of course. :-)
>>>>>
>>>>>> 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
>>>>>
>>>> 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
>>>
>> 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 majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <5565C654.3000101-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-27 13:33 ` Gerhard Wiesinger
@ 2015-05-28 12:19 ` Gerhard Wiesinger
[not found] ` <556707B5.4000707-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
1 sibling, 1 reply; 19+ messages in thread
From: Gerhard Wiesinger @ 2015-05-28 12:19 UTC (permalink / raw)
To: Harald Hoyer, Andrei Borzenkov; +Cc: initramfs
On 27.05.2015 15:27, Harald Hoyer wrote:
> Am 27.05.2015 um 15:21 schrieb Gerhard Wiesinger:
>> On 27.05.2015 15:07, Harald Hoyer wrote:
>>> Am 27.05.2015 um 15:03 schrieb Gerhard Wiesinger:
>>>> On 27.05.2015 14:43, Harald Hoyer wrote:
>>>>> Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
>>>>>> On 27.05.2015 14:25, Harald Hoyer wrote:
>>>>>>> Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
>>>>>>>> On Wed, May 27, 2015 at 3:09 PM, Gerhard Wiesinger <lists-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
>>>>>>>> wrote:
>>>>>>>>> On 27.05.2015 13:56, Harald Hoyer wrote:
>>>>>>>>>> Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
>>>>>>>>>>> Hello,
>>>>>>>>>>>
>>>>>>>>>>> After upgrading one machine it does't boot anymore. Booting the old
>>>>>>>>>>> kernel
>>>>>>>>>>> works well.
>>>>>>>>>>>
>>>>>>>>>>> It is a RAID, LUKS, LVM setup. Find relevant details below.
>>>>>>>>>>>
>>>>>>>>>>> So it looks RAID assembling doesn't work any more.
>>>>>>>>>>>
>>>>>>>>>>> Any ideas?
>>>>>>>>>>>
>>>>>>>>>>> Thank you.
>>>>>>>>>>>
>>>>>>>>>>> Ciao,
>>>>>>>>>>> Gerhard
>>>>>>>>>>>
>>>>>>>>>>> blkid
>>>>>>>>>>> /dev/sda1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>> PARTUUID="5ec6792c-01"
>>>>>>>>>>> /dev/sdb1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>> PARTUUID="1c7cffaf-01"
>>>>>>>>>>> /dev/sdc1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>> PARTUUID="0079dfc3-01"
>>>>>>>>>>> /dev/sdd1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>> PARTUUID="fadeaffe-01"
>>>>>>>>>>> /dev/sde1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>> PARTUUID="539b5814-01"
>>>>>>>>>>> /dev/sdf1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>> PARTUUID="badeaffe-01"
>>>>>>>>>>> /dev/sdh1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>> PARTUUID="15631562-01"
>>>>>>>>>>> /dev/sdg1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>> PARTUUID="162f0d0b-01"
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> blkid -o udev
>>>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>> ID_FS_PARTUUID=5ec6792c-01
>>>>>>>>>>>
>>>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>> ID_FS_PARTUUID=1c7cffaf-01
>>>>>>>>>>>
>>>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>> ID_FS_PARTUUID=0079dfc3-01
>>>>>>>>>>>
>>>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>> ID_FS_PARTUUID=fadeaffe-01
>>>>>>>>>>>
>>>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>> ID_FS_PARTUUID=539b5814-01
>>>>>>>>>>>
>>>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>> ID_FS_PARTUUID=badeaffe-01
>>>>>>>>>>>
>>>>>>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>> ID_FS_PARTUUID=15631562-01
>>>>>>>>>>>
>>>>>>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>> ID_FS_PARTUUID=162f0d0b-01
>>>>>>>>>>>
>>>>>>>>>>> [ 2.479836] myhost systemd[1]: Device
>>>>>>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0.device appeared
>>>>>>>>>>> twice
>>>>>>>>>>> with different sysfs paths /sys
>>>>>>>>>>>
>>>>>>>>>>> /devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.0/host8/target
>>>>>>>>>>> 8:0:0/8:0:0:0/block/sdg
>>>>>>>>>>> [ 2.500826] myhost systemd[1]: Device
>>>>>>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0\x2dpart1.device
>>>>>>>>>>> appeared twice with different sysfs p
>>>>>>>>>>> aths
>>>>>>>>>>>
>>>>>>>>>>> /sys/devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.
>>>>>>>>>>> 0/host8/target8:0:0/8:0:0:0/block/sdg/sdg1
>>>>>>>>>>> [ 2.632754] myhost kernel: Switched to clocksource tsc
>>>>>>>>>>> [ 91.162986] myhost systemd[1]: Job dev-md0.device/start timed out.
>>>>>>>>>>> [ 91.163138] myhost systemd[1]: Timed out waiting for device
>>>>>>>>>>> dev-md0.device.
>>>>>>>>>>> [ 91.163251] myhost systemd[1]: Dependency failed for Cryptography
>>>>>>>>>>> Setup for
>>>>>>>>>>> luks-md0.
>>>>>>>>>>> [ 91.163360] myhost systemd[1]: Dependency failed for
>>>>>>>>>>> dev-mapper-luks\x2dmd0.device.
>>>>>>>>>>> [ 91.163474] myhost systemd[1]: Job
>>>>>>>>>>> dev-mapper-luks\x2dmd0.device/start
>>>>>>>>>>> failed with result 'dependency'.
>>>>>>>>>>> [ 91.163586] myhost systemd[1]: Dependency failed for Encrypted
>>>>>>>>>>> Volumes.
>>>>>>>>>>> [ 91.163694] myhost systemd[1]: Job cryptsetup.target/start failed
>>>>>>>>>>> with
>>>>>>>>>>> result 'dependency'.
>>>>>>>>>>> [ 91.163801] myhost systemd[1]: Job
>>>>>>>>>>> systemd-cryptsetup@luks\x2dmd0.service/start failed with result
>>>>>>>>>>> 'dependency'.
>>>>>>>>>>> [ 91.163910] myhost systemd[1]: Job dev-md0.device/start failed with
>>>>>>>>>>> result
>>>>>>>>>>> 'timeout'.
>>>>>>>>>>> [ 91.164021] myhost systemd[1]: Reached target System Initialization.
>>>>>>>>>>> [ 91.164129] myhost systemd[1]: Starting System Initialization.
>>>>>>>>>>> [ 91.164236] myhost systemd[1]: Reached target Basic System.
>>>>>>>>>>> [ 91.164346] myhost systemd[1]: Starting Basic System.
>>>>>>>>>>> [ 185.740238] myhost dracut-initqueue[340]: Warning: Could not boot.
>>>>>>>>>>> [ 185.741266] myhost systemd[1]: Received SIGRTMIN+20 from PID 341
>>>>>>>>>>> (plymouthd).
>>>>>>>>>>> [ 185.841257] myhost dracut-initqueue[340]: Warning:
>>>>>>>>>>> /dev/VolGroup00/root does
>>>>>>>>>>> not exist
>>>>>>>>>>> [ 185.841403] myhost systemd[1]: Starting Dracut Emergency Shell...
>>>>>>>>>>> [ 185.859366] myhost systemd[1]: Received SIGRTMIN+21 from PID 341
>>>>>>>>>>> (plymouthd).
>>>>>>>>>>>
>>>>>>>>>>> dracut:/# cat "/run/initramfs/rdsosreport.txt"
>>>>>>>>>>> + cat /lib/dracut/dracut-041-10.fc22.1
>>>>>>>>>>> dracut-041-10.fc22.1
>>>>>>>>>>> + cat /proc/cmdline
>>>>>>>>>>> BOOT_IMAGE=/vmlinuz-4.0.4-301.fc22.x86_64 root=/dev/VolGroup00/root ro
>>>>>>>>>>> quiet
>>>>>>>>>>> console=ttyS0,115200n8 rd_NO_PLYMOUTH SYSFONT=latarcyrheb-sun16
>>>>>>>>>>> LANG=en_US.UTF-
>>>>>>>>>>> 8 KEYTABLE=de-latin1
>>>>>>>>>> your kernel cmdline seems to be missing the raid configuration
>>>>>>>>>>
>>>>>>>>>> rd.md.uuid=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>> rd.md.uuid=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>> rd.md.uuid=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>
>>>>>>>>>> ... whatever is needed to boot your system.
>>>>>>>>>>
>>>>>>>>>> # dracut --print-cmdline
>>>>>>>>>>
>>>>>>>>>> should tell you what kernel cmdline parameters are needed
>>>>>>>>> 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
>>>>>>>> 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.
>>>>>>>>
>>>>>>>>> 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
>>>>>>
>>>>> Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?
>>>> Yes, of course. :-)
>>>>
>>>>> 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
>>>>
>>> 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
>>
> 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/
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <556707B5.4000707-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
@ 2015-05-31 7:51 ` poma
2015-05-31 18:08 ` Bruno Wolff III
0 siblings, 1 reply; 19+ messages in thread
From: poma @ 2015-05-31 7:51 UTC (permalink / raw)
To: Gerhard Wiesinger, Harald Hoyer, Andrei Borzenkov
Cc: initramfs, For testing and quality assurance of Fedora releases
On 28.05.2015 14:19, Gerhard Wiesinger wrote:
> On 27.05.2015 15:27, Harald Hoyer wrote:
>> Am 27.05.2015 um 15:21 schrieb Gerhard Wiesinger:
>>> On 27.05.2015 15:07, Harald Hoyer wrote:
>>>> Am 27.05.2015 um 15:03 schrieb Gerhard Wiesinger:
>>>>> On 27.05.2015 14:43, Harald Hoyer wrote:
>>>>>> Am 27.05.2015 um 14:39 schrieb Gerhard Wiesinger:
>>>>>>> On 27.05.2015 14:25, Harald Hoyer wrote:
>>>>>>>> Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
>>>>>>>>> On Wed, May 27, 2015 at 3:09 PM, Gerhard Wiesinger <lists-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
>>>>>>>>> wrote:
>>>>>>>>>> On 27.05.2015 13:56, Harald Hoyer wrote:
>>>>>>>>>>> Am 27.05.2015 um 13:28 schrieb Gerhard Wiesinger:
>>>>>>>>>>>> Hello,
>>>>>>>>>>>>
>>>>>>>>>>>> After upgrading one machine it does't boot anymore. Booting the old
>>>>>>>>>>>> kernel
>>>>>>>>>>>> works well.
>>>>>>>>>>>>
>>>>>>>>>>>> It is a RAID, LUKS, LVM setup. Find relevant details below.
>>>>>>>>>>>>
>>>>>>>>>>>> So it looks RAID assembling doesn't work any more.
>>>>>>>>>>>>
>>>>>>>>>>>> Any ideas?
>>>>>>>>>>>>
>>>>>>>>>>>> Thank you.
>>>>>>>>>>>>
>>>>>>>>>>>> Ciao,
>>>>>>>>>>>> Gerhard
>>>>>>>>>>>>
>>>>>>>>>>>> blkid
>>>>>>>>>>>> /dev/sda1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>>> PARTUUID="5ec6792c-01"
>>>>>>>>>>>> /dev/sdb1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>>> PARTUUID="1c7cffaf-01"
>>>>>>>>>>>> /dev/sdc1: UUID="56e9bde4-5cd1-630d-188c-22a54c1c8c37"
>>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>>> PARTUUID="0079dfc3-01"
>>>>>>>>>>>> /dev/sdd1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>>> PARTUUID="fadeaffe-01"
>>>>>>>>>>>> /dev/sde1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>>> PARTUUID="539b5814-01"
>>>>>>>>>>>> /dev/sdf1: UUID="eb295015-e20b-e133-15db-5c9130487300"
>>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>>> PARTUUID="badeaffe-01"
>>>>>>>>>>>> /dev/sdh1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>>> PARTUUID="15631562-01"
>>>>>>>>>>>> /dev/sdg1: UUID="51e8e983-8786-b868-dbc3-87357e1a9534"
>>>>>>>>>>>> TYPE="linux_raid_member"
>>>>>>>>>>>> PARTUUID="162f0d0b-01"
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> blkid -o udev
>>>>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>>> ID_FS_PARTUUID=5ec6792c-01
>>>>>>>>>>>>
>>>>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>>> ID_FS_PARTUUID=1c7cffaf-01
>>>>>>>>>>>>
>>>>>>>>>>>> ID_FS_UUID=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>>> ID_FS_UUID_ENC=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>>> ID_FS_PARTUUID=0079dfc3-01
>>>>>>>>>>>>
>>>>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>>> ID_FS_PARTUUID=fadeaffe-01
>>>>>>>>>>>>
>>>>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>>> ID_FS_PARTUUID=539b5814-01
>>>>>>>>>>>>
>>>>>>>>>>>> ID_FS_UUID=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>>> ID_FS_UUID_ENC=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>>> ID_FS_PARTUUID=badeaffe-01
>>>>>>>>>>>>
>>>>>>>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>>> ID_FS_PARTUUID=15631562-01
>>>>>>>>>>>>
>>>>>>>>>>>> ID_FS_UUID=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>>> ID_FS_UUID_ENC=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>>> ID_FS_TYPE=linux_raid_member
>>>>>>>>>>>> ID_FS_PARTUUID=162f0d0b-01
>>>>>>>>>>>>
>>>>>>>>>>>> [ 2.479836] myhost systemd[1]: Device
>>>>>>>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0.device appeared
>>>>>>>>>>>> twice
>>>>>>>>>>>> with different sysfs paths /sys
>>>>>>>>>>>>
>>>>>>>>>>>> /devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.0/host8/target
>>>>>>>>>>>> 8:0:0/8:0:0:0/block/sdg
>>>>>>>>>>>> [ 2.500826] myhost systemd[1]: Device
>>>>>>>>>>>> dev-disk-by\x2did-usb\x2dUSBDisk_RunDisk_ABCDEFGH\x2d0:0\x2dpart1.device
>>>>>>>>>>>> appeared twice with different sysfs p
>>>>>>>>>>>> aths
>>>>>>>>>>>>
>>>>>>>>>>>> /sys/devices/pci0000:00/0000:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> and /sys/devices/pci0000:00/0000:00:02.1/usb1/1-5/1-5:1.
>>>>>>>>>>>> 0/host8/target8:0:0/8:0:0:0/block/sdg/sdg1
>>>>>>>>>>>> [ 2.632754] myhost kernel: Switched to clocksource tsc
>>>>>>>>>>>> [ 91.162986] myhost systemd[1]: Job dev-md0.device/start timed out.
>>>>>>>>>>>> [ 91.163138] myhost systemd[1]: Timed out waiting for device
>>>>>>>>>>>> dev-md0.device.
>>>>>>>>>>>> [ 91.163251] myhost systemd[1]: Dependency failed for Cryptography
>>>>>>>>>>>> Setup for
>>>>>>>>>>>> luks-md0.
>>>>>>>>>>>> [ 91.163360] myhost systemd[1]: Dependency failed for
>>>>>>>>>>>> dev-mapper-luks\x2dmd0.device.
>>>>>>>>>>>> [ 91.163474] myhost systemd[1]: Job
>>>>>>>>>>>> dev-mapper-luks\x2dmd0.device/start
>>>>>>>>>>>> failed with result 'dependency'.
>>>>>>>>>>>> [ 91.163586] myhost systemd[1]: Dependency failed for Encrypted
>>>>>>>>>>>> Volumes.
>>>>>>>>>>>> [ 91.163694] myhost systemd[1]: Job cryptsetup.target/start failed
>>>>>>>>>>>> with
>>>>>>>>>>>> result 'dependency'.
>>>>>>>>>>>> [ 91.163801] myhost systemd[1]: Job
>>>>>>>>>>>> systemd-cryptsetup@luks\x2dmd0.service/start failed with result
>>>>>>>>>>>> 'dependency'.
>>>>>>>>>>>> [ 91.163910] myhost systemd[1]: Job dev-md0.device/start failed with
>>>>>>>>>>>> result
>>>>>>>>>>>> 'timeout'.
>>>>>>>>>>>> [ 91.164021] myhost systemd[1]: Reached target System Initialization.
>>>>>>>>>>>> [ 91.164129] myhost systemd[1]: Starting System Initialization.
>>>>>>>>>>>> [ 91.164236] myhost systemd[1]: Reached target Basic System.
>>>>>>>>>>>> [ 91.164346] myhost systemd[1]: Starting Basic System.
>>>>>>>>>>>> [ 185.740238] myhost dracut-initqueue[340]: Warning: Could not boot.
>>>>>>>>>>>> [ 185.741266] myhost systemd[1]: Received SIGRTMIN+20 from PID 341
>>>>>>>>>>>> (plymouthd).
>>>>>>>>>>>> [ 185.841257] myhost dracut-initqueue[340]: Warning:
>>>>>>>>>>>> /dev/VolGroup00/root does
>>>>>>>>>>>> not exist
>>>>>>>>>>>> [ 185.841403] myhost systemd[1]: Starting Dracut Emergency Shell...
>>>>>>>>>>>> [ 185.859366] myhost systemd[1]: Received SIGRTMIN+21 from PID 341
>>>>>>>>>>>> (plymouthd).
>>>>>>>>>>>>
>>>>>>>>>>>> dracut:/# cat "/run/initramfs/rdsosreport.txt"
>>>>>>>>>>>> + cat /lib/dracut/dracut-041-10.fc22.1
>>>>>>>>>>>> dracut-041-10.fc22.1
>>>>>>>>>>>> + cat /proc/cmdline
>>>>>>>>>>>> BOOT_IMAGE=/vmlinuz-4.0.4-301.fc22.x86_64 root=/dev/VolGroup00/root ro
>>>>>>>>>>>> quiet
>>>>>>>>>>>> console=ttyS0,115200n8 rd_NO_PLYMOUTH SYSFONT=latarcyrheb-sun16
>>>>>>>>>>>> LANG=en_US.UTF-
>>>>>>>>>>>> 8 KEYTABLE=de-latin1
>>>>>>>>>>> your kernel cmdline seems to be missing the raid configuration
>>>>>>>>>>>
>>>>>>>>>>> rd.md.uuid=56e9bde4-5cd1-630d-188c-22a54c1c8c37
>>>>>>>>>>> rd.md.uuid=eb295015-e20b-e133-15db-5c9130487300
>>>>>>>>>>> rd.md.uuid=51e8e983-8786-b868-dbc3-87357e1a9534
>>>>>>>>>>>
>>>>>>>>>>> ... whatever is needed to boot your system.
>>>>>>>>>>>
>>>>>>>>>>> # dracut --print-cmdline
>>>>>>>>>>>
>>>>>>>>>>> should tell you what kernel cmdline parameters are needed
>>>>>>>>>> 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
>>>>>>>>> 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.
>>>>>>>>>
>>>>>>>>>> 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
>>>>>>>
>>>>>> Did you add " rd.luks.uuid=luks-0c66fc77-a8a0-49e6-b96c-55e886a91f09 " also?
>>>>> Yes, of course. :-)
>>>>>
>>>>>> 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
>>>>>
>>>> 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
>>>
>> Does "dracut -f" help to get the update crypttab in the initramfs?
>>
>>
>
> 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.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
2015-05-31 7:51 ` poma
@ 2015-05-31 18:08 ` Bruno Wolff III
[not found] ` <20150531180858.GA27097-bdMChIhFSYk@public.gmane.org>
0 siblings, 1 reply; 19+ messages in thread
From: Bruno Wolff III @ 2015-05-31 18:08 UTC (permalink / raw)
To: poma
Cc: Gerhard Wiesinger, Andrei Borzenkov, initramfs, Harald Hoyer,
For testing and quality assurance of Fedora releases
>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.
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <20150531180858.GA27097-bdMChIhFSYk@public.gmane.org>
@ 2015-06-11 9:06 ` poma
[not found] ` <55794FA1.3070107-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
0 siblings, 1 reply; 19+ messages in thread
From: poma @ 2015-06-11 9:06 UTC (permalink / raw)
To: Bruno Wolff III
Cc: Gerhard Wiesinger, Harald Hoyer, Andrei Borzenkov, initramfs,
For testing and quality assurance of Fedora releases
On 31.05.2015 20:08, Bruno Wolff III wrote:
>> 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.
>
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
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <55794FA1.3070107-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
@ 2015-06-15 9:42 ` Harald Hoyer
[not found] ` <557E9DF5.2070809-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
0 siblings, 1 reply; 19+ messages in thread
From: Harald Hoyer @ 2015-06-15 9:42 UTC (permalink / raw)
To: poma, Bruno Wolff III
Cc: Gerhard Wiesinger, Andrei Borzenkov, initramfs,
For testing and quality assurance of Fedora releases
On 11.06.2015 11:06, poma wrote:
> On 31.05.2015 20:08, Bruno Wolff III wrote:
>>> 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.
>>
>
>
> 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.
^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: Update FC22 - doesn't find root fs and doesn't boot
[not found] ` <557E9DF5.2070809-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
@ 2015-06-15 10:37 ` poma
0 siblings, 0 replies; 19+ messages in thread
From: poma @ 2015-06-15 10:37 UTC (permalink / raw)
To: Harald Hoyer, Bruno Wolff III
Cc: Gerhard Wiesinger, Andrei Borzenkov, initramfs,
For testing and quality assurance of Fedora releases
On 15.06.2015 11:42, Harald Hoyer wrote:
> On 11.06.2015 11:06, poma wrote:
>> On 31.05.2015 20:08, Bruno Wolff III wrote:
>>>> 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.
>>>
>>
>>
>> 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.
>
rd.OhLordwontyoubuymeaMercedesBenzMyfriendsalldrivePorschesImustmakeamends
^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~2015-06-15 10:37 UTC | newest]
Thread overview: 19+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-27 11:28 Update FC22 - doesn't find root fs and doesn't boot Gerhard Wiesinger
[not found] ` <5565AA58.6000409-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
2015-05-27 11:56 ` Harald Hoyer
[not found] ` <5565B0E6.3050204-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-27 12:09 ` Gerhard Wiesinger
[not found] ` <5565B3E6.4010806-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
2015-05-27 12:13 ` Andrei Borzenkov
[not found] ` <CAA91j0UysOKJG6LpuvCdrh3jcRMdj9+=XaD-R+Shw7WFZSvbUw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-27 12:25 ` Harald Hoyer
[not found] ` <5565B7BF.4010604-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-27 12:39 ` Gerhard Wiesinger
[not found] ` <5565BAEA.6080202-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
2015-05-27 12:43 ` Harald Hoyer
[not found] ` <5565BBF8.1050509-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-27 13:03 ` Gerhard Wiesinger
[not found] ` <5565C0AC.2070106-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
2015-05-27 13:07 ` Harald Hoyer
[not found] ` <5565C182.30709-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-27 13:21 ` Gerhard Wiesinger
[not found] ` <5565C4E7.6010301-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
2015-05-27 13:27 ` Harald Hoyer
[not found] ` <5565C654.3000101-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-27 13:33 ` Gerhard Wiesinger
[not found] ` <5565C7AF.70009-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
2015-05-27 17:21 ` Andrew Udvare
2015-05-28 12:19 ` Gerhard Wiesinger
[not found] ` <556707B5.4000707-tcxHB8FAk+J54TAoqtyWWQ@public.gmane.org>
2015-05-31 7:51 ` poma
2015-05-31 18:08 ` Bruno Wolff III
[not found] ` <20150531180858.GA27097-bdMChIhFSYk@public.gmane.org>
2015-06-11 9:06 ` poma
[not found] ` <55794FA1.3070107-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-06-15 9:42 ` Harald Hoyer
[not found] ` <557E9DF5.2070809-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-06-15 10:37 ` poma
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.