NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
tips from other users
896 TopicsOld ReadyNAS 212 won't boot up
So, many, MANY, years ago, my workplace merged with another company, and as part of that merger, I took over their IT system, which consisted of a few peer-to-peer PCs and a central storage system consisting of two ReadyNAS devices, one primary and one backup. Some time later, the backup NAS failed. Rather than fix or replace it, I opted to move to a cloud storage backup system instead, and the old unit was shelved. Fast forward to the modern day, amid a bunch of other IT problems cropping up (mainly, the current state of Microsoft OneDrive causing a cascade of problems with the cloud backup), the question of the the longevity of our current NAS device was raised. By my best estimation, that NAS has been going strong for upwards of 11 years now, and while it's performance has been incredible, it's at a point where it could fail at any moment. As part of the disaster recovery planning, the decision was made to try to refurbish the old backup NAS, just in case an immediate replacement is necessary before a full replacement can be purchased and implmented. That brings me to my current issue. The old NAS is able to power up, but then all the lights go out and it doesn't load anything. I have probed the Hard Drives on my PC, and while I haven't been able to access the files directly, the disks themselves seem to be fully functional. Most worryingly, attempting to access the Boot Menu with the reset button has failed entirely. Any advice of how I can get this old thing functional again? Preserving the data doesn't matter, they're just outdated backups, I just need to get the NAS Enclosure itself functional and active.Failing ReadyNAS Ultra 4 Plus
I noticed one morning my NAS had powered down and couldn't turn it back on. After turning the power off to it completely and waiting a couple of minutes, it turned back on. Strangely it then turns off by itself sometimes after a few minutes, sometimes after 15 minutes. I've taken the PSU out and tested the voltage outputs on the pins and it seems ok. I'm going to get a spare PSU and modify the pins to see if it works any better. In the meantime does anyone have suspicions as to what's failing on the NAS? When I look at the logs after each reboot (if I can get that far) there's nothing indicating the reason why it shutdown. Temps look fine also. Additionally, since I can't get a hold of a spare chassis (none on eBay), how do I get data off the disks? They're working fine. Do I need to connect all 4 drives into a PC and then get the data? I'd prefer to use Windows and hear ReclaiMe works?Just installed Ubuntu Server 24.04.4 on Ultra4, how to organize partitions?
Hi, I tinkered with trying to get SMB multipath working on OS6, but as Debian Jessie has not been supported for many years I decided to try to load modern Linux distro on my Ultra 4. After lot of tinkering, I got it working. I used ubuntu-24.04.4-live-server-amd64.iso (but assume other distros would work too). For those who want to know how to install, I can detail the process later on in the thread. (I am still testing and might re-install again). It involved booting off a USB stick containing Ubuntu distro while "listening" via USB-to-serial connection in PuTTY and couple of extra steps. What I wonder is: What is the optimal/fault tolerant way of configuring boot partitions? My Ultra 4 contains one 128MB "USB drive" (basically internal USB stick) and four SATA drives. 128MB is too little for a modern Linux distribution so currently, bootloader boots off 128MB drive, but then continues from 100GB partition I created on one of the four 2TB drives. Rest of space (4x1.8TB) can be partitioned and formatted as RAID5. While everything works, if sdd (where I put Linux distro on) dies the system will not boot. How did this work on original firmware? Did whole Jessie fit on 128MB? Can I create a RAID 1+0 partition on all four drives, and somehow let NAS boot of 128MB drive and continue on RAID1+0? Many thanks.SolvedAnyone got SMB multichannel working on OS6?
Hi, I have old Ultra 4 Plus with OS6 6.10.8 connected on both 1Gbit ports to 2.5Gbit network switch (no teaming or bond configuration , just two separate adapters with two IP). PC is using a single 2.5Gbit to same switch. Samba used is version 4.8.0, which should support SMB 3.11 and multi channel (albeit experimental) I added multi path configuration into smb.conf, configured PC adapter for RSS and verified that network is indeed capable of >1Gbit speed by running two iperf3 sessions on two different ports and IP’s towards NAS (and was able to get >1.7Gbit) Yet, my SMB file transfers are capped at 1Gbit. I verified PC SMB configuration in Powershell and it is indeed using two different IP/paths to NAS and using SMB 3.11. But something is throttling in NAS Samba. It is not drives nor CPU. Did anyone succeed getting more than 1Gbit on single file transfer session? If yes, can I get your secret sauce? Worst case, is it possible to install newer Samba (backported to Debian Jessie)? thanksSolvedRN104: ghost “NG-8TB-Seagate” volume (RAID unknown) Inactive/Unprotected
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)ReadyNAS 426 - Modules kernel réseau manquants après tentative de réparation
Bonjour, Je possède un ReadyNAS 426 (N° de série : 511174EX0007E) sous firmware ReadyNAS OS 6.10.10. Suite à des manipulations malheureuses conseillées par une IA, les modules kernel réseau situés dans le dossier /lib/modules/4.4.218.x86_64.1/kernel/net/ ont été corrompus puis supprimés accidentellement. J'ai tenté de les restaurer en réinstallant les firmwares 6.10.9 puis 6.10.10 via l'interface d'administration, mais ces réinstallations n'ont pas restauré le dossier /net/ manquant. Conséquence : Docker ne peut plus démarrer car les modules réseau kernel (nf_nat, bridge, br_netfilter, etc.) sont absents. Ma question : pourriez-vous me fournir les modules kernel originaux correspondant à la version 4.4.218.x86_64.1 du firmware 6.10.10, ou m'indiquer une procédure pour les restaurer ? Toutes mes données sont intactes et le NAS fonctionne normalement hormis Docker. Je vous remercie par avance pour votre aide. CordialementSolved187Views0likes6CommentsNetgear Readynas NVX (Buisness)
I just bought the device for 30 euros and have managed to install the latest official firmware (4.2.31) with Root SSH and fixed the TLS issue. Now I am wondering moving onto flashing something more modern, like Alpine Linux x86. I was wondering if this is possible, advisable and what issues might arise. I have ordered a UART TTL to USB adapter and ask if I would need anything else for this. I appreciate all kinds of feedback. Thanks in advancedAntiVirus No Longer Updating
Since 30th September, I have been getting an email from my RN214 advising me that the "Antivirus scanner definition file update failed due to download failure. Check your Internet connection." I know that the internet connection is OK because Transmission BitTorrent client is working OK. SSHing in and trying "freshclam" does not work either: I get "WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.103.7 Recommended version: 1.0.9" On the ClamAV website it says for v0.103 LTS, "DB downloads allowed until Sep-14 2025", so that is the likely cause: https://docs.clamav.net/faq/faq-eol.html Does anyone has a solution for this please? Either a way to update ClamAV on an ARM device or to fool ClamAV into still providing database updates? My RN214 is running ReadyNAS OS v6.10.9 - will "upgrading" to 6.10.10 help to resolve this? From the latter's release notes I suspect not. TIA Paul