NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AMRivlin
Mar 20, 2013Apprentice
OS6 now works on x86 Legacy WARNING: NO NTGR SUPPORT!
Update: It is now unofficially possible using NTGR images to update legacy hardware to os6.X
See Post #3, for directions to install 6.2.1 on x86 Ultra and Pro Models. (ARM NOT SUPPORTED by this OS)
Be forewarned, this requires a SYSTEM WIPE and likely voids any warranty support from NTGR
Supported so far: pro 2/4/6, ultra 2/4/6, old pro / Pioneer Pro, 2100v2
Not Supported: NVX and 2100v1
Thanks go out to "HomeBrew Anonymous" for making this possible.
Update 2: A firmware image to downgrade back to 4.2.26 is now available. See this thread. While this downgrade should get you a working system again on the supported firmware, be forewarned this requires a SYSTEM WIPE and NetGear also does not provide support for this downgrade. If you have issues seek help on these forums.
Original Post/Gripes
I have been reading these forums since Monday's announcement and there has been a resounding "ooof" regarding the fact the Ultras and Pros are unsupported for future OS improvements.
To clear the air: it would appear Netgear will never support os6 on past hardware. I have almost come to grips with this, and at least they have been open and honest with their forward direction and aren't stringing us along. viewtopic.php?f=138&t=70131
The upside is our devices still work and are mostly stable and eventually we can upgrade to a new shell that has os6 support, but in the meantime our $500-1000 investment is unable to take advantage of modern features we all desire.
I don't think I can add a poll here at RN forums, but I would like to garner support for a 100% unsupported home brew of the os6 on Pro6 units.
If we get enough support perhaps a talented member(s) here would help release a homebrew of sorts.
The 3 main caveats are:
1. Netgear will never be held responsible/your warranty is void
2. A format is required (new FS and OS)
3. Data loss is highly possible
If you are still interested please post a reply to this thread.
mdgm and I have decided that its time to lock this thread. So please do post any new OS6 on Legacy issues on their own threads.
1,274 Replies
Replies have been turned off for this discussion
- DariusSkiAspirantI have installed 6.0.8 on Ultra4 and everything seems to be fine, front page reporting is broken, but other than that everything is fine. Even iSCSI is working great ( from windows 7 clients using mutual CHAP).
I have a bit "advanced" problems - please note that they should not stop anyone from using OS6 on older gear, they are just plea for advanced help:
1) I don't seem to be able to stop the NAS from "calling" home, i ran apt-get purge on some packages as recommended earlier in this thread, but i still get this:
root@poligonas:~# netstat -tan
tcp 0 0 192.168.1.72:35191 206.16.42.179:443 ESTABLISHED
Anyone got clue how to get rid of this stuff?
2) Power efficiency of OS6, it just seems to be chewing a few watts more than 4.2.24. While i don't really care about disk turning off, i decided to dig deeper and didn't like what i've found:
After running
pidstat -t -w
i saw this:
12:52:11 AM 1673 - 1.00 0.00 readynasd
12:52:11 AM - 1673 1.00 0.00 |__readynasd
12:52:11 AM - 1734 100.00 1.00 |__readynasd
12:52:11 AM - 1735 100.00 0.00 |__readynasd
12:52:11 AM - 1736 100.00 0.00 |__readynasd
12:52:11 AM - 1737 100.00 0.00 |__readynasd
12:52:11 AM - 1738 100.00 2.00 |__readynasd
12:52:11 AM - 1740 100.00 0.00 |__readynasd
12:52:11 AM - 1741 100.00 0.00 |__readynasd
12:52:11 AM - 1749 100.00 0.00 |__readynasd
12:52:11 AM - 1750 1.00 0.00 |__readynasd
12:52:11 AM - 1761 1.00 0.00 |__readynasd
12:52:11 AM - 1938 1.00 0.00 |__readynasd
Yup, you see it right, it is readynasd waking your CPU 800 times per second and not letting it go to deeper sleep states.
And unfortunately those threads are not doing anything important either, they are using technique that has fallen out of favor in any power use aware programming for years now:
strace -r -p 1734
Process 1734 attached - interrupt to quit
0.000000 restart_syscall(<... resuming interrupted call ...>) = 0
0.006898 nanosleep({0, 10000000}, NULL) = 0
0.010366 nanosleep({0, 10000000}, NULL) = 0
Yup, that is nanosleep for 10ms burning extra electricity.
4.2.24 had none of this, looking at vmstat you could see dozens of interrupts/wakeups instead of thousand+ on OS6 box...
Question is - can we get rid of all this madness? I can't dig deeper without gdb and powertop, but maybe some Jedi will have a clue wth is going on with those 8 threads?
3) Anyone got idea why Netgear is using acpi_idle instead of intel_idle? while both are using mwait in idle, intel_idle can go deeper. I wonder if anyone tested custom kernel with intel_idle, is it working? - SkywalkerNETGEAR Expert
DariusSki wrote: 1) I don't seem to be able to stop the NAS from "calling" home, i ran apt-get purge on some packages as recommended earlier in this thread, but i still get this:
root@poligonas:~# netstat -tan
tcp 0 0 192.168.1.72:35191 206.16.42.179:443 ESTABLISHED
Anyone got clue how to get rid of this stuff?
Which process is it?# apt-get purge busybox-net-tools
# apt-get install net-tools
# netstat -tanpDariusSki wrote: 2) Power efficiency of OS6, it just seems to be chewing a few watts more than 4.2.24. While i don't really care about disk turning off, i decided to dig deeper and didn't like what i've found:
...
Question is - can we get rid of all this madness? I can't dig deeper without gdb and powertop, but maybe some Jedi will have a clue wth is going on with those 8 threads?
Yes, you should find that the next release behaves much better in this regard. We should have a beta very soon.DariusSki wrote: 3) Anyone got idea why Netgear is using acpi_idle instead of intel_idle? while both are using mwait in idle, intel_idle can go deeper. I wonder if anyone tested custom kernel with intel_idle, is it working?
Just a simple oversight. intel_idle will be enabled in the next release as well. - DariusSkiAspirant
Skywalker wrote:
Which process is it?
tcp 0 0 192.168.1.72:35683 206.16.42.179:443 ESTABLISHED 16086/rcbrokerdSkywalker wrote:
Yes, you should find that the next release behaves much better in this regard. We should have a beta very soon.
Just an simple oversight. intel_idle will be enabled in the next release as well.
AWESOME, thanks a lot for keeping community updated. Looking forward to these low hanging fruits of power efficiency. OS6 is really shaping up. - mdgm-ntgrNETGEAR Employee Retired6.1.1 beta firmware is available if you would like to try it: http://www.readynas.com/forum/viewtopic.php?f=154&t=72282
- IridabikeAspirantTook the plunge and have 6.1.1 beta running on my Pro 6. Mostly all ok. Fans, temps and temp rrd trends still don't work on Pro 6 without some mods/patches.
Have some problems moving the apache port from 80 to 8080 as ports.conf no longer seems to be recognized but other than that all seems good.
Edit: apache2 ports are fine and can be set. I had a typo! Have noticed one problem though: Network config from frontview gives an error.
Edit2: Network trending isn't working in frontview performance monitoring either on a Pro 6. - SkywalkerNETGEAR Expert
DariusSki wrote: tcp 0 0 192.168.1.72:35683 206.16.42.179:443 ESTABLISHED 16086/rcbrokerd
That's the ReadyCloud service.systemctl disable rcbrokerd
should take care of it. There's supposed to be a way to disable this from the UI, but it doesn't appear to be straightforward at this point. - DariusSkiAspirantran
root@poligonas:~# systemctl disable rcbrokerd
rm '/etc/systemd/system/multi-user.target.wants/rcbrokerd.service'
but i can still see the process of "rcbrokerd". Killing it is not working either, it restarts immediately :) - SkywalkerNETGEAR ExpertOh, right, that's the saved state and wouldn't take effect until you reboot. For immediate action, you need to add "systemctl stop rcbrokerd".
- IridabikeAspirant6.1.1 beta on Pro 6 problems so far:
1) Network card is not recognised in frontview - gives an error and shows a blank screen and hence cannot change any network settings
2) Network data does not show in the performance trend
3) Cannot download the logs
Plus the usual problem with temps and fans
Does anyone know if I can switch back to 6.0.8? - demetrisAspirantSo some good news update
It seems sabnzb is added to the utility list of netgear yay!
apt-get update
apt-get install sabnzbd
will install: libcgi-pm-perl python-yenc libcgi-pm-perl python-yenc sabnzbd
Version? sabnzbd_0.7.13-0rnx1_all.deb Awesome!
Get:2 http://apt.readynas.com/packages/readynasos/ 6.0.8/apps sabnzbd all 0.7.13-0rnx1 [2695 kB]
Before you update go to sabnzb config then select General tab.
At SABnzbd Port change to 2708 and save changes then restart sabnzbd.
After Official Netgear install it will show up in apps panel and be able to launch it from there
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!