Hi Mohammed,
Force mounting doesnt work.
See message below
im suspecting this is due to the identifieer mismatch
/var/log # esxcli storage vmfs snapshot mount -l "RAID5 - LUN4"
Sysinfo error on operation returned status : Not supported. Please see the VMkernel log for detailed error information\
vmkernel.log
2013-01-24T15:35:03.672Z cpu2:4960)Res3: 1024: Inconsistency detected R/C 0, C/G 0, CG offset 0, CG size 0, totalR 0 #CGs 0
2013-01-24T15:35:03.677Z cpu6:4960)FSS: 4972: No FS driver claimed device '4d794102-84a76a63-48ba-485b3931a146': Not supported
2013-01-24T15:35:03.677Z cpu6:4960)LVM: 11802: Failed to mount 4d794102-84a76a63-48ba-485b3931a146 (now umounting): Not supported
2013-01-24T15:35:03.679Z cpu7:856447)NMP: nmp_ThrottleLogForDevice:2319: Cmd 0x1a (0x4124007b82c0, 0) to dev "naa.600050e0d071dd002b3b00013f0000" on path "vmhba4:C0:T0:L1" Failed: H:0x0 D:0x4 P:0x0 Possible sense data: 0x5 0x24 0x0. Act:NONE
2013-01-24T15:35:03.679Z cpu7:856447)ScsiDeviceIO: 2316: Cmd(0x4124007b82c0) 0x1a, CmdSN 0xf126 from world 0 to dev "naa.600050e0d071dd002b0001c23f0000" failed H:0x0 D:0x4 P:0x0 Possible sense data: 0x5 0x24 0x0.
2013-01-24T15:35:03.692Z cpu7:168855)NMP: nmp_ThrottleLogForDevice:2319: Cmd 0x1a (0x4124007b82c0, 0) to dev "naa.600050e0d071dd002b3b0000510000" on path "vmhba4:C0:T0:L0" Failed: H:0x0 D:0x4 P:0x0 Possible sense data: 0x5 0x24 0x0. Act:NONE
2013-01-24T15:35:03.692Z cpu7:168855)ScsiDeviceIO: 2316: Cmd(0x4124007b82c0) 0x1a, CmdSN 0xf132 from world 0 to dev "naa.600050e0d071dd002b0000bd510000" failed H:0x0 D:0x4 P:0x0 Possible sense data: 0x5 0x24 0x0.
2013-01-24T15:35:03.703Z cpu6:5022)LVM: 8315: Device naa.60019b90d9cb5f0017cc9f8d864308cd:1 detected to be a snapshot:
2013-01-24T15:35:03.703Z cpu6:5022)LVM: 8322: queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 11681237247857246036>
2013-01-24T15:35:03.703Z cpu6:5022)LVM: 8329: on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 13537078469181966595>
2013-01-24T15:35:03.709Z cpu2:168854)ScsiDeviceIO: 2316: Cmd(0x412400776980) 0x1a, CmdSN 0xf158 from world 0 to dev "naa.600050e0d071dd002b0001c23f0000" failed H:0x0 D:0x4 P:0x0 Possible sense data: 0x5 0x24 0x0.
2013-01-24T15:35:03.722Z cpu6:5022)LVM: 8315: Device naa.60019b90d9cb5f0017cc9f8e8602e52e:1 detected to be a snapshot:
2013-01-24T15:35:03.722Z cpu6:5022)LVM: 8322: queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 17086397103334917193>
2013-01-24T15:35:03.722Z cpu6:5022)LVM: 8329: on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 5245099047533556241>
2013-01-24T15:35:03.722Z cpu6:5022)LVM: 8315: Device naa.60019b90d9cb5f0017cc9f8e86258827:1 detected to be a snapshot:
2013-01-24T15:35:03.722Z cpu6:5022)LVM: 8322: queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 13503593553047812168>
2013-01-24T15:35:03.722Z cpu6:5022)LVM: 8329: on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 16146105025413919460>
2013-01-24T15:35:03.723Z cpu2:168863)ScsiDeviceIO: 2316: Cmd(0x41240078cac0) 0x1a, CmdSN 0xf164 from world 0 to dev "naa.600050e0d071dd002b0000bd510000" failed H:0x0 D:0x4 P:0x0 Possible sense data: 0x5 0x24 0x0.
2013-01-24T15:35:03.782Z cpu6:5022)Vol3: 692: Couldn't read volume header from control: Not supported
2013-01-24T15:35:03.782Z cpu6:5022)Vol3: 692: Couldn't read volume header from control: Not supported
2013-01-24T15:35:03.782Z cpu6:5022)FSS: 4972: No FS driver claimed device 'control': Not supported
2013-01-24T15:35:03.827Z cpu6:5022)VC: 1547: Device rescan time 62 msec (total number of devices 7)
2013-01-24T15:35:03.827Z cpu6:5022)VC: 1550: Filesystem probe time 57 msec (devices probed 5 of 7)
Regards,
Peter