Nitesh

OMG what a nightmare this has been. While building Drive 1. Drive 7 Failed. Luckily I was able to build both the drives without issues Thanks again for your help

I did the extended test as suggested and for sure had read errors and failed at 10%. Just added a new drive to the array and started the rebuild. Will keep you posted on how it goes. Thanks for your help with this

oops. here it is megaatlantis-diagnostics-20230508-2116.zip

followed the instruction and started rebuild but it failed. Screenshot attached. Also attached are the latest diagnostics

Will start the rebuild tonight and report back how I go

Thanks for checking this for me. I shut down the server and checked each disk cable by unplugging and plugging back in and when I restarted. Got a message 0 Errors. But still there is a X next to the disk. Whats the best way to solve this one ? Screen shot attached. Also thanks for pointing out the aggressive spin down. I did that for a test and never reverted back. I have reverted it back to 1 hour. Hoping that 1 hour is not considered aggressive.

Hi Guys, I had this error come up with one of my data drives (disk 1) and I am not sure if its drive failure or something to do with cables. Once the error came up for the drive in question. that drive showed up in unassigned devices for some reason. Never have I had a drive fail and it show up in unassigned devices. Attached are some of the screenshots and diagnostics attached. I always have spare drives on hand so can swap it immediately if its a drive issue. Any help would be awesome! Cheers megaatlantis-diagnostics-20230507-1411.zip

Thanks mate! Will replace the disk today

So did a Extended test and attached are the results megaatlantis-smart-20220820-1016.zip

Thanks for your reply Did a short test and it came back with no errors. Doing the extended now. It will take some time. Will report back in few hours.

Using Unraid for a while but haven't had a device error before. Do I have to replace the drive or can this be fixed ? Posting my diagnostics file and hoping for help. Thanks in advance for your time megaatlantis-diagnostics-20220819-2342.zip

Nope I really didn't mean it to. The parity and the disk 3 both had problems the same day. Hence I asked the question above in my original post asking if this was the case what should I do.

Yes I do. Why?

Thanks for your help @JorgeB will go ahead and create a new parity. This time installing two parities so less chances of this happening again

Yep I knew that was happening. I just wanted to check two things 1) Anyway to check what the corrupt data was. As I still have the old disk3 from which I am hoping to replace this from. That is if it is possible. 2) that it would be safe for me to go ahead and rebuild the parity from scratch after the newly rebuilt disk3 had errors while rebuilding.

Ran SMART test. Errors occurred - Check SMART report (attached) megaatlantis-smart-20201022-2359.zip

Does that mean that the new disk3 that was rebuilt has some data missing? or corrupt?

I didn't do a dd and thought to go straight for a standard rebuild as suggested. But I received 256 errors. These errors come from the Parity drive I believe. I have never done a rebuild before. If anyone can shed a light if these 256 errors is considered huge in number and if there is anyway to check which data was corrupted? I still have the old Disk 3 from the list above which I unassigned and have not yet erased the data from. I have attached the recent diagnostics Any help would Be appreciated @JorgeB @trurl megaatlantis-diagnostics-20201022-2113.zip

Cool thanks @JorgeB I will give dd a try and if it fails will do a rebuild

Yep that is true. But at this moment the parity is not in the best possible state either. Hence wanted to check if I rebuild will the parity be able to take up the extra read and writes with the error it currently has.

Thanks for the recommendation @JorgeB & @trurl. The wiki link gave me an idea. What I might do is actually swap the Disk3 4TB with a new 4TB that I am getting as an advance replacement from WD for the Parity drive. Following https://wiki.unraid.net/Replacing_a_Data_Drive Is there a better way to just copy the data from disk 3 to the new disk 3 without having to rebuild from parity? Just so i don't strain other drives in the process. Once that is done I will proceed with the just removing the current parity drive and adding two new 8TB ones and rebuilding the parity. Do let me know if I am not going the right way Cheers

Hey Guys, Have been searching this for a while so wanted to know what is the best way of doing this. What I want to do is replace the Parity drive from one 4TB to two 8TB drives. Whats the best way to do this. I am expanding the parity now to 2x8TB so I can then replace the 4TB data drives to 8TB when and if they start failing at a later stage and this will give me an option to add larger drives later. Below is my current structure. Parity Drive - 4TB (Reported uncorrect 1) Disk 1 - 4TB Disk 2 - 4TB (UDMA CRC error count 1) Disk 3 - 4TB (Raw read error rate 125) So i suspect this is failing. Disk 4 - 2TB Disk 5 - 2TB Disk 6 - 4TB Disk 7 - 4TB Also confused about the Disk 2 and 3 errors as some forums suggest that it might just be a loose cable. If I replace and expand the parity 1st and if the errors in Disk 2 and Disk 3 are serious. I worry I might loose that data. Attached is the diagnostics report in case anyone wants to look at it. Cheers megaatlantis-diagnostics-20200922-1958.zip

Thanks for this. I ran extended SMART test and it came back with no errors. So hoping that is OK for now.

Hey Guys, I have a drive read error on disk 3 on my server. Can someone help me solve this issue? I have attached the diagnostics Cheers, megaatlantis-diagnostics-20200401-0950.zip

As soon as i was looking for the relative paths to post the screenshot here, i realised my mistake. I was moving from Root > Unraid > Cache > Downloads which should have been Root > Unraid > user > Downlaods. Hence it was actually using the disk share to transfer, rather than using the user share which triggers the cache functionality of the server. My mistake. But thanks for making me look for the right thing Cheers,