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
- mdgm-ntgrNETGEAR Employee RetiredYou should be able to delete the snapshots manually using the GUI
- IcyKTutorUnfortunately, that doesn't work. When I select 'delete', they won't get deleted. Only the ones from the last day of the month I can delete, the rest remains there (and eating up space...).
I now have snapshots from June 15 till August 15 (the day I disabled snapshotting) but I can't get rid of them...
It is quite annoying: there is about 975 GB of data on the drive but the whole 1.75 TB is reported full. - mdgm-ntgrNETGEAR Employee RetiredWhat version of ReadyNAS OS are you running?
- IcyKTutorI'm running 6.0.6 with a custom 'boot menu' and a custom kernel to use a DVB-C receiver (HDHomerun), that's why I'm a bit reluctant to update.
And I haven't seen a reference to snapshots in the release notes of the newer versions.
/edit: I'm running it on an Ultra 2 - mdgm-ntgrNETGEAR Employee RetiredStill there may be relevant changes. Not everything is documented in the Release Notes. Compare the GPL and you will see that relevant software has changed.
Can you compile a custom version of the kernel for 6.1.4? - IcyKTutorWell, I did it once so I should be able to do it again I guess ;)
The problem is however that I build it on the NAS itself. Which has no space left at the moment...
So when the snapshot problem I experience is not addressed by a newer release, I end up with a full drive, a kernel that doesn't support DVB and I can't go back to 6.0.6. Which means no tv streams on XBMC.
I'd prefer to fix it from the command line, if possible. But as I have seen no other postings with this problem, it might as wel be some specific problem that's not OS6 related.
(I will continue in the morning, it's 3 AM now here in The Netherlands) - mdgm-ntgrNETGEAR Employee RetiredYou could try compiling the kernel in the VM: http://www.readynas.com/forum/viewtopic.php?f=35&t=70699
- ATCISTutor
IcyK wrote: Unfortunately, that doesn't work. When I select 'delete', they won't get deleted. Only the ones from the last day of the month I can delete, the rest remains there (and eating up space...).
I now have snapshots from June 15 till August 15 (the day I disabled snapshotting) but I can't get rid of them...
It is quite annoying: there is about 975 GB of data on the drive but the whole 1.75 TB is reported full.
Yo IcyK,
I own an Ultra 4 that has a similar problem. It has 4 X 1TB drives in it and has been running OS6 since version 6.0.3 (if my memory serves) or so. Like you, I disabled snapshots before successfully deleting them all, and now it seems I'll be stuck with them forever (or until I decide to reformat the array and start from scratch). I have tried everything I can think of to get rid of those fu**ers, to no avail. The weird thing about my particular scenario is I can move the snapshots, rename them, change permissions and manipulate them in just about every possible way I can think of, except DELETE THEM! It makes absolutely no sense to me. Personally I have chalked it up to one of the many bugs that still need to be ironed out in the BTRFS file system. I'm really astounded that you and I are the only ones out there that have come across this?!?!?
I currently have somewhere in the neighborhood of 700GB's of wasted space on my ReadyNAS, but like you I have a considerable amount of tweaking time invested in the unit and don't really feel like going through that effort all over again :( - mdgm-ntgrNETGEAR Employee RetiredO.K. Just had a look into this.
Snapshots can't be deleted like ordinary directories/files. You need to use the btrfs command.
Here is an example:
# btrfs subvolume list -s /data
ID 263 gen 93 cgen 93 top level 5 otime 2013-10-08 00:00:57 path ._share/stuff/.snapshot/c_1381215657
ID 264 gen 96 cgen 96 top level 5 otime 2013-10-09 00:00:00 path ._share/stuff/.snapshot/c_1381302000
ID 265 gen 99 cgen 99 top level 5 otime 2013-10-10 00:00:03 path ._share/stuff/.snapshot/c_1381388403
ID 266 gen 102 cgen 102 top level 5 otime 2013-10-11 00:00:08 path ._share/stuff/.snapshot/c_1381474808
ID 267 gen 116 cgen 116 top level 5 otime 2013-10-12 00:00:44 path ._share/stuff/.snapshot/c_1381561244
ID 268 gen 118 cgen 118 top level 5 otime 2013-10-13 00:00:47 path ._share/stuff/.snapshot/c_1381647647
ID 269 gen 121 cgen 121 top level 5 otime 2013-10-14 00:00:49 path ._share/stuff/.snapshot/c_1381734049
ID 270 gen 123 cgen 123 top level 5 otime 2013-10-15 00:00:52 path ._share/stuff/.snapshot/c_1381820452
ID 271 gen 125 cgen 125 top level 5 otime 2013-10-16 00:00:54 path ._share/stuff/.snapshot/c_1381906854
ID 272 gen 127 cgen 127 top level 5 otime 2013-10-17 00:00:57 path ._share/stuff/.snapshot/c_1381993257
ID 286 gen 200 cgen 200 top level 5 otime 2013-10-18 00:00:00 path ._share/stuff/.snapshot/c_1382079600
ID 287 gen 296 cgen 296 top level 5 otime 2013-10-19 00:00:04 path ._share/stuff/.snapshot/c_1382166004
ID 288 gen 320 cgen 320 top level 5 otime 2013-10-20 00:00:06 path ._share/stuff/.snapshot/c_1382252406
ID 289 gen 322 cgen 322 top level 5 otime 2013-10-21 00:00:09 path ._share/stuff/.snapshot/c_1382338809
ID 290 gen 324 cgen 324 top level 5 otime 2013-10-22 00:00:12 path ._share/stuff/.snapshot/c_1382425212
ID 291 gen 326 cgen 326 top level 5 otime 2013-10-23 00:00:15 path ._share/stuff/.snapshot/c_1382511615
ID 292 gen 329 cgen 329 top level 5 otime 2013-10-24 00:00:18 path ._share/stuff/.snapshot/c_1382598018
ID 293 gen 331 cgen 331 top level 5 otime 2013-10-25 00:00:21 path ._share/stuff/.snapshot/c_1382684421
ID 294 gen 333 cgen 333 top level 5 otime 2013-10-26 00:00:24 path ._share/stuff/.snapshot/c_1382770824
ID 295 gen 335 cgen 335 top level 5 otime 2013-10-27 00:00:26 path ._share/stuff/.snapshot/c_1382857226
ID 296 gen 337 cgen 337 top level 5 otime 2013-10-28 00:00:29 path ._share/stuff/.snapshot/c_1382943629
ID 297 gen 339 cgen 339 top level 5 otime 2013-10-29 00:00:32 path ._share/stuff/.snapshot/c_1383030032
ID 298 gen 341 cgen 341 top level 5 otime 2013-10-30 00:00:35 path ._share/stuff/.snapshot/c_1383116435
ID 299 gen 343 cgen 343 top level 5 otime 2013-10-31 00:00:39 path ._share/stuff/.snapshot/c_1383202839
ID 300 gen 345 cgen 345 top level 5 otime 2013-11-01 00:00:43 path ._share/stuff/.snapshot/c_1383289243
ID 301 gen 347 cgen 347 top level 5 otime 2013-11-02 00:00:46 path ._share/stuff/.snapshot/c_1383375646
# btrfs subvolume delete /data/._share/stuff/.snapshot/c_1383375646 - ATCISTutor
mdgm wrote: O.K. Just had a look into this.
Snapshots can't be deleted like ordinary directories/files. You need to use the btrfs command.
Here is an example:
# btrfs subvolume list -s /data
ID 263 gen 93 cgen 93 top level 5 otime 2013-10-08 00:00:57 path ._share/stuff/.snapshot/c_1381215657
# btrfs subvolume delete /data/._share/stuff/.snapshot/c_1383375646
OH MY GOSH mdgm! You are a frigging GENIUS! The command above WORKS! My disk space utilization just went from 40% down to under 20%. I don't care what anybody says - YOU ARE THE MAN! :worship:
Thank you soooooooo much!
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!