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 think I spoke too soon about VMFS v5... Even with VMFS v5 it isn't working as it goes to 100% but hangs there during vm creation and times out with the error: "A general system error occurred: The system returned an error. Communication with the virtual machine might have been interrupted"
And on the server:
2011-08-27T17:15:57.480Z cpu4:2052)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x93 (0x41240077ac40) to dev "naa.60014052e2962c00248d005000000000" on path "vmhba34:C0:T2:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0.Act:NONE
2011-08-27T17:15:57.504Z cpu6:2054)ScsiDeviceIO: 2305: Cmd(0x41240077ac40) 0x93, CmdSN 0x37f to dev "naa.60014052e2962c00248d005000000000" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0.
2011-08-27T17:15:57.509Z cpu6:2054)ScsiDeviceIO: 2305: Cmd(0x41240077ac40) 0x93, CmdSN 0x37f to dev "naa.60014052e2962c00248d005000000000" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0.
2011-08-27T17:15:57.529Z cpu6:2054)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x93 (0x41240077ac40) to dev "naa.60014052e2962c00248d005000000000" on path "vmhba34:C0:T2:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0.Act:NONE
2011-08-27T17:15:57.533Z cpu6:2054)ScsiDeviceIO: 2316: Cmd(0x41240077ac40) 0x93, CmdSN 0x37f to dev "naa.60014052e2962c00248d005000000000" failed H:0x3 D:0x0 P:0x0 Possible sense data: 0xb 0x24 0x0.
2011-08-27T17:15:57.533Z cpu6:2054)ScsiDeviceIO: 2949: CmdSN 0x3a8 to device naa.60014052e2962c00248d005000000000 timed out: expiry time occurs 0ms in the past
2011-08-27T17:15:57.533Z cpu2:3069)FS3DM: 2427: status Timeout zeroing 1 extents (8192 each)
2011-08-27T17:15:57.533Z cpu2:3069)J3: 2601: Aborting txn (0x410018c26330) callerID: 0xc1d00006 due to failure pre-committing: Timeout
2011-08-27T17:15:57.533Z cpu2:3069)Fil3: 13341: Max timeout retries exceeded for caller Fil3_FileIO (status 'Timeout')
2011-08-27T17:15:57.533Z cpu2:3069)BC: 4347: Failed to flush 1 buffers of size 8192 each for object 'ccc.vmx' f530 28 3 4e59095c 17ec0508 898cf726 94e818a5 1809944 9 0 0 0 0 0: Timeout
So in other words, ReadyNAS NVX isn't usable with ESXi 5.0 at all from my tests. - What version of RAIDiator are you running?
RAIDiator 4.2.19 (currently in public beta) is due for production release soon and it would be good if you could check once that's released if you still have issues using that.
Welcome to the forum! - I'm running 4.2.17... I'm not sure about using a beta release unless it would fix the problem for sure as I have some critical data on the NAS...
- I suggested waiting for the production release soon.
Is ESXi 5 a production release of ESXi? If it is a production release and only recently released compatibility may not be addressed in 4.2.19. It would still be worth trying 4.2.19 once a production release has come out to see if NetGear has addressed compatibility. One would expect they'll want ESXi 5.0 certification. - Yes ESXi 5.0 was recently released for production. I guess I will wait till 4.2.19 is out but it seems to be a common problem with ESXi as there are reports that even FreeNAS and Openfiler are having problems
- I guess it could be a little while then before the issue is resolved. An update may require a fair bit of testing. Especially when it comes to be business applications, stability is important. Also they won't want to break other uses of iSCSI in addressing compatibility with ESXi 5. Personally I wouldn't expect this to be resolved in 4.2.19, but then I'm just a user making a guess so I could be wrong.
- i have a similar issue in my lab with esxi5.0 and a readynas pro running 4.2.18. with nfs everything works. when i try iscsi i get all kinds of weird issues including the one described here.
my system.log shows this:
Aug 29 16:13:31 ESX-ISCSI kernel: WRITE_SAME w/o UNMAP bit not supported for Block Discard Emulation
Aug 29 16:14:02 ESX-ISCSI last message repeated 8768 times
Aug 29 16:14:32 ESX-ISCSI last message repeated 8642 times
can you check your system.log if it shows similar entries? - Yes I do have the same kind of messages as well...
- okidoki. i would suggest opening a case with techsupport and emailing them your logs.
- Hi,
Having the exact same issues here on a ReadyNas 3200 with 4.2.17. Hope this is resolved soon as 1/3 of my cluster of hosts now cannot run VMs on the shared storage :(
Btw : it works fine with a Windows 2008R2 box configured as ISCSI target with the MS software. Seems to be related to the (open source ?) iscsi target implementation.
Peter.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
