Boot failure after Kernel update
Dear list, I've installed the latest kernel patches (announced last Wednesday) today on several machines and one of them fails to boot now. We probably won't have physical access to this machine until Monday so I currently have no idea what happened or where the boot process stops. The machine in questions is running SuSE 9.0. Another SuSE 9.0 machine, one SuSE 9.1 and three SuSE 9.2 machines did not show this problem and booted up fine after the update. The working 9.0 machine is basically identically configured as the failing one but has different hardware. The working machine has a single P4 CPU, 1 GB RAM and a single 160 GB parallel ATA disk. The failing machine has 2 Xeons, 4 GB RAM and 4 S-ATA disks, 160 GB each, in a RAID 0+1 attached to a 3ware Escalade RAID Controller. Both machines are running reiserfs and a SMP kernel. In case anybody else has experienced this problem any information about it would be appreciated so that we can get up the machine again as quickly as possible on Monday. Best regards, Stefan
Hello,
The working 9.0 machine is basically identically configured as the failing one but has different hardware. The working machine has a single P4 CPU, 1 GB RAM and a single 160 GB parallel ATA disk. The failing machine has 2 Xeons, 4 GB RAM and 4 S-ATA disks, 160 GB each, in a RAID 0+1 attached to a 3ware Escalade RAID Controller. Both machines are running reiserfs and a SMP kernel.
In case anybody else has experienced this problem any information about it would be appreciated so that we can get up the machine again as quickly as possible on Monday.
have you run lilo ?? -- MfG / Regards Günther J. Niederwimmer
On Saturday 04 December 2004 17:51, Günther J. Niederwimmer wrote:
Hello,
The working 9.0 machine is basically identically configured as the failing one but has different hardware. The working machine has a single P4 CPU, 1 GB RAM and a single 160 GB parallel ATA disk. The failing machine has 2 Xeons, 4 GB RAM and 4 S-ATA disks, 160 GB each, in a RAID 0+1 attached to a 3ware Escalade RAID Controller. Both machines are running reiserfs and a SMP kernel.
In case anybody else has experienced this problem any information about it would be appreciated so that we can get up the machine again as quickly as possible on Monday.
have you run lilo ??
No, I'm using grub. CU, Stefan
Well, I think it is very sec.-realted! When kernel update causes system crashes and I had to re-install the 1-year (?) old kernel or to sit about two days to find out where is the problem?? I'hv had s.th. simular with SuSE 9.1 incl all updates from them (and nothing else)! It started when I unpluged my usb-mouse and plugged it with an (working) adapter into ps/2 'plugin'. First this mouse did not work again, neither there nor as normal usb-mouse (..?), second within yast the module select-mouse device crashed immediately after starting and from here I started a two days orgy of repairing, re-installing, updating, .. using yast (org. cd) and sax2 with lots of strange messages inbetween: harddisk totally demaged, usb and pci not working, no X11 working (boot stopped t init 5), totally damaged picture, In between I thought I had to trash this pc. Now it is working again, I re-installed the old cd-kernel (2.6.4-52) and not 2.6.5-7.111.5. But may be it is the module-init-tool, it came together with the new kernel. By the way does any body can recommand a good Debian book? Bye, Carl Am Samstag, 4. Dezember 2004 14:34 schrieb Stefan Proels:
Dear list,
I've installed the latest kernel patches (announced last Wednesday) today on several machines and one of them fails to boot now. We probably won't have physical access to this machine until Monday so I currently have no idea what happened or where the boot process stops.
The machine in questions is running SuSE 9.0. Another SuSE 9.0 machine, one SuSE 9.1 and three SuSE 9.2 machines did not show this problem and booted up fine after the update.
The working 9.0 machine is basically identically configured as the failing one but has different hardware. The working machine has a single P4 CPU, 1 GB RAM and a single 160 GB parallel ATA disk. The failing machine has 2 Xeons, 4 GB RAM and 4 S-ATA disks, 160 GB each, in a RAID 0+1 attached to a 3ware Escalade RAID Controller. Both machines are running reiserfs and a SMP kernel.
In case anybody else has experienced this problem any information about it would be appreciated so that we can get up the machine again as quickly as possible on Monday.
Best regards, Stefan
As several others (german suse linux list) had problems with different usd devices (mouse, extrenal hd) I assumethat you better do not plug anything into usb. I hardly convinced that this is the problem - as far as the dummy user is always guilty.. Carl Am Samstag, 4. Dezember 2004 14:34 schrieb Stefan Proels:
Dear list,
I've installed the latest kernel patches (announced last Wednesday) today on several machines and one of them fails to boot now. We probably won't have physical access to this machine until Monday so I currently have no idea what happened or where the boot process stops.
The machine in questions is running SuSE 9.0. Another SuSE 9.0 machine, one SuSE 9.1 and three SuSE 9.2 machines did not show this problem and booted up fine after the update.
The working 9.0 machine is basically identically configured as the failing one but has different hardware. The working machine has a single P4 CPU, 1 GB RAM and a single 160 GB parallel ATA disk. The failing machine has 2 Xeons, 4 GB RAM and 4 S-ATA disks, 160 GB each, in a RAID 0+1 attached to a 3ware Escalade RAID Controller. Both machines are running reiserfs and a SMP kernel.
In case anybody else has experienced this problem any information about it would be appreciated so that we can get up the machine again as quickly as possible on Monday.
Best regards, Stefan
Give this one a try. Add the boot parameter "barrier=off" at the grub command line. Some SATA disks need it. It solved a booting problem for me a few months ago. Roel Vestjens On Sunday 05 December 2004 15:59, Carl A. Schreiber wrote:
As several others (german suse linux list) had problems with different usd devices (mouse, extrenal hd) I assumethat you better do not plug anything into usb. I hardly convinced that this is the problem - as far as the dummy user is always guilty..
Carl
Am Samstag, 4. Dezember 2004 14:34 schrieb Stefan Proels:
Dear list,
I've installed the latest kernel patches (announced last Wednesday) today on several machines and one of them fails to boot now. We probably won't have physical access to this machine until Monday so I currently have no idea what happened or where the boot process stops.
The machine in questions is running SuSE 9.0. Another SuSE 9.0 machine, one SuSE 9.1 and three SuSE 9.2 machines did not show this problem and booted up fine after the update.
The working 9.0 machine is basically identically configured as the failing one but has different hardware. The working machine has a single P4 CPU, 1 GB RAM and a single 160 GB parallel ATA disk. The failing machine has 2 Xeons, 4 GB RAM and 4 S-ATA disks, 160 GB each, in a RAID 0+1 attached to a 3ware Escalade RAID Controller. Both machines are running reiserfs and a SMP kernel.
In case anybody else has experienced this problem any information about it would be appreciated so that we can get up the machine again as quickly as possible on Monday.
Best regards, Stefan
participants (4)
-
Carl A. Schreiber -
Günther J. Niederwimmer -
R.G.J. Vestjens -
Stefan Proels