February 2, 20188 yr I added 3 four Tb disks to the system. Added them to the array and started the clearing op. The system started going quite fast (100ish mb/sec) but has now slowed down to 2.3 MB/sec. Its saying its going to be done in 17 days...... other operations have not had this level of slowness. I also dont appear to be able to cancel the operation. Any help figuring this out would be appreciated. Edited February 3, 20188 yr by TheCDay
February 2, 20188 yr Author So when I tried to do the diags nothing happened, I ended up having to do a hard reboot. I have been running for 30 days with no issues like this. Today I bought a license (YAY!) and switched to a different usb key (copied the config folder per the instructions) cdaystorage-diagnostics-20180201-2243.zip
February 2, 20188 yr Community Expert Your diagnostics is showing disk3 disabled, and it doesn't appear in the SMART. Check connections and post another diagnostic.
February 2, 20188 yr Author So I am not really sure what is happening here. The connections all seem fine. The drive spins up in a different system. I also appear to be able to run a smart short self test from unraid and it says that it completes successfully. When I hover over the X in the array device listing it says "device disabled, contents emulated". I am not sure how this has become disabled or how to reverse it.
February 2, 20188 yr Community Expert Disk3 looks OK. You can rebuild it to itself if you don't have a spare. https://lime-technology.com/wiki/Troubleshooting#Re-enable_the_drive
February 2, 20188 yr Community Expert You might take a look at the contents of the emulated disk3 before rebuilding to make sure everything looks OK. Even though unRAID has disabled the disk and will not use it, the disk's data is still available from the parity calculation. unRAID disables a disk when a write to it fails. The failed write is used to update parity though, so the data from the write is still in the parity array. Once unRAID disables a disk it will not use the disk again until it is rebuilt. This is because the disk data is now invalid and out of sync with parity. The disabled disk is emulated by the parity calculation, and its data can be read, and the emulated disk can even be written. The disk must be rebuilt before your array will be protected again. Parity plus all other disks are required to rebuild a missing or disabled disk, so if another disk were to have a problem, you could lose data. Often even in those cases most data can be recovered unless more than one disk is actually dead.
February 2, 20188 yr Author Thank you for all your help. I am rebuilding now. I think I will just add one disk at a time tomorrow and see how it goes.
Archived
This topic is now archived and is closed to further replies.