NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
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
- Hi there,
at first I'm enjoing the silence with my pro 6! Did it the glem-way. :D Thank you!!!! :worship:
From time to time I cannot login via ssh:
Sometimes on 192.168.1.16 (static) I get no respone at all.
Sometimes I can only access the nas vie the second interface. Any clues?
Also I have problems with samba, I guess: The Pro 6 (OS 6.05) often cannot be seen, neighter with android (es file browser) nor under Windows 7 (32/64). :( And if it shows up, I cannot access the shares (factory settings!), because (translated errormessage:) "\\Nas couldn't be accessed". The Windows7 assistance says there is no computer names "Nas" on the network also it showed up...
If the VirtualBox NASOS6.05 (many thanks
)showes up all the shares can be accessed with no problems... strange
btw: no proplems with my Duo V1 at all.
Best regards,
Martin - btw:
:rofl:
unused : "Frei"
Kostenlos: free of charge
used: Belegt (in this context)
Daten: data
don't worry, be happy!
brgs,
Martin mwlodarc wrote: great solution with fancontrol.
And with 6.0.5 firmware readycloud work on legacy ULTRA 4
rgds
Updating my Ultra to OS 6 worked straight away. Thanks to those who made this available.
However I could not get readycloud to work on my Ultra with OS 6.05. At the end of the registration proces it asks for the Backup button to be pressed.
But nothing happens when this button is pressed.
Is there a work around for this?
Also activating the Dropbox functionality in OS 6.05 did not work. The Dropbox webpage says "The request to link the app is invalid"- I have the ReadyNAS Pro 6 and this is my values for /etc/fancontrol
INTERVAL=5
DEVPATH=hwmon0=device/platform/coretemp.0 hwmon1=devices/platform/w83627ehf.2576
DEVNAME=hwmon0=coretemp hwmon1=w83627dhg
FCTEMPS=hwmon1/device/pwm2=hwmon1/device/temp2_input hwmon1/device/pwm1=hwmon1/device/temp1_input
FCFANS=hwmon1/device/pwm2=hwmon1/device/fan2_input hwmon1/device/pwm1=hwmon1/device/fan1_input
MINTEMP=hwmon1/device/pwm2=20 hwmon1/device/pwm1=20
MAXTEMP=hwmon1/device/pwm2=60 hwmon1/device/pwm1=60
MINSTART=hwmon1/device/pwm2=45 hwmon1/device/pwm1=15
MINSTOP=hwmon1/device/pwm2=14 hwmon1/device/pwm1=10
MINPWM= hwmon1/device/pwm2=70 hwmon1/device/pwm1=15
MAXPWM= hwmon1/device/pwm2=150 hwmon1/device/pwm1=150
Correct me if I'm wrong but I think theses are the best values so far, I think a little more test is in order once the volume rebuild is complete. pywong wrote: I have the ReadyNAS Pro 6 and this is my values for /etc/fancontrol
INTERVAL=5
DEVPATH=hwmon0=device/platform/coretemp.0 hwmon1=devices/platform/w83627ehf.2576
DEVNAME=hwmon0=coretemp hwmon1=w83627dhg
FCTEMPS=hwmon1/device/pwm2=hwmon1/device/temp2_input hwmon1/device/pwm1=hwmon1/device/temp1_input
FCFANS=hwmon1/device/pwm2=hwmon1/device/fan2_input hwmon1/device/pwm1=hwmon1/device/fan1_input
MINTEMP=hwmon1/device/pwm2=20 hwmon1/device/pwm1=20
MAXTEMP=hwmon1/device/pwm2=60 hwmon1/device/pwm1=60
MINSTART=hwmon1/device/pwm2=45 hwmon1/device/pwm1=15
MINSTOP=hwmon1/device/pwm2=14 hwmon1/device/pwm1=10
MINPWM= hwmon1/device/pwm2=70 hwmon1/device/pwm1=15
MAXPWM= hwmon1/device/pwm2=150 hwmon1/device/pwm1=150
Correct me if I'm wrong but I think theses are the best values so far, I think a little more test is in order once the volume rebuild is complete.
Here's my updated fancontrol file
INTERVAL=5
DEVPATH=hwmon0=devices/platform/coretemp.0 hwmon1=devices/platform/w83627ehf.2576
DEVNAME=hwmon0=coretemp hwmon1=w83627dhg
FCTEMPS= hwmon1/device/pwm2=hwmon1/device/temp2_input hwmon1/device/pwm1=hwmon1/device/temp1_input
FCFANS= hwmon1/device/pwm2=hwmon1/device/fan2_input hwmon1/device/pwm1=hwmon1/device/fan1_input
MINTEMP= hwmon1/device/pwm2=20 hwmon1/device/pwm1=40
MAXTEMP= hwmon1/device/pwm2=60 hwmon1/device/pwm1=65
MINSTART= hwmon1/device/pwm2=45 hwmon1/device/pwm1=15
MINSTOP= hwmon1/device/pwm2=14 hwmon1/device/pwm1=10
MINPWM= hwmon1/device/pwm2=70 hwmon1/device/pwm1=15
MAXPWM= hwmon1/device/pwm2=240 hwmon1/device/pwm1=75
But I am still having problems it does not seem to be working, the fan speed does not change and it's quite loud.
Also the LCD does not seem to turn off.
So it looks like that the new OS6 does not work on the ReadyNAS Pro 6.
Any Ideas?
Thanks- You can try (to download the latest packages):
apt-get update && apt-get upgrade
You have to stop/start fancontrol daemon for changes in file /etc/fancontrol takes effect
...change values in file
/etc/init.d/fancontrol stop
/etc/init.d/fancontrol start - Is your volume still resyncing? The display won't turn off while the volume is resyncing.
- Slowly, slowly getting there. Maybe maboehme could share how he makes logitechmediaserver start automatically when the nas starts, as there is no icon, and i don´t manage with the console. Vielen Dank!!
maboehme wrote :
From time to time I cannot login via ssh:
May be you have a problem with your two ip addresses configuration on the same NAS in the same subnetwork... Why one static address and one DHCP? Normally, the MTU would be the same within a given network... strange issues are possible when you mix MTU within a subnetwork, and within a multi-NIC server too...
You have one hostname with two IP addresses in the same network... As you described before, Windows use hostname and doesn't like it.
You can try bonding the two NICs in "Adaptative Load Balancing" mode, you don't need any special switch configuration for this mode. You will have only one mac address and one IP address....and one MTU. Go to network menu to activate it.- I did a apt-get update and upgrade. The unit has finished restriping.
I install fancontrol and did a reboot but it does not work right.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
