Re: Kernel panic with hardware RAID
Thomas Lange wrote: On Mon, 03 Nov 2008 15:32:05 -0500, Ryan Steele [EMAIL PROTECTED] said: I'm using FAI 3.2.14 on my Ubuntu systems (booting the 2.6.24-21 kernel), and it all seems to work, except when I have a hardware RAID [ 81.860291] sd 0:0:0:1: [sdb] Attached SCSI disk [ 82.021455] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 82.085003] sd 0:0:0:1: Attached scsi generic sg1 type 0 [ 82.384012] Kernel panic - not syncing: Attempted to kill init! Hmm. It may be a kernel bug. Add the option debug to the kernel commands line, this may give you more output from the initrd. But if it's the kernel panics before the initrd is startet you have no chance to debug this. Than it's a problem of the kernel. I found the problem; the initrd didn't have all the necessary drivers for my card. I ended up updating the initrd so that it included those drivers. The error was definitely cryptic though... no mention anywhere that it was network related. Thanks for putting eyes on it. Ryan
Re: Kernel panic with hardware RAID
Ryan Steele wrote: Thomas Lange wrote: On Mon, 03 Nov 2008 15:32:05 -0500, Ryan Steele [EMAIL PROTECTED] said: I'm using FAI 3.2.14 on my Ubuntu systems (booting the 2.6.24-21 kernel), and it all seems to work, except when I have a hardware RAID [ 81.860291] sd 0:0:0:1: [sdb] Attached SCSI disk [ 82.021455] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 82.085003] sd 0:0:0:1: Attached scsi generic sg1 type 0 [ 82.384012] Kernel panic - not syncing: Attempted to kill init! Hmm. It may be a kernel bug. Add the option debug to the kernel commands line, this may give you more output from the initrd. But if it's the kernel panics before the initrd is startet you have no chance to debug this. Than it's a problem of the kernel. I found the problem; the initrd didn't have all the necessary drivers for my card. I ended up updating the initrd so that it included those drivers. The error was definitely cryptic though... no mention anywhere that it was network related. Thanks for putting eyes on it. Ryan Err, I left out a key word there. For my *network* card. -- Ryan Steele[EMAIL PROTECTED] Systems Administrator +1 215-825-2196 x758 AWeber Communications http://www.aweber.com
Re: Kernel panic with hardware RAID
Ryan Steele wrote: Thomas Lange wrote: On Mon, 03 Nov 2008 15:32:05 -0500, Ryan Steele [EMAIL PROTECTED] said: I'm using FAI 3.2.14 on my Ubuntu systems (booting the 2.6.24-21 kernel), and it all seems to work, except when I have a hardware RAID [ 81.860291] sd 0:0:0:1: [sdb] Attached SCSI disk [ 82.021455] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 82.085003] sd 0:0:0:1: Attached scsi generic sg1 type 0 [ 82.384012] Kernel panic - not syncing: Attempted to kill init! Hmm. It may be a kernel bug. Add the option debug to the kernel commands line, this may give you more output from the initrd. But if it's the kernel panics before the initrd is startet you have no chance to debug this. Than it's a problem of the kernel. I found the problem; the initrd didn't have all the necessary drivers for my card. I ended up updating the initrd so that it included those drivers. The error was definitely cryptic though... no mention anywhere that it was network related. Thanks for putting eyes on it. Ryan Err, I left out a key word there. For my *network* card. Oh well, so this was actually not related to the missing partition tables at all? That just means it can't boot off of NFS, and thus panics? Best, Michael pgpGm7Nblqh5Y.pgp Description: PGP signature
Re: Kernel panic with hardware RAID
On Mon, 03 Nov 2008 15:32:05 -0500, Ryan Steele [EMAIL PROTECTED] said: I'm using FAI 3.2.14 on my Ubuntu systems (booting the 2.6.24-21 kernel), and it all seems to work, except when I have a hardware RAID [ 81.860291] sd 0:0:0:1: [sdb] Attached SCSI disk [ 82.021455] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 82.085003] sd 0:0:0:1: Attached scsi generic sg1 type 0 [ 82.384012] Kernel panic - not syncing: Attempted to kill init! Hmm. It may be a kernel bug. Add the option debug to the kernel commands line, this may give you more output from the initrd. But if it's the kernel panics before the initrd is startet you have no chance to debug this. Than it's a problem of the kernel. -- regards Thomas
Re: Kernel panic with hardware RAID
Thomas Lange wrote: On Mon, 03 Nov 2008 15:32:05 -0500, Ryan Steele [EMAIL PROTECTED] said: I'm using FAI 3.2.14 on my Ubuntu systems (booting the 2.6.24-21 kernel), and it all seems to work, except when I have a hardware RAID [ 81.860291] sd 0:0:0:1: [sdb] Attached SCSI disk [ 82.021455] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 82.085003] sd 0:0:0:1: Attached scsi generic sg1 type 0 [ 82.384012] Kernel panic - not syncing: Attempted to kill init! Hmm. It may be a kernel bug. Add the option debug to the kernel commands line, this may give you more output from the initrd. But if it's the kernel panics before the initrd is startet you have no chance to debug this. Than it's a problem of the kernel. This was with debug on, unfortunately. I'm going to rebuild my FAI setup from scratch, hoping that maybe I zigged where I should have zagged at some point during the setup. I'll let you know how it goes. Thanks for your input, Ryan
Kernel panic with hardware RAID
Hey folks, I'm using FAI 3.2.14 on my Ubuntu systems (booting the 2.6.24-21 kernel), and it all seems to work, except when I have a hardware RAID with no existing partition table. When the client PXE boots the kernel that FAI puts in to the TFTP directory, I get kernel panics, where the kernel complains that it can't find partition tables on any of the arrays. I don't have this problem testing in my VM's which have no hardware RAID. Has anyone else seen this? If it matters, I'm using setup-storage. I can provide a logfile of the boot process that I captured via a serial console and minicom, if that would be useful. But everything looks normal up until it can't find the partition tables on the arrays and panics. Thanks, Ryan
