NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
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.