Vmware 4.0esxi cannot connect to datastore on iscsi device

[willgc2000]

Hi, we restarted our Vmware ESXi 4.0 server today and after the reboot we cannot see the datastore which is located on an iscsi device.

On the vSphere client you can see the iscsi device within "Storage Adaptors" but you cannot see the datastore within "Storage"

I have tried to rescan etc.... But cant seem to get it back.

Any ideas?

 

[mrdenny]

What kind of storage is it?

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

 

[willgc2000]

Hi, its an Iomega Storcenter ix4-200d. I have done some more diggin around and have found the following errors in the /var/log/messages file.....

Jan 25 09:08:48 Hostd: [2011-01-25 09:08:48.749 177E6B90 verbose 'FSVolumeProvider'] RescanVmfs called
Jan 25 09:08:48 vmkernel: 0:17:55:38.288 cpu9:8153)Vol3: 1488: Could not open device 'naa.600508b1001052395359574746470000:6' for probing: Permission denied
Jan 25 09:08:48 vmkernel: 0:17:55:38.288 cpu9:8153)Vol3: 608: Could not open device 'naa.600508b1001052395359574746470000:6' for volume open: Permission denied
Jan 25 09:08:48 vmkernel: 0:17:55:38.292 cpu9:8153)Vol3: 1488: Could not open device 'naa.600508b1001052395359574746470000:2' for probing: Permission denied
Jan 25 09:08:48 vmkernel: 0:17:55:38.292 cpu9:8153)Vol3: 608: Could not open device 'naa.600508b1001052395359574746470000:2' for volume open: Permission denied
Jan 25 09:08:48 vmkernel: 0:17:55:38.293 cpu9:8153)FSS: 3702: No FS driver claimed device 'naa.600508b1001052395359574746470000:2': Not supported
Jan 25 09:08:48 vmkernel: 0:17:55:38.293 cpu9:8153)Vol3: 1488: Could not open device 'naa.600508b1001052395359574746470000:5' for probing: Permission denied
Jan 25 09:08:48 vmkernel: 0:17:55:38.294 cpu9:8153)Vol3: 608: Could not open device 'naa.600508b1001052395359574746470000:5' for volume open: Permission denied
Jan 25 09:08:48 vmkernel: 0:17:55:38.297 cpu9:8153)Vol3: 1488: Could not open device 'naa.600508b1001052395359574746470000:8' for probing: Permission denied
Jan 25 09:08:48 vmkernel: 0:17:55:38.297 cpu9:8153)Vol3: 608: Could not open device 'naa.600508b1001052395359574746470000:8' for volume open: Permission denied
Jan 25 09:08:48 Hostd: [2011-01-25 09:08:48.775 2D233B90 verbose 'Hostsvc:atastoreSystem'] VmfsUpdate: got VMFS message [N11HostdCommon18VmkernelUpdateVmfsE:0xf5be5a0] timestamp=1295946528775762 specific=0 name= label=
Jan 25 09:08:48 Hostd: [2011-01-25 09:08:48.837 177E6B90 verbose 'FSVolumeProvider'] RefreshVMFSVolumes: refreshed volume, id 4a6da393-781c6277-133e-78e7d1e13754, name datastore1
Jan 25 09:08:48 Hostd: [2011-01-25 09:08:48.837 177E6B90 verbose 'Hostsvc:atastore'] SetVolume: Datastore 4a6da393-781c6277-133e-78e7d1e13754 has changed provider volume pointer
Jan 25 09:08:48 Hostd: [2011-01-25 09:08:48.837 177E6B90 verbose 'Hostsvc:atastoreSystem'] ReconcileVMFSDatastores: Done discovering new filesystem volumes.
Jan 25 09:08:48 Hostd: [2011-01-25 09:08:48.837 177E6B90 info 'TaskManager'] Task Completed : haTask-ha-host-vim.host.StorageSystem.rescanVmfs-356 Status success

I have also run some fdisk commands to try and fix as other threads have suggested.

 

[mrdenny]

The answer is right there in the log.

"Could not open device 'naa.600508b1001052395359574746470000:8' for volume open: Permission denied". You need to check the rights on the array and ensure that you have rights to the LUNs. You should also make sure that the rights on the devices are correct. One of them is screwed up.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog