NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

ReadyNAS

73 Topics

ReadyNAS Ultra 6 Plus No volume after replacing failed drive
I have a ReadyNAS Ultra 6 Plus (RNDP600U) with 6 x 3TB drives. It is running RAIDiator version 4.2.31. I thought that I had created a backup of the media and backup volumes, but either I did not complete that task or I cannot find the USB drive I was using for that. That is my fault. Recently, I found that drive #2 had failed. I replaced it with a new drive and the system started a rebuild. The rebuild failed. Now when I try to access the media or backup volumes I am told there is no volume. The ReadyNAS boots ok, but when I first attempt to access the WebUI for the admin area a popup window says: The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. media backup When I access the WebUI for the shares it states, "No shares currently accessible." I tried reinstalling RAIDiator version 2.4.31 Additionally, /dev/c/c does not exist nor does /dev/c. The UI for RAIDar shows the status as "Healthy" and all six drives are operational and ok. The logs for the ReadyNAS show: Severity Date Message Fri Nov 28 20:55:55 MST 2025 System is up. Fri Nov 28 20:55:54 MST 2025 The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. media backup Fri Nov 28 20:55:37 MST 2025 Volume scan failed to run properly. Fri Nov 28 13:43:25 MST 2025 The default backup button job copies the contents of the [backup] share to the USB hard drive directly attached to the front of the NAS. Please attach a USB hard drive directly to the front USB port before pressing the backup button. Fri Nov 28 13:41:30 MST 2025 System is up. Fri Nov 28 13:41:29 MST 2025 The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. media backup Fri Nov 28 13:41:12 MST 2025 Volume scan failed to run properly. Fri Nov 28 12:45:27 MST 2025 Powering off device Fri Nov 28 12:45:27 MST 2025 Please close this browser session and use RAIDar to reconnect to the device after it is powered back on. System powering off... Tue Nov 25 22:57:39 MST 2025 System is up. Tue Nov 25 22:57:38 MST 2025 The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. media backup Tue Nov 25 22:57:21 MST 2025 Successfully enabled root SSH access. The root password is now the same as your admin password. Tue Nov 25 22:57:19 MST 2025 Volume scan failed to run properly. Tue Nov 25 22:56:26 MST 2025 Please close this browser session and use RAIDar to reconnect to the device. System rebooting... Tue Nov 25 21:27:49 MST 2025 System is up. Tue Nov 25 21:27:48 MST 2025 The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. media backup Tue Nov 25 21:27:31 MST 2025 Volume scan failed to run properly. Tue Nov 25 21:26:38 MST 2025 Rebooting device... Tue Nov 25 21:26:38 MST 2025 Please close this browser session and use RAIDar to reconnect to the device. System rebooting... Mon Nov 24 21:44:17 MST 2025 Successfully started FTP service. Mon Nov 17 22:09:41 MST 2025 System is up. Mon Nov 17 22:09:41 MST 2025 The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. media backup Mon Nov 17 22:09:28 MST 2025 Your ReadyNAS device has been updated with a new firmware image. (RAIDiator-x86 4.2.31) Mon Nov 17 22:09:26 MST 2025 Volume scan failed to run properly. Mon Nov 17 22:07:29 MST 2025 Please close this browser session and use RAIDar to reconnect to the device. System rebooting... Mon Nov 17 21:45:32 MST 2025 Fan will be recalibrated over the next few minutes. Mon Nov 17 21:41:07 MST 2025 HTTP service restarted. Mon Nov 17 21:38:18 MST 2025 System is up. Mon Nov 17 21:38:17 MST 2025 The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. media backup Mon Nov 17 21:38:00 MST 2025 Volume scan failed to run properly. Mon Nov 17 21:36:58 MST 2025 Please close this browser session and use RAIDar to reconnect to the device. System rebooting... Mon Nov 17 21:32:56 MST 2025 ReadyDLNA media file rescan completed. Mon Nov 17 21:32:56 MST 2025 ReadyDLNA media file rescan started. Mon Nov 17 21:31:52 MST 2025 Alert settings saved. Mon Nov 17 21:30:08 MST 2025 Fan will be recalibrated over the next few minutes. Mon Nov 17 21:16:53 MST 2025 New disk detected. If multiple disks have been added, they will be processed one at a time. Please do not remove any added disk(s) during this time. [Disk 1] Mon Nov 17 21:16:36 MST 2025 A disk was removed from the ReadyNAS. Mon Nov 17 21:16:36 MST 2025 Disk removal detected. [Disk 1] Mon Nov 17 21:04:20 MST 2025 System is up. Mon Nov 17 21:04:19 MST 2025 The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. media backup Mon Nov 17 21:04:02 MST 2025 Volume scan failed to run properly. Wed Nov 5 08:51:12 MST 2025 System is up. Wed Nov 5 08:51:12 MST 2025 The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. media backup Wed Nov 5 08:51:05 MST 2025 Volume scan failed to run properly. Tue Sep 30 21:39:42 MDT 2025 System is up. Tue Sep 30 21:39:41 MDT 2025 The paths for the shares listed below could not be found. Typically, this occurs when the ReadyNAS is unable to access the data volume. media backup Tue Sep 30 21:24:22 MDT 2025 Volume scan failed to run properly. Tue Sep 30 21:38:07 MDT 2025 System is up. Tue Sep 30 19:32:32 MDT 2025 RAID sync started on volume C. Tue Sep 30 19:32:07 MDT 2025 Data volume will be rebuilt with disk 2. Tue Sep 30 19:30:00 MDT 2025 New disk detected. If multiple disks have been added, they will be processed one at a time. Please do not remove any added disk(s) during this time. [Disk 2] Tue Sep 30 19:25:56 MDT 2025 A disk was removed from the ReadyNAS. One or more RAID volumes are currently unprotected, and an additional disk failure or removal may result in data loss. Please add a replacement disk as soon as possible. Tue Sep 30 19:25:56 MDT 2025 Disk removal detected. [Disk 2] Tue Sep 30 01:25:32 MDT 2025 Data volume will be rebuilt with disk 2. Tue Sep 30 01:20:04 MDT 2025 System is up. Mon Sep 29 22:05:58 MDT 2025 Fan will be recalibrated over the next few minutes. Mon Sep 29 00:06:29 MDT 2025 The on-line filesystem consistency check completed without errors for Volume C. Mon Sep 29 00:00:01 MDT 2025 The on-line filesystem consistency check has started for Volume C. I install the app to allow SSH via root to the ReadyNAS. When I login via SSH I see the following: # ls -l /dev/md* brw-rw---- 1 root disk 9, 0 2025-11-28 21:05 /dev/md0 brw-rw---- 1 root disk 9, 1 2025-11-28 21:05 /dev/md1 /dev/md: total 0 lrwxrwxrwx 1 root root 6 2025-11-28 21:05 0 -> ../md0 lrwxrwxrwx 1 root root 6 2025-11-28 21:05 1 -> ../md1 brw------- 1 root root 9, 2 2025-11-28 21:05 2 # readynas:~# mdadm --detail /dev/md2 mdadm: cannot open /dev/md2: No such file or directory # readynas:~# mdadm --detail /dev/md/2 mdadm: md device /dev/md/2 does not appear to be active. # readynas:~# vgscan Reading all physical volumes. This may take a while... No volume groups found # readynas:~# vgchange -ay No volume groups found # lvm pvs No output # lvm vgs No volume groups found # lvm lvs No volume groups found # readynas:~# mdadm /dev/md/2 /dev/md/2: is an md device which is not active I was able to boot the ReadyNAS into Tech Support mode and access the command line. On the command line while logged on in Tech Support mode I see the following information. # ls -l /dev/md* lrwxrwxrwx 1 4 Nov 29 03:04 /dev/md0 -> md/0 lrwxrwxrwx 1 4 Nov 29 03:04 /dev/md1 -> md/1 lrwxrwxrwx 1 4 Nov 29 03:04 /dev/md2 -> md/2 /dev/md: brw------- 1 9, 0 Nov 29 03:04 0 brw------- 1 9, 1 Nov 29 03:04 1 brw------- 1 9, 2 Nov 29 03:04 2 # /bin/start_raid.sh mdadm: /dev/md/0 has been started with 6 drives. mdadm: /dev/md/1 has been started with 6 drives. mdadm: failed to RUN_ARRAY /dev/md/2: Input/output error mdadm: failed to RUN_ARRAY /dev/md/2: Input/output error # vgscan -v Wiping cache of LVM-capable devices Wiping internal VG cache Reading all physical volumes. This may take a while... Finding all volume groups No volume groups found # vgchange -ay No volume groups found # lvm pvs No output # lvm vgs No volume groups found # lvm lvs No volume groups found # mdadm --detail /dev/md2 /dev/md2: Version : 1.02 Creation Time : Sun Jan 20 05:15:26 2013 Raid Level : raid5 Used Dev Size : -1 Raid Devices : 6 Total Devices : 6 Preferred Minor : 2 Persistence : Superblock is persistent Update Time : Wed Oct 1 03:38:34 2025 State : active, degraded, Not Started Active Devices : 5 Working Devices : 6 Failed Devices : 0 Spare Devices : 1 Layout : left-symmetric Chunk Size : 64K Name : 001F33EAFC49:2 UUID : 9e31c8bc:f2765365:abe63c40:f5037492 Events : 42539 Number Major Minor RaidDevice State 6 8 3 0 active sync /dev/sda3 8 8 19 1 spare rebuilding /dev/sdb3 2 8 35 2 active sync /dev/sdc3 3 8 51 3 active sync /dev/sdd3 4 8 67 4 active sync /dev/sde3 7 8 83 5 active sync /dev/sdf3 Why would sdb3 still be trying to rebuilding when the ReadyNAS believes it is done and operational according to the information seen in "RAIDar"? The logs state the sync of drive 2 the Should I pull out /dev/sdb (Drive #2) and put it back in to restart the rebuild? Running "mdadm --detail /dev/md0" and "mdadm - -detail /dev/md1" do not show any issues and all drive partitions are active. Note: The second time back logged in under Tech Support mode running "mdadm --detail /dev/md2" states "mdadm: md device /dev/md2 does not appear to be active." I cannot repeat getting md2 apparently active to show that /dev/sdb3 is rebuilding. Does anyone have an idea how I fix this to recover access to the data? Or, do I need to acquire an enclosure to put the drives in there and attach to a Windows system to attempt data recovery with COTS software? Any help is greatly appreciated.
shaneswartz
Nov 30, 2025 Place Use your ReadyNAS
27Views
0likes
6Comments
Readynas 314 - No internet connection
Would someone mind helping me to get the internet working on my NAS? I don't tend to access it very often when I'm away from home so I'm not sure exactly when the problem began. I want it to work so I get notifcations of any problems. It was working for at least a year. Causes could be: New Router, New Modem. My Telstra Smart modem is set to bridge mode. It's IP is 192.168.0.1 My Ubiquiti Security gateway router's IP is 192.168.1.1 I have an unmanaged switch. The local network and internet is working. I have had the smart modem for a month, purchased it so I was ready for NBN which was connected this week. The internet has never worked on the NAS when using this modem. This may or may not be the cause. The NAS is plugged into one of the spare ports on the unmanaged switch. My Nas Et0 is set to static, Eth1 is dynamic. Adaptor Eth0 had no DNS server in the IPV4 settings, Eth1 had 192.168.0.1 I've tried adding 8.8.8.8 to both adaptors. No cigar.
Solved
david_spittle
Apr 23, 2018 Place Use your ReadyNAS
2.4KViews
0likes
2Comments
RN3138 From linux to SMB share
Hello. I'm running a FreePBX VoiP server and I'm trying to share recorded calls directly to the ReadyNAS SMB share. The problem is that I'm constantly getting a permision denied error. I've mapped the smb share on the PBX and I'm able to create folders and even files through mkdir or nano logged as root. Unfortunately the automatic system which saves the recordings is not using a root account or privilages - it uses different user. And that's where I'm stuck and I don't really know how to make it work. I've created a username on ReadyNAS with same credentials as on the PBX and it still doesn't want to work. Does anyone know how to make it work, or should I just try to do it in a different way (maybe an rsync? FTP?). I know it sounds complicated, but the goal that I want to achive is simple - to give everyone an access to their recorded calls right after they finish the conversation, and the default location of the recorded calls is on the PBX server where only I have access (and it has to stay that way :) ). I'm aware that it's not only ReadyNAS related, but maybe someone had simillar problem (maybe not directly with PBX but with any other linux-based system). Cheers.
Solved
BlackMagic
Apr 17, 2018 Place Use your ReadyNAS
1.3KViews
0likes
1Comment
Erreur can_overcommit
Hi everybody, My ReadyNAS 104 version 6.9.2 didn't respond. I rebooted it. One hour after Boot process, only one message displays : can_overcommit+20 I don't have SSH or Web access, only ping. What can I do ?
Solved
Wil31
Apr 12, 2018 Place Use your ReadyNAS
2.4KViews
0likes
10Comments
ReadyNAS 6.7.1 and Google Drive Cloud Sync
Bidirectional sync with Google Drive Cloud does not seem to work. On the Bidirectional setting it only syncs from the NAS to Google Drive Cloud but not the other way round. I did some tests with all 3 sync modes: up / down / bidirectional. Even on the down settings it still does not sync from Google Drive Cloud to the NAS. Only the up mode works (NAS to Google Drive Cloud). On other posts/threads I've seen mention of setting the synchronisation check frequency but that does not appear anywhere. Can anyone help?
socross
Apr 09, 2018 Place Use your ReadyNAS
14KViews
0likes
21Comments
ReadyNAS NV+ -failure
Hi all, I am hoping for some answers/help here. I have a ReadyNAS NV+, model number on the back says RND4000-100 v3. Up until a couple weeks ago it's been a faithful and amazing machine. I had it on a time schedule for auto on/off and one morning it just didn't come on. No bad smells (fried electronics), hooked to a surge protector, etc. Pushing the power button did nothing. No sounds, no lights flickering, nothing. From reading these forums I assumed it was a bad PSU. I tried to secure one through Netgear, but no luck. I found one on eBay that I probably paid too much for (after more reading), replaced it, and now the fan comes on and the hard drive lights flash briefly, but that's it. The LCD screen remains dark and it doesn't sound like anything else is happening. In my panic to preserve my data I tried a couple different programs that claimed to be able to read the NAS' file system. I purchased one of them - RTools for Windows. From drive 1 it recovered the folder I wanted, but only maybe a quarter of it in size. Most of the sub folders are empty. I assume that this is because it was a 4 drive system and the data is spread out? This is turning out to be a crash course in NASs for me. I'm having a lot of mixed results, and to be honest I don't actually know what I'm doing. It seems prudent to ask for advice here before I actually screw something up. Ideally there would be a way to simply revive the NAS itself of course. If not, I guess I'm looking for the full spectrum of advice here. I have a MacBook and a Windows laptop in the house to troubleshoot with. Any help is greatly appreciated.
MeatPopsicle
Apr 02, 2018 Place Use your ReadyNAS
1.3KViews
0likes
6Comments
Issue on power loss / failure - automatically rebooting after manual shutdown
There's an issue on ReadyNas RN202 , firmware 6.9.3 On power loss / failure the NAS is automatically rebooting after manual shutdown. how this issue happens: 1. WakeOnLAN enabled 2. Readynas connected via ethernet port 1 3. power failure from electricity loss or shutdown while the NAS is operating 4. electricity coming back and NAS restarting automatically 5. shuting down the NAS via web interface or double click on power button manually 6. the NAS is rebooting automatically everytime i try to shut it down what i checked: 1. preventing outdside connections coming from the port 9 Wake On LAN: 1.a - searching in the log files any connections of this type 1.b - by disconnecting the ethernet cable after shut down even in these cases, the NAS continues to automatically rebooting after manual shutdown. 2. disabling the WakeOnLAN option if disabled the NAS doesn't reboot automatically. I found the solution but, at this point, I would like to report a technical problem. I do not think the rebooting depends on the Wake on LAN as I have disabled all ports and continues to persist. I also checked log files and there is no access to port 9. Reading some comments I recorded that others have the same problem. They talked about the problem of power failure and somehow the power supply and the NAS were in PowerLoss mode like that of motherboards that restart automatically after such an event. So I tried as the follow: 1. Keep the WakeOnLAN option active 2. Turn off the NAS via the web interface/power on double pressed manually 3. As soon as the NAS turns off, I disconnected the POWER SUPPLY FROM THE ELECTRICAL OUTLET 4. I waited for the classic 20sec to neutralize the residual energy in the circuits. 5. I reconnected the power supply plug to the electrical outlet 6. Leds blinked and after few seconds they turned off and the NAS has not restarted. 7. I turned on the NAS by the power button on the front panel. 8. I opened the web interface and checked if everything was as before (WakeOnLAN still active) 9. I turned off the NAS again from the web interface 10. This time the NAS did not restart itself automatically! problem solved but remains a flaw that I would like to report.
fr33soul
Mar 19, 2018 Place Use your ReadyNAS
979Views
0likes
2Comments
ReadyNAS RND2000 V2 Flashing Power button
Hi all. My wife accidentally powered down my ReadyNAS Duo V2 the other day and when I plugged it back in and powered it back on the power light is flashing blue and I am unable to access the NAS Drives. The power light flashes 4 time and then stops for a coouple of seconds and then repeats the same pattern. I checked in RAIDarbut it cannot locate the drives. I looked at the light indicator legend in RAIDar and it says that a flashing blue light means that there is a lengthy background task in progress but it doesn't indicate of the blue light is the power light or the HDD LEDs. Based on this I have left the ReadyNAS over night but it is now almost 12 hours later and the power light is still flashing in the same pattern. It has 2 x 2TB drives installed which have about 600GB spare. Is it doing some sort of background data integrity check or repair? If so does the length of this task depend on the amount of data stored on the drives? Many thanks for any advice.
Pooly-DW
Feb 22, 2018 Place Use your ReadyNAS
1.8KViews
0likes
3Comments
ReadyNAS Ultra 6 Does Not Show Up On Windows 10 Network ... But Did At First
RE: ReadyNAS Ultra 6 Does Not Show Up On Windows 10 Network ... But Did At First At first the ReadyNAS 6 showed up and then it didn't. I restarted, switched the Network on and then off and back on ... but it still wouldn't show the files up. The ReadyNAS-Ultra-6 appears ... but the files are not available. Trying to locate the correct Windows 10 instructional ... or if there is something more fundamentally different between Netgear OS's which I can correct on the Windows side. I am able to see the files from my Mac Computers ... but the single Windows 10 machine is having trouble; are there some walkthroughs to double check if I need to set up a HomeGroup or WorkGroup ... or if it's related to the Firewall or other interferences which can switch if off by default. Will post answer if I get it first. Thanks.
Solved
HBGChristo
Feb 14, 2018 Place Use your ReadyNAS
6KViews
0likes
11Comments
Reboot ALWAYS fails after firmware upgrade on ReadyNAS RR4312X
Hi, I've just upgraded our NetGear ReadyNAS RR4312X from 6.8.0 to 6.9.1 and actioned a reboot using the webUI after the upgrade. However once again (this happens after every FW upgrade), the system fails to come online again. The system doesn't even respond to PINGs. - We have to power cycle the system after every upgrade to get it back online again. NB: The firmware installs successfully everytime, so it's just the reboots afterwards that are problematic. Not good for remote sites! Any idea's please? P.S. my entered text 'ReadyNAS RR4312X wont save in the 'Model' section of this web support form.
RL57
Jan 26, 2018 Place Use your ReadyNAS
1.7KViews
0likes
7Comments