Very slow data rebuild and errors on parity (1MB/sec)

[darber]

Version 6.11.5 2022-11-20

 

Im quite new to unraid. I had a disk fail in my array, bought another one and replaced it but its rebuiling the array at 1MB/sec.

 

Ive also noticed the number of errors on the parity disk increasing although SMART error log shows no errors.

 

Im not sure what to do.

tower-diagnostics-20230227-1151.zip

[darber]

I shut down the server and checked all the connections to the drives.

Booted the server and started the array.

The parity disk isnt logging errors any more but disk 1 is showing Unmountable: Wrong or no file system.

The rebuild starts and seems to be rebuilding back to disk 1 even though it is unmountable?

 

also

 

I have no shares and no docker containers, am I screwed?

Ill download and attach more diagnostics.

[MedicalDetective05]

Did you preclear the new hard drive? 

[darber]

26 minutes ago, MedicalDetective05 said:

Did you preclear the new hard drive? 

No I didnt

[JorgeB]

You are having issue with parity, looks more like a power/connection problem, replace cables an try again.

[darber]

Here are new diagnostics, im not sure if im in a better or worse position now.

No errors on parity but disk 1 Unmountable and all my shares containers and data seem to be missing.

The data rebuild still wants to start should I let it finish?

tower-diagnostics-20230228-0920.zip

[JorgeB]

No ATA errors for now, cancel the rebuild and check filesystem on the emulated disk1.

[darber]

Here is the filesystem check result

disk1fscheck.txt

[JorgeB]

Run it again without -n or nothing will be done, and if it asks for -L use it.

[darber]

It says this, does this mean I should run again with -L ?

 

Phase 1 - find and verify superblock... - block cache size set to 744800 entries

Phase 2 - using internal log - zero log...

zero_log: head block 1001598 tail block 1001594

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.

[itimpi]

9 minutes ago, darber said:

It says this, does this mean I should run again with -L ?

Yes

[darber]

ok done

disk1xfsrepair.txt

[JorgeB]

Emulated disk should now mount, since you've already started to rebuild on top not much point checking the emulated disk first, so just start the array to begin rebuild.

[darber]

Thanks for all your help, disk1 is mounted and rebuild is running at a good speed now.

Shares and data are back, docker tab says Docker Service failed to start but it was sying that before this, ill sort that issue next!

 

Thanks again.