[opensuse] Hard drive problem after suspend to disk
I have a problem with suspend to disk after a kernel update under SUSE 10.1. Using kernel-default-2.6.16.13-4 there is no problem with my hard drive. With the updated kernel version 2.6.16.21-0.13 and all following versions (including 2.6.16.27-989.2 from the Build Service) loading of the boot loader and the linux kernel is very slow while resuming after suspend to disk. This seems to be a hard drive problem which also appeared on my system after a system freeze (where the operating system couldn't access the hard disk properly). Could it be that suspend to disk with the updated kernel leaves the hard drive in some improper state? Is there a solution to the problem? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 20 August 2007, Theo Wollenleben wrote:
I have a problem with suspend to disk after a kernel update under SUSE 10.1. Using kernel-default-2.6.16.13-4 there is no problem with my hard drive. With the updated kernel version 2.6.16.21-0.13 and all following versions (including 2.6.16.27-989.2 from the Build Service) loading of the boot loader and the linux kernel is very slow while resuming after suspend to disk. This seems to be a hard drive problem which also appeared on my system after a system freeze (where the operating system couldn't access the hard disk properly). Could it be that suspend to disk with the updated kernel leaves the hard drive in some improper state? Is there a solution to the problem?
I've seen this same (?) behaviour on upenSUSE 10.2 after a system freeze: GRUB won't load anymore after a hard reboot, or if it loads, only after a long while. No matter what you do, after certain freezes it simply won't load. The only way to get GRUB back is to use the installer CD and ask it to rewrite GRUB even though it won't see any problem with the bootloader or the disks. 10.2 kernel versions seems to have had no effect. I never suspend to disk, though, and I only have IDE drives. I don't think this is a hard disk issue: I had this same master/boot hard disk while on SUSE 9.3 and never saw this issue there after a system freeze. GRUB always came up equally fast and always loaded without hiccups. System freezes were much less common on SUSE 9.3, of course, but still happened a few times. I've also heard of others who have seen this same "GRUB won't load" behaviour on openSUSE 10.2 on totally different hardware. Regards, Tero Pesonen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon August 20 2007 14:30, Tero Pesonen wrote:
I don't think this is a hard disk issue: I had this same master/boot hard disk while on SUSE 9.3 and never saw this issue there after a system freeze. GRUB always came up equally fast and always loaded without hiccups. System freezes were much less common on SUSE 9.3, of course, but still happened a few times. I've also heard of others who have seen this same "GRUB won't load" behaviour on openSUSE 10.2 on totally different hardware.
Hi Tero, et al Just tossing in an observation... When we lose power up here (I live out in the sticks) before grub will load and allow the system to boot normally, I must *first* boot into rescue mode using a network install CD or installation DVD, etc., to (reiser)fsck each partition that was mounted when the system went down. When not properly shut down, the mounted partitions are left in a 'dirty' state. Until reset to 'clean' mode (as happens during a normal shutdown,) the affected partitions seem to mount only in Read Only mode, which is slow and wastes time since they should be checked and reset before booting again, anyway. regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 20 August 2007, Carl Hartung wrote:
On Mon August 20 2007 14:30, Tero Pesonen wrote:
I don't think this is a hard disk issue: I had this same master/boot hard disk while on SUSE 9.3 and never saw this issue there after a system freeze. GRUB always came up equally fast and always loaded without hiccups. System freezes were much less common on SUSE 9.3, of course, but still happened a few times. I've also heard of others who have seen this same "GRUB won't load" behaviour on openSUSE 10.2 on totally different hardware.
Hi Tero, et al
Just tossing in an observation...
When we lose power up here (I live out in the sticks) before grub will load and allow the system to boot normally, I must *first* boot into rescue mode using a network install CD or installation DVD, etc., to (reiser)fsck each partition that was mounted when the system went down.
Do you mean you do not use the built-in "check and fix an installation" feature found in the installation program, but rather run fsck manually from somewhere? If so, what exactly are the steps you take? I've found relying on the automatic tools takes a lot of time, as I have to initiate a new installation and then select to troubleshoot an existing installation. This means I have to enter all the data for a new network installation and the installer makes all the possible preparations etc. required to start installing openSUSE, which can take a lot of time. If I could go to some kind of rescue mode or similar, and enter the appropriate commands from a command line, I wouldn't have to go through all the stuff it takes to start a new installation--only to never start one, as I would probably only need to run the filesystem checks and put the partitions back into clean state. And not fetch gigabyte's worth of RPM data and load all possible kernel modules. Is this what you do? Thanks for any feedback on this. Tero Pesonen
When not properly shut down, the mounted partitions are left in a 'dirty' state.
Until reset to 'clean' mode (as happens during a normal shutdown,) the affected partitions seem to mount only in Read Only mode, which is slow and wastes time since they should be checked and reset before booting again, anyway.
regards,
Carl
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon August 20 2007 16:12, Tero Pesonen wrote:
Do you mean you do not use the built-in "check and fix an installation" feature found in the installation program, but rather run fsck manually from somewhere?
If so, what exactly are the steps you take? <snip>
Sorry, but I don't have time right now to write out each step. A good start would be to download the network installation .iso and burn it to CD. It can then be used to either install a system from the network *or* boot to rescue mode. This is well documented. Try the .pdf documentation or 'Google' or await further input from others here as I've got to take off now. Good luck! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 21 August 2007, Carl Hartung wrote:
On Mon August 20 2007 16:12, Tero Pesonen wrote:
Do you mean you do not use the built-in "check and fix an installation" feature found in the installation program, but rather run fsck manually from somewhere?
If so, what exactly are the steps you take?
<snip>
Sorry, but I don't have time right now to write out each step. A good start would be to download the network installation .iso and burn it to CD. It can then be used to either install a system from the network *or* boot to rescue mode.
This is well documented. Try the .pdf documentation or 'Google' or await further input from others here as I've got to take off now.
I'll see what I can find in the documentation. I'll ask more here if need be. Thanks, Tero Pesonen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-08-20 at 15:21 -0400, Carl Hartung wrote:
Hi Tero, et al
Just tossing in an observation...
When we lose power up here (I live out in the sticks) before grub will load and allow the system to boot normally, I must *first* boot into rescue mode using a network install CD or installation DVD, etc., to (reiser)fsck each partition that was mounted when the system went down.
The init scripts do that checking automatically on boot. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGy+eRtTMYHG2NR9URAqfmAJ4p2CSYXez192qrRrP+KasSTmJOOwCfdqIt 7qjPrrzl9jifvpUZg6Mh76o= =hoBi -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed August 22 2007 03:36, Carlos E. R. wrote:
When we lose power up here (I live out in the sticks) before grub will load and allow the system to boot normally, I must *first* boot into rescue mode using a network install CD or installation DVD, etc., to (reiser)fsck each partition that was mounted when the system went down.
The init scripts do that checking automatically on boot.
Not if the system is failing *at* the boot loader, which was the original topic of this thread. ;-) Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Carl Hartung -
Carlos E. R. -
Tero Pesonen -
Theo Wollenleben