[SLE] Unclean shutdown SuSE 9.2
I am getting an un-clean shutdown with subsequent hang on on a SuSE V9.2 system. Symptoms: (at the final end of shutdown) Turning off swap Unmounting file system umount: /dev/pts: device busy umount: /: device busy Oops umount failed trying to mount read only mount: / is busy mount: / is busy mount can't find /sys in /etc/fstab or /etc/mtab devpts: on /dev/pts type devpts (ro) extra sync ... hope now its ok to reboot disabling hotplug umount: /proc: device is busy mount: proc already mounted umount: /proc: device is busy umount: /proc: device is busy the system will be halted immediately The system now hangs, and I have to press the reset button or power cycle. To me, this means a 130 km round trip to reset an un-attended system. I googled for a solution and most posts refer to powermanagement/powersave. So I tried to remove powersave. This is what I get: ERROR(InstTarget:E_RpmDB_subprocess_failed) --- 2006-06-15 19:35:31 powersave remove failed rpm output: ..failed error: %preun(powersave-0.8.19-2) scriptlet failed, exit status 1 2006-06-15 19:35:38 powersave remove failed rpm output: ..failed error: %preun(powersave-0.8.19-2) scriptlet failed, exit status 1 How to proceed? I tried re-installing powersave and then removing it, but get the same result. fstab entries: sysfs /sys sysfs noauto 0 0 /dev/hda2 /boot ext2 defaults 1 2 /dev/hda6 /home reiserfs defaults 1 2 /dev/fd0 /media/floppy auto noauto,user 0 0 /dev/hda3 / ext2 defaults 1 1 devpts /dev/pts devpts defaults 0 0 proc /proc proc defaults 0 0 /dev/dvdram /media/dvdram subfs noauto,ro,user,exec,iocharset=utf8 0 0 /dev/hda5 swap swap pri=42 0 0 Thanks for any help Peter -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Hi Peter, On Thursday 15 June 2006 07:49, Peter Sutter wrote:
I am getting an un-clean shutdown with subsequent hang on on a SuSE V9.2 system. <snip>
How long has this system been in service with the present configuration? Is the fault "out of the blue" or could you have done something beforehand to trigger it? e.g. software updates/additions, edit config files, etc.?
The system now hangs, and I have to press the reset button or power cycle. To me, this means a 130 km round trip to reset an un-attended system.
Then you'll probably want to fix the system in situ, not remotely, or else bring it back for repair, right? Is this a server? What hardware?
I googled for a solution and most posts refer to powermanagement/powersave. So I tried to remove powersave. This is what I get: <snip>
Anything interesting in the logs? Carl -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Thanks Carl, On Thursday 15 June 2006 20:36, Carl Hartung wrote:
Hi Peter,
On Thursday 15 June 2006 07:49, Peter Sutter wrote:
I am getting an un-clean shutdown with subsequent hang on on a SuSE V9.2 system.
<snip>
How long has this system been in service with the present configuration? Is the fault "out of the blue" or could you have done something beforehand to trigger it? e.g. software updates/additions, edit config files, etc.?
Well, the system just got a new motherboard and processor, the processor is now 64 bit capable. I run a 'system repair' just to make sure, and it installed some 64-bit software but was otherwise clean. It can't be hardware, because the rescue system and a test system I have on a usb portable drive shut down/restart completely and correctly, only when booting into the root partition does it hang, so it must be configuration related.
The system now hangs, and I have to press the reset button or power cycle. To me, this means a 130 km round trip to reset an un-attended system.
Then you'll probably want to fix the system in situ, not remotely, or else bring it back for repair, right? Is this a server? What hardware?
I am convinced that it is not hardware related. It got upgraded to a 3 Ghz Intel Pentium IV, before 1GHz Pentium IV. It is a kind of a server, running rsync, mysql, apache, php, and exports one nfs share and runs some special application software. The application software does not have any daemons. Original install was as standard workstation with kde, although nobody really logs now on to it interactively.
Anything interesting in the logs?
No, except one funny error at startup /etc/sysconfig/cron: line 48: syntax error near unexpected token `(' /etc/sysconfig/cron: line 48: `## "Set this to "yes" to entirely remove (rm -rf) all files and subdirectories' which is a comment line, but nothing for shutdown. The system says it is rebooting/powering off, but just doesn't do it, most likely because of the error. The root partition is always 'dirty' on startup. shutting down from runlevel s after dismounting all disks manually, still produces the error. Something must still be using /proc, but how do I find out what.
Carl
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Thursday 15 June 2006 09:28, Peter Sutter wrote:
Well, the system just got a new motherboard and processor
9.2 may not know how to properly support your new (presumably newer than 9.2) hardware. Can you put the existing disks aside, throw in a spare and see how 9.2 handles being installed and configured? If it works OK, you'll at least know it's supported and be closer to understanding what a successful configuration looks like. regards, Carl -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Thursday 15 June 2006 22:45, Carl Hartung wrote:
On Thursday 15 June 2006 09:28, Peter Sutter wrote:
Well, the system just got a new motherboard and processor
9.2 may not know how to properly support your new (presumably newer than 9.2) hardware. Can you put the existing disks aside, throw in a spare and see how 9.2 handles being installed and configured? If it works OK, you'll at least know it's supported and be closer to understanding what a successful configuration looks like.
regards,
Carl
I tried that already, no problem at all, all works fine, even the shutdown. Its just the shutdown that hangs on the existing system. regards, Peter -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Thursday 15 June 2006 11:15, Peter Sutter wrote:
I tried that already, no problem at all, all works fine, even the shutdown.
Is powersaved running on the broken system and not on the problem-free system? Carl -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Friday 16 June 2006 00:51, Carl Hartung wrote:
On Thursday 15 June 2006 11:15, Peter Sutter wrote:
I tried that already, no problem at all, all works fine, even the shutdown.
Is powersaved running on the broken system and not on the problem-free system?
No, the other way round, powersaved is running on the 'problem free' system but not on the 'broken system'. However, the problem fixed itself on its own. I assume that some configuration check script must have run overnight that fixed the problem. I am still curious to what caused the problem and which script had done the magic. Thank you very much for your help Peter -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Fri, 2006-06-16 at 09:33 +0800, Peter Sutter wrote:
On Friday 16 June 2006 00:51, Carl Hartung wrote:
On Thursday 15 June 2006 11:15, Peter Sutter wrote:
I tried that already, no problem at all, all works fine, even the shutdown.
Is powersaved running on the broken system and not on the problem-free system?
No, the other way round, powersaved is running on the 'problem free' system but not on the 'broken system'.
However, the problem fixed itself on its own. I assume that some configuration check script must have run overnight that fixed the problem. I am still curious to what caused the problem and which script had done the magic.
Thank you very much for your help
Just popping in here to ask this one question. Isn't there a log of what scripts are run when? It would be nice to know. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
participants (3)
-
Carl Hartung
-
Mike McMullin
-
Peter Sutter