Re: Problems creating RAID 5 using mdadm
On Tue, May 09, 2006 at 07:25:22PM +0200, Stephan Ruggiero wrote:
> Then I created the file system:
> mkfs.ext3 -b 4096 -R stride=16 /dev/md1
> __________________________
> fsck.ext3: Invalid argument while trying to open /dev/md1
> /dev/md1:
> The superblock could not be read or does not describe a correct ext2
> filesystem. If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the
> superblock is corrupt, and you might try running e2fsck with an
> alternate superblock:
> e2fsck -b 8193 <device>
Just a guess, but what about specifying the block-size and/or
stripe-size to fsck as you did with mkfs?
man fsck.ext3:
-b superblock
Instead of using the normal superblock, use an alternative
superblock specified by superblock. This option is normally
used when the primary superblock has been corrupted. The loca-
tion of the backup superblock is dependent on the filesystem's
blocksize. For filesystems with 1k blocksizes, a backup
superblock can be found at block 8193; for filesystems with 2k
blocksizes, at block 16384; and for 4k blocksizes, at block
32768.
-B blocksize
Normally, e2fsck will search for the superblock at various dif-
ferent block sizes in an attempt to find the appropriate block
size. This search can be fooled in some cases. This option
forces e2fsck to only try locating the superblock at a particu-
lar blocksize. If the superblock is not found, e2fsck will
terminate with a fatal error.
GH
--
Life is hard; and then you die.
Reply to: