Page MenuHomeSolus

Disk not cleanly unmounted during shutdown
Closed, DuplicatePublic

Description

Hardware: Lenovo Thinkpad x230, 60GB SSD
Solus Budgie, latest updates installed. No other OS on this laptop

Issue: When selecting shutdown from Budgie, the system seems to just shut down instantly. Upon turning the laptop back on, I get a message that the journal is being recovered on /dev/sda2 (root partition), leading me to believe that the disk is not being unmounted at shutdown.

Output of journalctl -b -1, last few lines from previous boot showing issue:

Oct 17 16:39:09 tnettenba systemd[710]: Stopping Virtual filesystem service...
Oct 17 16:39:09 tnettenba systemd[710]: Stopping D-Bus User Message Bus...
Oct 17 16:39:09 tnettenba systemd[710]: Stopping Default.
Oct 17 16:39:09 tnettenba systemd[710]: Stopped target Default.
Oct 17 16:39:09 tnettenba systemd[710]: Stopped D-Bus User Message Bus.
Oct 17 16:39:09 tnettenba systemd[710]: Stopped Virtual filesystem service.
Oct 17 16:39:09 tnettenba systemd[710]: Stopping Basic System.
Oct 17 16:39:09 tnettenba systemd[710]: Stopped target Basic System.
Oct 17 16:39:09 tnettenba systemd[710]: Stopping Paths.
Oct 17 16:39:09 tnettenba systemd[710]: Stopped target Paths.
Oct 17 16:39:09 tnettenba systemd[710]: Stopping Sockets.
Oct 17 16:39:09 tnettenba systemd[710]: Stopped target Sockets.
Oct 17 16:39:09 tnettenba systemd[710]: Stopping Timers.
Oct 17 16:39:09 tnettenba systemd[710]: Stopped target Timers.
Oct 17 16:39:09 tnettenba systemd[710]: Stopping D-Bus User Message Bus Socket.
Oct 17 16:39:09 tnettenba systemd[710]: Closed D-Bus User Message Bus Socket.
Oct 17 16:39:09 tnettenba systemd[710]: Stopping -.slice.
Oct 17 16:39:09 tnettenba systemd[710]: Removed slice -.slice.
Oct 17 16:39:09 tnettenba systemd[710]: Starting Shutdown.
Oct 17 16:39:09 tnettenba systemd[710]: Reached target Shutdown.
Oct 17 16:39:09 tnettenba systemd[710]: Starting Exit the Session...
Oct 17 16:39:09 tnettenba systemd[715]: pam_unix(systemd-user:session): session closed for user fubar
Oct 17 16:39:09 tnettenba systemd[710]: Received SIGRTMIN+24 from PID 1120 (kill).

Event Timeline

tiredpixels edited projects, added Hardware; removed Lacks Project.Oct 18 2017, 3:44 AM

This is kind of a big issue for me, as I'd rather not lose data from drives not unmounting cleanly

Upon turning the laptop back on, I get a message that the journal is being recovered on /dev/sda2 (root partition)

Can we see these messages?

Any ideas on how to capture them? It happens on boot. I can check the logs and see if they are logged, but other than that I'm not sure I can grab them in time.

sudo journalctl -xb

Well, color me a fool, or something. I had this issue reproducing regularly yesterday, and today I cannot get it to reproduce at all. Logs are clean today. I've shutdown completely and restarted a few times and all seems to be fine. No idea how it cleared up, but it seems fine now. Self healing, perhaps?