you aren't the only one.
Something's definitely different. Open a case with your Linux support.
For all least all of the system volumes (ones needed to boot) , consider
erasing the 51-dasd* rules in /etc/udev/rules.d and then using "chzdev -e " to
put back new 41-dasd-eckd* rules.
Then running mkinitrd
Then running grub2-mkconfig -o /boot/grub2/grub.cfg; grub2-install
These things or some combo of them have solved it when we hit it (after using
rescue system get to a point where we could do this)
You can also "cat /run/initramfs/rdsosreport.txt" to get more info. It will
like complain of some missing devices or maybe you simply have to vgscan or
vgchange -ay that rootvg
Or boot with parm rd.debug as Mark Post mentioned here last week.
-----Original Message-----
From: Linux on 390 Port <LINUX-390@VM.MARIST.EDU> On Behalf Of Victor Echavarry
Sent: Wednesday, April 29, 2020 2:40 PM
To: LINUX-390@VM.MARIST.EDU
Subject: [LINUX-390] Dracut error after Booting default (grub) message
Hi:
The Unix Group is having an internment issue patching SLES Linux guest. They
patch every Linux guest on a monthly basis. A server patch various month
without a problem and for some unexplained reason after a successful
patch and reboot or IPL the guest, shows a warning error and go to Emergency
Shell
DIAG swap disk defined at virtual address 160 (24789 4K pages of swap space)
Enter a non-blank character and ENTER (or two ENTERs) within 10
seconds to interrupt Linux IPL.
DMSCYW2246I 16:31:36 WAKEUP in (10 sec).
DASD 0190 DETACHED
DASD 0191 DETACHED
DASD 019E DETACHED
Booting default (grub2)
dracut-initqueue[347]: Warning: dracut-initqueue timeout - starting timeout
scripts
dracut-initqueue[347]: Warning: dracut-initqueue timeout - starting timeout
scripts
dracut-initqueue[347]: Warning: dracut-initqueue timeout - starting timeout
scripts
.
.
.
.
dracut-initqueue[347]: Warning: Could not boot.
Starting Dracut Emergency Shell...
Warning: /dev/mapper/rootvg-usrlv does not exist
Warning: /dev/rootvg/usrlv 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
(or press Control-D to continue):
Does anyone saw this before and tell us what to do? We have SLES 12 SP5 under
z/VM 6.4.
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 lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
