NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Readynas 2100, ESXi 5.5u2?
Hey
We've got a ReadyNAS 2100 that we use as an iscsi datastore for a single esxi host. We're currently running esxi4.2, about to upgrade to 5.1.
One of our future paths involves upgrading some VM guests to Debian 7, which required esxi5+. Although he Radynas2100 isn't certified to run 5.5 - is there a reason it should or shouldn't work?
Thanks
We've got a ReadyNAS 2100 that we use as an iscsi datastore for a single esxi host. We're currently running esxi4.2, about to upgrade to 5.1.
One of our future paths involves upgrading some VM guests to Debian 7, which required esxi5+. Although he Radynas2100 isn't certified to run 5.5 - is there a reason it should or shouldn't work?
Thanks
10 Replies
Replies have been turned off for this discussion
- Can you email me your logs (see the link in my sig)?
What version of RAIDiator are you running? - Thanks for the reply. No logs - we haven't tried the upgrade yet. I thought I see if anyone has tried running esxi5.5 yet and whether there are any known issues.
Currently running 4.2.23, but we'll upgrade to 4.2.27 prior to the esxi upgrade. - Is this a 2100 v1 or a 2100 v2?
- 2100 v2
- I would suggest you ensure your backup is up to date before doing the upgrade.
Well seeing you have the v2, if it doesn't work on OS4 you could try OS6 though do note that our support team does not support running OS6 on legacy hardware.
I would try using it with OS4 first. - Thanks for the input.
We tried an temporary upgrade last week with ESXi 5.1 U3 which worked perfectly, detecting and upgrading the existing ESXi4.1. Then we rolled it back to the current setup.
Next step is to try the same thing again with 5.5 U3 and hope there are no significant changes in how it uses the scsi interface. - Hello,
I got the same issues with iSCSI LUNs. I have ReadyNAS 2100v2 and I'm trying to use it as iSCSI target for ESXi VMware ESXi 5.5.0 build-2302651 (I've updated it today).
No matter what I do - it fails all the time.
ESXi logs are mostly:
2015-01-05T13:08:14.591Z cpu0:32833)ScsiDeviceIO: 2325: Cmd(0x412e41fec300) 0x93, CmdSN 0x161 from world 34073 to dev "naa.60014052e1122400385d004000000000" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0.
2015-01-05T13:12:41.760Z cpu1:34073 opID=af1b9563)FS3DM: 2615: status Timeout zeroing 1 extents (65536 each)
2015-01-05T13:12:41.760Z cpu1:34073 opID=af1b9563)J3: 3114: Aborting txn (0x410bc5efde10) callerID: 0xc1d00006 due to failure pre-committing: Timeout
2015-01-05T13:12:42.160Z cpu13:33582)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410a20755670 network resource pool netsched.pools.persist.iscsi associated
2015-01-05T13:12:42.160Z cpu13:33582)iscsi_vmk: iscsivmk_ConnNetRegister: socket 0x410a20755670 network tracker id 216 tracker.iSCSI.10.216.252.111 associated
2015-01-05T13:12:42.161Z cpu13:33582)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: vmhba39:CH:0 T:2 CN:0: Failed to receive data: Connection closed by peer
2015-01-05T13:12:42.161Z cpu13:33582)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Sess [ISID: 00023d000001 TARGET: iqn.2011-06.nas-B2-B8-C8:nas0.my.iSCSI.target.com TPGT: 1 TSIH: 0]
2015-01-05T13:12:42.161Z cpu13:33582)WARNING: iscsi_vmk: iscsivmk_ConnReceiveAtomic: Conn [CID: 0 L: 10.216.252.125:40615 R: 10.216.252.111:3260]
2015-01-05T13:12:42.161Z cpu13:33582)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: vmhba39:CH:0 T:2 CN:0: Connection rx notifying failure: Failed to Receive. State=Bound
2015-01-05T13:12:42.161Z cpu13:33582)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Sess [ISID: 00023d000001 TARGET: iqn.2011-06.nas-B2-B8-C8:nas0.my.iSCSI.target.com TPGT: 1 TSIH: 0]
2015-01-05T13:12:42.161Z cpu13:33582)iscsi_vmk: iscsivmk_ConnRxNotifyFailure: Conn [CID: 0 L: 10.216.252.125:40615 R: 10.216.252.111:3260]
2015-01-05T13:12:42.413Z cpu13:33582)WARNING: iscsi_vmk: iscsivmk_StopConnection: vmhba39:CH:0 T:2 CN:0: iSCSI connection is being marked "OFFLINE" (Event:4)
2015-01-05T13:12:42.413Z cpu13:33582)WARNING: iscsi_vmk: iscsivmk_StopConnection: Sess [ISID: 00023d000001 TARGET: iqn.2011-06.nas-B2-B8-C8:nas0.my.iSCSI.target.com TPGT: 1 TSIH: 0]
2015-01-05T13:12:42.413Z cpu13:33582)WARNING: iscsi_vmk: iscsivmk_StopConnection: Conn [CID: 0 L: 10.216.252.125:40615 R: 10.216.252.111:3260]
ReadyNAS logs are:
Jan 5 12:18:58 swnas kernel: Received iSCSI login request from 10.216.252.125 on TCP Network Portal 10.216.252.111:3260
Jan 5 12:18:58 swnas kernel: Unable to locate Target IQN: iqn.2011-06.nas-B2-B8-C8:nas0.my.iSCSI.target.com in Storage Node
Jan 5 12:18:58 swnas kernel: iSCSI Login negotiation failed.
Jan 5 12:18:58 swnas kernel: iSCSI Login negotiation failed.
Jan 5 12:18:58 swnas kernel: WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
10.216.252.125 - my ESXi host
10.216.252.111 - my ReadyNAS - Is there a reason you are using iSCSI not NFS?
- I can use NFS. I understand that this is currently only working solution? I use iSCSI for all the other machines (older ones: ESXi 4.x.x) and it's working. I thought that it shouldn't be problem in case of latest ESXi.
So you're suggesting that NFS would be better in that particular case? - iSCSI is a good option when there is no alternative. If there is an alternative e.g. NFS, then it is best to use the alternative.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
