Mailinglist Archive: opensuse (868 mails)

< Previous Next >
Re: [opensuse] incomplete shutdown

On 2011-05-12 benefici offered the following:

On Wednesday 11 May 2011 18:09:15 Richard Creighton wrote:
On 2011-05-11 benefici offered the following:
My desktop PC (with openSUSE 11.4) does not shutdown completely at
times. This is very worrying as one of the steps missed is the
unmounting of file systems. Then of course on the next boot-up the
file systems are found unclean. Unfortunately I have also lost data
because of this. I started collecting evidence about the problem by
making video recordings of shutdown messages. I compared a complete
shutdown with an incomplete one and found that the messages up to
"Running /etc/init.d/halt.local" were present in both videos (in a
different order). Then the following messages were missing from the
incomplete shutdown:

Turning off swap files
Set Hardware Clock to the current System Time
Unmounting file systems
none has been unmounted
/dev/md6 has been unmounted
/dev/md7 has been unmounted
Shutting down MD Raid
Stopping udevd:

After that both videos finished with the same messages:

Sending all processes the TERM signal...
Sending all processes the KILL signal...
The system will be halted immediately.

The above two videos were recorded about 2 hours apart, first the
complete then the incomplete one. I did nothing special in between -
used digiKam, checked my e-mail etc. I did not update my system or
changed any system files. Any ideas how to track down / fix this


Check out [Bug 590744] Unclean ext3 after online update . This and a
related bug

[Bug 450196] PATA ext3 - recovering journal on / on first boot on new
kernel/fresh system updates

I believe these two bugs are different from mine. In my case, unmounting
manually works. The problem is that the shutdown process does not execute
some of the steps (e.g. /etc/init.d/boot.localfs), which would among other
things umount file systems.
The problem also occurs whithout updating any software on my PC.
Thanks anyway,

....which is why I felt it pertinent, while a *manual* umount may not fail, the
that is common with your problem is the *shutdown* umount, eg, during
shutdown, the
umount doesn't seem to be either a)sucessful or b)attempted. This would give
symptoms you describe and explain the problem(s) seen after the update
requiring a
reboot, eg, if the umount after the update didn't run, as in your example, that
cause their problem, and conversely, if they find the reason it doesn't run
(correctly) during those bug(s) shutdown, it may well solve *your* problem.

That is why I suggested adding your comments to those bug reports because I
believe that (your) observation has been explored. Carlos also mentioned a
of other quite similar bugs, so your observation could clear 4 or more similar
*if* it can be determined why part of the shutdown script(s) aren't being
or otherwise fail.

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >