ReadyNAS Pro 192.168.168.168 case number: 19092544

The 192.168.168.168 address suggests that DHCP failed, so no dynamic address was defined.

You can do a direct connect by manually configuring your MAC IP address to 192.168.168.167 - that should let you into Frontview and SSH. Assigning a static IP address is one way to prevent this from happening again, though you do need to be careful to assign one that is within your subnet range, and which won't overlap with the dhcp addresses assigned by your router.

What kind of bonding do you have setup in your unit?
I can see this issue happening when the teaming is configured incorrectly.

I have teaming setup. The odd thing is I have had it setup for the past 2 years. I did not make any changes. I am curious if maybe one of the nic's is failing and thus causing the issue. I did go ahead and boot into tech support mode and when I did I noticed that it is getting the correct ip 192.168.7.183 when it booted in debug mode.

If it works with only one ethernet cable connected, then perhaps something went wrong with the teaming or one of the NIC interfaces.

So I shutdown the ReadyNAS, unplugged the top network cable, and powered it back on. Still IP on 192.168.168.168. Shutdown, plugged in the top network cable and unplugged the bottom network cable, powered on. Still IP on 192.168.168.168.

So I shutdown, plugged in a network cable directly from my MAC to ReadyNAS. Opened network preferences, clicked on ethernet, changed the config to manual, set the ip to 192.168.168.167, subnet to 255.255.255.0, router to 192.168.168.168. Powered on ReadyNAS. Once it booted up, I connected via browser to 192.168.168.168 and was able to login. Everything config wise looked normal. I went to Network / Interfaces, IPv4 Assignment, set it to use values below, IPv4 Address 192.168.7.183 which is what I have the router set to assign to the mac of the ReadyNAS, Subnet 255.255.255.0.

Shutdown the ReadyNAS, plugged both network cables back in, and rebooted. It of course assigned the IP of 192.168.7.183. I then connected my MAC back to the network and was able to reach the admin via browser at 192.168.7.183. That looks good.

Try to ssh again. It still fails.

Macintosh:~ Drew$ ssh root@192.168.7.183
ssh: connect to host 192.168.7.183 port 22: Connection refused
Macintosh:~ Drew$

Go to finder, go, connect to server.
afp://192.168.7.183
Connection Fails

Go to finder, go, connect to server.
smb://192.168.7.183
Connection Succeeds

Check ReadyNAS Admin, Services , Standard File Protocols, AFP is enabled.

Check ReadyNAS Admin, Shares, Share Listing, AFP is enabled for my shares.

So at this point, I can access via https and smb but not afp or ssh.

Any one have any ideas?

It sounds like we are getting closer! :)

The AFP and SSH is not working... I would try to disable/re-enable AFP to see if that helps.
Have you tried reinstalling the enable root ssh access to see the ssh service comes back?

I'm running into the same error, except once the broken pipe error occurs I'm unable to login via afp, cifs, or ssh. I was able to get in at one point via frontview, and was able to retrieve all of the logs.

In this, i was able to find this log message which occurred right before the connection crash:

Aug  4 09:37:26 nas kernel: message_handler[5845]: segfault at 0 ip 00000000f7508133 sp 00000000ffdac224 error 4 in libc-2.7.so[f7496000+138000]

After some time (~10 minutes) the situation appears to right itself and am able to log in via SSH and by cifs.

A couple of things that may be relevant:

• This is a brand new device, so I have the option of a factory reset or an OS reinstall.
  [**] (edit - made other progress that would make this an inconvenience)


• I have the following plugins installed: root/ssh, Dropbox, and Crashplan.


• I changed the hostname from the default via Frontview.


• This is an Ultra 4