[opensuse] incomplete shutdown
Hi, 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 problem? Tom -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
benefici@fastmail.fm said the following on 05/11/2011 05:28 AM:
My desktop PC (with openSUSE 11.4) does not shutdown completely at times.
This is happening to me as well, with a interesting variation. KDE4 is not saving the session on shut-down. I've tried logging out before shutting down; I've tried logging out, going to the text mode console. I go to 'init 3' and then I try unmounting the file systems one by one but find that KDE is still running. I unmount what I can and use 'shut-down -h now' but that doesn't do a complete shut-down; it takes an 'init 0'. When I come back up I find a lot of the session state has not been restored. * klipper was running in the system tray, now its not * konqueror was running, now its not * the names I've assigned to the virtual screen in the Pager are lost * sound is off. I have to run 'alsamixer -c 0' and find *everything* has been muted and levels set to zero I haven't seen lost files, but then I'm not saving large files as you are, Tom. If I were, I'd start by checking the file systems - FSCK, free space. Free space might matter since a lack of it can cause problems with latency in allocation with some file systems that make use of fragmented blocks. I'd check logs. *ALWAYS* check logs! I'd see if its a problem with file closing or with file unmounting independently from the shutdown. Slice and dice and localise the problem. That's what I'm doing with my KDE4/sound problems. Since I run LVM its easy for me to (re)create file systems using different formats - ext3, XFS, reiser or Btrfs configured for high-bandwidth. http://classic-web.archive.org/web/20040407211142/aurora.zemris.fer.hr/files... -- How inappropriate to call this planet `Earth' when it is quite clearly `Ocean'. -- Arthur C Clarke -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 11 May 2011 14:00:57 Anton Aylward wrote:
benefici@fastmail.fm said the following on 05/11/2011 05:28 AM:
My desktop PC (with openSUSE 11.4) does not shutdown completely at times.
This is happening to me as well, with a interesting variation. KDE4 is not saving the session on shut-down. I've tried logging out before shutting down; I've tried logging out, going to the text mode console. I go to 'init 3' and then I try unmounting the file systems one by one but find that KDE is still running.
I think this is different from my problem. KDE4 exits cleanly in my case. On the other hand, I have seen similar behaviour earlier and I believe it happened because I ran KDE4 applications in a KDE3 session. The KDE4 apps started kded4 which failed to exit on logging out. I had to manually kill kded4 with kill -9. I could see the stuck kded4 process after logging out with ps -fu $myuser I could not find a way around the problem so in the end gave up and removed all KDE3 packages. The problem does not occur in a clean KDE4 session.
I haven't seen lost files, but then I'm not saving large files as you are, Tom.
If I were, I'd start by checking the file systems - FSCK, free space. Free space might matter since a lack of it can cause problems with latency in allocation with some file systems that make use of fragmented blocks. I'd check logs. *ALWAYS* check logs! I'd see if its a problem with file closing or with file unmounting independently from the shutdown. Slice and dice and localise the problem. That's what I'm doing with my KDE4/sound problems.
Fsck runs without errors and free space does not seem to be a problem (more than 9 GB free on both of the file systems that are not umounted). Which logs should I check? There is hardly anything in /var/log/messages about a shutdown, and no errors at all even if the shutdown was incomplete (just checked the shutdown from yesterday evening). Are there any other logs? The problem clearly happens at shutdown time - some of the scripts are simply not executed. Unmounting manually works. Anyway, I find the behaviour of init quite stupid. If a file system was not successfully umounted then why still go on and power down the system? I think not even a sync is executed in such a case, based on the hundreds if not thousands of transactions to be replayed sometimes at next boot up. Tom -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2011-05-12 09:59, benefici@fastmail.fm wrote:
Which logs should I check? There is hardly anything in /var/log/messages about a shutdown, and no errors at all even if the shutdown was incomplete (just checked the shutdown from yesterday evening). Are there any other logs? The problem clearly happens at shutdown time - some of the scripts are simply not executed. Unmounting manually works.
No logs of this problem are possible. On one of the bugzillas I mentioned there is a procedure described about how to obtain the missing info. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk3LqsoACgkQtTMYHG2NR9VdkACeI5YYvYjGAsamYpt8vMj2eLcc 6IAAn3p/meNRbsWF3cS2JNpiT+P6ZyBZ =xpEH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
benefici@fastmail.fm said the following on 05/12/2011 03:59 AM:
On Wednesday 11 May 2011 14:00:57 Anton Aylward wrote:
benefici@fastmail.fm said the following on 05/11/2011 05:28 AM:
My desktop PC (with openSUSE 11.4) does not shutdown completely at times.
This is happening to me as well, with a interesting variation. KDE4 is not saving the session on shut-down. I've tried logging out before shutting down; I've tried logging out, going to the text mode console. I go to 'init 3' and then I try unmounting the file systems one by one but find that KDE is still running.
I think this is different from my problem. KDE4 exits cleanly in my case. On the other hand, I have seen similar behaviour earlier and I believe it happened because I ran KDE4 applications in a KDE3 session. The KDE4 apps started kded4 which failed to exit on logging out. I had to manually kill kded4 with kill -9. I could see the stuck kded4 process after logging out with ps -fu $myuser I could not find a way around the problem so in the end gave up and removed all KDE3 packages. The problem does not occur in a clean KDE4 session.
I've long since removed all KDE3 packages :-) The only one I miss is tickle. I wonder when that will be updated for KDE4? -- A good landing is one you can walk away from. A great landing is one from which the plane can take off again. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday, May 11, 2011 04:28 benefici@fastmail.fm wrote:
Hi, 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 problem? Tom
I had this same problem, but I'm using 11.3. After asking for help on this list and nothing coming up, I fell back to the old standard of checking the hardware. Come to find out that it was my video card causing all the problems. I was using the nVidia 256.53 straight from nVidia's website, but it wasn't the driver making any problems (my MOBO has nVidia chipsets and thus built-in video for my old monitor) because my system worked fine after I took out the video card and used the MOBO plug. I've finally graduated to the nVidia 270.41.06 driver and still it's working fine (turns out there just wasn't any need for me to 'upgrade' the driver since the newer one hasn't done anything better than the other one). Try unplugging one thing at a time on the MOBO. Maybe you guys also have some kind of hardware problem. -- "Properly read, the Bible is the most potent force for atheism ever conceived." -Isaac Asimov -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday, May 11, 2011 10:28:26 AM Insomniac wrote:
Try unplugging one thing at a time on the MOBO. Maybe you guys also have some kind of hardware problem.
Thought I should throw my own experiences in... I started having this problem when I upgraded to 11.4. In my case, it *always* hangs at "Turning off swap files". Worked fine in 11.3 on the same hardware. It hasn't been enough of an issue for me to hunt it down, but it seems like there's something going on that should be looked into. -Nick -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday, May 11, 2011 11:12:47 AM Nick LeRoy wrote:
On Wednesday, May 11, 2011 10:28:26 AM Insomniac wrote:
Try unplugging one thing at a time on the MOBO. Maybe you guys also have
some kind of hardware problem.
Thought I should throw my own experiences in... I started having this problem when I upgraded to 11.4. In my case, it *always* hangs at "Turning off swap files". Worked fine in 11.3 on the same hardware. It hasn't been enough of an issue for me to hunt it down, but it seems like there's something going on that should be looked into.
Oh, my swap is a 8G partition on a SCSI HD (same disk as the root f/s). Not sure if that's relevant or not... From /proc/scsi/scsi: Host: scsi6 Channel: 00 Id: 00 Lun: 00 Vendor: FUJITSU Model: MAU3073NP Rev: 0104 Type: Direct-Access ANSI SCSI revision: 03 Let me know if there's more than I can add. -Nick -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 11 May 2011 17:28:26 Insomniac wrote:
On Wednesday, May 11, 2011 04:28 benefici@fastmail.fm wrote:
Hi, 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 problem? Tom
I had this same problem, but I'm using 11.3.
After asking for help on this list and nothing coming up, I fell back to the old standard of checking the hardware.
Come to find out that it was my video card causing all the problems.
I was using the nVidia 256.53 straight from nVidia's website, but it wasn't the driver making any problems (my MOBO has nVidia chipsets and thus built-in video for my old monitor) because my system worked fine after I took out the video card and used the MOBO plug. I've finally graduated to the nVidia 270.41.06 driver and still it's working fine (turns out there just wasn't any need for me to 'upgrade' the driver since the newer one hasn't done anything better than the other one).
Try unplugging one thing at a time on the MOBO. Maybe you guys also have some kind of hardware problem.
Thanks for the suggestion. I also have an nvidia card and am using the 260.19.36 driver. Unfortunately I have no other graphic cards to replace it with. And also unfortunately (fortunately?) I don't have any other cards in my PC... I tried disabling desktop effects but that didn't help. Tom -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011-05-11 benefici offered the following:
Hi, 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 problem? Tom
Tom, 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 These seem to be pretty much the same as you describe. I never had the benefit of a "video" of the shutdown messages but I have a feeling your video information may be valuable in troubleshooting the above related bugs (which also affect ext4, and probably other FS types). In any event, if you add a comment to the 2nd bug (the 1st has been marked as a duplicate of the 2nd I believe) there may be a clue you can provide that helps resolve those, and possibly your problem. Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 11 May 2011 18:09:15 Richard Creighton wrote:
On 2011-05-11 benefici offered the following:
Hi, 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 problem? Tom
Tom,
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, Tom -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
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:
Hi, 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 problem? Tom
Tom,
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, Tom
....which is why I felt it pertinent, while a *manual* umount may not fail, the thing 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 the 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 would 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. Yes? That is why I suggested adding your comments to those bug reports because I don't believe that (your) observation has been explored. Carlos also mentioned a couple of other quite similar bugs, so your observation could clear 4 or more similar bugs *if* it can be determined why part of the shutdown script(s) aren't being executed, or otherwise fail. Richard -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2011/05/12 10:17 (GMT+0200) benefici@fastmail.fm composed:
On Wednesday 11 May 2011 18:09:15 Richard Creighton wrote:
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.
If by that you mean since 11.4 installation you performed no system updates, you may be wasting everyone's time with this thread. sysvinit and aaa_base have both been updated for problems with stuff in initscripts being skipped at startup. Maybe these same things are also being skipped on shutdown. Maybe parallel boot applies to shutdown as well as startup? You could try changing that to no in /etc/init.d/boot. cf. https://bugzilla.novell.com/show_bug.cgi?id=665720 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 12 May 2011 13:47:08 Felix Miata wrote:
On 2011/05/12 10:17 (GMT+0200) benefici@fastmail.fm composed:
On Wednesday 11 May 2011 18:09:15 Richard Creighton wrote:
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.
If by that you mean since 11.4 installation you performed no system updates, you may be wasting everyone's time with this thread. sysvinit and aaa_base have both been updated for problems with stuff in initscripts being skipped at startup. Maybe these same things are also being skipped on shutdown.
That's not what I meant. My system is up to date. What I meant is that in my case the problem is not triggered by an update.
Maybe parallel boot applies to shutdown as well as startup? You could try changing that to no in /etc/init.d/boot. cf. https://bugzilla.novell.com/show_bug.cgi?id=665720
Yes, that's my idea as well. I added the line RUN_PARALLEL="no" to /etc/init.d/halt right after the variable got set originally. Haven't tried shutting down that many times since but so far so good. Tom -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday, May 12, 2011 11:45:04 AM benefici@fastmail.fm wrote:
On Thursday 12 May 2011 13:47:08 Felix Miata wrote:
On 2011/05/12 10:17 (GMT+0200) benefici@fastmail.fm composed:
On Wednesday 11 May 2011 18:09:15 Richard Creighton wrote:
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.
If by that you mean since 11.4 installation you performed no system updates, you may be wasting everyone's time with this thread. sysvinit and aaa_base have both been updated for problems with stuff in initscripts being skipped at startup. Maybe these same things are also being skipped on shutdown.
That's not what I meant. My system is up to date. What I meant is that in my case the problem is not triggered by an update.
Maybe parallel boot applies to shutdown as well as startup? You could try changing that to no in /etc/init.d/boot. cf. https://bugzilla.novell.com/show_bug.cgi?id=665720
Yes, that's my idea as well. I added the line RUN_PARALLEL="no" to /etc/init.d/halt right after the variable got set originally. Haven't tried shutting down that many times since but so far so good. Tom Tom: Where did you add it. I'm not a programme but know how to add things. I'd like to see if it solves my problem.
Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2011-05-13 18:20, upscope wrote:
Yes, that's my idea as well. I added the line RUN_PARALLEL="no" to /etc/init.d/halt right after the variable got set originally. Haven't tried shutting down that many times since but so far so good. Tom Tom: Where did you add it. I'm not a programme but know how to add things. I'd like to see if it solves my problem.
The correct place is "/etc/sysconfig/boot". ## Type: yesno ## Default: yes # # Run all scripts or rather start/stop all services # which are independent from each other in parallel. # RUN_PARALLEL=yes Change to "no". You can also do it inside YaST. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk3NcL0ACgkQtTMYHG2NR9V1cACZAbfM+mRkeJOJoG82mI8gDACd JUoAnjV25gT4SDe77AKCqZlOEDLcCvW/ =GFK/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 13 May 2011 19:56:13 Carlos E. R. wrote:
On 2011-05-13 18:20, upscope wrote:
Yes, that's my idea as well. I added the line RUN_PARALLEL="no" to /etc/init.d/halt right after the variable got set originally. Haven't tried shutting down that many times since but so far so good. Tom
Tom: Where did you add it. I'm not a programme but know how to add things. I'd like to see if it solves my problem.
The correct place is "/etc/sysconfig/boot".
## Type: yesno ## Default: yes # # Run all scripts or rather start/stop all services # which are independent from each other in parallel. # RUN_PARALLEL=yes
Change to "no".
You can also do it inside YaST.
This is indeed the correct place to change the parameter. I changed the halt script instead (as described here: https://bugzilla.novell.com/show_bug.cgi?id=679671)) so that it only affects shutdown. Booting the system still runs in parallel. Tom -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2011-05-15 10:02, benefici@fastmail.fm wrote:
This is indeed the correct place to change the parameter. I changed the halt script instead (as described here: https://bugzilla.novell.com/show_bug.cgi?id=679671)) so that it only affects shutdown. Booting the system still runs in parallel.
Ah, that's a hack :-) - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk3P5SEACgkQtTMYHG2NR9V7egCfa8JH2VzyXskadIUVeWNSMgRZ wUsAn3Oiwo6Yh9oFY67kbiBDO6f8WSkz =MnLP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday, May 12, 2011 01:17:00 AM benefici@fastmail.fm wrote:
On Wednesday 11 May 2011 18:09:15 Richard Creighton wrote:
On 2011-05-11 benefici offered the following:
Hi, 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 problem? Tom
Tom,
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, Tom Take a look at Bug 619754 (https://bugzilla.novell.com/show_bug.cgi?id=619754)
This has been around for a long time. Started on 11.3 but still exists on clean install of 11.4 (2.6.37) and KDE 4.6. Sometimes like last week after a kernel upgrade, it worked five nights in a row and then back to same okd problem, its done that before. Not sure which program is causing it. There are a few thinks to try on the bug above, maybe they will help you! If one of them works, please post which one and I'll try it again. Good Luck -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 12 May 2011 21:41:56 upscope wrote:
On Thursday, May 12, 2011 01:17:00 AM benefici@fastmail.fm wrote:
On Wednesday 11 May 2011 18:09:15 Richard Creighton wrote:
On 2011-05-11 benefici offered the following:
Hi, 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 problem? Tom
Tom,
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, Tom
Take a look at Bug 619754 (https://bugzilla.novell.com/show_bug.cgi?id=619754)
This bug is different from mine. My problem is best described by https://bugzilla.novell.com/show_bug.cgi?id=679671 In your case all steps of the shutdown process are executed but the last step (i.e. powering down) fails. In my case some of the steps are not executed at times. But when they are then they work.
This has been around for a long time. Started on 11.3 but still exists on clean install of 11.4 (2.6.37) and KDE 4.6. Sometimes like last week after a kernel upgrade, it worked five nights in a row and then back to same okd problem, its done that before. Not sure which program is causing it. There are a few thinks to try on the bug above, maybe they will help you!
If one of them works, please post which one and I'll try it again.
Good Luck -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2011-05-11 11:28, benefici@fastmail.fm wrote:
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.
Bug 626580 - Failure to unmount the / partition Bug 679671 - 11.4 At shutdown or reboot reiserfs is not unmounted - causing replay of journal at startup And I think there is another one I forget. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk3K3nMACgkQtTMYHG2NR9WTAwCffbrIEX3xccjTWYC7pMcmCSG+ 40EAnA6UD5eQjJe5hnYwwblJ0o7OTGss =ydGQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 11 May 2011 21:07:31 Carlos E. R. wrote:
On 2011-05-11 11:28, benefici@fastmail.fm wrote:
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.
Bug 626580 - Failure to unmount the / partition Bug 679671 - 11.4 At shutdown or reboot reiserfs is not unmounted - causing replay of journal at startup
And I think there is another one I forget.
Thanks! Both bug reports are similar to my problem. I'm investigating... Tom -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Anton Aylward -
benefici＠fastmail.fm -
Carlos E. R. -
Felix Miata -
Insomniac -
Nick LeRoy -
Richard Creighton -
upscope