Shutting down the system always works perfectly, but restarting always failed. (using menu or typing reboot or sudo init 6, obviously)
DRACUT FROM THIS POINT FORWARD
It loads dracut and stops with the fallowing message
dracut: Warning:
/run/initramfs/rdosreport.txt
/sbin/rdosreport.sh line 7 Read only file system
...
/lib/dracut_lib.sh line 1088 /.profile read-only file system
Using the DRACUT shell I tried to reboot but
# reboot
failed to unlink reboot parameter file read only file system
and typing halt
# halt
failed to connect to bus: Connection refused
**END DRACUT **
so I pressed the reset button.
Please help I don’t want to damage my file system
OS: Tumbleweed:
4.11.8-1-default #1 SMP PREEMPT Thu Jun 29 14:37:33 UTC 2017 (42bd7a0) x86_64 x86_64 x86_64 GNU/Linux[/QUOTE]
This is likely rdsosreport.txt. Please try to pay attention to details, otherwise it quickly becomes “garbage in - garbage out”.
/lib/dracut_lib.sh line 1088 /.profile read-only file system
That’s rather interesting. This line is in dracut branch for non-systemd initrd. Could you upload “lsinitrd /boot/path-to-your-initrd” to http://susepaste.org/?
So it is apparently during shutdown, not during boot after restart. Someone reported problems during shutdown in recent TW as well. Could you try disable (and stop) dracut-shutdown.service and report if it changes anything?
Perpetual shutdown …
Shows the shutdown TW screen and does nothing. I can only change screens with F1 ~ F12
F1 shows shutdown TW screen
F2 ~ F11 are black
F12 shows init messages
ESC does not work
It probably would timeout at some point. Booting with “plymouth.enable=0” and without “quiet” on kernel command line may give some more hints what’s going on. Of course, the first step is to reduce complexity - boot into run level 3 so output is not obscured by eye candy, Unfortunately unless someone will be able to reproduce it, further debugging without some means to capture console output during shutdown is not feasible. If you have second system, you may try to setup netconsole (see https://www.kernel.org/doc/Documentation/networking/netconsole.txt); then we can try to get some more information. Or use serial console if you have serial port in both systems and suitable cable.
