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
- First of all: A BIG THANKS to the devs and contributors making it possible to run os6 on legacy hardware!
Big thanks.
But I do have some questions:
- is it and will it always be safe to use apt-get upgrade? I've red somewhere in the post it is safe.
just wanna be sure
- before upgrading, I would still do something like this:
rsync -ahHAXv /* /c/osbackup --delete --numeric-ids --exclude={/dev/*,/proc/*,/sys/*,/tmp/*,/run/*,/mnt/*,/media/*,/c/*,/lost+found}
so in case something breaks I can restore previous state
- proftp is not registered as service?
/etc/init.d/proftpd restart
Services proftpd restart
Do not work => any idea how to restart? Or should i just reboot the Nas? - While some packages may be pinned, an apt-get upgrade is risky. I would do an apt-get update and install just the packages you need and their dependencies. If unsure whether installing something will cause problems as well as maintaining a regular backup (which you should do anyway) I would recommend getting another unit for testing (could be e.g. a 312 or a Ultra 2 you found cheap and updated to OS6) or testing using the VM. If it causes problems in the VM it will probably also cause problems on physical hardware.
systemctl is used for stopping and starting services in OS6. - Great!
Thanks! - I hit a snag while upgrading disks on BTRFS that I dont think would happen on Ext4. Maybe someone can assist ?
More details in this thread: viewtopic.php?f=66&t=76459 - Hi!
Finaly I was able to install LogAnalyzer on a Pro6 running 6.1.8 via apt-get (no change to install it via frotview, btw.). Now I see some "WRONG FILE OWNER " messages in the logs for the following files:Messagetype Syslog
Syslogtag /usr/sbin/cron
ProcessID 1725
Message (root) WRONG FILE OWNER (crontabs/root)Messagetype Syslog
Syslogtag /usr/sbin/cron
ProcessID 1725
Message (*system*poweroff) WRONG FILE OWNER (/etc/cron.d/poweroff)Messagetype Syslog
Syslogtag /usr/sbin/cron
ProcessID 1725
Message (*system*php5) WRONG FILE OWNER (/etc/cron.d/php5)
At the moment these are the owners::/etc/cron.d# ls -l
total 4
-rw-r--r-- 1 guest guest 565 Mar 4 2013 php5
-rw-r--r-- 1 guest guest 0 Oct 28 2013 poweroff
I don't know which 'file' is(root) WRONG FILE OWNER (crontabs/root)
Who should be the owner of these files?
Best regards,
Martin - I just had now a very strange behavior of my legacy NAS under 6.1.8 :
I couldn't access it via web interface neither by SSH !! still... I can access the shared folders from my mac.
My router is set to give a specific IP for the MAC address of my Ultra2. No response to ping on this address neither on 9 adresses in lower and upper range.
So either the NAS changed his IP on its own despite the router's config either it's a very weird bug !!
I rebooted once the router and nothing changed.
Of course after a full reboot of both NAS and router it is now working again with the expected assigned IP. But that hickup was surprising ! (I didn't tried to use raidar on my pc). ATCIS wrote: Mine shuts down just fine also. . .
1.) Log in to GUI
2.) Click on "Shut Down"
3.) Within 30 to 45 seconds NAS is powered down
4.) Wait 3 to 5 minutes (never actually timed it)
5.) Pro 6 turns itself back on
The only way to prevent it from coming back on all by itself is to flip the physical power switch on the back of the NAS. . .
My Pro6 definitely does not do this. This is a typical sign of a failing power supply, so it likely has little to do with OS6, except perhaps that using it put more stress on the supply and accelerated its demise.Sandshark wrote:
My Pro6 definitely does not do this. This is a typical sign of a failing power supply, so it likely has little to do with OS6, except perhaps that using it put more stress on the supply and accelerated its demise.
Thanks for your opinion. . .- I have an ultra 4 which I am using to backup my main pro 6 before upgrading it as well. I had a lock up overnight while copying the data, the machine appeared to lock hard not responding to ping request or button pushes (outside of a hard reset). I down loaded the logs, but don't see any obvious errors, is there one log I should look at which may provide some insight?
I like OS6 a lot, but 4.2.x has been a proven performer over the years. - Hello all,
what system would you guys recommend setting up for max reliability and good speed:
It is a ReadyNas ProPioneer x86 system with 6 3TB drives
1) OS6 with btrfs-raid5
2) NAS4free with ZFS
Already read this thread and this one about ZFS and FreeNAS: http://www.readynas.com/forum/viewtopic.php?f=51&t=74678
Is btrfs in OS6 stable enough now for daily use?
Does the automatic file repair described in the arstechnica article here http://arstechnica.com/information-technology/2014/01/bitrot-and-atomic-cows-inside-next-gen-filesystems/2/ work on the Netgear?
Switching to btrfs would lead to a data reset of an existing XRAID2 setup?
Do Add ons like plex media server work on the x86 legacy devices?
Thanks in advance and sorry for the newbie questions.
PAS
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
