Hi,

 

i´m using unraid 6.17 and last night i start a parity check. In the morning i have a red cross on my first data disk1 ST4000DM000-1F2168_Z300LN0W.

 

Here is my server-diagnostics.

 

I try to upload the zip to the forum, but i could only upload files smaller than 192 kb and the file is 389 kb, her is a download link.

 

http://www.share-online.biz/dl/E9BPO04OXQ

 

 

Could anyone look at this file and give me a hint.

 

Thanks

Disk1 dropped offline, power off server, check all cabling, power on and attach new diagnostics.

@johnnie.black

 

thanks for your answer. Here is the smart report from disk.

 

Sorry for late report, but i got an other problem, after try to reboot the server the server didn´t boot anymore from the usb stick. I though it was the power supply, but after changing the server didn´t boot. I think it´s not a problem with the hdd, rather the mainboard. I have a mainboard with 6 sata onboard ports. After take one of the 6 sata cable from the mainboard the server boot absolut ok.

 

Thanks

server-smart-20160315-1952.zip

SMART for disk1 (and all your other disks) looks fine, it’s not a guarantee, but usually a good indication that the disk is ok, also good news is that you did a non-correcting parity check, so your parity is intact, assuming the problem was the one of the sata ports and it's not in use anymore, you have to two options depending on if you wrote/changed anything on disk1 since it redballed.

 

If the answer is yes rebuild to the same disk:

 

-stop array

-unassign disk1 (select no device)

-start array

-stop array

-reassign disk1

-start array to begin rebuild

 

 

If the answer is no, do a new config and trust parity:

 

-take a screenshot of all your disks assignments

-go to tools and click new config

-reassign all disks, double check parity disk is in the parity slot

-before starting array check “parity is already valid” check box

-start array

-do a non-correcting parity check to make sure parity is in sync.

 

Thanks for your answer. I didn´t change anything on disk1 since the red cross, so i will try the second option. If this did not work i have the first option to rebuild the complete disk because as you say the parity is intact.

 

Thanks !!

Just one more thing, when doing a new config and trusting parity it’s normal to get a few sync errors in the beginning, still recommend you first do a non-correcting check, in case disk1 gives trouble again so there’s no chance of corrupting parity and you have the option of doing a rebuild, if the non-correcting check finishes successfully then do a correcting one.

Thanks for your help. After changing the mainboard all work fine. Parity check finding 20 errors and all is good.