NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS NVX problems with ESXi 5.0 [Case #16549549]
Hello,
I'm trying out ESXi 5.0 with iSCSI on ReadyNAS NVX but it seems that it is not able to write to the volume VMFS v3.46, which it should be able to. I can add the target perfectly fine and the ESXi can see all the LUNs but once I try to write or create a VM it just keeps showing In Progress but after a while it says Unable to access file xxx/xxx.vmxf. I have two other ESXi 4.1 on the ReadyNAS volume and they are working perfectly fine. Furthermore, when this ESXi 5.0 machine was ESXi 4.1 it was also working fine together with the two other machines on the same VMFS volume.
I tried adding a new LUN using VMFS v5 and it seems to be writing fine but here I only have one machine accessing the VMFS LUN.
Some errors I see on ESXi 5.0 for the VMFS 3.46 volume are as follows:
2011-08-27T15:28:49.063Z cpu0:2056)ScsiDeviceIO: 2305: Cmd(0x412400749ac0) 0x93, CmdSN 0x226 to dev "naa.60014052e2962c00248d003000000000" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0.
2011-08-27T15:28:49.083Z cpu0:2056)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x93 (0x412400749ac0) to dev "naa.60014052e2962c00248d003000000000" on path "vmhba34:C0:T1:L1" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0.Act:NONE
2011-08-27T15:28:49.099Z cpu0:2056)ScsiDeviceIO: 2305: Cmd(0x412400749ac0) 0x93, CmdSN 0x226 to dev "naa.60014052e2962c00248d003000000000" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0.
2011-08-27T15:28:49.103Z cpu0:2056)ScsiDeviceIO: 2305: Cmd(0x412400749ac0) 0x93, CmdSN 0x226 to dev "naa.60014052e2962c00248d003000000000" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0.
2011-08-27T15:28:49.123Z cpu0:2056)ScsiDeviceIO: 2316: Cmd(0x412400749ac0) 0x93, CmdSN 0x226 to dev "naa.60014052e2962c00248d003000000000" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0xb 0x24 0x0.
2011-08-27T15:28:49.123Z cpu6:2177)ScsiDeviceIO: 2949: CmdSN 0x24f to device naa.60014052e2962c00248d003000000000 timed out: expiry time occurs 1ms in the past
2011-08-27T15:28:49.123Z cpu6:4241)FS3DM: 2427: status Timeout zeroing 1 extents (65536 each)
2011-08-27T15:28:49.123Z cpu6:4241)J3: 2601: Aborting txn (0x410018c24c50) callerID: 0xc1d00006 due to failure pre-committing: Timeout
2011-08-27T15:28:49.123Z cpu6:4241)Fil3: 13341: Max timeout retries exceeded for caller Fil3_FileIO (status 'Timeout')
2011-08-27T15:28:49.123Z cpu6:4241)BC: 4347: Failed to flush 1 buffers of size 8192 each for object '1' f530 28 3 4e04f371 46875229 1c00457f dca691c0 3401444 13 0 0 0 0 0: Timeout
Does anyone have any idea of why this is happening on the ReadyNAS NVX with ESXi 5.0 or whether the ReadyNAS isn't really compatible with ESXi 5.0?
Thanks,
I'm trying out ESXi 5.0 with iSCSI on ReadyNAS NVX but it seems that it is not able to write to the volume VMFS v3.46, which it should be able to. I can add the target perfectly fine and the ESXi can see all the LUNs but once I try to write or create a VM it just keeps showing In Progress but after a while it says Unable to access file xxx/xxx.vmxf. I have two other ESXi 4.1 on the ReadyNAS volume and they are working perfectly fine. Furthermore, when this ESXi 5.0 machine was ESXi 4.1 it was also working fine together with the two other machines on the same VMFS volume.
I tried adding a new LUN using VMFS v5 and it seems to be writing fine but here I only have one machine accessing the VMFS LUN.
Some errors I see on ESXi 5.0 for the VMFS 3.46 volume are as follows:
2011-08-27T15:28:49.063Z cpu0:2056)ScsiDeviceIO: 2305: Cmd(0x412400749ac0) 0x93, CmdSN 0x226 to dev "naa.60014052e2962c00248d003000000000" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0.
2011-08-27T15:28:49.083Z cpu0:2056)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x93 (0x412400749ac0) to dev "naa.60014052e2962c00248d003000000000" on path "vmhba34:C0:T1:L1" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0.Act:NONE
2011-08-27T15:28:49.099Z cpu0:2056)ScsiDeviceIO: 2305: Cmd(0x412400749ac0) 0x93, CmdSN 0x226 to dev "naa.60014052e2962c00248d003000000000" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0.
2011-08-27T15:28:49.103Z cpu0:2056)ScsiDeviceIO: 2305: Cmd(0x412400749ac0) 0x93, CmdSN 0x226 to dev "naa.60014052e2962c00248d003000000000" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0.
2011-08-27T15:28:49.123Z cpu0:2056)ScsiDeviceIO: 2316: Cmd(0x412400749ac0) 0x93, CmdSN 0x226 to dev "naa.60014052e2962c00248d003000000000" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0xb 0x24 0x0.
2011-08-27T15:28:49.123Z cpu6:2177)ScsiDeviceIO: 2949: CmdSN 0x24f to device naa.60014052e2962c00248d003000000000 timed out: expiry time occurs 1ms in the past
2011-08-27T15:28:49.123Z cpu6:4241)FS3DM: 2427: status Timeout zeroing 1 extents (65536 each)
2011-08-27T15:28:49.123Z cpu6:4241)J3: 2601: Aborting txn (0x410018c24c50) callerID: 0xc1d00006 due to failure pre-committing: Timeout
2011-08-27T15:28:49.123Z cpu6:4241)Fil3: 13341: Max timeout retries exceeded for caller Fil3_FileIO (status 'Timeout')
2011-08-27T15:28:49.123Z cpu6:4241)BC: 4347: Failed to flush 1 buffers of size 8192 each for object '1' f530 28 3 4e04f371 46875229 1c00457f dca691c0 3401444 13 0 0 0 0 0: Timeout
Does anyone have any idea of why this is happening on the ReadyNAS NVX with ESXi 5.0 or whether the ReadyNAS isn't really compatible with ESXi 5.0?
Thanks,
51 Replies
Replies have been turned off for this discussion
- I don't want to blame just Netgear. For sure it was definitely VMware who changed the iSCSI stack.
I can remember they did this the same way with the transition from ESX3 to 3.5 - what a shame!
But I don't think VMware changed critical coding inside the iSCSI Stack since the ESXi 5 announcement
at the partner exchange in june, so Netgear had plenty of time to prepare for the launch - or at least
warn everyone not to install it.
pain2k - You have a point there. I still wonder why VMware felt there was a need for change anyway and why they didn't work closer with third party storage vendors.
-Stefan - Not sure if you guys have looked or not, but as of now all of the ReadyNAS products are not on the Hardware Compatability Listing for vSphere 5.0 4.1 U1 is the highest release. I would also make sure you have checked your server hardware to ensure it is on the list as well.
I have included a link to the HCL below.
http://www.vmware.com/resources/compatibility/search.php - If you follow VMware and their HCL for some time, you will see, that it will take some time until all systems are evaluated again.
It's on Netgear to recertify the ReadyNAS line for 5.0 again, as VMware has not enough ressources to recertify all HW on the HCL
by themself.
So - Netgear - hurry up!
BTW: Updated to 4.2.19 and still not working! Waiting for 4.2.20.... - We are aware of the issue, and are actively working on it. Support does not have to reproduce it, our developers already have the environments running.
Anyone using LIO (http://linux-iscsi.org/wiki/Main_Page) will have this issue on ESXi5, including Qnap, etc.
As mentioned, VMware's HCL listing for ReadyNAS is only v4 at this point. - We have a beta firmware with a fix for ESXi 5. For those who wish to test it, send me a PM and I'll give you a link. I don't want to post it here yet, as it has not been fully tested by our QA guys, was only built 20 minutes ago.
- Nope! 4.2.20-T1 is also not working... T2 please :D
- We've had another report of that. The logs from that site were not available though. If you can provide the NAS logs and ESX logs, that would help greatly. You can send them to the logs link in my signature below if possible.
- @chirpa The problem still exists with me as well. I have emailed the logs to you so you can have a look.
If you require any further information please let me know.
Thanks, - yep - my logs are also on the way...
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
