New Idea

(Can't search existing ideas, so... hoping this wasn't posted before)

It is rare that this error is displayed in an expected situation, inserting a dirty disk (a disk already containing partitions) and wanting to wipe it to use it in the NAS. 

In all other situations, this error message is inaccurate, confusing and dangerous.

If the RAID array failed to start, if the volume failed to mount, the user really should NOT be prompted to remove the inactive volumes! It's actually the only thing NOT to do.

Instead, the message should clearly explain what's happening. It wouldn't be difficult to improve this. It wouldn't even have any impact on performance of anything like that, as it would be done only in one of these situations.

If the partitions are not recognized, the NAS should say it: "Disks contain unrecognized partitions".

If the partitions are recognized but the RAID array(s) can't be assembled: "Disks contain RAID array(s) that couldn't be assembled".

If the RAID array(s) can't be mounted, eg. BTRFS corruption: "Disks contain a damaged data volume". 

If the user actually wants to wipe the disks, he's still able to use the format feature if necessary, that doesn't change.

Currently HTTP cannot be turned off. I want to force all my traffic over HTTPS.


Currently this isn't allowed for unknown, possibly legacy reasons that no longer make sense.

Yes, there will be overhead, but internal and external transfers won't be visible to the the local LAN, etc.


The capability to force PFS / HSTS on for HTTPS would be nice as well.

Show last SMART stats for spun down disks.

Status: New Idea
by Guru StephenB Guru on ‎2017-04-20 04:42 AM

If a disk is spun down, it generally does not respond to SMART queries.  Therefore Netgear doesn't query them when it is spun down.


Currently, during spin down the temperature field next to the disk (on the performance tab) is blanked.  If you click on the disk icon, you see -1s in all the SMART stats.  When the disk is spun up, after a short lag (up to 3 minutes) the temperature and stats are shown.


I want to always be able to see the disk health, even if it is spun down at the moment.


I suggest

  • adding the spin up/down status to the SMART stats - with the time that the disk entered that state.
  • adding the time when the SMART stats were last queried.
  • showing the last SMART status available when the disk is spun down.
  • Perhaps showing "spun down" in the temperature field instead of blanking it.

I recently went through all the Ideas in this exchange. What a nightmare! Not the ideas, navigation through all the pages.


Currently, when clicking "Return to the Idea Exchange", it takes you back to page 1!  So if you were on page 5, 8, 10... Ackkk.


There are currently 14 pages on this exchange. Eventually there will be 40-50 (or more). There needs to be a index, or Go Back needs to take you back to the previous section, both would be preferable.


Otherwise, ideas posted a month or more ago, will no longer be seen or receive upvotes, not a good thing.


Obviously this should apply to all the exchange sections.

Shutdown on failed disk

Status: New Idea
by vandermerwe Master on ‎2017-04-19 12:19 PM

This feature is great when the NAS is unattended, however in the event that a removed or failed disk is replaced with a new disk, the shutdown should be cancelled. Currently the NAS will shutdown even when a new disk is inserted immediately (the case with a disk replacement)
Perhaps the GUI could allow a user to cancel the scheduled shotdown if a new disk is inserted within the 30 minute window.

Under Shares -> Browse, right clicking in an empty space in the file view area should give the option to create folders, view properties etc.

The ReadyNAS OS is soooo underdelevoped compared to QNAP.

