Replaced and initialised HDD. RAID no longer intact

[boerie]

Oh dear…

Code: Select all

 Setup task fscheck.sh is now running
Found disk: sdb(ZFN0QXQM)
Found disk: sdc(ZFN0SR45)
Found disk: sdd(ZW62NQ4S)
Found disk: sde(ZFN0SQ5J)
Check file system on md0(please wait, take a long time... ca 1 hour/TB)
=>e2fsck 1.43.4 (31-Jan-2017)
ext2fs_check_desc: Corrupt group descriptor: bad block for block bitmap
/usr/sbin/e2fsck: Group descriptors look bad... trying backup blocks... Resize inode not valid. Recreate? yes
Pass 1: Checking inodes, blocks, and sizes
Inode 34824 has an invalid extent node (blk 487620607, lblk 0)
Clear? yes
Killed
Fail (could not check the file system)

[Jocko]

I am sorry that seems not good for your data :dry

We go to try to use some backup superblock
First step will be to get the list of these superblock.

I assume the nas is still on setup mode, open a shell window and do

Code: Select all

 dumpe2fs /dev/md0|grep superblock

wait because you have a big partition size

[boerie]

Oh dear…

Code: Select all

 root@LacieNAS:/ # dumpe2fs /dev/md0|grep superbloc
k
dumpe2fs 1.43.4 (31-Jan-2017)
Killed
root@LacieNAS:/ #

[Jocko]

:crazy

But I know the first backup superblock is the block 32768.

So try this command

Code: Select all

e2fsck -vy -b 32768 -B 4096 /dev/md0

[boerie]

Code: Select all

 root@LacieNAS:/ # cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid5 sdb8[0] sde8[3] sdd8[4] sdc8[1]
      11712345600 blocks super 1.0 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
     
unused devices: <none>
root@LacieNAS:/ # e2fsck -vy -b 32768 -B 4096 /dev
/md0
e2fsck 1.43.4 (31-Jan-2017)
LacieNASShare was not cleanly unmounted, check forced.
Resize inode not valid.  Recreate? yes

Pass 1: Checking inodes, blocks, and sizes
Inode 34824 has an invalid extent node (blk 487620607, lblk 0)
Clear? yes

Killed
root@LacieNAS:/ #


[Jocko]

Hi

I am sorry but currently I have no more idea to restore your data on the raid and the fs seems definitively corrupted.

You can try to use another superblock, the followings are 98304 and 163840 but I think you will get the same response :pissed

[boerie]

Thank you for all your advice. I truly appreciate it

One last question- would there be any chance of success for f I replaced the drive that was flagged as having errors but had not actually failed?

Thank you

[Jocko]

Hi

Raid status and fs status are not linked. The first one is about redundancy and the 2d is about tables to manage the file and data present on the raid device.

Currently you have a clean raid but the fs seems to be corrupted without the possibility of repairing it (it is the purpose of the backup superblocks which should allow to restore the fs tables)