Hey all, I had a 4TB drive that started producing some errors so sent it in for warranty and just received/popped the new one in last night. Now I'm getting the same errors as before. Is it possible my parity is messed up and the errors are coming from the rebuild? Thankfully there isn't anything important on this drive, that said if it is parity errors how would I go about completely removing this drive from the array and re-adding as a blank new drive? Diagnostics attached. Cheers!

 

tower-diagnostics-20230207-1302.zip

Those errors in the Errors column are I/O errors and have nothing to do with parity. The drive has disconnected.

 

Check connections, SATA and power, both ends, including splitters.

 

How do you know there was anything wrong with the drive you returned? Bad connections are much more common than bad disks.

 

Also, better if you keep the original drive with its data until you are satisfied with the rebuild.

 

And, better if you don't wait to get your server protected again. Since you only have single parity, if you are running your server with a missing disk, none of your other disks are protected.

 

Emulated disk7 is mounted and contains nearly 2TB of data.

Unrelated, but your system share has files on the array and is set to be moved to the array.

 

https://wiki.unraid.net/Manual/Shares#Default_Shares

 

Ideally, appdata, domains, system shares would be all on a fast pool and configured to stay there, so Docker/VM performance isn't impacted by slower parity array, and so array disks can spin down since these files are always open.

2 hours ago, trurl said:

Those errors in the Errors column are I/O errors and have nothing to do with parity. The drive has disconnected.

 

Check connections, SATA and power, both ends, including splitters.

 

How do you know there was anything wrong with the drive you returned? Bad connections are much more common than bad disks.

 

Also, better if you keep the original drive with its data until you are satisfied with the rebuild.

 

And, better if you don't wait to get your server protected again. Since you only have single parity, if you are running your server with a missing disk, none of your other disks are protected.

 

Emulated disk7 is mounted and contains nearly 2TB of data.

 

The original drive showed bad sectors when I plugged it into a dock into my PC, so that was for sure faulty, but sounds like I have a different issue now. I will check physical connections and replace the sata cable for good measure this evening. 

Edited February 7, 20233 yr by CrunchyWalrus
Fix

2 hours ago, trurl said:

Unrelated, but your system share has files on the array and is set to be moved to the array.

 

https://wiki.unraid.net/Manual/Shares#Default_Shares

 

Ideally, appdata, domains, system shares would be all on a fast pool and configured to stay there, so Docker/VM performance isn't impacted by slower parity array, and so array disks can spin down since these files are always open.

 

My AppData is already set to just use the Cache drive(s), but good point on the System share. I will change that to use the Cache too. I don't use the Domains folder, only running 1 VM and it uses a SATA SSD directly passed through to the VM. 

 12 Power_Cycle_Count       -O--CK   100   100   000    -    50
192 Power-Off_Retract_Count -O--CK   200   200   000    -    48

 

These SMART values seem very high for a drive that was taken out of the packaging and put in less than 24 hours ago. Definitely think there is a power issue now. 

9 minutes ago, CrunchyWalrus said:

good point on the System share. I will change that to use the Cache too

That won't get it moved. To get mover to move from array to cache, the share must be cache:prefer. Nothing can move open files. You have to disable Docker and VM Manager in Settings before these files can be moved.