I’ve a list of items to try and include however the RAID is powered down. I’ll do my best to answer the customary questions at bottom of this post:
I have a RAID5 array. One drive reports Faulty. A second reports Warning. The drive that says warning shows no errors, it just says “warning”.
I tried to swap the other drive that says “faulty” but the Qnap won’t let me rebuild the Raid array. I think because of the “warning” flag on the second drive.
I’m currently cloning the “warning” drive to a fresh drive with hopes I can put it back in the QNAP…
I may also try to clone the faulty drive. OR simply replace it with a fresh drive and let the RAID try and rebuild?
Any advice is greatly appreciated.
Your Operating System you are using to access your NAS.
Windows 10 ultimate, I use the web browser.
NAS model
TS-932X
Firmware Version/Build numbers - not just “The latest”
I only have one failed disk. The system has locked the raid due to a warning on the other disk that reports no errors otherwise. The warning appeared to be due to the disks age, 2800+ days in use. I’m unsure how to remove the “warning” flag on the old disk so I can recover the failed disk, I’m attempting a clone of that disk.
And there are ways to recover a raid 5 with dual failure, all be it with some corrupted data. Not sure if I want to go to that effort yet.
Thank you I am aware of how RAID 5 works. One drive said warning which is a little vague IMO. It showed no read write errors otherwise. I also have a backup but it’s not 100% of my data so I’m going to try and get this thing going before I give up and wipe it.
I cloned the two problem drives and put the clones in the enclosure. Curious if QNAP OS allows me to load the RAID as read only to prevent potential corruption of data?
Hey thanks! Yeah I am playing with the Qnap. The warning drive has no errors other than it says operating below threshold. However, this seems to have restricted me from doing a rebuild of the array on the disk that did fail.
I opened a ticket. Also updated specs for my build in this thread.
The screenshots say more than 300 abnormal sectors though, the drive might be working on recovering/reallocating these, but if the drive cannot do that, you have no parity to rebuild the data from.
One of my HGST drives has over 2400 days running and it is fine. No errors or anything.
I do want to say that you can adjust the warning notice somewhere in QTS. But I don’t think that is stopping your rebuild. I bet it’s the abnormal sector count as @dolbyman stated.
The disk is recovering the sectors (or is attempting to),some disks can only do it when no other ‘chatter’ is happening, it could take days/weeks/forever. It all depends on what the issue is and if the disk can fix these.
I seem to be making things worse I probably should have just left the defective drives in place to see if it would recover. I have enough knowledge about RAID to be dangerous. It seems cloning them may have confused the system as to which drives were suspect.
Thanks for the help. My practice historically has been to replace drives every few years even if they present no errors. I seem to have missed this one though.
Curious is there a way to have the system to remind you of old drives? Also a reminder to show if there’s an issue w/ a drive? I think it has a red LED on the box itself. However, it’d be perfect if it just switched to read only access as I’d notice that immediately and check the server then.
I cloned both disks; the warning disk and the faulty disk. I tried to access the RAID with the cloned warning disk first and faulty disk removed. When I couldn’t get read access, I put in the cloned faulty disk.
It may have tried to run the RAID then and corrupted? idk.
Right now I put back in both issue disks (warning & faulty) for which the report was run on.
I opened a ticket. They replied with instructions for them to remote connect to the server. I get an error though, which I sent over to them. Haven’t heard back yet. I’ve went through the instructions in their email and checked the ticket number as well as my login multiple times.
I probably should have just left the defective drives in place to see if it would recover. I have enough knowledge about RAID to be dangerous. It seems cloning them may have confused the system as to which drives were suspect.
