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? -- Best regards, Juha Vuori On 14.7.2019 1.08, Marcy Cortes wrote: > Exactly what happened to us. I posted here last month when it happenend. > > SUSE has given us a temp PTF that we've just started testing > > What you need to do to recover is to boot a rescue system and bring on all > your devices with chzdev. > Then run mkinitrd and grub2-install and cross your fingers. > > Marcy > > On 7/13/19, 6:11 AM, "Linux on 390 Port on behalf of Victor Echavarry" > <[email protected] on behalf of [email protected]> wrote: > > Hi: > > Yesterday after perform an update in one of our test servers (SLES12 > SP4) and after updating & rebooting, now the server won't boot. This are the > messages > > Booting default (grub2) > dracut-initqueue[403]: Warning: dracut-initqueue timeout - starting > timeout scri > pts > dracut-initqueue[403]: Warning: dracut-initqueue timeout - starting > timeout scr > > dracut-initqueue[403]: Warning: dracut-initqueue timeout - starting > timeout scri > pts > dracut-initqueue[403]: Warning: Could not boot. > Starting Dracut Emergency Shell... > Warning: /dev/mapper/sys-user does not exist > Warning: /dev/sys/user does not exist > > > Generating "/run/initramfs/rdsosreport.txt" > > > Entering emergency mode. Exit the shell to continue. > Type "journalctl" to view system logs. > You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick > or /boot > after mounting them and attach it to a bug report. > > > Give root password for maintenance > > Please note, this server has the following filesystem layout: > > > 1. DASD device (non-LVM) --- (root filesystem) > (5) DASD devices for "sys" volume group for the rest of filesystem: > /var, /usr etc.. > > We can mount / filesystem on another zLinux system and have access to > /boot and /etc and trying to rebuild grub and is unsussceful. > > Any help? > > Regards, > > Victor Echavarry > System Programmer > Operating Systems > EVERTEC, LLC > > > > > WARNING: This email and any files transmitted with it are confidential > and intended solely for the use of the individual or entity to whom they are > addressed. If you have received this email in error please delete it > immediately. Please note that any views or opinions presented in this email > are solely those of the author and do not necessarily represent those of > EVERTEC, Inc. or its affiliates. Finally, the integrity and security of this > message cannot be guaranteed on the Internet, and as such EVERTEC, Inc. and > its affiliates accept no liability for any damage caused by any virus > transmitted by this email. > > ---------------------------------------------------------------------- > 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 > > > ---------------------------------------------------------------------- > 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 > ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
