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
mdgm wrote: 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).
I don't know what the best application would be to do that.
Thank you,- # sqlite3 /var/readynas/db.sq3
# .dump mdgm wrote: # sqlite3 /var/readynas/db.sq3
# .dump
Thank you.
Results:SQLite version 3.7.13 2012-06-11 02:05:22
Enter ".help" for instructions
Enter SQL statements terminated with a ";"
sqlite> .dump
Error: unable to open database "/var/readynas/db.sq3": unable to open database file- Oops. Typo.
The file is /var/readynasd/db.sq3 - The SMART / ATA error history database will get re-created automatically if it doesn't exist. But it will get rid of the previous history, so the disk health checks will operate from a clean slate from that point onward.
Skywalker wrote: The SMART / ATA error history database will get re-created automatically if it doesn't exist. But it will get rid of the previous history, so the disk health checks will operate from a clean slate from that point onward.
Dear Skywalker,
I totally understand your intent with this command:rm -f /var/readynasd/smart.sq3
. . .and I concur that if that's where the ATA Error Data resides, deleting that file should force the statistics into a "Clean Slate" sort of mode, but in my case it doesn't do squat.
In case you missed my earlier post, it's the one with the four item list. . .
Please do not misunderstand my tone as I am mearly a Padawan and mean no disrespect
Next, I will see if I can figure out what mdgm is asking me to try out. . .
Thanks as always,- Hmmm maybe after removing the smart.sq3 file you need to restart readynasd?
mdgm wrote:
The file is /var/readynasd/db.sq3
Dear mdgm,
Okay, I found the data in the .dump that you instructed me about. It reads:INSERT INTO "$log" VALUES(7,1374018379,'notice','disk','LOGMSG_SMART_ATA_ERR_30DAYS_WARN','<args Count="24638" Channel="6" Model="WDC WD2002FYPS-02W3B0" Serial="WD-WCAVY5956816" Events="3"/>');
So now that I've found it, how do I get rid of it in the db.sq3 file?
Thanks in advance,mdgm wrote: Hmmm maybe after removing the smart.sq3 file you need to restart readynasd?
Wouldn't restarting the entire NAS basically accomplish the same thing?
Just asking. . .- How are you concluding that it didn't clear the history? 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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
