NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
After upgrading to 6.7.1 on RN214 no volumes can be loaded
Hello, I just installed the new upgrade 6.7.1 on my RN214 and got the confusing message that my volumes can`t be loaded. It`s the same problem others have: ReadyNAS 516 just upgraded to 6.7....
You could perhaps try ReadyNASOS 6.7.3-T283 (Beta 1)
There's a fix in there for one possible reason why a volume may not mount. I wonder if you ran into that.
Not necessarily, no.
Let's wait for mdgm's feedback.
Let's wait for mdgm's feedback.
What do you mean?
I don't want to argue with you I am only curios.
Best regards
KalleI'm not arguing either :smileywink:
There are multiple reasons for the volume to appear "inactive", some of the most common:
- Full root: the volume dedicated to the system is completely full, preventing it from booting properly. In your case, it could be related to the process of updating the F/W (any F/W). Or some add-on that filled the volume and the consequence appeared after the reboot, as part of the update process.
- Corrupt system: often due to the previous condition, but also rarely occur without full root.
- Multiple disk failure: your drives could have been slowly dying but seemlessly "working", or suddenly died, or a mix. Updating a firmware implies writing to the drives which can trigger failure(s).
- Erroring disk: a disk can be flapping and cause the NAS to be enable to mount the volume.
- BTRFS corruption: any operation on the volume, even mount/unmount can lead to filesystem corruption if an unexpected event occur (at FS or HW level). It happens.
Etc.
It's a shame that the NAS doesn't show why is the volume inactive, in the GUI. It would reasonably easy to integrate it and really useful for anyone running into the issue, hence the post in the "idea" section.
Not sure why it hasn't started. Would need a remote look to get more of an idea.
In a nutshell, loading the new OS version may have been the "last straw" in a series of events that caused the problem. So the new OS, in and of itself, may not be to blame. The new OS version itself may be a contributer if it does not tolerate a pre-exisitng problem as well as the previous version, or the simple process of doing an update (which uses space in the OS partition) may have been all it took.
There are also a couple posts in the idea exchange about better controlling OS partition problems (if that's what your issue is) that you may also want to up-vote.
Sandshark wrote:In a nutshell, loading the new OS version may have been the "last straw" in a series of events that caused the problem. So the new OS, in and of itself, may not be to blame. The new OS version itself may be a contributer if it does not tolerate a pre-exisitng problem as well as the previous version, or the simple process of doing an update (which uses space in the OS partition) may have been all it took.
There are also a couple posts in the idea exchange about better controlling OS partition problems (if that's what your issue is) that you may also want to up-vote.
This makes sense given I had a pre-existing error prior to upgrading from 6.6.1 to 6.7.1.
Not sure from the logs why it's not mounting. The logs show:
May 14 19:55:19 ReadyNAS start_raids[1041]: mdadm: device data-0 exists but is not an md array.
The disks appear to be healthy from looking at smart_history.log, but the RAID hasn't started.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
