RESOLVED: Re: 3ware 9550 SATA RAID controller problems
Hi all, I finally got around to figuring out a fix for this problem and wanted to post a follow up in case someone else has this problem. The fix is to add the disk device driver modules to the yaird config file. In my case I added to /etc/yaird/Default.cfg MODULE ata_piix MODULE 3w_9xxx following the existing module defs for the input devices. I then rebuilt the initrd.img with: $ yaird -o /boot/initrd.img-test # based on the current running kernel $ cd /boot $ rm initrd.img # a symlink, otherwise move it $ ln -s initrd.img-test initrd.img $ reboot If your system has a problem booting, then reboot to you backup kernel, (You DO have a backup kernel, don't you? otherwise you are on your own). Then remove the symlink and link in your original initrd.img and reboot. You want to change this back so when you make changes to your config you are rebuilding against the current running kernel config not your backup, or you can read man yaird and try other options and your on your own again ;) I tried to load JUST the 3w_9xxx device above, but that reordered the drives and initrd then tried to mount root from the wrong disk, so it is important that you load all the disk devices in the same order as your running kernel or you will get unexpected results. I hope this helps someone else. -Steve Stephen Woodbridge wrote: Interesting, I have found another list thread in Germany with this same problem only I can't read much German. The two suggestions I was able to make out were: 1) try adding a sleep in the boot scripts to give the raid array more time to initialize at startup. 2) effectively the same, by setting the fstab to "noauto" and adding appropriate /etc/rc?.d/S99mountraid scripts to check the array and mount it. Unfortunately, I could not determine if either of these were successful. The German thread is at https://mlists.in-berlin.de/pipermail/linux-l/msg51879.html My other thought was to load the 3w-9xxx sooner in /etc/modules so the raid would be recognized and may initialized sooner while the other modules were loading. I'll give this a try as soon as I can reboot. -Steve Stephen Woodbridge wrote: Hi all, I have not been able to find anything useful on the problem described below. I could really use some ideas or suggestions. The one thing I have not tried is to build the driver based on the 3ware source, but I have not had much luck building a kernel that works :( I'm willing to try that again if I can get some detailed steps to do that, maybe based on modifying the existing linux-image-2.6.15-1-em64t-p4-smp and config. Thanks, -Steve Stephen Woodbridge wrote: OK, things are very close to completely working. Running the sid linux-image-2.6.15-1-em64t-p4-smp Have the ATAPI CDROM working :) Recognizing the 3ware 9550 raid card. Have built an ext3 filesystem and it mounts and read writes seem to be fine. BUT there is a problem on reboot. The fsck check of the /dev/sdb1 fails to read the superblock and throws the boot process into maintenance mode. The device is fine and fsck reports that it is clean. and a ^D whether I fsck it or not brings up the system and the disk is fine. I seems like it might be a timing problem in that the array is not fully online before the system goes to check it. Or I didn't do something right when I partitioned and made the filesystem. Boot messages are: ... scsi2 : 3ware 9000 Storage Controller 3w-9xxx: scsi2: Found a 3ware 9000 Storage Controller at 0xda20, IRQ: 18. input: ImPs ... 3w-9xxx: scsi2: Firmware FE9X 3/02.00.012, BIOS BE9X 3.01.00.024, Ports 8. Vendor: AMCC Model: 9550X-8LP DISK Rev 3.02 Type: Direct-Access ANSI SCSI revision: 03 SCSI device sdb: 3417817088 512-byte hdwr sectors (1749922 MB) SCSI device sdb: drive cache: none SCSI device sdb: 3417817088 512-byte hdwr sectors (1749922 MB) SCSI device sdb: drive cache: none sdb: sdb1 sd 2:0:0:0: Attached scsi disk sdb All modules loaded. Checking all file systems... fsck 1.37 (21-Mar-2005) fsck.ext3: No such file or directory while trying to open /dev/sdb1 /dev/sdb1: The superblock could not be read or does not describe a correct ext2 filesystem. ... [and suggests trying] e2fsck -b 8193 and prompts for the root password to enter maintenence mode. So trying the above reports: $ e2fsck -b 8193 /dev/sdb1 e2fsck 1.37 (21-Mark-2005) e2fsck: Bad magic number in super-block while trying to open /dev/sdb1 The superblock could not be read or does not describe a correct ext2 filesystem. ... [and suggests trying] e2fsck -b 8193 (none):~# fsck -v /dev/sdb1 fsck 1.37 (21-Mark-2005) e2fsck 1.37 (21-Mark-2005) /dev/sdb1: clean, 11/213614592 files, 6711696/427226577 blocks (none):~# fsck -v -f /dev/sdb1 [checks the disk and reports no problems] ^D system continues to boot and everything looks fine. I think the key to this problem is likely the error message: fsck.ext3: No such file or directory while trying to
Re: 3ware 9550 SATA RAID controller problems
Interesting, I have found another list thread in Germany with this same problem only I can't read much German. The two suggestions I was able to make out were: 1) try adding a sleep in the boot scripts to give the raid array more time to initialize at startup. 2) effectively the same, by setting the fstab to "noauto" and adding appropriate /etc/rc?.d/S99mountraid scripts to check the array and mount it. Unfortunately, I could not determine if either of these were successful. The German thread is at https://mlists.in-berlin.de/pipermail/linux-l/msg51879.html My other thought was to load the 3w-9xxx sooner in /etc/modules so the raid would be recognized and may initialized sooner while the other modules were loading. I'll give this a try as soon as I can reboot. -Steve Stephen Woodbridge wrote: Hi all, I have not been able to find anything useful on the problem described below. I could really use some ideas or suggestions. The one thing I have not tried is to build the driver based on the 3ware source, but I have not had much luck building a kernel that works :( I'm willing to try that again if I can get some detailed steps to do that, maybe based on modifying the existing linux-image-2.6.15-1-em64t-p4-smp and config. Thanks, -Steve Stephen Woodbridge wrote: OK, things are very close to completely working. Running the sid linux-image-2.6.15-1-em64t-p4-smp Have the ATAPI CDROM working :) Recognizing the 3ware 9550 raid card. Have built an ext3 filesystem and it mounts and read writes seem to be fine. BUT there is a problem on reboot. The fsck check of the /dev/sdb1 fails to read the superblock and throws the boot process into maintenance mode. The device is fine and fsck reports that it is clean. and a ^D whether I fsck it or not brings up the system and the disk is fine. I seems like it might be a timing problem in that the array is not fully online before the system goes to check it. Or I didn't do something right when I partitioned and made the filesystem. Boot messages are: ... scsi2 : 3ware 9000 Storage Controller 3w-9xxx: scsi2: Found a 3ware 9000 Storage Controller at 0xda20, IRQ: 18. input: ImPs ... 3w-9xxx: scsi2: Firmware FE9X 3/02.00.012, BIOS BE9X 3.01.00.024, Ports 8. Vendor: AMCC Model: 9550X-8LP DISK Rev 3.02 Type: Direct-Access ANSI SCSI revision: 03 SCSI device sdb: 3417817088 512-byte hdwr sectors (1749922 MB) SCSI device sdb: drive cache: none SCSI device sdb: 3417817088 512-byte hdwr sectors (1749922 MB) SCSI device sdb: drive cache: none sdb: sdb1 sd 2:0:0:0: Attached scsi disk sdb All modules loaded. Checking all file systems... fsck 1.37 (21-Mar-2005) fsck.ext3: No such file or directory while trying to open /dev/sdb1 /dev/sdb1: The superblock could not be read or does not describe a correct ext2 filesystem. ... [and suggests trying] e2fsck -b 8193 and prompts for the root password to enter maintenence mode. So trying the above reports: $ e2fsck -b 8193 /dev/sdb1 e2fsck 1.37 (21-Mark-2005) e2fsck: Bad magic number in super-block while trying to open /dev/sdb1 The superblock could not be read or does not describe a correct ext2 filesystem. ... [and suggests trying] e2fsck -b 8193 (none):~# fsck -v /dev/sdb1 fsck 1.37 (21-Mark-2005) e2fsck 1.37 (21-Mark-2005) /dev/sdb1: clean, 11/213614592 files, 6711696/427226577 blocks (none):~# fsck -v -f /dev/sdb1 [checks the disk and reports no problems] ^D system continues to boot and everything looks fine. I think the key to this problem is likely the error message: fsck.ext3: No such file or directory while trying to open /dev/sdb1 above. Is it not finding the executable fsck.ext3 or the device /dev/sdb1?? fsck.ext3 is in the /sbin directory with its ilk. -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 3ware 9550 SATA RAID controller problems
Could be caused by having udev installed? Could it be interfering with the creation of /dev devices in some way? I'm reaching for straws here. -Steve Stephen Woodbridge wrote: Hi Clive, Thanks this sounds like it might do it. I tried it but no luck yet. I some more details below, maybe I missed an important module. I'm running a Sarge system with the sid kernel and backported yaird. /etc/modprobe.d/libata options libata atapi_enabled=1 /etc/mkinitrd/modules # has nothing [EMAIL PROTECTED]:~$ cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file should contain the names of kernel modules that are # to be loaded at boot time, one per line. Comments begin with # a "#", and everything on the line after them are ignored. ide-cd ide-disk ide-generic psmouse sd_mod scsi_mod sg sr_mod libata ata_piix 3w-9xxx isofs mbcache jbd cdrom [EMAIL PROTECTED]:~$ lsmod Module Size Used by ipv6 279168 16 parport_pc 41712 0 parport43532 1 parport_pc floppy 71688 0 pcspkr 6664 0 i2c_i801 13844 0 i2c_core 27264 1 i2c_i801 i6300esb 12072 0 uhci_hcd 36256 0 shpchp 49184 0 pci_hotplug16260 1 shpchp ehci_hcd 36360 0 e1000 106164 0 tsdev 12928 0 isofs 39936 0 3w_9xxx38560 1 sr_mod 22308 0 sg 42032 0 psmouse40196 0 ide_generic 5760 0 [permanent] ide_disk 21120 0 ide_cd 44704 0 cdrom 40632 2 sr_mod,ide_cd ext3 135056 6 jbd63016 1 ext3 mbcache15240 1 ext3 sd_mod 22784 9 ata_piix 14852 6 libata 61336 1 ata_piix scsi_mod 151288 5 3w_9xxx,sr_mod,sg,sd_mod,libata generic 9732 0 [permanent] ide_core 147064 4 ide_generic,ide_disk,ide_cd,generic evdev 16128 0 Here are the boot up messages: ... Calculating module dependencies... done. Loading modules... ide-cd ide-disk ide-generic ide0: I/O resource 0x1F0-0x1F7 not free. ide0: ports already in use, skipping probe ide1: I/O resource 0x170-0x177 not free. ide1: ports already in use, skipping probe psmouse sd_mod scsi_mod sg 0:0:1:0: Attached scsi generic sg0 type 5 sd 1:0:0:0: Attached scsi generic sg1 type 0 sr_mod sr0: scsi3-mmc drive: 24x/24x cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 libata ata_piix 3w-9xxx 3ware 9000 Storage Controller device driver for Linux v2.26.02.004. GSI 18 sharing vector 0xB9 and IRQ 18 ACPI: PCI Interrupt :03:02.0[A] -> GSI 72 (level, low) -> IRQ 18 input: ImPS/2 Generic Wheel Mouse as /class/input/input1 scsi2 : 3ware 9000 Storage Controller 3w-9xxx: scsi2: Found a 3ware 9000 Storage Controller at 0xda20, IRQ: 18. 3w-9xxx: scsi2: Firmware FE9X 3.02.00.012, BIOS BE9X 3.01.00.024, Ports: 8. Vendor: AMCC Model: 9550SX-8LP DISK Rev: 3.02 Type: Direct-Access ANSI SCSI revision: 03 SCSI device sdb: 3417817088 512-byte hdwr sectors (1749922 MB) SCSI device sdb: drive cache: none SCSI device sdb: 3417817088 512-byte hdwr sectors (1749922 MB) SCSI device sdb: drive cache: none sdb: sdb1 sd 2:0:0:0: Attached scsi disk sdb sd 2:0:0:0: Attached scsi generic sg2 type 0 isofs mbcache jbd cdrom All modules loaded. Checking all file systems... fsck 1.37 (21-Mar-2005) fsck.ext3: No such file or directory while trying to open /dev/sdb1 /dev/sdb1: The superblock cound not be read or does not describe a correct ext2 filesystem. ... [and suggests trying] e2fsck -b 8193 and prompts for the root password to enter maintenence mode. All of the other ext3 partition that are on the system disk had no problem. It is only trying to access the 3ware array. I hope this sheds more like on the problem. -Steve Clive Menzies wrote: Stephen Woodbridge wrote: Hi all, I have not been able to find anything useful on the problem described below. I could really use some ideas or suggestions. The one thing I have not tried is to build the driver based on the 3ware source, but I have not had much luck building a kernel that works :( I'm willing to try that again if I can get some detailed steps to do that, maybe based on modifying the existing linux-image-2.6.15-1-em64t-p4-smp and config. Thanks, -Steve Stephen Woodbridge wrote: OK, things are very close to completely working. Running the sid linux-image-2.6.15-1-em64t-p4-smp Have the ATAPI CDROM working :) Recognizing the 3ware 9550 raid card. Have built an ext3 filesystem and it mounts and read writes seem to be fine. BUT there is a problem on reboot. The fsck check of the /dev/sdb1 fails to read the superblock and thro
Re: 3ware 9550 SATA RAID controller problems
Clive, Thanks for the suggestions, I really appreciate it. The 3ware is a pretty mature HW raid card, I would not try this with a Promise. I have an earlier PATA 3ware card in an older server with no problems and the card is working great except this reboot problem. -Steve Clive Menzies wrote: On (11/01/06 14:16), Stephen Woodbridge wrote: Thanks this sounds like it might do it. I tried it but no luck yet. I some more details below, maybe I missed an important module. I'm running a Sarge system with the sid kernel and backported yaird. /etc/modprobe.d/libata options libata atapi_enabled=1 /etc/mkinitrd/modules # has nothing [EMAIL PROTECTED]:~$ cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file should contain the names of kernel modules that are # to be loaded at boot time, one per line. Comments begin with # a "#", and everything on the line after them are ignored. ide-cd ide-disk ide-generic psmouse sd_mod scsi_mod sg sr_mod libata ata_piix 3w-9xxx isofs mbcache jbd cdrom This all looks OK AFAICT. However, I don't know much about h/w raid or even whether the card in question is a 'grown up' RAID card or a 'quasi raid' card. There are cheap 'RAID' controllers that don't provide full RAID capability, under Linux at any rate - I'm no techie and this is what I've picked up from the list and from my own experience with a Promise card. I would disable H/W raid and use software RAID in Debian by installing the mdadm package. I've got it working on a number of servers (SATA and IDE), faultlessly. The only problem I've had is that some kernels don't load the requisite Sata modules before the boot process tries to check the disks, hence putting them in /etc/modules. I put some brief notes up but the links therein are (or were) very useful. http://www.clivemenzies.co.uk/selfhelp/FileServer_Install_manual.html Sorry, I can't be more help. Regards Clive -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 3ware 9550 SATA RAID controller problems
On (11/01/06 14:16), Stephen Woodbridge wrote: > Thanks this sounds like it might do it. I tried it but no luck yet. I > some more details below, maybe I missed an important module. > > I'm running a Sarge system with the sid kernel and backported yaird. > > /etc/modprobe.d/libata >options libata atapi_enabled=1 > > /etc/mkinitrd/modules ># has nothing > > [EMAIL PROTECTED]:~$ cat /etc/modules > # /etc/modules: kernel modules to load at boot time. > # > # This file should contain the names of kernel modules that are > # to be loaded at boot time, one per line. Comments begin with > # a "#", and everything on the line after them are ignored. > > ide-cd > ide-disk > ide-generic > psmouse > sd_mod > scsi_mod > sg > sr_mod > libata > ata_piix > 3w-9xxx > isofs > mbcache > jbd > cdrom This all looks OK AFAICT. However, I don't know much about h/w raid or even whether the card in question is a 'grown up' RAID card or a 'quasi raid' card. There are cheap 'RAID' controllers that don't provide full RAID capability, under Linux at any rate - I'm no techie and this is what I've picked up from the list and from my own experience with a Promise card. I would disable H/W raid and use software RAID in Debian by installing the mdadm package. I've got it working on a number of servers (SATA and IDE), faultlessly. The only problem I've had is that some kernels don't load the requisite Sata modules before the boot process tries to check the disks, hence putting them in /etc/modules. I put some brief notes up but the links therein are (or were) very useful. http://www.clivemenzies.co.uk/selfhelp/FileServer_Install_manual.html Sorry, I can't be more help. Regards Clive -- www.clivemenzies.co.uk ... ...strategies for business -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 3ware 9550 SATA RAID controller problems
Hi Clive, Thanks this sounds like it might do it. I tried it but no luck yet. I some more details below, maybe I missed an important module. I'm running a Sarge system with the sid kernel and backported yaird. /etc/modprobe.d/libata options libata atapi_enabled=1 /etc/mkinitrd/modules # has nothing [EMAIL PROTECTED]:~$ cat /etc/modules # /etc/modules: kernel modules to load at boot time. # # This file should contain the names of kernel modules that are # to be loaded at boot time, one per line. Comments begin with # a "#", and everything on the line after them are ignored. ide-cd ide-disk ide-generic psmouse sd_mod scsi_mod sg sr_mod libata ata_piix 3w-9xxx isofs mbcache jbd cdrom [EMAIL PROTECTED]:~$ lsmod Module Size Used by ipv6 279168 16 parport_pc 41712 0 parport43532 1 parport_pc floppy 71688 0 pcspkr 6664 0 i2c_i801 13844 0 i2c_core 27264 1 i2c_i801 i6300esb 12072 0 uhci_hcd 36256 0 shpchp 49184 0 pci_hotplug16260 1 shpchp ehci_hcd 36360 0 e1000 106164 0 tsdev 12928 0 isofs 39936 0 3w_9xxx38560 1 sr_mod 22308 0 sg 42032 0 psmouse40196 0 ide_generic 5760 0 [permanent] ide_disk 21120 0 ide_cd 44704 0 cdrom 40632 2 sr_mod,ide_cd ext3 135056 6 jbd63016 1 ext3 mbcache15240 1 ext3 sd_mod 22784 9 ata_piix 14852 6 libata 61336 1 ata_piix scsi_mod 151288 5 3w_9xxx,sr_mod,sg,sd_mod,libata generic 9732 0 [permanent] ide_core 147064 4 ide_generic,ide_disk,ide_cd,generic evdev 16128 0 Here are the boot up messages: ... Calculating module dependencies... done. Loading modules... ide-cd ide-disk ide-generic ide0: I/O resource 0x1F0-0x1F7 not free. ide0: ports already in use, skipping probe ide1: I/O resource 0x170-0x177 not free. ide1: ports already in use, skipping probe psmouse sd_mod scsi_mod sg 0:0:1:0: Attached scsi generic sg0 type 5 sd 1:0:0:0: Attached scsi generic sg1 type 0 sr_mod sr0: scsi3-mmc drive: 24x/24x cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.20 libata ata_piix 3w-9xxx 3ware 9000 Storage Controller device driver for Linux v2.26.02.004. GSI 18 sharing vector 0xB9 and IRQ 18 ACPI: PCI Interrupt :03:02.0[A] -> GSI 72 (level, low) -> IRQ 18 input: ImPS/2 Generic Wheel Mouse as /class/input/input1 scsi2 : 3ware 9000 Storage Controller 3w-9xxx: scsi2: Found a 3ware 9000 Storage Controller at 0xda20, IRQ: 18. 3w-9xxx: scsi2: Firmware FE9X 3.02.00.012, BIOS BE9X 3.01.00.024, Ports: 8. Vendor: AMCC Model: 9550SX-8LP DISK Rev: 3.02 Type: Direct-Access ANSI SCSI revision: 03 SCSI device sdb: 3417817088 512-byte hdwr sectors (1749922 MB) SCSI device sdb: drive cache: none SCSI device sdb: 3417817088 512-byte hdwr sectors (1749922 MB) SCSI device sdb: drive cache: none sdb: sdb1 sd 2:0:0:0: Attached scsi disk sdb sd 2:0:0:0: Attached scsi generic sg2 type 0 isofs mbcache jbd cdrom All modules loaded. Checking all file systems... fsck 1.37 (21-Mar-2005) fsck.ext3: No such file or directory while trying to open /dev/sdb1 /dev/sdb1: The superblock cound not be read or does not describe a correct ext2 filesystem. ... [and suggests trying] e2fsck -b 8193 and prompts for the root password to enter maintenence mode. All of the other ext3 partition that are on the system disk had no problem. It is only trying to access the 3ware array. I hope this sheds more like on the problem. -Steve Clive Menzies wrote: Stephen Woodbridge wrote: Hi all, I have not been able to find anything useful on the problem described below. I could really use some ideas or suggestions. The one thing I have not tried is to build the driver based on the 3ware source, but I have not had much luck building a kernel that works :( I'm willing to try that again if I can get some detailed steps to do that, maybe based on modifying the existing linux-image-2.6.15-1-em64t-p4-smp and config. Thanks, -Steve Stephen Woodbridge wrote: OK, things are very close to completely working. Running the sid linux-image-2.6.15-1-em64t-p4-smp Have the ATAPI CDROM working :) Recognizing the 3ware 9550 raid card. Have built an ext3 filesystem and it mounts and read writes seem to be fine. BUT there is a problem on reboot. The fsck check of the /dev/sdb1 fails to read the superblock and throws the boot process into maintenance mode. The device is fine and fsck reports that it is clean. and a ^D whether I fsck it or not brings up the system and the disk is fine. I s
Re: 3ware 9550 SATA RAID controller problems
Stephen Woodbridge wrote: Hi all, I have not been able to find anything useful on the problem described below. I could really use some ideas or suggestions. The one thing I have not tried is to build the driver based on the 3ware source, but I have not had much luck building a kernel that works :( I'm willing to try that again if I can get some detailed steps to do that, maybe based on modifying the existing linux-image-2.6.15-1-em64t-p4-smp and config. Thanks, -Steve Stephen Woodbridge wrote: OK, things are very close to completely working. Running the sid linux-image-2.6.15-1-em64t-p4-smp Have the ATAPI CDROM working :) Recognizing the 3ware 9550 raid card. Have built an ext3 filesystem and it mounts and read writes seem to be fine. BUT there is a problem on reboot. The fsck check of the /dev/sdb1 fails to read the superblock and throws the boot process into maintenance mode. The device is fine and fsck reports that it is clean. and a ^D whether I fsck it or not brings up the system and the disk is fine. I seems like it might be a timing problem in that the array is not fully online before the system goes to check it. Or I didn't do something right when I partitioned and made the filesystem. I had a similar problem and found putting libata and the sata drivers in /etc/modules solved the problem. Regards Clive -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 3ware 9550 SATA RAID controller problems
Hi all, I have not been able to find anything useful on the problem described below. I could really use some ideas or suggestions. The one thing I have not tried is to build the driver based on the 3ware source, but I have not had much luck building a kernel that works :( I'm willing to try that again if I can get some detailed steps to do that, maybe based on modifying the existing linux-image-2.6.15-1-em64t-p4-smp and config. Thanks, -Steve Stephen Woodbridge wrote: OK, things are very close to completely working. Running the sid linux-image-2.6.15-1-em64t-p4-smp Have the ATAPI CDROM working :) Recognizing the 3ware 9550 raid card. Have built an ext3 filesystem and it mounts and read writes seem to be fine. BUT there is a problem on reboot. The fsck check of the /dev/sdb1 fails to read the superblock and throws the boot process into maintenance mode. The device is fine and fsck reports that it is clean. and a ^D whether I fsck it or not brings up the system and the disk is fine. I seems like it might be a timing problem in that the array is not fully online before the system goes to check it. Or I didn't do something right when I partitioned and made the filesystem. Boot messages are: ... scsi2 : 3ware 9000 Storage Controller 3w-9xxx: scsi2: Found a 3ware 9000 Storage Controller at 0xda20, IRQ: 18. input: ImPs ... 3w-9xxx: scsi2: Firmware FE9X 3/02.00.012, BIOS BE9X 3.01.00.024, Ports 8. Vendor: AMCC Model: 9550X-8LP DISK Rev 3.02 Type: Direct-Access ANSI SCSI revision: 03 SCSI device sdb: 3417817088 512-byte hdwr sectors (1749922 MB) SCSI device sdb: drive cache: none SCSI device sdb: 3417817088 512-byte hdwr sectors (1749922 MB) SCSI device sdb: drive cache: none sdb: sdb1 sd 2:0:0:0: Attached scsi disk sdb All modules loaded. Checking all file systems... fsck 1.37 (21-Mar-2005) fsck.ext3: No such file or directory while trying to open /dev/sdb1 /dev/sdb1: The superblock could not be read or does not describe a correct ext2 filesystem. ... [and suggests trying] e2fsck -b 8193 and prompts for the root password to enter maintenence mode. So trying the above reports: $ e2fsck -b 8193 /dev/sdb1 e2fsck 1.37 (21-Mark-2005) e2fsck: Bad magic number in super-block while trying to open /dev/sdb1 The superblock could not be read or does not describe a correct ext2 filesystem. ... [and suggests trying] e2fsck -b 8193 (none):~# fsck -v /dev/sdb1 fsck 1.37 (21-Mark-2005) e2fsck 1.37 (21-Mark-2005) /dev/sdb1: clean, 11/213614592 files, 6711696/427226577 blocks (none):~# fsck -v -f /dev/sdb1 [checks the disk and reports no problems] ^D system continues to boot and everything looks fine. I think the key to this problem is likely the error message: fsck.ext3: No such file or directory while trying to open /dev/sdb1 above. Is it not finding the executable fsck.ext3 or the device /dev/sdb1?? fsck.ext3 is in the /sbin directory with its ilk. -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 3ware 9550 SATA RAID controller problems
OK, things are very close to completely working. Running the sid linux-image-2.6.15-1-em64t-p4-smp Have the ATAPI CDROM working :) Recognizing the 3ware 9550 raid card. Have built an ext3 filesystem and it mounts and read writes seem to be fine. BUT there is a problem on reboot. The fsck check of the /dev/sdb1 fails to read the superblock and throws the boot process into maintenance mode. The device is fine and fsck reports that it is clean. and a ^D whether I fsck it or not brings up the system and the disk is fine. I seems like it might be a timing problem in that the array is not fully online before the system goes to check it. Or I didn't do something right when I partitioned and made the filesystem. Boot messages are: ... scsi2 : 3ware 9000 Storage Controller 3w-9xxx: scsi2: Found a 3ware 9000 Storage Controller at 0xda20, IRQ: 18. input: ImPs ... 3w-9xxx: scsi2: Firmware FE9X 3/02.00.012, BIOS BE9X 3.01.00.024, Ports 8. Vendor: AMCC Model: 9550X-8LP DISK Rev 3.02 Type: Direct-Access ANSI SCSI revision: 03 SCSI device sdb: 3417817088 512-byte hdwr sectors (1749922 MB) SCSI device sdb: drive cache: none SCSI device sdb: 3417817088 512-byte hdwr sectors (1749922 MB) SCSI device sdb: drive cache: none sdb: sdb1 sd 2:0:0:0: Attached scsi disk sdb All modules loaded. Checking all file systems... fsck 1.37 (21-Mar-2005) fsck.ext3: No such file or directory while trying to open /dev/sdb1 /dev/sdb1: The superblock could not be read or does not describe a correct ext2 filesystem. ... [and suggests trying] e2fsck -b 8193 and prompts for the root password to enter maintenence mode. So trying the above reports: $ e2fsck -b 8193 /dev/sdb1 e2fsck 1.37 (21-Mark-2005) e2fsck: Bad magic number in super-block while trying to open /dev/sdb1 The superblock could not be read or does not describe a correct ext2 filesystem. ... [and suggests trying] e2fsck -b 8193 (none):~# fsck -v /dev/sdb1 fsck 1.37 (21-Mark-2005) e2fsck 1.37 (21-Mark-2005) /dev/sdb1: clean, 11/213614592 files, 6711696/427226577 blocks (none):~# fsck -v -f /dev/sdb1 [checks the disk and reports no problems] ^D system continues to boot and everything looks fine. I think the key to this problem is likely the error message: fsck.ext3: No such file or directory while trying to open /dev/sdb1 above. Is it not finding the executable fsck.ext3 or the device /dev/sdb1?? fsck.ext3 is in the /sbin directory with its ilk. -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
CDROM Resolved. Re: SUCCESS: Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
Resolved the CDROM recognition problem. create a file named libata into /etc/modprobe.d/ with the content: options libata atapi_enabled=1 Then: # dpkg-reconfigure linux-image-`uname -r` This regenerate the initrd image with the special parameter. It tried to pass libata.atapi_enabled=1 at boot params but didn't worked. I now have /dev/sr0 and can mount a read the CDROM. -Steve Lennart Sorensen wrote: On Sun, Jan 08, 2006 at 10:42:20AM -0500, Stephen Woodbridge wrote: Hi Len, Thank You! Thank you! Thank you! Using the kernel from sid did the trick! I guess I was too focused on having to build a kernel to step back from the problem and see that. Also the kernel-image to linux-image tripped me up so I didn't see them in apt-cache search. I now can see the 3ware device as /dev/sdb but I seem to have lost the CDROM drive again. I suppose the 2.6.15 wants the BIOS settings changed again or I have run up against the problem that the CDROM seems to only run as a slave device on the PATA IDE bus. Any idea what causes the: ata1(1): WARNING: ATAPI is disabled, device ignored. There is an option I think might have to be enabled. There is also a bug in 2.6.15 that I just read on lkml about 30 minutes ago, that on intel ICH controllers, PATA secondary slave is currently broken. primary master, primary slave, and secondary master all work, but no atapi on secondary slave. If your cdrom is secondary slave, change it. Otherwise look for the libata.atapi_enabled=1 or something option and add that to the module options, or the kernel boot command. Might have to add it to the initrd configuration and generate a new initrd with that option enabled. yaird has a config file where you can list modules to load, and modules options and such. Adding it to the kernel boot options might work too. SCSI subsystem initialized libata version 1.20 loaded. ata_piix :00:1f.2: version 1.05 ata_piix :00:1f.2: combined mode detected (p=0, s=1) GSI 17 sharing vector 0xB1 and IRQ 17 ACPI: PCI Interrupt :00:1f.2[A] -> GSI 18 (level, low) -> IRQ 17 PCI: Setting latency timer of device :00:1f.2 to 64 ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0x1470 irq 14 ata1: dev 1 cfg 49:0f00 82:4210 83:4000 84:4000 85: 86: 87:4000 88:0407 ata1: dev 1 ATAPI, max UDMA/33 ata1: dev 1 configured for UDMA/33 scsi0 : ata_piix ata1(1): WARNING: ATAPI is disabled, device ignored. ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1478 irq 15 ata2: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 88:207f ata2: dev 0 ATA-7, max UDMA/133, 488397168 sectors: LBA48 ata2: dev 0 configured for UDMA/133 scsi1 : ata_piix Vendor: ATA Model: WDC WD2500JS-00N Rev: 10.0 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) SCSI device sda: drive cache: write back SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 > sd 1:0:0:0: Attached scsi disk sda Yeah I think the libata.atapi_enabled option would help. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: SUCCESS: Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
On Sun, Jan 08, 2006 at 10:42:20AM -0500, Stephen Woodbridge wrote: > Hi Len, > > Thank You! Thank you! Thank you! Using the kernel from sid did the > trick! I guess I was too focused on having to build a kernel to step > back from the problem and see that. Also the kernel-image to linux-image > tripped me up so I didn't see them in apt-cache search. > > I now can see the 3ware device as /dev/sdb but I seem to have lost the > CDROM drive again. I suppose the 2.6.15 wants the BIOS settings changed > again or I have run up against the problem that the CDROM seems to only > run as a slave device on the PATA IDE bus. > > Any idea what causes the: > > ata1(1): WARNING: ATAPI is disabled, device ignored. There is an option I think might have to be enabled. There is also a bug in 2.6.15 that I just read on lkml about 30 minutes ago, that on intel ICH controllers, PATA secondary slave is currently broken. primary master, primary slave, and secondary master all work, but no atapi on secondary slave. If your cdrom is secondary slave, change it. Otherwise look for the libata.atapi_enabled=1 or something option and add that to the module options, or the kernel boot command. Might have to add it to the initrd configuration and generate a new initrd with that option enabled. yaird has a config file where you can list modules to load, and modules options and such. Adding it to the kernel boot options might work too. > SCSI subsystem initialized > libata version 1.20 loaded. > ata_piix :00:1f.2: version 1.05 > ata_piix :00:1f.2: combined mode detected (p=0, s=1) > GSI 17 sharing vector 0xB1 and IRQ 17 > ACPI: PCI Interrupt :00:1f.2[A] -> GSI 18 (level, low) -> IRQ 17 > PCI: Setting latency timer of device :00:1f.2 to 64 > ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0x1470 irq 14 > ata1: dev 1 cfg 49:0f00 82:4210 83:4000 84:4000 85: 86: 87:4000 > 88:0407 > ata1: dev 1 ATAPI, max UDMA/33 > ata1: dev 1 configured for UDMA/33 > scsi0 : ata_piix > ata1(1): WARNING: ATAPI is disabled, device ignored. > ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1478 irq 15 > ata2: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 > 88:207f > ata2: dev 0 ATA-7, max UDMA/133, 488397168 sectors: LBA48 > ata2: dev 0 configured for UDMA/133 > scsi1 : ata_piix > Vendor: ATA Model: WDC WD2500JS-00N Rev: 10.0 > Type: Direct-Access ANSI SCSI revision: 05 > SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) > SCSI device sda: drive cache: write back > SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) > SCSI device sda: drive cache: write back > sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 > > sd 1:0:0:0: Attached scsi disk sda Yeah I think the libata.atapi_enabled option would help. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
SUCCESS: Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
Hi Len, Thank You! Thank you! Thank you! Using the kernel from sid did the trick! I guess I was too focused on having to build a kernel to step back from the problem and see that. Also the kernel-image to linux-image tripped me up so I didn't see them in apt-cache search. I now can see the 3ware device as /dev/sdb but I seem to have lost the CDROM drive again. I suppose the 2.6.15 wants the BIOS settings changed again or I have run up against the problem that the CDROM seems to only run as a slave device on the PATA IDE bus. Any idea what causes the: ata1(1): WARNING: ATAPI is disabled, device ignored. below: SCSI subsystem initialized libata version 1.20 loaded. ata_piix :00:1f.2: version 1.05 ata_piix :00:1f.2: combined mode detected (p=0, s=1) GSI 17 sharing vector 0xB1 and IRQ 17 ACPI: PCI Interrupt :00:1f.2[A] -> GSI 18 (level, low) -> IRQ 17 PCI: Setting latency timer of device :00:1f.2 to 64 ata1: PATA max UDMA/100 cmd 0x1F0 ctl 0x3F6 bmdma 0x1470 irq 14 ata1: dev 1 cfg 49:0f00 82:4210 83:4000 84:4000 85: 86: 87:4000 88:0407 ata1: dev 1 ATAPI, max UDMA/33 ata1: dev 1 configured for UDMA/33 scsi0 : ata_piix ata1(1): WARNING: ATAPI is disabled, device ignored. ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x1478 irq 15 ata2: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 88:207f ata2: dev 0 ATA-7, max UDMA/133, 488397168 sectors: LBA48 ata2: dev 0 configured for UDMA/133 scsi1 : ata_piix Vendor: ATA Model: WDC WD2500JS-00N Rev: 10.0 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) SCSI device sda: drive cache: write back SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) SCSI device sda: drive cache: write back sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 > sd 1:0:0:0: Attached scsi disk sda Lennart Sorensen wrote: On Sat, Jan 07, 2006 at 05:07:10PM -0500, Stephen Woodbridge wrote: OK, I am making some progress ... I found this link and it seems pretty clean and straight forward. http://www.dominik-epple.de/Sarge-Linux_2.6.14-yaird/ and I have followed these steps except I'm using 2.6.15, ie: Backporting yaird, texi2html, make, kernel-package I spent all day going through menuconfig and follow an example config file the Andrew sent me. You can just skip building a new kernel and use the one from sid. You only need to get yaird and such rebuilt and installed, then you can use the prebuilt package for the kernel from sid. But when I try to compile the kernel it looks like it thinks it should be trying to cross compile. I'm wonder if it is somehow confused by the packages I backported? You are running amd64 right? Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
On Sat, Jan 07, 2006 at 09:26:21PM -0500, Stephen Woodbridge wrote: > Fixed the cross-compile problem by adding --arch=amd64 to the make-kpkg > command and the kernel compiles but of the package is strange and it > will not install. > > fakeroot make-kpkg --arch=amd64 --initrd --append-to-version=.20060107 > kernel-image Don't use a . at the start of your append to version. Use a - That way the kernel version will look sane (2.6.15, not 2.6.15.20060107) Apparently yaird does things based on the version of the kernel, and with your append, it has no clue what to make of it. I still suggest starting with just the prebuilt debian kernel instead. > The package name is: > > linux-image-2.6.15.20060107_2.6.15.20060107-10.00.Custom_amd64.deb > > which is strange because I gave the target as kernel-image not > linux-image and 2.6.15.20060107 is added to the name twice. > > and yaird failed on the install see below. New kernels are named linux-image nor kernel-image on debian. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
On Sat, Jan 07, 2006 at 05:07:10PM -0500, Stephen Woodbridge wrote: > OK, I am making some progress ... I found this link and it seems pretty > clean and straight forward. > > http://www.dominik-epple.de/Sarge-Linux_2.6.14-yaird/ > > and I have followed these steps except I'm using 2.6.15, ie: > > Backporting yaird, texi2html, make, kernel-package > > I spent all day going through menuconfig and follow an example config > file the Andrew sent me. You can just skip building a new kernel and use the one from sid. You only need to get yaird and such rebuilt and installed, then you can use the prebuilt package for the kernel from sid. > But when I try to compile the kernel it looks like it thinks it should > be trying to cross compile. I'm wonder if it is somehow confused by the > packages I backported? You are running amd64 right? Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
Fixed the cross-compile problem by adding --arch=amd64 to the make-kpkg command and the kernel compiles but of the package is strange and it will not install. fakeroot make-kpkg --arch=amd64 --initrd --append-to-version=.20060107 kernel-image The package name is: linux-image-2.6.15.20060107_2.6.15.20060107-10.00.Custom_amd64.deb which is strange because I gave the target as kernel-image not linux-image and 2.6.15.20060107 is added to the name twice. and yaird failed on the install see below. -Steve [EMAIL PROTECTED]:/usr/src$ sudo dpkg -i linux-image-2.6.15.20060107_2.6.15.20060107-10.00.Custom_amd64.deb Password: Selecting previously deselected package linux-image-2.6.15.20060107. (Reading database ... 41199 files and directories currently installed.) Unpacking linux-image-2.6.15.20060107 (from linux-image-2.6.15.20060107_2.6.15.20060107-10.00.Custom_amd64.deb) ... Done. Setting up linux-image-2.6.15.20060107 (2.6.15.20060107-10.00.Custom) ... Finding valid ramdisk creators. Using mkinitrd.yaird to build the ramdisk. yaird error: unknown kernel version: 2.6.15.20060107 (fatal) mkinitrd.yaird failed to create initrd image. Failed to create initrd image. dpkg: error processing linux-image-2.6.15.20060107 (--install): subprocess post-installation script returned error exit status 9 Errors were encountered while processing: linux-image-2.6.15.20060107 [EMAIL PROTECTED]:/usr/src$ sudo dpkg -P linux-image-2.6.15.20060107 (Reading database ... 41349 files and directories currently installed.) Removing linux-image-2.6.15.20060107 ... Running postrm hook /sbin/update-grub . Searching for GRUB installation directory ... found: /boot/grub . Purging configuration files for linux-image-2.6.15.20060107 ... Running postrm hook /sbin/update-grub . Searching for GRUB installation directory ... found: /boot/grub . dpkg: error processing linux-image-2.6.15.20060107 (--purge): subprocess post-removal script returned error exit status 128 Errors were encountered while processing: linux-image-2.6.15.20060107 Stephen Woodbridge wrote: OK, I am making some progress ... I found this link and it seems pretty clean and straight forward. http://www.dominik-epple.de/Sarge-Linux_2.6.14-yaird/ and I have followed these steps except I'm using 2.6.15, ie: Backporting yaird, texi2html, make, kernel-package I spent all day going through menuconfig and follow an example config file the Andrew sent me. But when I try to compile the kernel it looks like it thinks it should be trying to cross compile. I'm wonder if it is somehow confused by the packages I backported? $ fakeroot make-kpkg --initrd --append-to-version=.20060107 kernel-image [snip] /usr/bin/make EXTRAVERSION=.20060107 ARCH=x86_64 \ CROSS_COMPILE=x86_64-linux- bzImage make[1]: Entering directory `/usr/src/linux-2.6.15' CHK include/linux/version.h CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/file2alias.o HOSTCC scripts/mod/modpost.o HOSTCC scripts/mod/sumversion.o HOSTLD scripts/mod/modpost HOSTCC scripts/kallsyms HOSTCC scripts/conmakehash CC init/main.o CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o CC init/do_mounts.o CC init/do_mounts_rd.o CC init/do_mounts_initrd.o LD init/mounts.o /bin/sh: line 1: x86_64-linux-ld: command not found make[2]: *** [init/mounts.o] Error 127 make[1]: *** [init] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.15' make: *** [debian/stamp-build-kernel] Error 2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
OK, I am making some progress ... I found this link and it seems pretty clean and straight forward. http://www.dominik-epple.de/Sarge-Linux_2.6.14-yaird/ and I have followed these steps except I'm using 2.6.15, ie: Backporting yaird, texi2html, make, kernel-package I spent all day going through menuconfig and follow an example config file the Andrew sent me. But when I try to compile the kernel it looks like it thinks it should be trying to cross compile. I'm wonder if it is somehow confused by the packages I backported? $ fakeroot make-kpkg --initrd --append-to-version=.20060107 kernel-image [snip] /usr/bin/make EXTRAVERSION=.20060107 ARCH=x86_64 \ CROSS_COMPILE=x86_64-linux- bzImage make[1]: Entering directory `/usr/src/linux-2.6.15' CHK include/linux/version.h CC scripts/mod/empty.o HOSTCC scripts/mod/mk_elfconfig MKELF scripts/mod/elfconfig.h HOSTCC scripts/mod/file2alias.o HOSTCC scripts/mod/modpost.o HOSTCC scripts/mod/sumversion.o HOSTLD scripts/mod/modpost HOSTCC scripts/kallsyms HOSTCC scripts/conmakehash CC init/main.o CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o CC init/do_mounts.o CC init/do_mounts_rd.o CC init/do_mounts_initrd.o LD init/mounts.o /bin/sh: line 1: x86_64-linux-ld: command not found make[2]: *** [init/mounts.o] Error 127 make[1]: *** [init] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.15' make: *** [debian/stamp-build-kernel] Error 2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
On Fri, Jan 06, 2006 at 06:37:43PM -0500, Stephen Woodbridge wrote: > Lennart Sorensen wrote: > >On Fri, Jan 06, 2006 at 01:11:04AM -0500, Stephen Woodbridge wrote: > > > >>Tried to build my first kernel, but no joy. This is what I did ... > >> > >>cd /usr/src > >>wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.15.tar.bz2 > > > > > >Try getting the linux-source package from unstable instead. It has > >debian's patches and such. You can also get the config file from one of > >the newer kernels for your cpu as a start for oldconfig. It's a big > >jump from 2.6.8 to 2.6.15. A lot has changed. > > > >For that matter, you could probably see if there is a new linux-image > >package already for your cpu in unstable. Would be even simpler. > > > >Len Sorensen > > > > I tried to install it: > > sudo apt-get install linux-image-2.6.15-1-em64t-p4-smp > > The following packages have unmet dependencies: > linux-image-2.6.15-1-em64t-p4-smp: Depends: yaird but it is not going > to be installed or > initramfs-tools but it is > not going to be installed or > linux-initramfs-tool > > I tried to install yaird: > > sudo apt-get install yaird > > The following packages have unmet dependencies: > yaird: Depends: libc6 (>= 2.3.5-1) but 2.3.2.ds1-22 is to be installed > > yaird is at backports.org but there are no amd64 arch packages at > backports.org. > > Someone mentioned back porting yaird, how would I go about doing that if > that is the right thing to do? apt-get source -b yaird If it has any build dependancies, do those too. It only depends on libc6 2.3.5-1 because it was build on sid not sarge. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
Lennart Sorensen wrote: On Fri, Jan 06, 2006 at 01:11:04AM -0500, Stephen Woodbridge wrote: Tried to build my first kernel, but no joy. This is what I did ... cd /usr/src wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.15.tar.bz2 Try getting the linux-source package from unstable instead. It has debian's patches and such. You can also get the config file from one of the newer kernels for your cpu as a start for oldconfig. It's a big jump from 2.6.8 to 2.6.15. A lot has changed. For that matter, you could probably see if there is a new linux-image package already for your cpu in unstable. Would be even simpler. Len Sorensen I tried to install it: sudo apt-get install linux-image-2.6.15-1-em64t-p4-smp The following packages have unmet dependencies: linux-image-2.6.15-1-em64t-p4-smp: Depends: yaird but it is not going to be installed or initramfs-tools but it is not going to be installed or linux-initramfs-tool I tried to install yaird: sudo apt-get install yaird The following packages have unmet dependencies: yaird: Depends: libc6 (>= 2.3.5-1) but 2.3.2.ds1-22 is to be installed yaird is at backports.org but there are no amd64 arch packages at backports.org. Someone mentioned back porting yaird, how would I go about doing that if that is the right thing to do? -Steve -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
On Fri, Jan 06, 2006 at 01:11:04AM -0500, Stephen Woodbridge wrote: > Tried to build my first kernel, but no joy. This is what I did ... > > cd /usr/src > wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.15.tar.bz2 Try getting the linux-source package from unstable instead. It has debian's patches and such. You can also get the config file from one of the newer kernels for your cpu as a start for oldconfig. It's a big jump from 2.6.8 to 2.6.15. A lot has changed. For that matter, you could probably see if there is a new linux-image package already for your cpu in unstable. Would be even simpler. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
First Kernel Build Attempt Failed was: Re: 3ware 9550 SATA RAID controller problems
Tried to build my first kernel, but no joy. This is what I did ... cd /usr/src wget http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.15.tar.bz2 tar xjf linux-2.6.15.tar.bz2 ln -s linux-2.6.15 linux cd linux cp /boot/config-2.6.8-11-em64t-p4-smp .config make oldconfig # answer 20,000 questions, mostly took the defaults # man there is a lot of junk I know I don't need # man there is a lot of stuff I have NO IDEA if I need it fakeroot make-kpkg clean fakeroot make-kpkg --apend-to-version=.20060105 kernel-image cd .. ls sudo dpkg -i kernel-image-2.6.15.20060105_10.00.Custom_amd64.deb # I'm running grub sudo reboot # system goes through its normal reboot steps # and console reports Booting 'Debian GNU/Linux, Kernel 2.6.15.20060105 Default ' kernel direct mapping tables upto 8100ffc0 @ 8000-c000 root (hd0,0) Filesystem type ext2fs, partition type 0x83 Kernel /boot/vmlinuz root=/dev/sda1 ro console=tty0 [Linux-bzImage, setup=0x1e00, size=0x122a9c] savedefault boot . Decompressing Linux...done. Booting the kernel. _(hangs here) Too late to think straight now, maybe you will have some thoughts in the morning. Thanks, -Steve Stephen Woodbridge wrote: OK following this thread and the good advice from the thread: Re: no updates to amd64 stable in last 3 weeks? I have to ask what is udev and what does it do for me? Where/how do I get 2.6.15 that I can build for sarge and can someone walk me (a noobie) through the steps of building and installing it on sarge in the "Debian way", so that is is similar to Linux carto 2.6.8-11-em64t-p4-smp #1 SMP Mon Oct 3 00:07:51 CEST 2005 x86_64 GNU/Linux but with the driver needed for the 3ware 9550 card. I say similar to the above because I have that working. While I don't mind wading through a bunch of questions in menuconfig, but concern is that I will not have a clue about what hardware is in my system or not. I'm reading http://newbiedoc.sourceforge.net/system/kernel-pkg.html but it would really make me feel better if someone with experience outlined the critical steps. For example, I have the 3ware linux driver source but I think from other reports, the 2.6.15 already supports the 3ware 9550 card, so maybe just taking the .config from 2.6.8-11 and starting with that, ahh how do I start with that? Do I still need to go through menuconfig? While while I waiting on a response I will wing it and try to do something is I can find 2.6.15 somewhere. -Steve Andrew McMillan wrote: On Wed, 2006-01-04 at 20:39 -0500, Stephen Woodbridge wrote: Hi Again, After finally getting Sarge installed on my SuperMicro X6DHT-G motherboard system, I am having a problem recognizing the 3ware 9550 SATA Raid Controller card. I have loaded the 3w-9xxx module but that is not getting me anywhere yet. This system boots from a separate SATA disk so the system is running, just without the 1.6TB raid array :( lspci is reporting: :03:02.0 RAID bus controller: 3ware Inc: Unknown device 1003 So, I think what needs to happen next is one or more of the following: You can get lspci to show the full and correct details if you run update-pciids. 1) upgrade to the 2.6.12 kernel 2) compile the updated vendor source for 3w-9xxx module on either 2.6.8-11 or 2.6.12 3) something simpler that I am missing. Ideally, I would like to use a stock kernel which was why I was thinking of getting 2.6.12 from etch otherwise I will need to try and figure out how to use the kernel-package system and long term maintenance becomes a bigger problem. Thoughts and suggestions would be greatly appreciated. We recently bought a system with a 3ware 9550 controller and found 2.6.12 was not recent enough. We got it working with 2.6.15-rc6 in the end, and now that 2.6.15 is released we will upgrade it to a more stable release - fortunately the system using this machine is still under development. So I would heartily recommend coming to grips with kernel-package and building your own (hopefully simpler) kernel. When building with make-kpkg we generally don't use the .config from a Debian build as we can make it more hardware specific and so do not need the complexity of an initrd image for the build. I find it's better to spend 20 minutes going through all the options in make menuconfig and specifying appropriate settings for your hardware. Of course I have been doing that for more than ten years now, so I guess I'm not daunted by it... :-) Regards, Andrew McMillan. - Andrew @ Catalyst .Net .NZ Ltd, PO Box 11-053, Manners St, Wellington WEB: http://catalyst.net.nz/PHYS: Level 2, 150-154 Willis St DDI: +64(4)803-2201 MOB: +64(272)DEBIAN OFFICE: +64(4)499-2267 Make things as simple as possible, but no simpler -- Einstein - -- To UNSUBSCRIBE, email to [E
Re: 3ware 9550 SATA RAID controller problems
OK following this thread and the good advice from the thread: Re: no updates to amd64 stable in last 3 weeks? I have to ask what is udev and what does it do for me? Where/how do I get 2.6.15 that I can build for sarge and can someone walk me (a noobie) through the steps of building and installing it on sarge in the "Debian way", so that is is similar to Linux carto 2.6.8-11-em64t-p4-smp #1 SMP Mon Oct 3 00:07:51 CEST 2005 x86_64 GNU/Linux but with the driver needed for the 3ware 9550 card. I say similar to the above because I have that working. While I don't mind wading through a bunch of questions in menuconfig, but concern is that I will not have a clue about what hardware is in my system or not. I'm reading http://newbiedoc.sourceforge.net/system/kernel-pkg.html but it would really make me feel better if someone with experience outlined the critical steps. For example, I have the 3ware linux driver source but I think from other reports, the 2.6.15 already supports the 3ware 9550 card, so maybe just taking the .config from 2.6.8-11 and starting with that, ahh how do I start with that? Do I still need to go through menuconfig? While while I waiting on a response I will wing it and try to do something is I can find 2.6.15 somewhere. -Steve Andrew McMillan wrote: On Wed, 2006-01-04 at 20:39 -0500, Stephen Woodbridge wrote: Hi Again, After finally getting Sarge installed on my SuperMicro X6DHT-G motherboard system, I am having a problem recognizing the 3ware 9550 SATA Raid Controller card. I have loaded the 3w-9xxx module but that is not getting me anywhere yet. This system boots from a separate SATA disk so the system is running, just without the 1.6TB raid array :( lspci is reporting: :03:02.0 RAID bus controller: 3ware Inc: Unknown device 1003 So, I think what needs to happen next is one or more of the following: You can get lspci to show the full and correct details if you run update-pciids. 1) upgrade to the 2.6.12 kernel 2) compile the updated vendor source for 3w-9xxx module on either 2.6.8-11 or 2.6.12 3) something simpler that I am missing. Ideally, I would like to use a stock kernel which was why I was thinking of getting 2.6.12 from etch otherwise I will need to try and figure out how to use the kernel-package system and long term maintenance becomes a bigger problem. Thoughts and suggestions would be greatly appreciated. We recently bought a system with a 3ware 9550 controller and found 2.6.12 was not recent enough. We got it working with 2.6.15-rc6 in the end, and now that 2.6.15 is released we will upgrade it to a more stable release - fortunately the system using this machine is still under development. So I would heartily recommend coming to grips with kernel-package and building your own (hopefully simpler) kernel. When building with make-kpkg we generally don't use the .config from a Debian build as we can make it more hardware specific and so do not need the complexity of an initrd image for the build. I find it's better to spend 20 minutes going through all the options in make menuconfig and specifying appropriate settings for your hardware. Of course I have been doing that for more than ten years now, so I guess I'm not daunted by it... :-) Regards, Andrew McMillan. - Andrew @ Catalyst .Net .NZ Ltd, PO Box 11-053, Manners St, Wellington WEB: http://catalyst.net.nz/PHYS: Level 2, 150-154 Willis St DDI: +64(4)803-2201 MOB: +64(272)DEBIAN OFFICE: +64(4)499-2267 Make things as simple as possible, but no simpler -- Einstein - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 3ware 9550 SATA RAID controller problems
On Wed, 2006-01-04 at 20:39 -0500, Stephen Woodbridge wrote: > Hi Again, > > After finally getting Sarge installed on my SuperMicro X6DHT-G > motherboard system, I am having a problem recognizing the 3ware 9550 > SATA Raid Controller card. I have loaded the 3w-9xxx module but that is > not getting me anywhere yet. This system boots from a separate SATA disk > so the system is running, just without the 1.6TB raid array :( > > lspci is reporting: > > :03:02.0 RAID bus controller: 3ware Inc: Unknown device 1003 > > So, I think what needs to happen next is one or more of the following: You can get lspci to show the full and correct details if you run update-pciids. > 1) upgrade to the 2.6.12 kernel > 2) compile the updated vendor source for 3w-9xxx module on either > 2.6.8-11 or 2.6.12 > 3) something simpler that I am missing. > > Ideally, I would like to use a stock kernel which was why I was thinking > of getting 2.6.12 from etch otherwise I will need to try and figure out > how to use the kernel-package system and long term maintenance becomes a > bigger problem. > > Thoughts and suggestions would be greatly appreciated. We recently bought a system with a 3ware 9550 controller and found 2.6.12 was not recent enough. We got it working with 2.6.15-rc6 in the end, and now that 2.6.15 is released we will upgrade it to a more stable release - fortunately the system using this machine is still under development. So I would heartily recommend coming to grips with kernel-package and building your own (hopefully simpler) kernel. When building with make-kpkg we generally don't use the .config from a Debian build as we can make it more hardware specific and so do not need the complexity of an initrd image for the build. I find it's better to spend 20 minutes going through all the options in make menuconfig and specifying appropriate settings for your hardware. Of course I have been doing that for more than ten years now, so I guess I'm not daunted by it... :-) Regards, Andrew McMillan. - Andrew @ Catalyst .Net .NZ Ltd, PO Box 11-053, Manners St, Wellington WEB: http://catalyst.net.nz/PHYS: Level 2, 150-154 Willis St DDI: +64(4)803-2201 MOB: +64(272)DEBIAN OFFICE: +64(4)499-2267 Make things as simple as possible, but no simpler -- Einstein - signature.asc Description: This is a digitally signed message part
Re: 3ware 9550 SATA RAID controller problems
On Wed, Jan 04, 2006 at 08:39:30PM -0500, Stephen Woodbridge wrote: > After finally getting Sarge installed on my SuperMicro X6DHT-G > motherboard system, I am having a problem recognizing the 3ware 9550 > SATA Raid Controller card. I have loaded the 3w-9xxx module but that is > not getting me anywhere yet. This system boots from a separate SATA disk > so the system is running, just without the 1.6TB raid array :( > > lspci is reporting: > > :03:02.0 RAID bus controller: 3ware Inc: Unknown device 1003 > > So, I think what needs to happen next is one or more of the following: > > 1) upgrade to the 2.6.12 kernel > 2) compile the updated vendor source for 3w-9xxx module on either >2.6.8-11 or 2.6.12 > 3) something simpler that I am missing. > > Ideally, I would like to use a stock kernel which was why I was thinking > of getting 2.6.12 from etch otherwise I will need to try and figure out > how to use the kernel-package system and long term maintenance becomes a > bigger problem. > > Thoughts and suggestions would be greatly appreciated. My experience is that amd64 systems run much better with 2.6.12 than 2.6.8 in general. So I personally think the upgrade is very worthwhile. Keeping the rest with stable is usually fine. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 3ware 9550 SATA RAID controller problems
On Wed, 04 Jan 2006 20:39:30 -0500, Stephen Woodbridge <[EMAIL PROTECTED]> wrote: > > After finally getting Sarge installed on my SuperMicro X6DHT-G > motherboard system, I am having a problem recognizing the 3ware 9550 > SATA Raid Controller card. I have loaded the 3w-9xxx module but that is > not getting me anywhere yet. This system boots from a separate SATA disk > so the system is running, just without the 1.6TB raid array :( > > Thoughts and suggestions would be greatly appreciated. I can't comment on the 9550, but I'm using a 3Ware 9500 on a dual-Opteron 250 setup, and it works fine with 4x400Gb as hardware RAID5 (1.2TB). I used the 2.6.12 kernel for the install (I did a tftp install as the box has no CD drive - it's a 1U rackmount server with all drive bays full). The installer saw it as a single 1.2TB drive. Regards, Ozz. pgpAEwcPhocmj.pgp Description: PGP signature
