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
chirpa wrote: Tried the beta firmware? http://www.readynas.com/forum/viewtopic.php?f=51&t=57193
So far everything is working with new firmware... did some vmotion and created a new Virtual with no problems.
Thank you!!! :neener:- Same here for me! Did some VMotion, Backup, etc.. everything is working so far.. =)
thx
pain2k - Hey folks. I ran into this on my ESXi 5 box and quickly noticed it was for a SCSI 0x93 command. That's a write_same, which is not quite a command used often for regular VM operation. It's being attempted while either testing VAAI primitives (and repeatedly failing), and/or it's an issue with ESX/ESXi attempting to run array-accelerated commands. I can't really be bothered to drill down into it, but I think it's the former.
You'd run into this usually for your first foray into VM creation, migration, disk creation, etc. on the respective iSCSI LUN, I expect.
Anyway, long story short, disable VAAI (all three accelerated functions!) per the following KB article (http://kb.vmware.com/kb/1033665), try the operation again, and you're good to go.
If you're in a stuck loop with it flooding in your vmkernel logs already, do the nasty and disable iSCSI access via your ReadyNAS for at least five seconds (must result in I/O timeout + retry cycle on ESX), then enable it again.
Edit: I ran into this and got it working normally again, all on the latest release-level firmware, 4.2.19
Edit2: Here's a breakdown for anyone curious.
vmkernel.log from ESXi 5.0:
2011-11-16T03:12:07.518Z cpu3:2051)ScsiDeviceIO: 2305: Cmd(0x4124007ad0c0) 0x93, CmdSN 0x117 to dev "naa.60014052e2150400469d001000000000" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0.
2011-11-16T03:12:07.523Z cpu3:2051)ScsiDeviceIO: 2305: Cmd(0x4124007ad0c0) 0x93, CmdSN 0x117 to dev "naa.60014052e2150400469d001000000000" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0.
2011-11-16T03:12:07.528Z cpu3:2051)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x93 (0x4124007ad0c0) to dev "naa.60014052e2150400469d001000000000" on path "vmhba38:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0xb 0x24 0x0.Act:NONE
1) Note the bolded command type, 0x93.
2) Note the Sense Data provided: H:0x0 D:0x2 P:0x0, where D:0x2 means the device/bus was busy (not very helpful yet. But do understand that this will result in ESX retrying this I/O).
3) Note the valid additional sense data/qualifier/key (as opposed to "possible" sense data, which is not necessarily actually received/provided from an array). It says, 0xb 0x24 0x0. You'd need some reference material to figure out what this means. And I don't have it, as I'm not at work.
Looking at Biesser's logs (I don't have SSH enabled on my ReadyNAS yet), I am unsurprised and it all fits together in my head:beisser wrote: 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
- Write same command confirmed.
- unmap / block discard emulation isn't something I have spent time researching, but I presume it's unrelated to VAAI but the two are trying to mingle. So - disable VAAI and we're not going to see ESX/ESXi attempt write_same commands. - Hi, just got aware of that bug, I did read everything, got the link for the beta radiator.... but still, I have a question :
that bug was resolve apparently in september, how much time netgear take to compile an official radiator ?
we still have the 4.2.19 on netgear site.
cheers. - until the final 4.2.20 firmware is released you need to use the current beta if you want to use esxi5. no way around that except if you like to wait :)
- Do we have any ideas when the final 4.2.20 firmware will be released? I am nervous at the thought of running beta firmware in production!
Thanks - 4.2.20 will be released when it's ready to be.
- Watch the website closely over the next week for the 4.2.20 release, as well as the VMware HCL posting for NFS.
- vSphere 5 cert is posted on the VMware HCL now. Sample of 4200 with NFS on vSphere 5:
http://partnerweb.vmware.com/comp_guide ... 0&vcl=true
iSCSI has passed and is with VMware for listing, watch their site.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
