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
- (I am a hardware guy and know little about programming) but I would be willing to help raise awareness / indiegogo, or cheerlead this process.
And to anyone at Netgear or the Jedi Council, this is the spirit of ReadyNas users, we are a collection of enthuiasts of varying levels of technical ability. We want to tinker, enhance, and most of all expand our minds, I mean features. :)
XBMC, Plex, iOS, Android all have rich user bases helping to add and improve their experiences, now is our chance. Directions to upgrade your x86 legacy hardware from 4.X to 6.x
Supported so far: pro 2/4/6, ultra 2/4/6, old pro / Pioneer Pro, 2100v2
Not Supported: NVX and 2100v1
You will lose all of existing data on board.
You will most likely lose support from NTGR
1. BACKUP, BACKUP, BACKUP
2. Download 6.0.X package from NTGR
3. Edit the latest IMG for instalation by 4.2 Frontview
3. Install via 4.2.x menu
4. Reboot
5. Factory Default the system
Specifics here: http://netgear.nas-central.org/wiki/Con ... ReadyNASOS
OR (once your data is backed up)
Optional (do before step 2 below): R4toR6_Prep_Addon.bin (26 KB) (upload before modified IMG, don't reboot, avoids the need for manual factory default in between)
OS6 in 3 Steps: 1. Download pre modified IMG, (see link above to see what has been modified)
2. Upgrade firmware in Frontview 4.2 (with above file)
3. Reboot & factory default via boot menu
This has been tested on Pro6s and Ultra6s.
Current Issues:
-Fans run loud, possibly fixed via firmware edit soon.
-Genie (NTGR Appstore does not work, do NOT enable)
Post your experiences.
Thanks go out to "HomeBrew Anonymous" for making this possible.
AMRivlin wrote:
Directions to upgrade your x86 legacy hardware from 4.X to 6.x
Supported so far: pro 2/4/6, ultra 2/4/6, old pro / Pioneer Pro, 2100v2
Not Supported: NVX and 2100v1
You will lose all of existing data on board.
You will most likely lose support from NTGR
1. BACKUP, BACKUP, BACKUP
2. Download 6.0.X package from NTGR
3. Edit the latest IMG for instalation by 4.2 Frontview
3. Install via 4.2.x menu
4. Reboot
5. Factory Default the system
Specifics here: http://netgear.nas-central.org/wiki/Con ... ReadyNASOS
OR (once your data is backed up)
Optional (do before step 2 below): R4toR6_Prep_Addon.bin (26 KB) (upload before modified IMG, don't reboot, avoids the need for manual factory default in between)
OS6 in 3 Steps: 1. Download pre modified IMG, (see link above to see what has been modified)
2. Upgrade firmware in Frontview 4.2 (with above file)
3. Reboot & factory default via boot menu
Been following the above steps with no avail.I have an ultra 4 with os 4.2.27 wanting to upgrade to 0s6.4.0
installed thru 4.2.27 with R4 to R6 bin file and then the local update with 6.4.0 x86 64.img takes over 1 hour and still upgrading!!!
what is wrong?
can anyone help?
AMRivlin wrote: 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.
Interested, but unfortunatly, i think it'll all have to come from the community...
1. Netgear will never be held responsible/your warranty is void
As it already is when tweaking via SSH or tweaking the hardware, we have to factory defaut the nas if we want some support.
2. A format is required (new FS and OS)
Of course, but it was already mandatory with 4.2.16 when the FS changed and 3TB HDD came around- this is what i am proposing.
Homebrew=created at home, not in the lab.
Netgear won't bring it to fruition, so we (the community) will build it. The code is available, it will require some leg work. - Why would Netgear release their intellectual property for anyone to copy???
- BTRFS of which os6 is based on is GNU GPL.
I will monitor sf.net and see when it is posted there.
http://en.wikipedia.org/wiki/Btrfs
http://sourceforge.net/projects/easynas ... =directory
While NG won't support this effort directly, I think they see benefit in the user group continuing development and a rich user community (at least I hope they would) - Unfortunatly, they needed ample time and countless bumps from the community to release the source of their lastest firmwares (i still don't know if 4.2.22 sources are available)
But let's hope ! - hundred percent interested by a new software/boot-loader, but why a port of OS6 and not something more "free" ?
let's back-engineer - As a long-time Debian junkie, just putting my interest down... to put some longevity into my (not actually that old) Pro 6. :?
I have a Pro 6 RNDP6000-200 that I am going to redo this weekend, and hopefully end up with NOS ver. 6.x.
Wish me luck!
Dave
- +1
I too am more of a 'hardware' guy than dev but I can at least offer to beta test on any of the models I own or have access to.
I still remain confused by Netgear's stance on supporting existing x86 models. Quoting JabbaTheHut:The ReadyNAS OS 6 is only available on the new products. We are not supporting units in the field based on older operating system versions to the latest version. There are many reasons for this. There is a fundamental file system change which makes upgrading difficult to impossible for devices in use. The data risk associated with any upgrade. Even with the factory default option, there are hardware limitations on the previous generations which would need to be overcome.
Fundamental file system change, agreed. Factory default should obviate this point, no? Wikipedia's entry on Btfrs states:
Makes it sound less daunting? Data risk associated, blah blah blah - yes, there is a data risk just getting out of bed in the morning - point conceded and ignored. Hardware limitations on previous generations - this one concerns me. What hardware limitations are there? RAM? Upgrade. CPU? On an x86 Pro, don't think so. SATA controller? Maybe? Either way, we are talking about a Debian system that supports Btfrs. Nothing special there. It has a web server and some pretty screens. It has a few services tweaked and quite a few scripts written. XRAID2 = Netgear and maybe there is the bigger issue. May need to be content with standard RAID modes? Also, for the same reasons you can't simply modify a Pioneer to a BE Netgear writes in some protective code to perform a model or signature check - is it a violation of licensing or copy-write to overcome this limitation?Btrfs can warp to fit unusual spatial layouts because it has very little metadata anchored in fixed locations. The btrfs-convert tool exploits this ability to do an in-place conversion of any ext[2,3,4] file system by nesting equivalent Btrfs metadata in its unallocated space. This produces a hybrid file system that can be mounted as either ext[2,3,4] or Btrfs. If mounted as a Btrfs, all the converted files are available and writeable in the default subvolume; the old ext[2,3,4] filesystem itself is made visible as a large sparse file (mountable as a read-only disk image) in separate subvolume that can be deleted to commit the conversion. If mounted as ext[2,3,4], the conversion is rolled back.[26]
Are there any encrypted modules or a requirement for encryption in the boot image? Is any of the code licensed in such a way as to prevent a homebrew? If it can run on a Pro (which, it has been stated is just an x86 box with a nice case) it could run on any x86 box, like a generic 2RU SuperMicro box. Would Netgear feel brand dilution was an issue and issue a C&D? Hopefully no. It would be nice to have an official NTGR 'blessing' (hint hint).
In any case count me in.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
