This morning my U2P was not 'visible'. ping does not work - destination host unreachable. Power button would not shut down the box and no access to Frontview.I rebooted with 5 second power off then power on again. RAIDar sees the box booting and file system check shows 100%, then the device disappears from RAIDar. I have done various reboots and at one point, after moving the box to another place, I could connect to Frontview and checked the logs and it had nothing wrong. I started to download the logs then the device disappeared again and I could no longer access it.It seems like sometimes the device can be pinged, other times it's not reachable. I tried both ethernet ports, different cables, different routers, but in all cases now I cannot map the drive in Windows and I cannot use Frontview to access the box and the box has to be shut down with the 5 second hold.I ran wireshark when trying to access the box with Frontview and I see lots of TCP SYN packets, followed immediately by RST/ACK from the NAS. Having rebooted for the nth time, ping is responding this time.Interestingly, if I ssh to the box now, I get the TCP connection, e.g. SYN/SYN-ACK/ACK, but then nothing else from the box...It sounds like a network hardware issue - we have had some odd problems over the last month which could have been network related. Is there anyway to connect a PC directly to the NAS without using a router? Anyone seen anything similar?

http://readynas.sphardy.com/2010/09/how-to-direct-connect-to-your-readynas_1197.html

Thanks for the link. Tried that in both ethernet ports. RAIDar sees nothing and I cannot ping 192.168.168.168. Wireshark shows ARP requests "Who has 192.168.168.168? Tell 192.168.168.169" but no response.NAS uses DHCP. Just in case, I tried setting the PC address to the IP that my router normally assigns to the box, still no joy. Odd that if it reconnect/reboot the NAS to the router, I can ping it, briefly before it stopped responding again this time.

Netgear support said reinstall OS. Did that. No joy, no change.

They might need to remotely login to your unit using tech support mode.

Now they tell me that "Issues like this can be associated with disks having errors or bad sectors. " and that I should remove the drives and run disk diagnostics... Maybe I am being naive, but I thought the purpose of running a mirror was to handle the case when a disk goes bad...Is this usual?

Unresponsive ultra 2 plus | NETGEAR Communities

13 Replies

mdgm-ntgr
NETGEAR Employee Retired
Mar 08, 2013
http://readynas.sphardy.com/2010/09/how-to-direct-connect-to-your-readynas_1197.html
adb1
Aspirant
Mar 08, 2013
Thanks for the link. Tried that in both ethernet ports. RAIDar sees nothing and I cannot ping 192.168.168.168. Wireshark shows ARP requests "Who has 192.168.168.168? Tell 192.168.168.169" but no response.

NAS uses DHCP. Just in case, I tried setting the PC address to the IP that my router normally assigns to the box, still no joy. Odd that if it reconnect/reboot the NAS to the router, I can ping it, briefly before it stopped responding again this time.
adb1
Aspirant
Mar 09, 2013
Netgear support said reinstall OS. Did that. No joy, no change.
mdgm-ntgr
NETGEAR Employee Retired
Mar 09, 2013
They might need to remotely login to your unit using tech support mode.
adb1
Aspirant
Mar 11, 2013
Now they tell me that "Issues like this can be associated with disks having errors or bad sectors. " and that I should remove the drives and run disk diagnostics... Maybe I am being naive, but I thought the purpose of running a mirror was to handle the case when a disk goes bad...

Is this usual?
adb1
Aspirant
Mar 11, 2013
I've taken the disks out and stuck them in a Windows 7 box and they are recognised by Windows, but Seatools does not see them! Anyway, I've been searching these forums on how to access the data on the drives.

I've tried rstudio, which in 4 hours will hopefully let me see the data, well I'll be asleep then, however, the Linux Disk reader mentioned in the thread
viewtopic.php?f=11&t=35153
did not work.

Does the DUO mentioned in that thread use the same file system as the U2Plus?
mdgm-ntgr
NETGEAR Employee Retired
Mar 11, 2013
The Ultra 2 Plus uses a different RAID format and the volume uses the EXT4 filesystem with the standard 4k block size. So the procedure to mount the array using Linux would be different (it is a bit easier to mount an array from a U2P than it is from a Duo).
adb1
Aspirant
Mar 11, 2013
Thanks, I'm getting there, however, I've got 2 DT2000DL003-9VT166-301 drives with F/W CC32 and I've just come across the thread

https://www.readynas.com/forum/viewtopi ... 24&t=63698

so now I'm wondering if all of a sudden both my drives have gone belly up in the NAS at the same time.

Anyway, just in the process of downloading an Ubuntu-12.04.2 to setup in VirtualBox and then try to access the drives via USB from there.
adb1
Aspirant
Mar 11, 2013
Both my disks seem OK, so I now have to try to work out it it's the Seagate disks causing the problem or the unit itself. I see a couple of options

1. Try each individual drive alone in the NAS
2. Put a brand new drive in the unit and see if I can boot

Can I do (1) just by powering on the unit with one disk at a time in it without affecting any oif the data on the disks?

I want to be absolutely sure I will not damage the disks in any way as I can still see the data using R-Studio

If I do (2) will any of my settings remain or are they all part of the data on the original disks?

I gather I'll need to factory reset the box. If I do so, will I be able to try putting my original disks back in again?

Help greatly appreciated
StephenB
Guru
Mar 11, 2013
The OS is on the disks. So there is no value in factory resetting the box, and then reinstalling the original disks. Also, that means (2) does not impact your original settings, as they are on your original disks.

Personally I'd back up the data before playing with your original drives. Theoretically you can do (1), but if you (or any process on the NAS) writes to the data drive then you lose the integrity of your RAID array.