[mythtv-users] Totally OT - but need help wit RAID5 array

[James Pifer]

> Yes - there should be a few redundant superblocks on the disk, so
> hopefully they're not all corrupt.  It really is going to depend just
> how broken the old disk was :(
> 

Well, here's what I get now...

[root at storage ~]# e2fsck -b 32768 /dev/md0
e2fsck 1.38 (30-Jun-2005)
Superblock has an invalid ext3 journal (inode 8).
Clear<y>? yes

*** ext3 journal has been deleted - filesystem is now ext2 only ***

Corruption found in superblock.  (blocks_count = 0).

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 32768 <device>

[root at storage ~]#
[root at storage ~]# e2fsck -b 32768 /dev/md0
e2fsck 1.38 (30-Jun-2005)
Superblock has an invalid ext3 journal (inode 8).
Clear<y>? no

e2fsck: Illegal inode number while checking ext3 journal for /dev/md0
[root at storage ~]#
[root at storage ~]# fsck /dev/md0
fsck 1.38 (30-Jun-2005)
e2fsck 1.38 (30-Jun-2005)
Group descriptors look bad... trying backup blocks...
Superblock has an invalid ext3 journal (inode 8).
Clear<y>? yes

*** ext3 journal has been deleted - filesystem is now ext2 only ***

Corruption found in superblock.  (blocks_count = 0).

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 32768 <device>

[root at storage ~]#

James