NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
j6harri
Jul 30, 2012Aspirant
ReadyNAS Pro 192.168.168.168 case number: 19092544
I was connected to my ReadyNAS Pro last night via ssh. This morning, I see my ssh window NASHOG:/usr/bin# Write failed: Broken pipe. No big deal. I try to ping the ReadyNAS and it is there. Mac...
ebridges
Aug 04, 2012Aspirant
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:
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:
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
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!