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
There's nothing wrong with keeping the 4.2.x firmware in place either. If you want to increase data safety, you could use raid-6/dual redundancy (either with 4.2.x or btrfs).Pasala wrote: what system would you guys recommend setting up for max reliability and good speed...
In my opinion yes.Pasala wrote: Is btrfs in OS6 stable enough now for daily use?
Netgear does not use the btrfs-raid modes. Instead it uses normal software RAID with btrfs. Note normal raid will handle that scenario if the disk write (or read) were to fail - which is the usual case.Pasala wrote: Does the automatic file repair described in the arstechnica article here http://arstechnica.com/information-tech ... systems/2/ work on the Netgear?
You would need to totally rebuild the NAS, including restoring data.Pasala wrote: Switching to btrfs would lead to a data reset of an existing XRAID2 setup?
Each platform type has its own add-ons. plex is available for the x86 legacy devices.Pasala wrote: Do Add ons like plex media server work on the x86 legacy devices? - Thank you very much for your answers.
I was looking for a new operating system for my Netgear because it has quite a lot of problems
(e.g. total failure when copying files with AFP on Macs, low speeds with SMB and quite some bit rots -exactly what is described in the arstechnica article).
At this instance it would probably be a good idea using a new OS either OS6 by Netgear or FreeNas/Nas4free with ZFS to prevent these kind of failures with more data safety.
If Netgear uses software RAID with btrfs does the array have the same self healing functionality as a redundant hardware raid like btrfs-raid5 or btrfs-raid1?
If not that would probably mean the need to go for ZFS.
Anyway thanks for the help.
The scenario in the arstechnica article is very rare. It assumes that the data somehow was written to the disk incorrectly (or that the data silently changes without being re-written). In either case, the reads and writes are completing with no error reported to the driver.Pasala wrote: ...quite some bit rots -exactly what is described in the arstechnica article
Sorry to be sound skeptical here, but if you were seeing these routinely I am thinking something else was going on.
Again, no. If a read fails, RAID kicks in. If a write fails, the normal reallocated sector occurs. If the I/O doesn't fail, but the data is invalid, software RAID doesn't help you.Pasala wrote: If Netgear uses software RAID with btrfs does the array have the same self healing functionality as a redundant hardware raid like btrfs-raid5 or btrfs-raid1? - Ok. Thank you.
StephenB wrote:
Sorry to be sound skeptical here, but if you were seeing these routinely I am thinking something else was going on.
Routinely is probably an overstatement. It happened to about 5 - 8 photo files and 2 -3 video files in 4 years.
But you are right there are quite some issues going on on my ReadyNAS, which mounted after rebuilding and upgrading the NAS because of a fatal disk failure.
Another issue is an AFP failure which makes several Macs crash by putting the finder.app hors de combat every time the Mac is connected via the AFP protocol and copies data. SMB works but horribly slow at 5 MB/s. ...
So the faith in the ReadyNAS as a reliable storage system is really low at the moment.
One last question:
When one disconnecs the drives of an existing X-RAID2 stripe before using the ReadyNAS OS6 "hack", testing it with other HDDs
and then downgrade eventually back to RAIDiator 4.2 installing them back
does the system recognise the existing RAID or does it ask to do a factory reset and delete all data on the RAID array?
All according to this manual: http://netgear.nas-central.org/wiki/OS6_on_Legacy_x86
Thank you very much for the help.
PAS - If you downgraded on the test disks, it would do a reset on them.
After that you could reinstall the original disks, and it would recognize them with no problem.
Ideally label the original disks by slot # when you remove them. ATCIS wrote: Here's a quick question for the x86 Legacy Gang:
Has anyone else ever noticed that if you shut down a ReadyNAS Pro 6 (via the GUI) running OS6, that it will automatically power itself back on after approximately 5 minutes? I also have an Ultra 4, and it does not exhibit this strange behavior.
Try enabling WoL.- Hi!
I recently updated my Ultra 4 to OS6 (more info to come!). It works fine but why is there a "data-filer"?
Before I could have \\READYNAS\Pictures
Now it's \\READYNAS\data\Pictures
Thanks! - Data is the volume name, and you should only be seeing that with CIFS/SMB if you are using admin credentials to access the NAS. If you were doing that with OS4, you'd have seen \\READYNAS\C\Pictures.
You are saying that just entering \\ReadyNAS doesn't show you the Pictures share?
BTW you do need the /data/ for NFS (which can be a nuisance). Skywalker wrote:
Try enabling WoL.
Thanks for the reply Skywalker!
After doing a bit more testing, I discovered that the symptoms that I described previously was quite rare (happens maybe 1 out of 10 times I tried). Since the particular Pro 6 in question is powered on probably 99.8% of the time, it is not really an issue of grave concern. However, as I have stated in the past, I do sincerely appreciate your input!- StephenB: I was transferring a bit of data back after the os6 upgrade. Then I received a message "cannot connect discovery service" and I haven't been able to contact the NAS again. Any ideas?
I'll report back later about the data-folder
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
