You can try booting up with just the 5 drives and see if it comes up with a degraded (non-redundant) volume. It's possible that the one bad drive was affecting the entire SATA subsystem, so it's your only problem. But it's not that likely. There is no "fix all" because there are too many things that can go wrong. @StephenB can help you with the commands needed to try and assemble the volume once he gets a look at your logs.
I am just wondering - there is a Fix All option in the software - any good to run this with that drive ? or would it destroy the data on it eg (RAID5 system)
My experience with that feature in the past was never good, so I don't use it.
Generally once a drive starts to fail, it rapidly gets worse. So the track sparing in the software doesn't seem to help for long.
My experience with that feature in the past was never good, so I don't use it.
Generally once a drive starts to fail, it rapidly gets worse. So the track sparing in the software doesn't seem to help for long.
I was thinking the same thing to be honest.
You can boot with 5 drives. The array should mount, and should be marked as degraded.
Yes again was thinking the same thing. With the degraded the NAS would still work but slower than normal. Also would I be able to add to the NAS while in degraded mode?
I re-inserted HDD5 after it passed the HDD test. Then powered on the NAS without HDD6 inserted and it booted up. Everything was normal as in the NAS was not displaying any issues on its display when I was expecting to see a notice of it saying that the system is degraded. So I went on my laptop and logged into the readynas Home Screen.
When. I logged in there was a message at the top but it wasn't a system degrading message. It was a message saying to remove the necessary drives BECAUSE when I clicked on Volumes icon all the drives are RED and it is saying that the NAS is FULL = zero space available.
I wonder if this has anything to do with the initial process it was doing as I am only 90% sure it was completed before the power was interrupted.
Will the NAS recover to normal when I insert a replacement drive into bay 6 ?
No, it will not self-repair when you replace Drive 6. It does appear the death of drive 6 caused a problem on the SATA bus, but did so during a write. So data on one or more other drives is corrupt or out of sync. Hopefully, you can now download the log .zip and @StephenB can use that information to better diagnose the specifics of your issue and help you at least get the volume mounted so as to allow you to get your backup up to date before factory defaulting the NAS with a new drive.
I wonder if this has anything to do with the initial process it was doing as I am only 90% sure it was completed before the power was interrupted.
Will the NAS recover to normal when I insert a replacement drive into bay 6 ?
The volume is probably out of sync. Download the full log zip file from the logs page.
I can take a look at that for you if you like. Just upload it to cloud storage (Dropbox, google drive, etc), and send me a download link in a PM (private message). Use the envelope link in the upper right of the forum page.
I will be traveling this week, so it might take me a couple days to get to it.
Please send your PM on the location of the logs to @StephenB, not me. I'm really mainly a hardware guy, but I've also run a lot of experiments on ReadyNAS to learn its ins and outs and have seen a ton of messages here in the forum about volume issues. But when it comes to diagnosing and repairing BTRFS and MDADM issues, @StephenB has far more experience than I.
The screen shot really doesn't clear things up except to say that there is something more wrong than just a missing drive, as I had already surmised. There are a lot of things that can go wrong and result in that display, thus the need to upload the logs to see which problem yours is.
My apologies and I have done so. Many thanks for all the advice and help as always. You and StephenB really show what a community stands for. Many thanks for this and everything else in the past.
I reckon it is going to be a long road ahead and expensive by the sounds of what StephenB has been correlating to me.
StephenB has already told me that the logs indicate that the RAID is in sync and it is more of a file system issue. So hence a long road ahead.
