Thanks for info, sounds like our case.. I will contact SUSE.
-- Best regards, Juha Vuori On 14.7.2019 22.47, Marcy Cortes wrote:
Seems to happen if disk were added after the SP4 upgrade and then on subsequent boot it can't find it. I've not been able to recreate though. Fix is to dracut and has this comment: * Fri Jun 28 2019 [email protected] - 95dasd_rules: find correct udev rules(bsc#1137784) And yes, it would be specific to s390x since "dasd" Call them and reference 1137784 -----Original Message----- From: Linux on 390 Port <[email protected]> On Behalf Of Juha Vuori Sent: Sunday, July 14, 2019 5:04 AM To: [email protected] Subject: Re: [LINUX-390] Server don't boot after patch Hi, Thanks for reporting this here, we are probably hit by the same: ... ... dracut-initqueue[338]: Warning: dracut-initqueue timeout - starting timeout scripts dracut-initqueue[338]: Warning: Could not boot. Starting Dracut Emergency Shell... Warning: /dev/mapper/system-usr does not exist Warning: /dev/system/usr does not exist Generating "/run/initramfs/rdsosreport.txt" ... ... No btrfs, only extN on and off LVM. This one was sles12sp4 migrated from sles11sp4 a few months ago, but now boot (after z/VM 6.4 -> 7.1) fails for the 1st time. So I'm not 100% sure yet what's causing what.. Wonderings popping into mind: - if the bug is specific to s390x - if the bug is related to specific kernel version, or dracut/grub version - if the bug is specific to ckd/fba/scsi PVs I guess the problem report is not available in public from SUSE?
---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
