NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Ready Nas 314 Firm 6.10.10 Raid Inactive
Status on Radar shows raid level 5 inactive. I cannot log in thru Raidar to see errors or anything else. The drives icons show green check boxes and the lights on the unit are all green. I have power cycled the unit, Did not help. I reset the drives Did not help. Boots fine and sets network without a problem What can I do? Willing to pay for support to get these drives back Thanks for any help Dave 201-647-6887 kuttler@yahoo.comReplacement fan ReadyNAS nv+ v2
I recently setup my ReadyNAS NV+ v2 from scratch with four 3 TB Hitachi DK7SAD300 drives, replacing the two 3 TB Western Digital WD30EFRX drives. This is now all working well, however recently the fan has been making a lot more noise than previously. The larger number of drives installed (four vs two) plus the fact that the Hitachi ones spin at 7200 rpm (vs 5400 rpm) will no doubt drive a higher power consumption (and lead to higher temperatures). Temperatures remain moderate in my view (40-45 degrees for the enclosure and individual drives), but I found that the fan varies between ~1350 en 3000+ rpm. The latter makes it very noisy, so for now I have relocated from the lounge to the electric cupboard in the hallway. This is a dry and clean space, however it's a little warmer than in the lounge (20-21 degrees). I just wrote a small shell script to monitor some metrics from /var/log/frontview/enclosure.log; here's what I see when it's making a lot of noise: root@vanrun:/tmp# tail -f /tmp/log-rpm-fan.log Sun May 17 09:55:52 CEST 2026 42.8 2792 Sun May 17 09:56:52 CEST 2026 42.8 3233 Sun May 17 09:57:52 CEST 2026 42.8 3150 Sun May 17 09:58:52 CEST 2026 41.8 3233 For a more permanent solution, I am considering replacing the stock fan Protechnic MGT9212YB-O25 (39.6 dBA - 61.62 CFM - 0.41A - 4.92 W) with one of the following: Noctua NF-A9 PWM - 22.8 dB - 46.44 CFM - 0.1 A - 1.2 W Noctua NF-A9 FLX - 17.1 dB - 38.02 CFM - 0.07 A - 0.84 W Noctua NF-B9 redux-1600 PWM - 17.6 dB - 37.85 CFM - 0.08 A - 0.96 W Noctua NF-B9 redux-1600 - 17.6 dB(A) - 37.85 CFM - 0.11 A - 1.32 W ARCTIC P9 PWM ARCTIC P9 Silent I noticed inA really silent fan! | NETGEAR Communities that there's been others opting for the Noctua NF-B9 in the ReadyNAS nv+. I could not find specs for the ARCTIC P9 though. Any recommendations? The PWM models come with a 4 pin connector, but can achieve slightly higher CFM. Looks like the 4 pin connector could be connected to the 3 pin connector in my ReadyNAS nv+ v2?Impossible de se connecter RNDU2000
Bonjour à tous, Depuis quelques jours je n'arrive plus à me connecter à mon ReadyNAS Ultra 2 (RNDU2000). Je n'ai pourtant pas fait de modif du mot de passe. J'y accédais via l'explorateur de fichiers windows (win 11) sans problème. J'ai essayé la procédure OS reinstall page 15 https://www.downloads.netgear.com/files/GDC/RNDU2000/ReadyNAS_Ultra_UltraPlus_NVX_Pro_HW_FR_02Aug11.pdf , il a réinitialisé l'adresse ip en 192.168.168.168/admin . Hier, j'avais la fenêtre qui me demande le mot de passe et aujourd'hui plus de fenêtre. J'ai juste changé de carte réseau du NAS. J'ai sauvegardé les données sur un autre support au cas où. Si certains d'entre vous ont une solution je suis preneur. Merci par avance pour votre aide. ps: Windows 11 Firefox TLS1.0Recovery of files
Hello all, I have an older RNDU2200. It seemed to be operating correctly until about 3 years ago. At that time, access to the drive became intermittent, but I always managed to find a way to connect. I didn't access the drive for 2 years, and when I tried recently, I found that I could not connect at all. I've tried with an older Windows 10 and newer Windows 11 OS laptop, and I've tried all the tricks/recommendations I've read here on the community site, including adjusting the SMB settings and addressing directly via \\NAS-xx-xx-xx. I've lost prior versions of the RAIDar app, which was the only way it worked in the past. The latest version can't see the drive when connected as a network resource and I even tried to connect directly from the PC to the drive via USB, detached from the network. No joy. Is there a way to get older versions of the RAIDar app ? Otherwise, I've reached my troubleshooting limits. I don't want to continue to use this unit, but I would like find a way to access the drive just long enough to get the files off. What recommendations do you have ? Any advice/guidance would be greatly appreciated. Many thanks, ErickWriting to the LCD (RN516)
Does anyone have any notes on how to enable hardware support or load kernel modules etc, in order to obtain a workable method to access the displays on ReadyNAS devices from within alternative linux OSs? Specifically I'm interested in RN516 and Pro6, but it would be great if we could start to share knowledge to help everyone with this particular issue. I've been running various different OSs on an RN516, and have stuff like fan control sorted. I've also sorted out a nasty ACPI issue which hogs a large chunk of CPU power due to interrupts from IRQ9. But, I've run out of talent so far on anything that lets me access the LCD hardware. Any pointers? And no, there's nothing in /dev like /dev/lcd or /dev/ttyS1 or similar that will do that job. Stuff that works inside ReadyNAS OS6 doesn't work in other linux OSs, presumably due to a lack of hardware support in the kernel, or the correct module. So far I've completely failed to work out how to resolve this. I managed for the fan/temperature/PWM hardware, but the LCD is kicking my butt.Using ReadyNAS as backend for lightweight web tools — is it reliable?
Hi everyone, I currently maintain a small web tool (for example a gratuity / end-of-service benefit calculator for users in the UAE), and I’m evaluating options to host user data, logs, JSON storage files, and backups. My ideal setup is a lightweight, always-on system without needing a full server. That’s where ReadyNAS caught my interest. Some of the things I’m considering: Using ReadyNAS to host REST APIs, static JSON or YAML config files, and backing up user session data. Ensuring data integrity and performance — especially under concurrent access. Handling firmware updates without breaking API endpoints. Syncing backups to cloud or another NAS for redundancy. A few questions for those experienced with ReadyNAS: 1. Has anyone used ReadyNAS to back a small web service or tool (not just file server)? 2. What is the maximum recommended concurrent requests for lightweight API files (JSON) on ReadyNAS? 3. Which methods have you used for version-safe firmware updates so that custom services are not lost? 4. How do you handle secure access (SSL, tokens) when serving APIs from a NAS that’s also storing private user data? If anyone’s already built similar backend or microservice setups using ReadyNAS, I’d love pointers or pitfalls to avoid. Thank you!Drive four premature failure in two Ready NAS devices - Coincidence?
Hi, I've got a ReadyNAS 426 and ReadyNas 516. All six drives in each device the same size/model, however, one contained 6 x 10TB and the other 6 x 18TB. Both had a failure on drive four after 36,000 and 49,000 hours. All other drives have no issues and are from similar batches. Is this just a massive coincidence, or has anyone else experienced the same? Thanks, Carl.RN104: ghost “NG-8TB-Seagate” volume (RAID unknown) flapping Inactive/Unprotected
Hi all, I have a ReadyNAS RN104 that’s working fine from the data point of view, but the volume configuration seems corrupted and is generating constant volume health alerts that I cannot clear. I’m hoping someone familiar with the ReadyNAS OS 6 config DB can advise on a safe way to remove the ghost volume entries without wiping any data. Hardware / firmware: - Model: RN104 - OS version: 6.10.10 - Disks: - sda: 2 TB (NG-WDRED-2TB-1) - sdb: 6 TB (NG-WDRP-6TB-1) - sdc: 3 TB (NG-WDRED-3TB-2) - sdd: 8 TB (NG-8TB-Seagate) – recently replaced a failed 3 TB Symptom: In the web UI → System → Volumes I see 6 volumes even though I only have 4 disks. The top four are green JBOD volumes with data and look healthy: - NG-8TB-Seagate (JBOD, ~7.27 TB, ~2.64 TB used) - NG-WDRED-3TB-2 (JBOD, ~2.72 TB, ~1.17 TB used) - NG-WDRP-6TB-1 (JBOD, ~5.45 TB, ~4.28 TB used) - NG-WDRED-2TB-1 (JBOD, ~1.81 TB, ~0.2 TB used) Below those, there are two blue entries with 0 data and “RAID unknown”: - NG-WDRED-3TB-1 (0 data, 0 free, RAID unknown) - NG-8TB-Seagate (0 data, 0 free, RAID unknown) I believe these are stale/ghost volumes from the old failed 3 TB drive and some mis-step when I first added the 8 TB. They show only “Disk test” and “Destroy” as options. When I try “Destroy” on the old 3 TB entry, it appears to succeed but the entry comes straight back. In the logs I constantly get messages like: - “Volume: Volume NG-8TB-Seagate health changed from Inactive to Unprotected.” - “Volume: Volume NG-8TB-Seagate health changed from Unprotected to Inactive.” These repeat every few seconds/minutes and are clearly coming from the ghost NG-8TB-Seagate entry (the 0-data, RAID-unknown one), not the real 8 TB JBOD volume which is mounted and in use. SSH diagnostics (all arrays look clean): lsblk sda 1.8T ├─sda1 -> md0 (/) ├─sda2 -> md1 (swap) └─sda3 -> md126 /NG-WDRED-2TB-1 sdb 5.5T ├─sdb1 -> md0 (/) ├─sdb2 -> md1 (swap) └─sdb3 -> md127 /NG-WDRP-6TB-1 sdc 2.7T ├─sdc1 -> md0 ├─sdc2 -> md1 └─sdc3 -> md125 /NG-WDRED-3TB-2 sdd 7.3T ├─sdd1 -> md0 ├─sdd2 -> md1 └─sdd3 -> md124 /NG-8TB-Seagate /proc/mdstat md124 : active raid1 sdd3 7809175808 blocks super 1.2 [1/1] [U] md125 : active raid1 sdc3 2925415808 blocks super 1.2 [1/1] [U] md126 : active raid1 sda3 1948663808 blocks super 1.2 [1/1] [U] md127 : active raid1 sdb3 5855671808 blocks super 1.2 [1/1] [U] md1 : active raid10 sda2 sdd2 sdc2 sdb2[1][2][3] 1044480 blocks super 1.2 512K chunks 2 near-copies [4/4] [UUUU] md0 : active raid1 sda1 sdb1 sdd1 sdc1[3][4][1] 4190208 blocks super 1.2 [4/4] [UUUU] /root/mdadm-detail-scan.txt ARRAY /dev/md/0 metadata=1.2 name=0e34093c:0 UUID=b1079eff:ca275c6a:4df7d648:6f176c9c ARRAY /dev/md/1 metadata=1.2 name=0e34093c:1 UUID=9ecdbab8:7ecf3da9:299f9966:0fa46d04 ARRAY /dev/md/NG-WDRP-6TB-1-0 metadata=1.2 name=0e34093c:NG-WDRP-6TB-1-0 UUID=1d40ffff:601db1f8:20e41e54:f5650fa6 ARRAY /dev/md/NG-WDRED-2TB-1-0 metadata=1.2 name=0e34093c:NG-WDRED-2TB-1-0 UUID=d69ab251:67e359ac:16c640ee:2a0409c0 ARRAY /dev/md/NG-WDRED-3TB-2-0 metadata=1.2 name=0e34093c:NG-WDRED-3TB-2-0 UUID=1c072ab5:ea01a5d6:646d6d07:76776925 ARRAY /dev/md/NG-8TB-Seagate-0 metadata=1.2 name=0e34093c:NG-8TB-Seagate-0 UUID=4a957007:c3c04e0b:0aacb1df:3a59d9e8 /root/btrfs-filesystems.txt Label: '0e34093c:NG-WDRP-6TB-1' uuid: 28fcc8ab-9e63-4529-83f4-1e9d4708bd1b Total devices 1 FS bytes used 4.27TiB devid 1 size 5.45TiB used 4.28TiB path /dev/md127 Label: '0e34093c:NG-8TB-Seagate' uuid: 2a912336-755a-48e6-bcee-fd373ae8e6df Total devices 1 FS bytes used 2.63TiB devid 1 size 7.27TiB used 2.64TiB path /dev/md124 Label: '0e34093c:NG-WDRED-3TB-2' uuid: fbd95853-4f22-4041-8583-4e0853decf9b Total devices 1 FS bytes used 1.17TiB devid 1 size 2.72TiB used 1.17TiB path /dev/md125 Label: '0e34093c:NG-WDRED-2TB-1' uuid: 1b34cda6-1cc8-4360-9ca6-4c209100aa48 Total devices 1 FS bytes used 200.08GiB devid 1 size 1.81TiB used 220.02GiB path /dev/md126 So from the RAID/Btrfs point of view, everything looks consistent: four md data arrays, four Btrfs filesystems, all mounted and in use. There is no extra md device and no Btrfs filesystem corresponding to the blue “RAID unknown” ghost NG-8TB-Seagate volume. What I’ve tried: - Using the GUI “Destroy” on the blue NG-WDRED-3TB-1 volume: it disappears briefly but comes back. - Running btrfs scrub on the real NG-8TB-Seagate volume. - Restarting services and rebooting; the ghost entries and the Inactive/Unprotected log spam persist. What I’m asking for: I’d like guidance on how to safely clean up the configuration/database so that the ghost NG-8TB-Seagate and NG-WDRED-3TB-1 volumes are removed from the ReadyNAS UI and stop generating volume-health events, without destroying the real md124/md125/md126/md127 arrays or their Btrfs filesystems. I’m comfortable with SSH and sqlite3 if needed, but I don’t know the internal ReadyNAS schema, so I’d really appreciate precise instructions like: - which DB file to open; - which table(s)/row(s) represent these phantom volumes; - exactly what to delete/change; - and which services to restart afterwards. I do have backups of the most critical data, but I’d obviously prefer not to wipe and rebuild the entire box just to clear two stale volume objects. Thanks in advance for any pointers.