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
Based on our recent experience, I would agree. Imagine applying an RSU
to a bunch of VM systems and then have them systematically die with file
system corruption errors. That's basically what happened to all of our
SLES 12 systems. We have been working with SUSE to find the cause
(other than
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 lidong.zh...@suse.com
- 95dasd_rules: find correct udev rules(bsc#1137784)
And yes, it would be
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 n