This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I, too, have had major issues upgrading from 6.7.2 to 6.7.3 or 6.7.4. Please note that I am running an external enclosure. If I upgrade with the external enclosure powered up, I get endless loops of the log sample below. The device never completes bootup. I've waited days and gotten nothing. I have to manually power it down, turn off the external enclosure, then boot back up so that I can downgrade.
I'm a little disgusted with Netgear on the whole. I've avoided Netgear's network devices because I have had very bad luck with stable operation and hardware that lasts past the warranty. Now I'm having issues with the NAS equipment. I specifically purchased Netgear because of BTRFS and a few other features that were unique at the time. Now all vendors are on a level playing field feature-wise and Netgear lags behind everyone in NAS OS development. Have you guys ever looked at an ASUSTOR or QNAP? Their feature set runs rings around ReadyNAS. ReadyNAS OS looks like it's from 2000 and runs like a badly tuned Linux port (which it is).
Seriously, guys. Is it too much to ask to make a serious effort at fixing the issues and modernizing the OS?
Fri May 26 2017 3:00:49
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:57:33
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:57:18
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:57:03
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:56:48
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:56:33
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:56:18
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:56:03
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:55:48
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:55:33
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:55:18
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:55:03
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:54:48
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:54:33
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:54:18
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:54:03
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:53:49
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:53:34
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:53:19
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:53:04
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:52:49
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:52:34
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:52:19
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:52:04
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:51:49
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:51:34
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:51:19
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:51:04
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:50:49
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:50:34
System: ReadyNASOS service or process (readynasd) was restarted.
Fri May 26 2017 2:50:19
System: ReadyNASOS service or process (readynasd) was restarted.
If you look under the hood our OS is based on Debian Jessie and the kernel is based on the 4.4 LTS kernel series with backported patches. We're ahead of at least most of the competition in this I believe.
Our experience with BTRFS is much greater than most too as we've been using it for all our new products since 2013 as the default and only filesystem for the data volume (and for the root volume as well on x86 systems).
If there's features you'd like to see added you can post them or upvote them in the Idea Exchange for ReadyNAS
It would be good if you could send in your logs (see the Sending Logs link in my sig).
You may have also got a core dump (/var/cores/core-readynasd) which would be useful for debugging the issue you encountered.
I'm in the same boat. Upgraded from 6.6.1 to 6.7.4. Volumes are up, system reachable through ssh, but admin page is offline. Readynasd is restarting every 15 secs.
What would the first step be: firmware reinstall?
Thanks
P
Model: EDA500|ReadyNAS Expansion Chassis 5-Bay,RN31200|ReadyNAS 300 Series 2-Bay
That seems to be doing the trick, thanks! Admin page is up, nothing unusual to been seen for now. I have to say though that I'm always very reluctant to upgrade this OS6 box, ran into serious trouble in the past. I never had any issues upgrading my NVX Pioneer, different OS though.
Well, the changelog (#3) mentioned 'Fixed "Management service offline" issue, with an EDA500 unit attached and an orphaned volume record.' That was one of visible symptoms I noticed (the 'Management service offline' message in Raidar) . From the logs I could not make a direct connection with the EDA500 attached to my 312 however.
