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 0xda200000,
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 <device>
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 <device>
(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
Reply to: