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...
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 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
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
