I experienced a failure in a 4TB hard drive. The failed drive was emulated, and I decided to replace it with a larger 16TB drive. The parity successfully rebuilt the data on the new drive, and it went through a successful data rebuild process. However, after the parity sync, the drive reverted back to being emulated. This is now my fourth attempt at rebuilding the data on the drive, and the process is very slow, taking approximately two days. Unfortunately, I haven't been able to confirm if the rebuild completes successfully because after two days, I lose access to the web portal, and I'm forced to restart my server. I would appreciate your advice on this issue.

 

 

 

diagnostics-20230622-2226.zip

Diagnostics are after reboot, so can't tell us anything that happened before.

 

Start rebuild again. In Main - Array Devices, you should see lots of writes to rebuilding disk, lots of reads from all other disks, zeros in errors column for all disks.

 

After rebuilding for a while, or you are seeing errors, post new diagnostics.

 

2 days is not unreasonable for rebuilding 16TB

22 minutes ago, trurl said:

Diagnostics are after reboot, so can't tell us anything that happened before.

 

Start rebuild again. In Main - Array Devices, you should see lots of writes to rebuilding disk, lots of reads from all other disks, zeros in errors column for all disks.

 

After rebuilding for a while, or you are seeing errors, post new diagnostics.

 

2 days is not unreasonable for rebuilding 16TB

Indeed, the rebuild process is actively writing data to the designated disk, and I can observe read operations from all the other disks. As of now, I can verify that there are no errors indicated in the errors column for any of the disks, as it consistently displays zeros. I will monitor the situation and provide an update in 24 hours. Should I do anything else or check anything else to make sure this rebuild is successful? 

The rebuild process was completed without any issues, but as soon as I activated the Dockers, the drive encountered a failure in reading data and became disabled once again, resorting to emulating data. Subsequently, I initiated a preliminary examination on another 16TB drive after the rebuild was finished, and unfortunately, that drive also presented read errors after activating the Dockers.

diagnostics-20230625-1153.zip

Don't see parity disk, only parity2. Did you have parity disk?

 

Disk3 has disconnected. Also looks like the disk you have for your vms pool has disconnected. And new Disk10 has disconnected, I assume you had no data on disk10 yet?

 

Can't tell which controller these disks might be connected to since they aren't talking.

 

How are your disks connected to power? Any splitters? Ideally there shouldn't be more than 4 disks per PSU cable.

 

 

2 hours ago, trurl said:

Don't see parity disk, only parity2. Did you have parity disk?

 

 

Disk3 has disconnected. Also looks like the disk you have for your vms pool has disconnected. And new Disk10 has disconnected, I assume you had no data on disk10 yet?

 

Can't tell which controller these disks might be connected to since they aren't talking.

 

 

How are your disks connected to power? Any splitters? Ideally there shouldn't be more than 4 disks per PSU cable.

 

 

 

 Yes, when I upgraded my parity from 8gb to 16gb I didn't do it the right per the forums so I ended up with a parity2 and no parity1.    

 

Disk10 does not have any data was adding another 16tb drive to remove all the 4tb drives. Not sure why the drives become this way when I turn on dockers? 

 

l have 6 on the mobo Sata ports and 6 on SSU SA3006 PCI-E 6 port Sata 3.0 controller expansion card.

 

I have an Corsair HX1000 with 3 modular power cables that has 4 power sata connecters per cable.

 

I put all the 16tb, 8tb on the mobo sata and everything else on the expansion card. The 16tb disk 3 is rebuilding again.

 

Edited June 26, 20233 yr by siviog1
To expand explanation