I've had a few errors with drives recently and trying to solve the problem. I've swapped out one drive with a new one and tested it in another system and its reported Ok on a long test so I believe its not a drive problem.

After the server booted up fine, array seemed to take a while to start, Disk 2 was a new disk and Disk 6 was removed and re added. After I started the rebuild it looked like it was going ok and writing to the 2 disks, I've checked now and I have lots of errors on the parity2 drive and it just seems to be reading the disks.

I have switched sata cables and the problems seems to stay with disk 2 and disk 6 so I want to try different power connectors next.

Whats the best way to handle the rebuild with all the errors going on?

Is there a way to rule out a bad controller? I guess that would effect all drives on the same controller if it was a controller issue though.

Thanks

chaos-diagnostics-20250610-1439.zip

Looks like a power/connection issue, check/replace cables for parity2 and post new diags after array start.

Checked and moved some cables around, sys log looks clear at the moment. Array started and currently re-building. New diag attached.

chaos-diagnostics-20250610-1934.zip

Emulated disks 2 and 6 are not mounting, before rebuilding, check filesystem on both.

The rebuild completed before I ran the filesystem check. The filesystem check on disk 2 and 6 found errors and fixed them. All files on disk 2 and 6 are in a lost + found folder, the folder names in the drive have been changed to numbers as below but the correct data is in the folders.

Do I need to run a parity check to restore the folder names on the disks to the correct folder names (the data inside the folders looks correct) or has my parity been ruined because of the rebuild done with the filesystem errors?

4 minutes ago, FastAd said:

Do I need to run a parity check to restore the folder names on the disks to the correct folder names (the data inside the folders looks correct)

This needs to be done manually. The repair process gave them numeric names because it could not find the directory entry that gave the correct name.

So if I manually rename the folders and move them into the base directory of the drive will unraid fix the links automatically to the folders or do I need to run a command?

I guess I won't need to run a parity check after renaming the folders manually?

1 hour ago, FastAd said:

So if I manually rename the folders and move them into the base directory of the drive will unraid fix the links automatically to the folders or do I need to run a command?

I guess I won't need to run a parity check after renaming the folders manually?

Just move them to where they should be and everything should look after itself. Do not forget that each top level folder on any drive is effectively a User Share with the same name. Parity is maintained throughout though it would not do any harm to run a parity check in case a few parity errors got introduced when the file system issue happened.

Make sure you are either doing a share->share or a disk->disk move. Do not do disk->share as this can lead to data loss.

Everything is looking back to normal after folders renamed and moved.

Thank you for your help!