Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - Linux
- >
- General
- >
- umount fails on reboot/shutdown.
General
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-30-2009 11:39 AM
01-30-2009 11:39 AM
umount fails on reboot/shutdown.
On openSUSE 11.1 with KDE 3.5 I noticed that it did not successfully umount /var, /home and /usr upon reboot or shutdown.
I'm getting error such as: umount: /dev/sda9 busy
I edited /etc/rc.d/boot.localfs and entered lsof > /var/log/openfiles.txt after the line "if test "$UMOUNT_FAILED" = true -a -z "$mtab" ; then" to figure out what files were open.
I found that the programs console-kit-daemon, pulseaudio and dcopserve were still running.
I then entered the following before the umount lines:
killall -q -TERM console-kit-daemon
killall -q -TERM pulseaudio
killall -q -TERM dcopserve
sleep 1
killall -q -KILL console-kit-daemon
killall -q -KILL pulseaudio
killall -q -KILL dcopserve
It now successfully umount's all filesystems, but why are these programs still running, is it known problems or something wrong with my configuration?
Here is the disk partitions:
Filesystem Size Used Avail Use% Mounted on
/dev/sda5 3.0G 224M 2.6G 8% /
udev 1001M 2.1M 999M 1% /dev
/dev/sda1 595M 30M 535M 6% /boot
/dev/sda6 595M 83M 482M 15% /tmp
/dev/sda8 2.0G 296M 1.6G 16% /var
/dev/sda9 20G 4.9G 14G 26% /usr
/dev/sda10 5.0G 998M 3.7G 21% /opt
/dev/sda11 5.0G 139M 4.6G 3% /usr/local
/dev/sda12 73G 6.1G 63G 9% /home
/dev/sdb1 294G 251G 31G 90% /mnt/datadisk1
/dev/sdc1 233G 99G 135G 43% /mnt/datadisk2
I'm getting error such as: umount: /dev/sda9 busy
I edited /etc/rc.d/boot.localfs and entered lsof > /var/log/openfiles.txt after the line "if test "$UMOUNT_FAILED" = true -a -z "$mtab" ; then" to figure out what files were open.
I found that the programs console-kit-daemon, pulseaudio and dcopserve were still running.
I then entered the following before the umount lines:
killall -q -TERM console-kit-daemon
killall -q -TERM pulseaudio
killall -q -TERM dcopserve
sleep 1
killall -q -KILL console-kit-daemon
killall -q -KILL pulseaudio
killall -q -KILL dcopserve
It now successfully umount's all filesystems, but why are these programs still running, is it known problems or something wrong with my configuration?
Here is the disk partitions:
Filesystem Size Used Avail Use% Mounted on
/dev/sda5 3.0G 224M 2.6G 8% /
udev 1001M 2.1M 999M 1% /dev
/dev/sda1 595M 30M 535M 6% /boot
/dev/sda6 595M 83M 482M 15% /tmp
/dev/sda8 2.0G 296M 1.6G 16% /var
/dev/sda9 20G 4.9G 14G 26% /usr
/dev/sda10 5.0G 998M 3.7G 21% /opt
/dev/sda11 5.0G 139M 4.6G 3% /usr/local
/dev/sda12 73G 6.1G 63G 9% /home
/dev/sdb1 294G 251G 31G 90% /mnt/datadisk1
/dev/sdc1 233G 99G 135G 43% /mnt/datadisk2
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-31-2009 12:36 AM
01-31-2009 12:36 AM
Re: umount fails on reboot/shutdown.
Those processes all look like things that might be started by a local X session. They are daemons in the traditional Unix sense, but on the other hand, they are related to your session.
Exactly how did you perform the shutdown?
Did you use the "shutdown" command from the command line? If so, try using the shutdown button in the KDE logout dialog instead. (If the shutdown button is not displayed by default, adjust the KDE settings in the KDE Control Center).
When you use the shutdown button in the KDE logout dialog, KDE will first log you out, ending all the processes started for your session, and only then initates the shutdown. This should make sure all the "session-specific daemons" are stopped properly.
MK
Exactly how did you perform the shutdown?
Did you use the "shutdown" command from the command line? If so, try using the shutdown button in the KDE logout dialog instead. (If the shutdown button is not displayed by default, adjust the KDE settings in the KDE Control Center).
When you use the shutdown button in the KDE logout dialog, KDE will first log you out, ending all the processes started for your session, and only then initates the shutdown. This should make sure all the "session-specific daemons" are stopped properly.
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-31-2009 03:39 AM
01-31-2009 03:39 AM
Re: umount fails on reboot/shutdown.
I used the shutdown from KDE, I've also tried to logout to console and then shutdown. And I've tried to set the runlevel to 3 and not start X at all, atleast one of those programs are running also without starting X/KDE.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP