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

[Robin Hill]

On Mon Nov 20, 2006 at 09:47:48AM -0500, James Pifer wrote:

> 
> > 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>
> 
Okay, looks like that one's corrupt as well :(  You can get a list of
superblock locations by running "mke2fs -n /dev/md0" (don't worry - this
won't actually create a filesystem, just print out what it would have
done).  You can then try each in turn (I'd start at the end, in case the
corruption is all at the start of the disk) with e2fsck.

If all of these fail then I'd say you're stuffed :(  Did you get any
feedback from the dd_recover as to how much of the disk it managed to
copy without errors?

Cheers,
        Robin
-- 
     ___        
    ( ' }     |       Robin Hill        <myth at robinhill.me.uk>  |
   / / )      | Little Jim says ....                            |
  // !!       |      "He fallen in de water !!"                 |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : http://mythtv.org/pipermail/mythtv-users/attachments/20061120/e5b29aba/attachment.pgp