[SOLVED]: URGENT 810 Software RAID failed after power outage

[Crumble]

no it wont hurt anything, just shouldn't have any valid superblocks on it as it was never part of the RAID.  should be blank.

[Beeker]

Thanks so do you think sdb will have bad superblock even though sdd was the faulty HDD

[Beeker]

This is what I got below from sdd so now I am going to check sdb

dcerouter_1024641:/home/bruce# fsck.ext3 -v /dev/sdd
e2fsck 1.41.3 (12-Oct-2008)
/dev/sdd has gone 1270 days without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

      11 inodes used (0.00%)
       0 non-contiguous inodes (0.0%)
         # of inodes with ind/dind/tind blocks: 0/0/0
 5798288 blocks used (1.58%)
       0 bad blocks
       1 large file

       0 regular files
       2 directories
       0 character device files
       0 block device files
       0 fifos
       0 links
       0 symbolic links (0 fast symbolic links)
       0 sockets
--------
       2 files
dcerouter_1024641:/home/bruce#

[Beeker]

This is what I get for sdb, sdc,sde

dcerouter_1024641:/home/bruce# fsck.ext3 -v /dev/sdb
e2fsck 1.41.3 (12-Oct-2008)
fsck.ext3: Superblock invalid, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to open /dev/sdb

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>

[Crumble]

ok, you will have to do one disk at a time.  start with sdb. 

try to reassemble after you fix the superblock on sdb.  you may not have to do all the disks.  if that does not work then fix the superblocks on c and e and then try the reassemble command.  it will work eventually.

[Beeker]

Sorry to be a pain in the you know where..........I have tried a number of the superblocks and I am getting the same error as per below and I tried e3fsck and that didn't work either as it came back as command not found

dcerouter_1024641:/home/bruce# e2fsck -b 32768 /dev/sdb
e2fsck 1.41.3 (12-Oct-2008)
e2fsck: Bad magic number in super-block while trying to open /dev/sdb

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>

[Crumble]

did you try them all?

[Beeker]

no did you want me to try and restore a super block on sdc & sde as well

[Crumble]

no start with the sdb drive.  after you restore one of the superblocks try the assemble command and see if that works.

[Beeker]

tried all the superblocks for sdb and none of them want to restore

[Crumble]

post the output of this again

sudo mdadm --assemble --force /dev/md1 /dev/sd[bcdef]1

[Crumble]

i was looking through the thread again and there was no 1 on the end of that assemble command.  that could cause a problem.

[Crumble]

haha i think that was the problem with the assemble and superblocks commands.  you always have to use the full drive name, that includes the number.

[Beeker]

here you go

dcerouter_1024641:/home/bruce# mdadm --assemble --force /dev/md1 /dev/sd[bcdef]1
mdadm: no RAID superblock on /dev/sdf1
mdadm: /dev/sdf1 has no superblock - assembly aborted

[Beeker]

tried putting a 1 and testing sdb,c,d & e again and below is what I got

dcerouter_1024641:/home/bruce# fsck.ext3 -v /dev/sdb1
e2fsck 1.41.3 (12-Oct-2008)
fsck.ext3: Group descriptors look bad... trying backup blocks...
Superblock has an invalid ext3 journal (inode .
Clear<y>? no

fsck.ext3: Illegal inode number while checking ext3 journal for /dev/sdb1

dcerouter_1024641:/home/bruce# fsck.ext3 -v /dev/sdc1
e2fsck 1.41.3 (12-Oct-2008)
fsck.ext3: Superblock invalid, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to open /dev/sdc1

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>

dcerouter_1024641:/home/bruce# fsck.ext3 -v /dev/sdd1
e2fsck 1.41.3 (12-Oct-2008)
fsck.ext3: No such file or directory while trying to open /dev/sdd1

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>

dcerouter_1024641:/home/bruce# fsck.ext3 -v /dev/sde1
e2fsck 1.41.3 (12-Oct-2008)
/dev/sde1 has unsupported feature(s): FEATURE_I26 FEATURE_R26
e2fsck: Get a newer version of e2fsck!
dcerouter_1024641:/home/bruce#