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
- IridabikeAspirantNo its still syncing with another 70+ hours to go. The drives are WD 2TB reds. I went from raid 5 to 6. I have a 6700 processor with 4GB of ram - cant believe the sync can take so long.
My next step is to add another to expand my storage. Probably do this when I go away.... - ATCISTutorOkay folks here's a new one:
About and hour ago I rebooted a ReadyNAS Ultra 4 with four 1TB drives. I did this about 30 minutes after deleting a share from the GUI that had about 80% of the data volume's files in it. I rebooted because the pie charts and graphs in the GUI were not reflecting any change of available free space. After the reboot, the GUI did reflect quite a bit more free space in the data volume, but now every 10 minutes I'm getting sent an E-Mail that says:System volume 'root' usage is 91 %. This condition should not occur in normal conditions. Please contact technical support.
System volume 'root' usage is 100 %. This condition should not occur in normal conditions. Please contact technical support.
System volume 'root' usage is 99 %. This condition should not occur in normal conditions. Please contact technical support.
System volume 'root' usage is 99 %. This condition should not occur in normal conditions. Please contact technical support.
Etc., etc., etc. over and over.
From the command line I ran:df
which resulted inFilesystem 1K-blocks Used Available Use% Mounted on
rootfs 4192192 3505532 48140 99% /
tmpfs 10240 4 10236 1% /dev
/dev/md0 4192192 3505532 48140 99% /
tmpfs 2021468 0 2021468 0% /dev/shm
tmpfs 2021468 4544 2016924 1% /run
tmpfs 2021468 0 2021468 0% /sys/fs/cgroup
tmpfs 2021468 0 2021468 0% /media
/dev/md127 2915731968 866720844 1933903372 31% /data
/dev/md127 2915731968 866720844 1933903372 31% /home
/dev/md127 2915731968 866720844 1933903372 31% /apps
Help! I have no clue how to troubleshoot this one.
Thanks in advance! - mdgm-ntgrNETGEAR Employee RetiredYour 4GB OS partition is full.
You can use the du command to find out what's filling it up.
You could start by doing e.g.
# du -csh /var/log - ATCISTutor
mdgm wrote: du -csh /var/log
Results in:121M /var/log
121M total
Pardon my ignorance, but that means nothing to me. . . :oops: - mdgm-ntgrNETGEAR Employee RetiredThat means 121MB of the 4GB is in use in /var/log, so the problem is somewhere else. There's probably a folder somewhere with roughly 3GB in use that is on the OS partition (not on your data volume(s)).
- ATCISTutor
mdgm wrote: That means 121MB of the 4GB is in use in /var/log, so the problem is somewhere else. There's probably a folder somewhere with roughly 3GB in use that is on the OS partition (not on your data volume(s)).
Is there some sort of filter, option, or pipe that I can use in conjunction with "du" that would give me a summary list of the directory tree from largest to smallest (or vice versa) so I can figure out what directory to start looking in?
EDIT: Never mind. I think I figured that one out on my own. I used:du -h --max-depth=1 /
Which resulted in:7.1M /bin
0 /boot
4.0K /dev
6.4M /etc
72K /home
21M /lib
4.0K /lib64
0 /media
0 /mnt
5.0M /opt
0 /proc
24K /root
4.5M /run
8.2M /sbin
0 /selinux
0 /srv
0 /sys
52K /tmp
444M /usr
2.8G /var
18M /frontview
2.8T /data
928K /apps
2.8T /
It looks like there is something going on in /var. . . - super_poussinVirtuoso
find {/path/to/directory} -type f -size +{file-size-in-kb}k -exec ls -lh {} \; | awk '{ print $8 ": " $5 }' - super_poussinVirtuosoor
find . -type f -print0 | xargs -0 du -s | sort -n | tail -10 | cut -f2 | xargs -I{} du -sh {} - mdgm-ntgrNETGEAR Employee RetiredYes it is in /var, just not in /var/log
Let us know what filled it up. - ATCISTutor
mdgm wrote: Yes it is in /var, just not in /var/log
Let us know what filled it up.
So this particular ReadyNAS is running as a Network Video Recorder (Not NETGEAR's prohibitively expensive one). All the actual video gets deposited into /data/NVR/Video/*.* so not problem there. However, the NVR Database (MongoDB) resides in '/var/lib/nvr/db/' and '/var/lib/nvr/db/journal'.
So my dilemma now is what do I do? Can I somehow move the database somewhere else where there is more room? Can the rootfs be enlarged to say 8GB's from 4GB's. I mean this database is only going to get bigger over time, and now that I'm at 99%, there is no more room for it to grow.
Anyone got any ideas?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!