So there are some great KB articles out there, like:


  • How to create a backup job using Rsync, whereas the actual documentation is out of date or incorrect.
  • How to manually access a Time Machine share (unknown to even some of the L2 folks. Not in the documentation.
  • How the front panel buttons work. Not in the docs.
  • How to create an XRAID RAID6 volume, ditto...




I would love a way to disable the popup (everytime i log into the GUI) that asks if I want to upgrade to the next firmware version.  It would be nice if it asked once then not again for this release, or just kept a banner up or something. EVERYTIME is annoying.


I do not want to accidentally upgrade to 6.6.1 for example--ever.  I have a solid box and want to keep it that way.

Apparently factory default to RAID5 is still standard on 6-bay units, even with ReadyOS 6.6+.

I realize most customers might not want/need this, but the work of allowing the factory install complete, destroying the volume, creating a Flex-RAID RAID6 volume, then converting it:

  • Takes a substantial amount of time, both for the hardware and customer
  • Likely results in sub-optimal volume layout


Can't the OS just provide a selectable option on Factory Default?



It would be extremely nice to have an automated redirect to HTTPS when admin page is launched.

There have been several cases where inadvertent deletion of a ReadyCloud user account has result in massive data loss because the user's home folder is deleted.


The system shouldn't delete these folders so easily.  I suggest that there should be a system setting which preserves user folders when the user account is deleted (for any user account, not just readycloud), and that it should be turned on by default.  The administrator could then manually delete a folder via the web ui.

This month’s PC Magazine has a great overview/tutorial regarding the Internet of Things – cameras, Alexa, thermostats, refrigerators, washers, etc.  It is fairly short and after reading it there should be a general sense of alarm.  Once a device (camera, refrigerator, etc.)  is within your network it can start to launch attacks.  Within the privacy of your LAN network protections are lax.  Network probes coupled with known sniffing solutions can readily determine the type of device, its address and possible strategic value.  Attacks can come in the millions since LAN communication is essentially instantaneous. 


The Netgear NAS devices have one password that needs to be ‘guessed’ prior to access. 


What is needed is a method to set a logon attempt threshold coupled with a timeout value prior to another round of password logon attempts.  This has been the standard in server systems and most workstations for over a decade – it needs to be implemented in this critical device. 


For example…

Retry count = 5, Timeout = 15 minutes. 

Both of these values should be a configuration parameter.  After 5 failed attempts there would be a mandatory 15 minute quiet time prior to acknowledging another logon attempt.  Logon failures should throw an effort message and if desired an email message as well.


The amount of effort required should be low but the improvement in security would be immense.


Eventually the ReadyNAS will be targeted in a 'proff of concept' exploit.  Hopefully this change will be accepted and implemented prior to that event. 



It should be possible to define what's the behaviour of the Antivirus. In former installations there was an Addon to define additional Settings for Antivirus.

It should come back again. Because I'd like to know whats going on with right detected files, and with wrong positive detected files (I've to many false positives in my IT career).

And also I know, I've got many files on my NAS which normally will be known "somehow as bad" (e.g. many nirsoft tools). There has to be a exclude option (exactly many exlude options).

It'd be great if there was a way to get email notifications when ReadyCloud/Remote services are disrupted and when they are restored.  An opt-in for these notifications could be done on the ReadyCloud and Remote portals.

Backup job progress indicator

Status: New Idea
by leo037 Star on ‎2017-02-22 08:03 PM

It would be great if the backup jobs had a progress indicator


x of 100% based on file count or data set size, etc



I'm currently waiting for a job to complete that's multi-terebyte and I look at either the backup job "in progress" or at my Meraki dashboard and see the traffic still flowing. 




BTRFS Plus app

Status: New Idea
by jak0lantash Prodigy on ‎2017-03-09 12:13 PM

Reposting deleted idea:



It would be interesting and very useful to have more information about the status of the BTRFS volume(s), and more control on them, from the GUI. Like seeing the data allocation, metadata allocation, the list of snapshots, the ability to run specific balance, pause/cancel balance etc.

Including this (or some of it) in main GUI might create confusion to most of the users. Instead, it could be available in a "Plus" app, like SMB Plus and Anti-Virus Plus.



# btrfs filesystem usage /data
    Device size:                 461.13GiB
    Device allocated:             15.03GiB
    Device unallocated:          446.11GiB
    Device missing:                  0.00B
    Used:                         12.26GiB
    Free (estimated):            446.88GiB      (min: 223.83GiB)
    Data ratio:                       1.00
    Metadata ratio:                   1.99
    Global reserve:               32.00MiB      (used: 0.00B)

