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
- So, I just lost about 15 minutes worth of typing due to this error:
Sorry but the board is temporarily unavailable, please try again in a few minutes.
Anyway, what I think I was saying was:Skywalker wrote: How are you concluding that it didn't clear the history?
Because that is what the GUI is telling me. . .Skywalker wrote: We'll still read the current information from the drive and re-populate the database. If your ATA error count was high before, it will still be high, because that count is stored in the drive and we can't reset it. However, any alert messages about your ATA error count increasing should go away, unless it continues to increase more than expected.
Okay now I'm confused. . . Earlier you said:Skywalker wrote: Diagnostic programs don't pay attention to ATA errors. ATA errors can be caused on some drives by simply sending the drive an invalid command. But we don't expect that to be happening on the ReadyNAS, so ATA error are out of the ordinary.
and. . .Skywalker wrote: If you have SSH, you can check your SMART data and ATA errors by running these commands: smartctl -a /dev/disk/internal/0:5*
. . .which I did, and the drive reported that it was perfectly heathy. No errors whatsoever. Hence my confusion. . . :?
If you would like to see the output of the command above, this is what it looks like:
https://dl.dropboxusercontent.com/u/4603388/SmartData.txt
Is there some other stored data on the drive that "smartctl" isn't reporting?
Please clarify, and. . .
Thanks again! - I added an additional disk to my Pro6 and the rebuild is taking an age. Anyone got any ideas how I can speed it up?
- SSH in and run "top". Are any services hogging resources?
- Heres what I have running:
- Try disabling Plex Media Server and the iTunes (forked-daapd) server and see if the rebuild speeds up.
- That's reduced it to around 100 hours -Thanks. Still seems a long time though.
- Hopefully it will speed up further.
- So my ultra2 gave up on me, nothing helped (os re-install/factory default/usb recovery). No contact at all with the NAS. Just starting and fan goes on and off on an interval. Anyhow in case anyone of you in a similar situation this really helped on getting the data back from the drives in x-raid and formatted as btrfs as no app i found could manage.
install ubuntu with widows installer (usb stick install was messy)
http://www.ubuntu.com/download/desktop/install-ubuntu-with-windows
then with all rives connected use terminal:
http://www.readynas.com/forum/viewtopic.php?f=4&t=71423
#sudo su
#apt-get mdadm install
# mdadm --assemble --scan
# cat /proc/mdstat (mine was md127 change if diferent)
# mount -t btrfs -o ro /dev/md127 /mnt
and the drive can be opened from the disk tools mounted as /mnt - Another option would have been to migrate your disks to a new ReadyNAS running ReadyNAS OS.
Iridabike wrote: That's reduced it to around 100 hours -Thanks. Still seems a long time though.
So has your RAID Array re-sync finished yet? It looks like your NAS is configured in a similar fashion to the one I have been stress testing with OS6. When I expanded my array from 5 drives to 6, the process took approximately 32 hours.
Please report back when yours finishes. I'd be curious to hear how long yours took.
P.S.: What type of drives are you using?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
