shutdown tumbleweed: failed to unmount /home; failed to unmount /var
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Rep:
shutdown tumbleweed: failed to unmount /home; failed to unmount /var
I searched the web for these Messages. Culprit is systemd which gets tangled with some files still in use(?). The remedies I found were for Arch-Linux (and I couldn't really follow them), talking of "HOOK"s and "mkinitcpio", both of which SUSE seemingly lacks.
Are these messages recurring on every reboot or shutdown?
With systemd and dracut, failure during boot not unusually leads to shutdown delays produced by failing to start things that should be being shut down.
Are these messages recurring on every reboot or shutdown?
Mostly yes, but at least one of them always (changes...).
Quote:
Originally Posted by mrmazda
With systemd and dracut, failure during boot not unusually leads to shutdown delays produced by failing to start things that should be being shut down.
It is not a failure to boot. Machine runs with no problems, I just want to avoid data corruption due to incorrect shut down(s).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.