Hello everyone- my old ReadyNAS NV (Infrant Ready label) powers up, I can ping it successfully but cannot access the files on the drives. Tried remapping the drives in file manager but the connection fails. I also can’t access the NAS web interface. The status lights on on the front show 4 solid green for the drives, the blue power LED flashes somewhat slowly 12 times then the activity green LED flashes once, then 12 more flashes of the blue power LED, and this repeats. Could not locate any info on what this LED sequence indicates. Any of you know?Is my trusty NAS finally dead? Most data is backed up but I have about 6 months of new data that I neglected to backup that I can hopefully recover.If all else fails can I buy an old chassis and put the drives in there to recover my data or is there another method I can use to recover the data?Any guidance on troubleshooting is greatly appreciated. Thank you.

I'm running RAIDar on Windows 10 and 11, so it is compatible. You do need a compatible version of Java installed. RAIDar is how you find out the status of your NAS. Your description doesn't sound like any of the documented LED error codes. But those are listed as being for 2-drive systems (after the NV was replace4d by the NV+, the only units without a display): LED blink behavior for 2 disk systems is three quick blinks of all disk LEDs and the backup LED, followed by a 1s delay, followed by a number of slow blinks. The number of slow blinks will be the error code. Current error codes: 1 - Vendor mismatch 2 - No disks detected 3 - Bad contents on root partition of disks 4 - Flash error 5 - Unsupported RAID configuration

wb26 wrote:Installed Java 8 update 441 but no luck running RAIDar 4.3.8. I can’t even uninstall version 4.3.8.I tried redownloading and reinstalling 4.3.8 but get an immediate error of “The application was unable to start correctly” This is the same error I get when I try to run the already installed copy of RAIDar 4.3.8. Use this one for 4.3.8: https://faucet.aas.duke.edu/pub/pc/bigfix/patches/java/jre-8u221-windows-i586.exe But 6.5 should find the NAS also. Turn off any internet security and antivirus software on the PC, and see if that makes any difference. If that gives the same result, try removing the disks and powering up the NAS. RAIDar should detect the system and give you a "no disks" status. On LED codes, there is an NV listing here: https://www.readynas.com/download/documentation/support/ReadyNAS-LED But I am not seeing your particular pattern there.

If you choose to get another NAS for your volume, you can also use an NV+ (the original, silver one, not the V2 black one). But before you do that, lets make sure it's the chassis, not the volume, that's the problem. What RAIDar sees with no drives will go a long way to determine that.

Would it help to insert one spare scratch disk into the NAS to reinstall the OS by pressing the reset button for 30 seconds during power up?If the above is successful and I can access the single volume could I then reinstall the original four drives and read them assuming they are in working order?

wb26 wrote:Would it help to insert one spare scratch disk into the NAS to reinstall the OS by pressing the reset button for 30 seconds during power up?If the above is successful and I can access the single volume could I then reinstall the original four drives and read them assuming they are in working order? That process won't work, since the OS is installed on the drive. So there is no path to get the OS onto the original drives. However, if the factory install works on the scratch disk, you could then power down the NAS, move the disk to slot 2, and see if that also boots. Repeat for slots 3 and 4. If the system boots with the disk in each slot, then you'd know that the hardware is ok.

ReadyNAS NV rnv1-s2-0000 can’t connect

35 Replies

StephenB
Guru
Feb 04, 2025
wb26 wrote:

If all else fails can I buy an old chassis and put the drives in there to recover my data or is there another method I can use to recover the data?

Any guidance on troubleshooting is greatly appreciated. Thank you.

Have you tried RAIDar? It might give you more information.

I suggest testing the disks in a Windows PC with vendor tools (Seatools for Seagate, Dashboard for Western Digital). Run the short test first, if that passes then run the long test. You can connect the disks with a USB adapter/dock.

There are of course other possibilities, including a memory failure.

As far as recovery goes, you could also get a 4-bay enclosure and use R-Studio (or similar RAID recovery software) to recover data.

https://www.r-studio.com/Buy-Data-Recovery-Software.html

You'd need the $79.99 license.

wb26 wrote:

I also can’t access the NAS web interface.

What error are you getting?
- Sandshark
  Sensei
  Feb 04, 2025
  How does it behave and what does RAIDar indicate with the drives removed?
- wb26
  Star
  Feb 04, 2025
  RAIDar does not work on my windows 10 system. I also tried running RAIDar in windows 7 compatibility mode but no luck. Is there a version that is compatible with windows 10?
  
  Will R-Studio work if I configured the NAS as X-RAID?
  
  When I try to access the admin interface at http://192.168.1.80/admin I get a can’t reach this page error even though the can ping the address successfully.
  
  Any idea what the blinking power LED indicates?
  
  Once on, the NAS is also difficult to power down. Only way I can power down is to hold the powering button down for about one minute.
  
  Thanks
  - Sandshark
    Sensei
    Feb 05, 2025
    I'm running RAIDar on Windows 10 and 11, so it is compatible. You do need a compatible version of Java installed.
    
    RAIDar is how you find out the status of your NAS. Your description doesn't sound like any of the documented LED error codes. But those are listed as being for 2-drive systems (after the NV was replace4d by the NV+, the only units without a display):
    
    LED blink behavior for 2 disk systems is three quick blinks of all disk LEDs and the backup LED, followed by a 1s delay, followed by a number of slow blinks. The number of slow blinks will be the error code. Current error codes: 1 - Vendor mismatch 2 - No disks detected 3 - Bad contents on root partition of disks 4 - Flash error 5 - Unsupported RAID configuration