NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
On No - "Remove inactive volumes to use the disk. Disk #1,2,3,4,5,6."
First of all the volume became very slow and then went read-only. After a reboot I now get a message "Remove inactive volumes to use the disk. Disk #1,2,3,4,5,6." and the data volume is totally gone!
All the drives are showing red for some unknown reason. I also reseated them all with the device turned off.
I am running a RAID-X 10 system so I should be able to lose two drives but what happened?
Halp!
Sandshark wrote:
If you already made that backup, you can save yourself some time and just delete and re-create the volume or do a factory default and restore your data from backup.
The good news is that MWT has a backup.There were a bunch of ATA errors (both read and write failures), which affected several of the disks. Three of the disks were out-of-sync when the NAS was rebooted, so the array failed to assemble.
No clear cause for the ATA errors at this point. Hopefully not the NAS hardware.
7 Replies
Replies have been turned off for this discussion
MWT wrote:
but what happened?
Download the log zip file from the logs page. It can be hard to decipher - if you like I can take a look.
Just send me a private message (PM) using the envelope icon in the upper right of the forum page. Put the log zip file into cloud storage, and include a link in the PM. Make sure the permissions are set so anyone with the link can download.
It is unfortunate that you didn't come here before you re-booted. Unless you first made sure your backup was current, that was not the correct action for a read-only volume. The volume goes read-only because it is damaged and any additional writes could further damage it. Rebooting usually results in what you are seeing.
It is almost certain your volume cannot be recovered in a manner that will make it usable, but it may be recoverable enough to make a backup. If you already made that backup, you can save yourself some time and just delete and re-create the volume or do a factory default and restore your data from backup. If you didn't make a backup, then StephenB may be able top help you mount it such that at least most of your data is recoverable once he looks at your logs.
It is unfortunate that Windows has "trained" us to re-boot when something goes wrong. With other OS's, that's often the worst thing you can do.
Thanks for the heads-up about that. From the lsblk information, those partitions aren't even being recognized as RAID partitions and the system is only seeing 3 disks for some reason. So something is terribly wrong!
What should I do next time it happens?
Sandshark wrote:
If you already made that backup, you can save yourself some time and just delete and re-create the volume or do a factory default and restore your data from backup.
The good news is that MWT has a backup.There were a bunch of ATA errors (both read and write failures), which affected several of the disks. Three of the disks were out-of-sync when the NAS was rebooted, so the array failed to assemble.
No clear cause for the ATA errors at this point. Hopefully not the NAS hardware.
It must be because of Christmas magic but the array just appeared again from nowhere and is fully working again. I'm capturing the logs in case there's something there to look at but the big question is: Should I reboot?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
