February 26, 20188 yr Just a few days ago I mynas hanged and I had to force shutdown, and when I boot up back, I notice the disk 2 is marked with red X. So I clicked on the disk and SMART extended self-test and it completed without error. Seeing from the other post, I`m posting the diagnostic zip file as well. Do I have to replace the disk? mynas-diagnostics-20180223-1932.zip
February 26, 20188 yr Community Expert Disk2 looks fine, problem was likely caused by a bad SATA cable, screenshot also shows errors on parity disk, and the diagnostics you posted has 0 sized SMART reports and don't cover the parity errors, post new diags.
February 26, 20188 yr Community Expert SMART for parity also looks fine but the error is more consistent with a disk problem, so you should run an extended SMART test. If all is well rebuild disk2, it would be much safer to use a new disk in case the rebuild goes wrong, but if you prefer, depending how important is the data and if you have backups, you can also rebuild to the old disk. Edit: either way don't forget to replace the SATA cable for disk2 Edited February 26, 20188 yr by johnnie.black
February 27, 20188 yr Author Thanks for the help! I will try replacing first the SATA Cable, if it doesnt help, maybe next month I`ll purchase the disk. It is fine running with a red X, content emulated for now?
February 27, 20188 yr Community Expert 3 minutes ago, sevenz said: Thanks for the help! I will try replacing first the SATA Cable, if it doesnt help, maybe next month I`ll purchase the disk. It is fine running with a red X, content emulated for now? No that is not an acceptable state, your array is unprotected until the disk is rebuilt, either to itself or to a new disk.
February 28, 20188 yr Author Ah alright, I will replace the SATA cable first and see if it helps. Thanks!
February 28, 20188 yr Community Expert 27 minutes ago, sevenz said: Ah alright, I will replace the SATA cable first and see if it helps. Thanks! Replacing the SATA cable may help, but it won't get your array back to a normal state. The disk must be rebuilt. unRAID disables a disk when a write fails. But the write still updates parity, and any subsequent writes to the emulated disk also update parity. The contents of the physical disk are now invalid, and out of sync with parity, but the array is emulating the disk, and the emulated contents are valid and in sync with parity. So the disk must be rebuilt, either to itself or to another disk.
Archived
This topic is now archived and is closed to further replies.