NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
AMRivlin
Mar 20, 2013Apprentice
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
- MueRAspirantBTRFS did receive some major performance improvements in the Linux 3.12 kernel. Perhaps Netgear can investigate if adding the new kernel will improve things?
- mdgm-ntgrNETGEAR Employee RetiredThat python release is from last year, as is the version of unrar you have installed. Not sure about par2 bit I think that's old as well. You may well find compiling the latest version from source gives you better results (might need some backporting to get things working properly). Whilst WhoCares? does charge for his add-ons he works hard to make his add-ons work well, often using newer versions of packages that are newer than what can be found in the apt-get repository for the Debian distro running on the NAS. In fact for legacy OSes he has to run newer packages than what are in the distro or do some backporting or more likely a bit of both. All this work takes time.
- MueRAspirant
mdgm wrote: That python release is from last year, as is the version of unrar you have installed. Not sure about par2 bit I think that's old as well.
Par2 simply hasn't been updated since 0.4. For unrar, I pulled the latest from testing, it's now on 1:5.0.10-1. Python 2 hasn't been updated past 2.7.3-4 and quite frankly I'm not familiar enough with python to fix issues in the software I want to run if I upgrade to v3. Also, while older versions of packages may contribute a small amount to the problem, they cannot be the sole cause, since a simple FTP or SMB copy to the device results in the same performance issues whenever the btrfs processes wake up. Setting noatime on the volume helped reduce load and iowait by a large amount, but still it shows up (and already caused two complete lockups within two hours).
To further add proof that it's btrfs causing issues: the following commands on shell took 15 seconds each (btrfs-transact was active both times)mkdir /data/addons/config/sabnzbd/postproc
chown bas:admins /data/addons/config/sabnzbd/postproc/
Now, you can't in all seriousness tell me that a mkdir on shell taking that long could be caused by a potentially outdated unrar/par2/python package. It simply does not happen. It's the btrfs processes. At the same time as this is taking place, I see SQL errors on sabnzbd with the message that the database is locked. File system access is completely locked by btrfs wanting to be clever and snapshot stuff. I did disable snapshots on all shares (and antivirus too), but I doubt that disables the feature in btrfs.
Tomorrow I should receive a new 4GB ram unit for the box, maybe some more memory will improve things. It's worth a shot anyway. The only other reason besides memory and FS I can think of is failing hardware. Without a comparative test by someone else with a similar device, it's hard to say either way. - ATCISTutor
MueR wrote:
Tomorrow I should receive a new 4GB ram unit for the box, maybe some more memory will improve things. It's worth a shot anyway. The only other reason besides memory and FS I can think of is failing hardware. Without a comparative test by someone else with a similar device, it's hard to say either way.
Dear MueR,
In the interest of helping you and possibly the legacy ReadyNAS community at large, I would be willing to provide you with remote SSH access (and HTTPS GUI if needed) to a Pro 6 for testing purposes if you would be so inclined. If that would be of any interest to you, please PM me with any particulars with regard to Hard Drive configuration etc. to make your testing most fruitful.
Regards, - mangroveApprentice
mangrove wrote: How do you solve the performance problem with your own encryption? Larger blocksize?
Well, I guess... they did in some way. Compressed performance is ten times better than TrueCrypt, still measly but 25MB/s (write) on an iSCSI container on an encrypted volume (sequential writes). On an unencrypted volume, it is closer to 70MB/s. This looks normal in comparison to competing devices for an Atom platform. - MueRAspirant
ATCIS wrote: Dear MueR,
In the interest of helping you and possibly the legacy ReadyNAS community at large, I would be willing to provide you with remote SSH access (and HTTPS GUI if needed) to a Pro 6 for testing purposes if you would be so inclined. If that would be of any interest to you, please PM me with any particulars with regard to Hard Drive configuration etc. to make your testing most fruitful.
Regards,
Hey,
Thanks for the offer, that's great :) I'm still working on several potential fixes myself, once I have the results of those I'll contact you to see if the problem can be replicated :) - F_L_TutorAbout to take the step over to OS6 (doing backup right now)
Just to be sure
If using the prep-file:
R4toR6_Prep_Addon.bin
There is no need for factory default in step 3?OS6 in 3 Steps:
1. Download pre modified IMG, (see link above to see what has been modified)
2. Upgrade firmware in Frontview 4.2 (with above file)
3. Reboot & factory default - mdgm-ntgrNETGEAR Employee RetiredThe prep add-on will automatically trigger a factory default at the end of the update process so you don't need to trigger it manually. After installing the add-on, upload the firmware and reboot.
- ATCISTutor
MueR wrote:
Hey,
Thanks for the offer, that's great :) I'm still working on several potential fixes myself, once I have the results of those I'll contact you to see if the problem can be replicated :)
Hey MueR,
I just wanted to let you know that the Pro 6 is ready for you! Please check your PM's for details. . .
Happy Friday! - IcyKTutorDoes anyone know how to delete the snapshots by hand?
My complete drive is filled with snapshot it seems, but they cant's be deleted because it's a read only file system (????)
root testix /data/Pictures # du -h --max-depth=1
3.4G ./tomtom
1.1G ./phonecard
445G ./snapshot
450G .
root testix /data/Pictures # rm -rf snapshot
rm: cannot remove `c_2013_10_25__00_01_28/phonecard/20130901_121037.jpg': Read-only file system
I already disabled the snapshots in the GUI but that doesn't seem to help (no new snapshots are being made, but the old ones aren't deleted).
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!