I’m installing another machine with a 3ware raid card and am having some problems with it. It looks like the module gets loaded ok, but when it tries to mount the disk that’s listed in /etc/fstab, I get this error:
fsck.ext3: /dev/sda1:
The superblock could not be read or does not describe a correct ext2 filesystem.
First of all, it’s an ext3 filesystem and it’s looking at -b 8193 for the location of the superblock. According to the mkfs command, there is no superblock there.
I’m recreating the filesystem and am outputting everything here:
[root@cs4 ~]# fdisk /dev/sda The number of cylinders for this disk is set to 243147. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Command (m for help): p Disk /dev/sda: 1999.9 GB, 1999957393408 bytes 255 heads, 63 sectors/track, 243147 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-243147, default 1): Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-243147, default 243147): Using default value 243147 Command (m for help): p Disk /dev/sda: 1999.9 GB, 1999957393408 bytes 255 heads, 63 sectors/track, 243147 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 1 243147 1953078246 83 Linux Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks. [root@cs4 ~]# mkfs -v /dev/sda1 mke2fs 1.35 (28-Feb-2004) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 244137984 inodes, 488269561 blocks 24413478 blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks=490733568 14901 block groups 32768 blocks per group, 32768 fragments per group 16384 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968, 102400000, 214990848 Writing inode tables: done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 38 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. [root@cs4 ~]# tune2fs -c0 -i0 -j /dev/sda1 tune2fs 1.35 (28-Feb-2004) Setting maximal mount count to -1 Setting interval between check 0 seconds Creating journal inode: done This filesystem will be automatically checked every -1 mounts or 0 days, whichever comes first. Use tune2fs -c or -i to override.
Now mount the disk
[root@cs4 ~]# mount /dev/sda1 /local/s7 [root@cs4 ~]# df -H Filesystem Size Used Avail Use% Mounted on /dev/hda2 157G 4.0G 145G 3% / /dev/hda1 128M 18M 104M 15% /boot none 1.6G 0 1.6G 0% /dev/shm /dev/sda1 2.0T 114M 1.9T 1% /local/s7
Works fine, but will it work when I reboot? Nope. I give up. I added the following to /etc/rc.d/rc.local and things work fine.
# Mount raid mount /dev/sda1 /local/s7
Usually, the problem is that the driver isn’t loaded, but here, I don’t need to run a modprobe 3w-9xxx because it is already loaded. Go figure.