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
- mdgm-ntgrNETGEAR Employee Retired1. You can downgrade if you don't like it (I can PM you a link to an image to downgrade if you like. I might even post a link at some point). You should maintain a regular backup anyway
2. If you backup important data regularly it should be low risk. If you run into issues the community here will do its best to help. - I'm definitely interested in upgrading and down grading potential, but I need to read 57 pages of threads before I know what I need to do.
I browsed by a comment about the bios needing upgrading first so I put the brakes on, is there a recommend link to help shortcut all the reading,
not trying to be lazy but is there a better starting thread than the start of this one? as it has grown huge.
I am looking at buying my 4th ReadyNAS and have been looking at the 516 and 6HDD Raid6 but I need to read a little more. - chirpaLuminaryMaybe we need to grow this thread: viewtopic.php?f=51&t=73874
- mangroveApprenticeRight now I can hardly see a point for normal users in being a beta tester for an unfinished system. The next update will require a factory default to fix a BTRFS bug, for example.
My points from the beginning has been:
1) OS6 was far from finished when released
2) BTRFS wasn't a very smart choice as the main file system
Events are fully validating those points. Oh, except for a few apologists, of course. - chirpaLuminaryYes. Since the OS name changed from RAIDiator to ReadyNASOS, would have been nice to use a realistic versioning number. At least ReadyDATA started out at a proper 1.0.0. ReadyNASOS should be around 1.0.3 by now. Still a very immature release as many have commented.
- tadgy1Aspirant
mangrove wrote: The next update will require a factory default to fix a BTRFS bug, for example.
Whosaidwhatnowhuh?
I've recently upgraded my Ultra4 to 6.1.4 (which obviously involved the factory reset), and now i'm going to have to factory default AGAIN for 6.1.5?
Can I ask where you read/saw that? I'd like some info on it, and - if you happen to have it - some info on the BTRFS bugs you mention?
FWIW, I share the concerns over BTRFS. As a Linux user of more years than I care to remember, i've always stuck with the mature and reliable ext* filesystem. The claim that BTRFS is reliable and production ready seems a little premature. But, there's little point complaining about it now - Neatgear have engineered OS6 to use it, so nothing we say here is going to change that. The key is going to be for the community to find ways to avoid data loss or filesystem issues because of it.
Having a much more up to date Linux system underneath is a great positive for people who want to tinker with what their NAS can do; so i'm glad of the upgrade for that. But BTRFS worries me, i'll admit. - F_L_Tutor
tadgy wrote: mangrove wrote: The next update will require a factory default to fix a BTRFS bug, for example.
Whosaidwhatnowhuh?
I've recently upgraded my Ultra4 to 6.1.4 (which obviously involved the factory reset), and now i'm going to have to factory default AGAIN for 6.1.5?
Can I ask where you read/saw that? I'd like some info on it, and - if you happen to have it - some info on the BTRFS bugs you mention?
FWIW, I share the concerns over BTRFS. As a Linux user of more years than I care to remember, i've always stuck with the mature and reliable ext* filesystem. The claim that BTRFS is reliable and production ready seems a little premature. But, there's little point complaining about it now - Neatgear have engineered OS6 to use it, so nothing we say here is going to change that. The key is going to be for the community to find ways to avoid data loss or filesystem issues because of it.
Having a much more up to date Linux system underneath is a great positive for people who want to tinker with what their NAS can do; so i'm glad of the upgrade for that. But BTRFS worries me, i'll admit.
More info here: viewtopic.php?f=65&t=73537&start=45#p411589 - darshanAspirantHello there,
first: I didn't read the post properly.
second: I am an idiot.
Now, long story short: I upgraded to OS 6.1.4, which was very easy. Thanks for that. But I didn't realize that when you guys said "all data" it literally meant everything in the hard drives (my thoughts were more or less along the lines of the settings and whatnot).
So now I have a fully functioning ReadyNas Ultra 4 with apparently no data in it.
I am knowledgeable enough to know that the data is still there, as no low level formatting has happened. But I am not sure if there is an easier way than a proper data recovery process to get this information back.
I am trying to boot back to 4.2.24 with a USB, but any further suggestions are accepted (or you can ignore me, which I would understand that too considering how idiotic I am).
thanks - darshanAspirantok, managed to downgrade to 4.2.24, but obviously now wants to rebuild the x-raid2 setup.
any suggestions if I can rebuild the x-raid2 setup without creating a new volume (which then I am guessing will destroy data). - tadgy1Aspirant
darshan wrote:
I am knowledgeable enough to know that the data is still there, as no low level formatting has happened. But I am not sure if there is an easier way than a proper data recovery process to get this information back.
I'm afraid that assumption is a little wrong.
As far as I could tell, from the first boot of 6.x a new btrfs filesystem is created on your drives. Since btrfs is a totally different filesystem from ext* (which 4.x used), it would have had to re-format the disk table/inode structure to suit the new filesystem. That is a data destructive operation - unless (and i'm no expert on this subject) btrfs does "lazy" init of it's filesystem elements (ie, it initialises them as it begins to use the space).
However, even with the lazy init (if btrfs does indeed do that, which remains to be seen...) the filesystem superblock(s) will have been over-written making them un-mountable as the old ext* filesystem. Also given the OS6 init process puts a load of stuff on the disks, depending on where your data was located on those disks (in a physical sense), it may have also been over-written already.
In short, you are unlikely to recover any data by going back to 4.x; and even if you are, it's going to need forensic data-recovery tools, a truck load of desire and a metric shit-tonne of time to do so.
Sorry to say it, but unless you've got £4m in bitcoins on that disk, you're better off having a few shots of your favourite tipple and cutting your losses.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!