NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS 2100 goes down
Hello. Not sure if I am posting the thread in the correct section, so move it somewhere else if I did something wrong. I will try to explain the trouble briefly. I have ReadyNAS 2100 in the company ...
I finally got the reason why the NAS was instable. The reason are CIFS shares. These shared were added as Veeam backup repositories. I have removed these shares to add as iSCSI targets to the Veeam server afterwards. The NAS is stable now.
Still goes down. Today it happened again.
Oct 8 04:03:18 te-nas03-m kernel: rx_data() returned an error.
Oct 8 04:03:18 te-nas03-m kernel: iSCSI Login negotiation failed.
Oct 8 04:03:32 te-nas03-m kernel: rx_data() returned an error.
Oct 8 04:03:32 te-nas03-m kernel: iSCSI Login negotiation failed.
Oct 8 04:03:43 te-nas03-m kernel: rx_data returned -104, expecting 48.
Oct 8 04:03:43 te-nas03-m kernel: iSCSI Login negotiation failed.
Oct 8 04:03:56 te-nas03-m kernel: rx_data returned -104, expecting 48.
Oct 8 04:03:56 te-nas03-m kernel: iSCSI Login negotiation failed.
Oct 8 04:04:11 te-nas03-m kernel: iSCSI Login timeout on Network Portal xxx.xxx.xxx.xxx:3260
Oct 8 04:04:11 te-nas03-m kernel: rx_data() returned an error.
Oct 8 04:04:11 te-nas03-m kernel: iSCSI Login negotiation failed.
Oct 8 04:04:22 te-nas03-m kernel: rx_data() returned an error.
Oct 8 04:04:22 te-nas03-m kernel: iSCSI Login negotiation failed.
Oct 8 04:04:37 te-nas03-m kernel: iSCSI Login timeout on Network Portal xxx.xxx.xxx.xxx:3260
Oct 8 04:04:37 te-nas03-m kernel: rx_data() returned an error.
Oct 8 04:04:37 te-nas03-m kernel: iSCSI Login negotiation failed.
Oct 8 04:04:40 te-nas03-m kernel: rx_data() returned an error.
Oct 8 04:04:40 te-nas03-m kernel: iSCSI Login negotiation failed.
Oct 8 04:04:55 te-nas03-m kernel: iSCSI Login timeout on Network Portal xxx.xxx.xxx.xxx:3260
Oct 8 04:04:55 te-nas03-m kernel: rx_data() returned an error.
When you disabled LACP, did you remove the second NIC cable?
Is the NAS only hosting iSCSI LUNs? Do you know what LUN is causing the error? Are you seeing any operational issues with the device that is running the iSCSI initiator?
Of course, I did. The NAS has 1 CIFS resourse which is used by 1 server and 4 iSCSI targets for 4 different servers, no iSNS. The servers are fine, no errors, nothing suspicious. When the NAS goes down, it's getting unavailable for everything.
vitaliyvolkov wrote:
Of course, I did.
You'd be surprised on how many people don't.
vitaliyvolkov wrote:
The NAS has 1 CIFS resourse which is used by 1 server and 4 iSCSI targets for 4 different servers, no iSNS. The servers are fine, no errors, nothing suspicious. When the NAS goes down, it's getting unavailable for everything.
You might need paid support for this problem. Or perhaps just replace the NAS? It is pretty old at this point.
I know, it's old and hence I hold nothing critical there. I just don't get why this problem happens to this NAS cause I have 3 NAS of the same manufacturer and device model. They all are identical, but one of them is not stable.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
