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
woodbri@carto:~$ 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
woodbri@carto:~$ lsmod
Module Size Used by
ipv6 279168 16
parport_pc 41712 0
parport 43532 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_hotplug 16260 1 shpchp
ehci_hcd 36360 0
e1000 106164 0
tsdev 12928 0
isofs 39936 0
3w_9xxx 38560 1
sr_mod 22308 0
sg 42032 0
psmouse 40196 0
ide_generic 5760 0 [permanent]
ide_disk 21120 0
ide_cd 44704 0
cdrom 40632 2 sr_mod,ide_cd
ext3 135056 6
jbd 63016 1 ext3
mbcache 15240 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 0000: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 0xda200000,
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 <device>
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 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