Disk failed, replaced, rebuild stuck at ~1%, reboot, now unmountable

[alinkognito]

Hello community.

Sunny greeting.

 

I think I messed up somewhere and require your help or direction to the right place.

 

I replaced drive 12 recently with a new 18TB HDD as the one before failed.

Everything was running fine with drive 12 emulated.

 

New disk in - started re-building nicely but stopped at around 1% with a few drives showing errors.

Replaced my cables, checked all the connections and rebooted.

 

Started re-building again but again stuck at around 0.6%

 

Rebooted again and now drive shows as "unmountable: wrong or no file system" with the option to format the new drive.

Also my total array space seems to of changed too.

 

I paused the data-rebuild as I cant stop the array and now reaching out to you AMAZING peps for help as I don't want to lose any data.

 

Could someone assist please?

 

Much appriciated.

Al

 

 

 

kraken-diagnostics-20220714-1844.zip

[alinkognito]

There is also a XFS error on sceen on md12 

 

Above my skill level on what to do 😥

Edited July 14, 2022 by alinkognito

[JorgeB]

Check filesystem on disk 12

[JorgeB]

Yes, or use the GUI.

[alinkognito]

Powered down the server.

On reboot to ran the command.

 

# xfs_repair -v /dev/md12 
Phase 1 - find and verify superblock...
bad primary superblock - bad CRC in superblock !!!

attempting to find secondary superblock...
.found candidate secondary superblock...
verified secondary superblock...
writing modified primary superblock
        - block cache size set to 1397184 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 142733 tail block 142729
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed.  Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair.  If you are unable to mount the filesystem, then use
the -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.

 

Now drive is back up and it's re-building - phew

 

Let's see what if it get's over the 1%

 

Thanks in the meanwhile

 

 

 

[JorgeB]

2 minutes ago, alinkognito said:

Let's see what if it get's over the 1%

If it doesn't grab the diags before rebooting.

[alinkognito]

aye aye captain

[alinkognito]

just got to 1.3% woot woot!