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 infrastructure, it's old but still used for some non-critical purposes. The problem is that device has started to go down spontaneously.
This is what I usually see in the syslog.
Sep 28 06:12:42 te-nas03-m kernel: sky2 0000:01:00.0: eth0: rx length error: status 0x5ea0100 length 2962
Sep 28 06:13:20 te-nas03-m kernel: iSCSI Login timeout on Network Portal xxx.xxx.xxx.xxx:3260
Sep 28 06:13:20 te-nas03-m kernel: rx_data() returned an error.
Sep 28 06:13:20 te-nas03-m kernel: iSCSI Login negotiation failed.
Sep 28 06:13:35 te-nas03-m kernel: iSCSI Login timeout on Network Portal xxx.xxx.xxx.xxx:3260
Sep 28 06:13:35 te-nas03-m kernel: rx_data returned -512, expecting 48.
Sep 28 06:13:35 te-nas03-m kernel: iSCSI Login negotiation failed.
Sep 28 06:13:56 te-nas03-m kernel: iSCSI Login timeout on Network Portal xxx.xxx.xxx.xxx:3260
Sep 28 06:13:56 te-nas03-m kernel: rx_data() returned an error.
Sep 28 06:13:56 te-nas03-m kernel: iSCSI Login negotiation failed.
Sep 28 06:15:26 te-nas03-m kernel: MODE SENSE: unimplemented page/subpage: 0x1c/0x00
Where xxx.xxx.xxx.xxx is its IP-address, both Ethernet interfaces are configured for LACP 2+3. The firmware is up to date.
I'd really like to know if you had the same problem or if you could help me somehow. Thank you anyway.
Kind regards
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.
11 Replies
Replies have been turned off for this discussion
@vitallyvolkov
Welcome to the Community!
It might be network related, have oyu enabled Jumbo frames on your servers or on the NAS? What firmware are you running? Can you send us the full logs through sharing link so we can check.
Regards
Hello, MarcV.
No, Jumbo frames weren't enabled on the NAS and the servers connected to the NAS. The RAIDiator version is 4.2.31. Which log-file I have to send and where? What e-mail?
vitaliyvolkov wrote:
Which log-file I have to send and where? What e-mail?
Download the full log zip file from the web ui. Marc_V is asking you to send him a downloadable link to the full zip (google drive, onedrive, etc) in a private message. Click on the envelope link in the upper right of the forum to do that.
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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
