Was this with BTRFS or another filesystem?  We have had huge problems with BTRFS and now have had to convert all of our SLES 12 servers to ext4 to avoid it.  The problems all hit when we moved to SP4 from earlier levels of SLES 12.  One by one, even the stable servers failed.

Martha

On 7/13/2019 6:08 PM, 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" <LINUX-390@VM.MARIST.EDU on behalf of victor.echava...@evertecinc.com> 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 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

--
Martha McConaghy
Marist: System Architect/Technical Lead
SHARE Association: Vice President
Marist College IT
Poughkeepsie, NY 12601

----------------------------------------------------------------------
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

Reply via email to