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
- Any update on this. Thank GOD I did not upgrade my ESX machines...!
jeremyotten wrote: Any update on this. Thank GOD I did not upgrade my ESX machines...!
yup pretty awful that vmware broke stuff before telling anyone about it :)- This is a good example of why it's a bad idea to rush to adopt a major new version of software/a operating system in a production environment. Large businesses can setup test environments whereas smaller companies can use the web (e.g. forums like this) to check for issues that arise which early adopters discover.
- Hello Netgear,
any update? - I can't speak for the actual problem as I have not seen it myself, but, hopefully this will help point you in the right direction.
The message "vmhba34:C0:T2:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0" indicates that there was a Check Condition from the array (D:0x2), aborted command (0xb) indicating an invalid field in the Command Descriptor Block -- http://en.wikipedia.org/wiki/SCSI_CDB (0x24 0x0).
More resources for decoding SCSI messages can be found here: http://kb.vmware.com/kb/1030381
Also, you might want to have a look at the vmkernel logs during/shortly after a rescan to see if there are any other useful messages.
Cheers! - Any updates? It's getting me frustrated...
Want to play around with the new and nice stuff like vsphere and view 5!
Also willing to test a pre-beta or alpha version of 4.2.20! - I guess it's time to look for an alternative...
- True...
Probably the Jedi Consil is watching the new Star-Wars Blu-Rays instead of programming :wink:
Regards,
pain2k - hey is there a 3D version in Blu-Ray? :)
... Working on it and will keep you posted as soon as possible. - Tried the beta firmware? viewtopic.php?f=51&t=57193
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
