The fsck fails because your raid set is not running (as /proc/mdstat shows).
Did you tried a ckraid --fix?
Thomas
> Hi,
>
> Someone just turned my Server off and now it wont remount the Raid set.
> Im using raidtools-19990421-0.90.tar.gz.
>
> So how do i fix this?
> Mark Beck
>
> fsck /dev/md0
> Parallelizing fsck version 1.14 (9-Jan-1999)
> e2fsck 1.14, 9-Jan-1999 for EXT2 FS 0.5b, 95/08/09
> fsck.ext2: Attempt to read block from filesystem resulted in short read
> while trying to open /dev/md0
> Could this be a zero-length partition?
>
>
> cat /proc/mdstat
> Personalities : [raid0] [raid1] [raid5] [translucent]
> read_ahead not set
> unused devices: <none>
>
> cat /etc/raidtab
> # Sample raid-0 configuration
>
> raiddev /dev/md0
>
> raid-level 0 # it's not obvious but this *must* be
> # right after raiddev
>
> persistent-superblock 0 # set this to 1 if you want autostart,
> # BUT SETTING TO 1 WILL DESTROY PREVIOUS
> # CONTENTS if this is a RAID0 array created
> # by older raidtools (0.40-0.51) or mdtools!
>
> chunk-size 16
>
> nr-raid-disks 4
> nr-spare-disks 0
>
> device /dev/hda1
> raid-disk 0
>
> device /dev/hdb1
> raid-disk 1
>
> device /dev/hdc1
> raid-disk 2
>
> device /dev/hdd1
> raid-disk 3
>
>
>
>
