We ran into similar again on a couple of servers a week or two ago for unknown reasons. Neither had recent disk changes. This solved it for us
Boot with rescue media vary on the devices with chzdev -e Make a chroot environment with the following (your filesystems may vary) mount /dev/dasda1 /mnt mount -t proc none /mnt/proc mount --rbind /dev /mnt/dev mount --rbind /sys /mnt/sys mount /dev/mapper/system-var--lv /mnt/var mount /dev/mapper/system-usr--lv /mnt/usr mount /dev/mapper/system-tmp--lv /mnt/tmp mount /dev/mapper/system-home--lv /mnt/home mount /dev/mapper/system-opt--lv /mnt/opt chroot /mnt /bin/bash mount -a Then this solved it: rescue:/ # vgs WARNING: Failed to connect to lvmetad. Falling back to device scanning. Not repairing metadata for VG system. Recovery of volume group "system" failed. rescue:/ # vgscan WARNING: Failed to connect to lvmetad. Falling back to device scanning. Reading all physical volumes. This may take a while... WARNING: Inconsistent metadata found for VG system - updating to use version 10 Found volume group "system" using metadata type lvm2 rescue:/ # vgscan WARNING: Failed to connect to lvmetad. Falling back to device scanning. Reading all physical volumes. This may take a while... Found volume group "system" using metadata type lvm2 rescue:/ # vgs WARNING: Failed to connect to lvmetad. Falling back to device scanning. VG #PV #LV #SN Attr VSize VFree system 2 5 0 wz--n- 15.10g 88.00m The second server told us it was "updating to use version 11" Not sure what that means - both had the same software on them. -----Original Message----- From: Linux on 390 Port <[email protected]> On Behalf Of Victor Echavarry Sent: Wednesday, May 13, 2020 1:02 PM To: [email protected] Subject: Re: [LINUX-390] Dracut error after Booting default (grub) message After various testing we found that the issue making the system doesn't boot is when expanding the LVM OS file system, ex. /opt, /var. The Unix administrator send a photo of a message when he resized the filesystem. https://imgur.com/j57a7aL When he reboots the system, the system stop under Booting default (grub2) for a couple of minutes and then show the Dracut message going to Give root password for maintenance (or press Control-D to continue): Right now there an open case under SUSE waiting for a solution. Regards, Victor Echavarry System Programmer Operating Systems EVERTEC, LLC -----Original Message----- From: Linux on 390 Port <[email protected]> On Behalf Of Marcy Cortes Sent: Wednesday, April 29, 2020 7:54 PM To: [email protected] Subject: Re: Dracut error after Booting default (grub) message 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 <[email protected]> On Behalf Of Victor Echavarry Sent: Wednesday, April 29, 2020 2:40 PM To: [email protected] 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 [email protected] with the message: INFO LINUX-390 or visit https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CVictor.Echavarry%40evertecinc.com%7C10cfe8ef798e40d3b6c808d7ec98f9d9%7C2b5b7d77f19b4c6db1805768c09ad43b%7C0%7C0%7C637238014090805463&sdata=mOR%2BZ%2Be9TzroshpuG8poBZIhLdx7U2JWY4%2BdXFaPe0o%3D&reserved=0 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=02%7C01%7CVictor.Echavarry%40evertecinc.com%7C10cfe8ef798e40d3b6c808d7ec98f9d9%7C2b5b7d77f19b4c6db1805768c09ad43b%7C0%7C0%7C637238014090805463&sdata=mOR%2BZ%2Be9TzroshpuG8poBZIhLdx7U2JWY4%2BdXFaPe0o%3D&reserved=0 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
