NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Diagnose Readynas Duo
Trying to start my ReadyNas Duo RND2210v2 after it probably was shut down non-gracefully (power outage). It's been stuck for 12 hours and the only LED showing is the Disc Activity LED that blinks eve...
Picked up on this issue now.
I bought a SATA - USB adapter, and while Seatools can't detect any hard drive - HDDScan can detect both. It seems disk 1 has many, many errors but disk 2 might be healthy.
What do you suggest I do as a next step? Is it harmless to try and start the NAS with only disk 2 inserted?
Edit: It seems disk 2 has no partitions according to Windows Disk Management.
If you don't have email alerts set up, you might want to take care of that after everything is up and running. Disk errors would have resulted in you getting an email.
Andy1337 wrote:
Is it harmless to try and start the NAS with only disk 2 inserted?
Yes, I'd try this next. I'd put it back in bay 2 (leaving slot 1 empty).
Andy1337 wrote:
Edit: It seems disk 2 has no partitions according to Windows Disk Management.
The RAID array in the original Duo is hardware accelerated, and at least the data volume has no partition. So I think this is normal.
Inserted disk 2 in slot 2 and it shows up in RAIDar but I can't access web interface, and I can't browse it. It shows up like this in RAIDar:
Don't know if the image works but otherwise, it's here: https://www.dropbox.com/s/psbgmxyr5473ppc/raidar.jpg?dl=0
It says "RAID Level X, Not redundant. A disk failure will render this volume dead.". The first yellow dot under the disks says that disk 1 is dead (which I guess is logical, since it's not in place).
Can you ping 192.168.1.59?
What happens if you enter \\192.168.1.59 into the file explorer address bar? Be careful to use the correct slash direction.
No, I can neither ping it, browse it nor access its web interface.
Hmm, maybe I have weird subnets honestly. The NAS used to be on 192.168.1.* network but now I moved it. Will figure out a way to fix it...
Andy1337 wrote:
Hmm, maybe I have weird subnets honestly. The NAS used to be on 192.168.1.* network but now I moved it. Will figure out a way to fix it...
Well, it still is on a 192.168.1.x network.
If you changed your router address space, try changing it back temporarily. Then change the NAS network connection to use DHCP (and optionally reserve an IP address in the router).
I fixed my network issues by connecting both my computer and the NAS to a switch and "hardcoded" my IPv4 local address to something on 192.168.1.* and then I could access it and browse it. Every file intact!
Thank you so much for your help! If you ever come to Stockholm, I will buy you a nice dinner! ;)
Andy1337 wrote:
I fixed my network issues by connecting both my computer and the NAS to a switch and "hardcoded" my IPv4 local address to something on 192.168.1.* and then I could access it and browse it. Every file intact!
Great. I'd back up the files next (data is at more at risk, since one disk has failed).
Andy1337 wrote:
If you ever come to Stockholm, I will buy you a nice dinner! ;)
I've been there a couple of times - it's a great place! But no plans to travel right now.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
