What were you trying to do that didn't work?
14:22
hi guys, i need assistance on a leapp case. the system boots fine on RHEL7, when booting the RHEL8 kernel+initramfs, a DASD is missing:
$ grep "New DASD 3390" sos_commands/kernel/dmesg
[ 0.611270] dasd-eckd 0.0.0100: New DASD 3390/0C (CU 3990/01) with 32276 cylinders, 15 heads, 224 sectors
[ 0.613932] dasd-eckd 0.0.0301: New DASD 3390/0A (CU 3990/01) with 3338 cylinders, 15 heads, 224 sectors
[ 0.614043] dasd-eckd 0.0.0403: New DASD 3390/0C (CU 3990/01) with 64553 cylinders, 15 heads, 224 sectors
[ 0.654598] dasd-eckd 0.0.0401: New DASD 3390/0C (CU 3990/01) with 64553 cylinders, 15 heads, 224 sectors
[ 0.656446] dasd-eckd 0.0.0400: New DASD 3390/0A (CU 3990/01) with 3338 cylinders, 15 heads, 224 sectors
[ 1.748148] dasd-eckd 0.0.0402: New DASD 3390/0C (CU 3990/01) with 10016 cylinders, 15 heads, 224 sectors
once in RHEL8:
$ grep "New DASD 3390" rdsosreport_for_z00000.txt
[ 0.735249] localhost kernel: dasd-eckd 0.0.0100: New DASD 3390/0C (CU 3990/01) with 32276 cylinders, 15 heads, 224 sectors
[ 0.745246] localhost kernel: dasd-eckd 0.0.0301: New DASD 3390/0A (CU 3990/01) with 3338 cylinders, 15 heads, 224 sectors
[ 0.755494] localhost kernel: dasd-eckd 0.0.0400: New DASD 3390/0A (CU 3990/01) with 3338 cylinders, 15 heads, 224 sectors
[ 0.764889] localhost kernel: dasd-eckd 0.0.0401: New DASD 3390/0C (CU 3990/01) with 64553 cylinders, 15 heads, 224 sectors
[ 0.776696] localhost kernel: dasd-eckd 0.0.0402: New DASD 3390/0C (CU 3990/01) with 10016 cylinders, 15 heads, 224 sectors
Here above 0.0.0403 is not seen by the kernel. Even though kernel params are identical:
rd_DASD=0.0.0100 rd_DASD=0.0.0301 rd_DASD=0.0.0403
Any idea how to troubleshoot this ?

14:23
here above the kernel sees 0.0400, 0.0401 and 0.0402 even though there is no kernel param for those, so I would expect the kernel sees 0.0403 automatically without any hack somewhere
14:24

isn't there /etc/dasd.conf as well?
14:25

ahah, just found there is a dup entry in the sosreport's one (rhel7):
[...]
0.0.0403 use_diag=0 readonly=0 erplog=0 failfast=0
0.0.0402 use_diag=0 readonly=0 erplog=0 failfast=0
0.0.0403 use_diag=0 readonly=0 erplog=0 failfast=0
which seems to end up not having it at all once in the initramfs for upgrade!
0.0.0100 use_diag=0 readonly=0 erplog=0 failfast=0
0.0.0301 use_diag=0 readonly=0 erplog=0 failfast=0
0.0.0400 use_diag=0 readonly=0 erplog=0 failfast=0
0.0.0401 use_diag=0 readonly=0 erplog=0 failfast=0
0.0.0402 use_diag=0 readonly=0 erplog=0 failfast=0
14:25
@dhorak ++
14:25
there is hence a bug there ...
14:26

but the 0403 dasd should be always discovered, because it's on the kernel cmdline ...
14:28

well apparently not
14:29
told the cust to remove the dup and reexecute leapp upgrade but not reboot
14:29
then check dasd.conf in the initrd
14:29
let's see
14:44

@rmetrich: No real clue, but if you've got a working shell prompt, you could try "cio_ignore -l" to see whether the device is ignored, and maybe "cio_ignore -r 0.0.0403" to see whether it can be removed from the ignore-list
14:45
please never mind ... slack wasn't showing me the full context
14:45
slack--
15:12

hehe slack-- indeed
15:12
will report anyway
15:12
@thuth ++
15:13

@rmetrich is it rd_DASD?! i'm familiar with rd.dasd
15:14
and on older distros i think it was plain "DASD"
15:14

it's oldish deprecated but still works
15:14
gets parsed on cmdline
15:14

for the kernel parameters i mean
15:14
hmmm, ok
15:14

it's probably that dasd.conf that doesn't list the DASD there because of the dup
15:15
but i have no s390x to test (actually i could since you gave me access, but i'm lazy)

:54

hi @smitterl @dhorak @thuth i got confirmation that removing the dup entry in /etc/dasd.conf fixed the issue: the leapp initramfs started containing the entry and upgrade went fine

10:57

makes me wonder what exactly gets confused, is it the dasd module in dracut? or leapp?