This has been happening since I installed Leap 42.1 (currently I use 42.3). Nothing seems to have been broken so far but during the last boot there was some more extensive disk check.
Also what means “Runtime Directory” (is that /run?)? Could you help to customize the debug.sh given there to match my issue, so I can post more relevant feedback after that:
#!/bin/sh
mount -o remount,rw /
lsof /run > /shutdown-log.txt
dmesg >> /shutdown-log.txt
mount -o remount,ro /
create /usr/lib/systemd/system-shutdown/debug.sh and make it
executable with the following content
#!/bin/sh
mount -o remount,rw /
lsof /run > /shutdown-log.txt
dmesg >> /shutdown-log.txt
mount -o remount,ro /
Reboot the system
I don’t have the situation described there, i.e. plymouth is not trying to display splash screen on shutdown. In fact my grub command line parameters have always been:
If it still occurs, then boot with the debug options and post the whole (rather than just extracts) of shutdown-log.txt
Right after uninstalling plymouth packages I added systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M to bootloader as explained on the link. Rebooted twice to make sure it has come into effect. The first time I didn’t see any red notice during shutdown. The second time it was there again. The 2 logs I saved as shutdown-log-1.txt and shutdown-log-2.txt. Then I removed the added bootloader options.
I am reluctant to pasting the full text of shutdown-log.txt in a public forum for security and privacy reasons as it seems to reveal too much info about how the data is structured on this system, local usernames etc. Please let me know what in particular I should look for, so I can paste additionally only the relevant parts. Thanks.
No. And I haven’t run any updates either. Why is adding locks necessary?
did you rebuild initrd?
After reading your post - yes + rebooted twice. The red error messages still appear on shutdown. The only change is that on boot the number of text info messages which display are less. They used to be a whole screen and more, now only 1/3 of the screen.
Look at the very start of the shutdown-log (for the lsof output), any open files? (There didn’t appear to be anything shown by https://susepaste.org/4723773c but we don’t know if it includes the start of the log). As plymouth is now eliminated, journalctl files maybe?
Then look through the remainder of the log for anything suspicious (using | grep -i mount | grep -iE “var|runtime” won’t necessarily pick out the offending line). I’m sorry I can’t tell you what to specifically look for. I also understand your reasons and hence reluctance to share the entire log.
Also, you wrote in the initial post:
This has been happening since I installed Leap 42.1 (currently I use 42.3).
Could you clarify that: What version is it happening with? Was it a clean install or a (down?)grade? Or did you mean it has been happening all the time since 42.1 through 42.2 to 42.3 ???
[QUOTE=tannington;2843568]Still for /var and /run ?
[/QUOTE]
Yes.
Look at the very start of the shutdown-log (for the lsof output), any open files? (There didn’t appear to be anything shown by https://susepaste.org/4723773c but we don’t know if it includes the start of the log).
As plymouth is now eliminated, journalctl files maybe?
Please explain.
Then look through the remainder of the log for anything suspicious (using | grep -i mount | grep -iE “var|runtime” won’t necessarily pick out the offending line). I’m sorry I can’t tell you what to specifically look for. I also understand your reasons and hence reluctance to share the entire log.
The message “Failed to unmount /var” appears during shutdown right before this message (I don’t know why it is not in the log though):
31.245825] systemd-shutdown[1]: Unmounting /var.
/var is sdb3
Does that clarify anything?
Could you clarify that: What version is it happening with? Was it a clean install or a (down?)grade? Or did you mean it has been happening all the time since 42.1 through 42.2 to 42.3 ???
I am running Leap 42.3, upgraded from 42.2, upgraded from 42.1, upgraded from 13.2. IIRC it started happening after upgrading from 13.2 to Leap 42.1.