VMware Cloud Community
rrobbemond
Contributor
Contributor

Datastore detected as snapshot LUN + naa identifieer mismatch

Hello Everyone,

im hoping someone is able to help to resolve my problem im having with my datastores on ESXi 5.1 server.

Server contains 2 RAID controllers,

1x 3Ware 9650 SE 4MPL

1x DELL PERC 5/I

after performing a firmware update of the motherboard the DELL PERC 5/I LUN's / Datastore's arent visible anymore on the ESXi server.

And being detected as snapshot LUN's

The NAA identifieer is changed, the queried identifieer doesnt match the on disk identiefieer and im unable to mount or access the VMFS datastores residing on the LUN's

i would like to regain access to the datastores and save my VMDK's that reside on there, without damaging the datastores.

vmkernel log:

2013-01-06T13:28:09.941Z cpu2:5034)LVM: 8315: Device naa.60019b90d9cb5f0017cc9f8d864308cd:1 detected to be a snapshot:

2013-01-06T13:28:09.941Z cpu2:5034)LVM: 8322:   queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 11681237247857246036>

2013-01-06T13:28:09.941Z cpu2:5034)LVM: 8329:   on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 13537078469181966595>

2013-01-06T13:28:09.945Z cpu3:4099)ScsiDeviceIO: 2316: Cmd(0x41240079bfc0) 0x1a, CmdSN 0x220c from world 0 to dev "naa.600050e0d071dd002b3b0000bd510000" failed H:0x0 D:0x4 P:0x0 Possible sense data: 0x5 0x24 0x0.

2013-01-06T13:28:09.948Z cpu2:5034)LVM: 8315: Device naa.60019b90d9cb5f0017cc9f8e8602e52e:1 detected to be a snapshot:

2013-01-06T13:28:09.948Z cpu2:5034)LVM: 8322:   queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 17086397103334917193>

2013-01-06T13:28:09.948Z cpu2:5034)LVM: 8329:   on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 5245099047533556241>

2013-01-06T13:28:09.948Z cpu3:4099)ScsiDeviceIO: 2316: Cmd(0x4124007d8a40) 0x1a, CmdSN 0x2216 from world 0 to dev "naa.600050e0d071dd002b3b0001c23f0000" failed H:0x0 D:0x4 P:0x0 Possible sense data: 0x5 0x24 0x0.

2013-01-06T13:28:09.949Z cpu2:5034)LVM: 8315: Device naa.60019b90d9cb5f0017cc9f8e86258827:1 detected to be a snapshot:

2013-01-06T13:28:09.949Z cpu2:5034)LVM: 8322:   queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 13503593553047812168>

2013-01-06T13:28:09.949Z cpu2:5034)LVM: 8329:   on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 16146105025413919460>

2013-01-06T13:28:09.973Z cpu0:5034)Vol3: 692: Couldn't read volume header from control: Not supported

2013-01-06T13:28:09.973Z cpu0:5034)Vol3: 692: Couldn't read volume header from control: Not supported

2013-01-06T13:28:09.973Z cpu0:5034)FSS: 4972: No FS driver claimed device 'control': Not supported

I would be very greatfull if someone is able to get this fixxed.

With friendly regards,

Peter

0 Kudos
4 Replies
a_p_
Leadership
Leadership

Take a look at http://kb.vmware.com/kb/1011387 for details about identifying a snapshot LUN and how to mount it again.

André

rrobbemond
Contributor
Contributor

Andre,

I resignatured 1 single LUN, after this the LUN will no longer show up as a Snapshot LUN.

The thing that is worrying me is the the disk identifieer that has changed.

there was a 4the LUN that is no longer visible anymore after assigning a new signature.

Im afraid that mounting the luns or resignaturing will make the other 3 LUNs below unavailble as well and no longer will show up as snapshot LUNs

2013-01-06T13:28:09.941Z cpu2:5034)LVM: 8322:   queried disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 11681237247857246036>

2013-01-06T13:28:09.941Z cpu2:5034)LVM: 8329:   on-disk disk ID: <type 2, len 22, lun 0, devType 0, scsi 0, h(id) 13537078469181966595>

if you look at the vmware post the queried disk ID and on-disk ID identifieers match.

LVM: 8452: queried disk ID: <type 1, len 17, lun 36, devType 0, scsi 0, h(id) 7683208289187576905>
LVM: 8459: on-disk disk ID: <type 1, len 17, lun 17, devType 0, scsi 0, h(id) 7683208289187576905>

# esxcli storage vmfs snapshot list

   Volume Name: RAID5 - LUN2

   VMFS UUID: 4d7940c8-30095ea2-637b-485b3931a146

   Can mount: true

   Reason for un-mountability:

   Can resignature: true

   Reason for non-resignaturability:

   Unresolved Extent Count: 1

4d794104-bc89b836-7ca9-485b3931a146

   Volume Name: RAID5 - LUN4

   VMFS UUID: 4d794104-bc89b836-7ca9-485b3931a146

   Can mount: true

   Reason for un-mountability:

   Can resignature: true

   Reason for non-resignaturability:

   Unresolved Extent Count: 1

4d7940e2-16e83486-ca9a-485b3931a146

   Volume Name: RAID5 - LUN3

   VMFS UUID: 4d7940e2-16e83486-ca9a-485b3931a146

   Can mount: true

   Reason for un-mountability:

   Can resignature: true

   Reason for non-resignaturability:

   Unresolved Extent Count: 1

Regards,

Peter

0 Kudos
memaad
Virtuoso
Virtuoso

Hi ,

Why dont you force mount datastore, it will not chance any UUID  datastore

esxcli storage vmfs snapshot mount -l  datastorename

Regards

Mohammed

Mohammed | Mark it as helpful or correct if my suggestion is useful.
0 Kudos
rrobbemond
Contributor
Contributor

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

0 Kudos