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

2015-06-15 Thread Harald Hoyer 
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.

--
To unsubscribe from this list: send the line unsubscribe initramfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

2015-06-15 Thread poma 
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


--
To unsubscribe from this list: send the line unsubscribe initramfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

2015-06-11 Thread poma 
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


--
To unsubscribe from this list: send the line unsubscribe initramfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

2015-05-31 Thread Bruno Wolff III 

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.

--
To unsubscribe from this list: send the line unsubscribe initramfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

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

2015-05-31 Thread poma 
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 
 li...@wiesinger.com
 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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh



 and 
 /sys/devices/pci:00/: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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1



 and /sys/devices/pci:00/: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).
 [

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

2015-05-28 Thread Gerhard Wiesinger 

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 li...@wiesinger.com
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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh



and /sys/devices/pci:00/: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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1



and /sys/devices/pci:00/: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

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

2015-05-27 Thread 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 li...@wiesinger.com 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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh

and /sys/devices/pci:00/: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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1

and /sys/devices/pci:00/: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

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

2015-05-27 Thread Harald Hoyer 
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 li...@wiesinger.com 
 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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh

 and /sys/devices/pci:00/: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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1

 and /sys/devices/pci:00/: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

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

2015-05-27 Thread Harald Hoyer 
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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
 and /sys/devices/pci:00/: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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
 and /sys/devices/pci:00/: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

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

2015-05-27 Thread Gerhard Wiesinger 

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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
and /sys/devices/pci:00/: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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
and /sys/devices/pci:00/: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

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

2015-05-27 Thread 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 li...@wiesinger.com
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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh


and /sys/devices/pci:00/: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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1


and /sys/devices/pci:00/: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

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

2015-05-27 Thread Gerhard Wiesinger 

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 li...@wiesinger.com
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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh



and /sys/devices/pci:00/: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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1



and /sys/devices/pci:00/: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

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

2015-05-27 Thread Harald Hoyer 
Am 27.05.2015 um 14:13 schrieb Andrei Borzenkov:
 On Wed, May 27, 2015 at 3:09 PM, Gerhard Wiesinger li...@wiesinger.com 
 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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
 and /sys/devices/pci:00/: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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
 and /sys/devices/pci:00/: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

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

2015-05-27 Thread Harald Hoyer 
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 li...@wiesinger.com
 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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh


 and /sys/devices/pci:00/: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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1


 and /sys/devices/pci:00/: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

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

2015-05-27 Thread Andrei Borzenkov 
On Wed, May 27, 2015 at 3:09 PM, Gerhard Wiesinger li...@wiesinger.com 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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh
 and /sys/devices/pci:00/: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/pci:00/:00:04.1/usb2/2-5/2-5:1.0/host9/target9:0:0/9:0:0:0/block/sdh/sdh1
 and /sys/devices/pci:00/: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

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

2015-05-27 Thread Andrew Udvare 
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.0 -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 li...@wiesinger.com 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
 li...@wiesinger.com
 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