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
- possible. please open a case with reference to this forum thread and your logfiles.
- Hi,
Is there an open case for this error yet? If not I will open one. I opened one on the QNAP board yesterday and they have already reproduced it and are working on a fix.
Regards,
Darren - If beisser asks you to open a case I would guess that there is none yet. He should know if there was one already.
-Stefan - I did open a case and first they said it is a problem with esxi 5.0 and now they are asking for remote access!!! With their agreement to hold no liability for data loss and confidentiality I would never grant access! Moreover, they would be able to reproduce it easily in their labs.
- Yeah, oh well, Netgear sometimes seems to have a clumsy hand when handling some special problems that aren't covered by their standard textbook. Thanks for opening the case anyway, I'll try to reproduce the issue and give'em hell once I'm back in my office ;)
-Stefan yoicks wrote: I did open a case and first they said it is a problem with esxi 5.0 and now they are asking for remote access!!! With their agreement to hold no liability for data loss and confidentiality I would never grant access! Moreover, they would be able to reproduce it easily in their labs.
can you update your thread-title with the case-number?- Don't blame you.... It is trivial to reproduce. QNAP did it about 1 hour after I opened a case with them!
Take ReadyNAS (tons of those lying around) install ESXi connect using iSCSI bang.... - Hi,
I have not got an iSCSI NAS, nor an NFS one, I have a simple JBOD FC SAN which used to work with vSphere 4.1 and previous.
The reason I am posting is that I get the same errors as the OP in the vmkernel.log, but when trying to scan the HBA attached to the FC storage. The Adapter is recognised, but it just hangs in the vSphere Client and eventually times out after 30 mins or so with no devices found.
I have searched on these errors and the error seems to occuring on many 'low end' storage systems, not specific to NetGear, QNAP or others.... so I would suggest it is a 'BUG' with VMware.
I'm looking to see if I can wipe one of the 6 FC disks (I have all data backed up and running from the local SATA disks now as I thankfully took the precaution, but it is running slowly) and see if it is because of the format of VMFS 3.xx that is causing it, but I'm not convinced as local SATA drives were 3.46 too and they are fine.
Hoping for a fix from VMware and sorry to butt in, but felt it was relevant rather than everyone chasing their own errors with storage, when it may not be that simple to fix for the storage vendors.
MrPix - I have the same Problem with ESXi 5 and a 4200 iSCSI Box..
I thought Netgear is VMware Certified - so they should have been able to test the Beta version already wih their boxes...
A short warning would have saved my sunday - with downgrading my ESX 5 to 4.1....
pain2k - Not having access to VMware betas I don't know what really happened but VMware wouldn't be the first company to make some "minor" last minute changes to their software before release without shipping the code to beta testers for the changes are believed to be inconsequential. Seeing that there are so many problems with VMware and iSCSI (not only the one Netgear uses) I tend to think it was VMware who didn't do proper testing.
-Stefan
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
