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
- Did you check the SMART stats for ATA errors using LifeGuard Diagnostics or another tool?
A factory would wipe all the tweaks you did. mdgm wrote: Did you check the SMART stats for ATA errors using LifeGuard Diagnostics or another tool?
YES. Both tools reported that the drive was in PERFECT Health.
Check out this screen shot:
The Array rebuild is almost 2/3rds completed and has been running for several hours now. Wouldn't you suppose that if this drive was REALLY BAD, that the ATA errors would have incremented (even slightly) by now? Upon drive insertion the ATA Error count was 24638. I just checked it again three plus hours into the rebuild and it is still at 24638. Doing an Array rebuild is a VERY Disk I/O intensive operation, is it not? Wouldn't you have thought the errors would have increased by now?
:werd:- whelp, after several tries and 3x readynas ultra pro 2; ReadyNAS OS6.0.x is NOT stable for production. i knew it was a bad ideal to try to run it in an production environment. but particularly, after trying multiple times running iscsi lun with mpio connections from multiple hosts, initially after x amount of days the lun would literally drop the filesystem. this is an hyper-v 3.x environment with the lun as an CSV; this happened three times, with the same result.
fortunately i learned a trick to be able to remount the lun as a readable filesystem, and all the data is intact, but any further use would render the filesystem useless again.
having this occur with running VM's is simply not worth the risk. i think there is something inherently wrong with the way iscsi is handle in readynasos6 compared to raidiator 4x for the readynas models. so just a warning to others, please be advise about using iscsi lun on an ultra pro 2;if you have ran into this issue and trying to get your data back from the raw filesystem, message me and i'll help you through it ATCIS wrote: Which leads me to three questions, which are:
1.) Why do you suppose the ReadyNAS thinks that this drive has issues when two different Hard Drive diagnostic programs say otherwise?
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. If you have SSH, you can check your SMART data and ATA errors by running these commands:apt-get install smartmontools
smartctl -a /dev/disk/internal/0:5*ATCIS wrote: 2.) Does OS6 have some sort Hard Drive Database that remembers every Hard Drive that has ever been in it?
3.) If number 2 above = YES, is there some way to clear that data so that the ReadyNAS reassess the condition of a particular drive from scratch sometime in the future?
From SSH, run this command to reset the error history log:rm -f /var/readynasd/smart.sq3
- Thanks Skywalker!
Awesome reply! :worship: 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. If you have SSH, you can check your SMART data and ATA errors by running these commands:
CODE: SELECT ALL
smartctl -a smartctl -a /dev/disk/internal/0:5*
I just tried the above and I kept getting an error. I'm pretty sure it was just a typo. Did you mean:smartctl -a /dev/disk/internal/0:5*
Anyway, it was STILL an awesome reply! Thank you again for stopping by to enlighten us wannabe hackers. . .- Yes it is a typo. Try that.
ATCIS wrote: Did you mean: smartctl -a /dev/disk/internal/0:5*
Yep, that's what I meant. Sorry, copy/paste error on my part. BTW, that command will check SMART data on disk 6. If you want to check disk 1, it would be 0:0:* (the channel numbers are 0-based).- Dear Skywalker,
Allow me to thank you one more time for your guidance. . .
However. . . This command:Skywalker wrote: From SSH, run this command to reset the error history log:
rm -f /var/readynasd/smart.sq3
Is not working for me. I have literally deleted /var/readynasd/smart.sq3 four different times, four different ways, and my ATA Error history still prevails. These are the four ways I've done it:
1.) Simply the way you stated above. . .
2.) Ditto + a reboot
3.) With a SSH-FTP Client
4.) Same as number 1 above, then shutdown, then shuffle all the drives around, and power back up. What I have found is that the ATA Error count follows the physical hard drive not the Bay number. . .
I have confirmed that the file does actually delete. I really think you were on to something, so any other recommendations would also be appreciated.
Perhaps the smart.sq3 does not actually contain the ATA Error history? Just asking. . . :?
Best wishes, - Is there anything in /var/readynasd/db.sq3 (don't delete this database. If there are offending lines they would need to be edited or removed - whichever is appropriate - manually).
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