Data,single: Size:13.00GiB, Used:12.23GiB
   /dev/md127     13.00GiB

Metadata,single: Size:8.00MiB, Used:0.00B
   /dev/md127      8.00MiB

Metadata,DUP: Size:1.00GiB, Used:17.94MiB
   /dev/md127      2.00GiB

System,single: Size:4.00MiB, Used:0.00B
   /dev/md127      4.00MiB

System,DUP: Size:8.00MiB, Used:32.00KiB
   /dev/md127     16.00MiB

   /dev/md127    446.11GiB
# btrfs balance start --help
usage: btrfs balance start [options] <path>

    Balance chunks across the devices

    Balance and/or convert (change allocation profile of) chunks that
    passed all filters in a comma-separated list of filters for a
    particular chunk type.  If filter list is not given balance all
    chunks of that type.  In case none of the -d, -m or -s options is
    given balance all chunks in a filesystem.

    -d[filters]    act on data chunks
    -m[filters]    act on metadata chunks
    -s[filters]    act on system chunks (only under -f)
    -v             be verbose
    -f             force reducing of metadata integrity
# btrfs balance --help
usage: btrfs balance <command> [options] <path>
   or: btrfs balance <path>

    btrfs balance start [options] <path>
        Balance chunks across the devices
    btrfs balance pause <path>
        Pause running balance
    btrfs balance cancel <path>
        Cancel running or paused balance
    btrfs balance resume <path>
        Resume interrupted balance
    btrfs balance status [-v] <path>
        Show status of running or paused balance
# btrfs subvolume list -s /data
ID 292 gen 180 cgen 180 top level 278 otime 2016-03-16 16:15:27 path test1/.snapshots/7/snapshot
ID 350 gen 328 cgen 328 top level 278 otime 2016-03-19 00:00:14 path test2/.snapshots/63/snapshot
ID 680 gen 1361 cgen 1361 top level 643 otime 2016-03-31 00:00:23 path clone_test1/.snapshots/13/snapshot

List is not complete, of course - Please comment 


(201) do not disable HTTP or HTTPS under any circumstances
(202) do not encrypt a volume
(203) do not have antivirus service enabled
(204) do not have ftp service enabled, if not urgently needed
(205) do not have afp service enabled in case your macs only need to access a windows share
(206) do not have nfs service enabled in case your linux machines (includes android) only need to access a windows share
(207) do not have bitrot protection enabled; if you must, do not enable compression, though
(208) do not have quota for volumes enabled
(209) do not use larger disks beyond 2TB (with increasing diskspace all related activities get painfully slow; resynch, scrub, defrag, balance)
(210) do not install any app before thoroughly researching its reliability and potential pitfalls
(211) do not copy a bunch of (very) small files; throughput will get painfully slow
(212) do not install beta firmware in case your nas is critical to any of the processes you let it support
(213) do not enable disk spin-down
(214) do not enable snapshots for your volumes; have regular backups instead
(215) do not fix it, if it is not broken (eg no fw upgrade in case your current release is running fine or the new release fixes security issues)

Hi All,


it will be nice if after a disk test in the mail there is also disk/smart info.



Amazon Cloud Drive

Status: New Idea
by Zonker Apprentice on ‎2016-06-15 06:13 AM

The default action with the Amazon Cloud Drive is to Sync.  I would like to see an option added to just backup the ReadyNAS shares to Amazon Cloud Drive and not Sync.



Amazon S3 Backup features

Status: New Idea
by ryanrk Tutor on ‎2017-04-05 09:26 AM

I know with 6.7.0 we have Amazon S3 sync.   Here's a couple improvements I would like to see.


1) Filter file and filetypes.   I hate seeing .AppleDouble, .DS_Store being sync across can we filter extensions?

2) Encryption (I know AWS has it's own encryption but I would like to see a TNO (Trust No One) type encryption.  This could just be a TAR blob that is encrypted on the way over.  Maybe doing full encryption with diff's with rotation.      I could see this with the other online services also (Google Drive, Amazon Drive, etc)

Top Contributors