VMFS Problem

kidboyadm · ‎12-20-2019

Hi, i have a vSphere 6.5, with 1 VM, after a crash in vm, i reboot the machine and after that my datastore dont show any more. Someone can help to restore vmfs partition ? There is the logs:

vmkernel:

2019-12-20T17:50:35.156Z cpu5:2097881)NMP: nmp_ThrottleLogForDevice:3802: Cmd 0x28 (0x459a40bcac00, 2098547) to dev "naa.5000c500b702bf3b" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Va

2019-12-20T17:50:35.156Z cpu5:2097881)ScsiDeviceIO: 3449: Cmd(0x459a40bcac00) 0x28, CmdSN 0x1 from world 2098547 to dev "naa.5000c500b702bf3b" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x3 0x1

2019-12-20T17:50:35.749Z cpu3:2097419)WARNING: NFS: 1227: Invalid volume UUID mpx.vmhba1:C0:T4:L0

2019-12-20T17:50:35.749Z cpu1:2097419)FSS: 6092: No FS driver claimed device 'mpx.vmhba1:C0:T4:L0': No filesystem on the device

2019-12-20T17:50:35.802Z cpu8:2097412)WARNING: NFS: 1227: Invalid volume UUID naa.5000c500b702bf3b:3

2019-12-20T17:50:35.820Z cpu8:2097412)FSS: 6092: No FS driver claimed device 'naa.5000c500b702bf3b:3': No filesystem on the device

______________________________________________________________________________________________________________________________________________

[root@vmware04:/dev/disks] fdisk -l /vmfs/devices/disks/naa.5000c500b702bf3b

*

* The fdisk command is deprecated: fdisk does not handle GPT partitions. Please use partedUtil

*

Found valid GPT with protective MBR; using GPT

Disk /vmfs/devices/disks/naa.5000c500b702bf3b: 1172123568 sectors, 2981M

Logical sector size: 512

Disk identifier (GUID): cb59f4eb-4a6a-4ff2-8a3b-e0a95a604c22

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 1172123534

Number Start (sector) End (sector) Size Name

1 64 8191 4064K

2 7086080 15472639 4095M

3 15472640 1170997214 550G

4 8224 520191 249M

5 520224 1032191 249M

6 1032224 1257471 109M

7 1257504 1843199 285M

8 1843200 7086079 2560M

___________________________________________________________________________________________________________________________

[root@vmware04:/dev/disks] partedUtil getptbl /vmfs/devices/disks/naa.5000c500b702bf3b

gpt

72961 255 63 1172123568

1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128

4 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

5 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

6 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0

7 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

8 1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0

2 7086080 15472639 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

3 15472640 1170997214 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

________________________________________________________________________________________________________________________

Mount Point Volume Name UUID Mounted Type Size Free

------------------------------------------------- ----------- ----------------------------------- ------- ---- ---------- ----------

/vmfs/volumes/d764097a-908b92d4-180b-7d7633d7d443 d764097a-908b92d4-180b-7d7633d7d443 true vfat 261853184 106246144

/vmfs/volumes/5da1138f-8c37d4c0-f8a6-842b2b688783 5da1138f-8c37d4c0-f8a6-842b2b688783 true vfat 4293591040 4273799168

/vmfs/volumes/6132ef79-569f72e4-1515-4428b45bee3e 6132ef79-569f72e4-1515-4428b45bee3e true vfat 261853184 261840896

/vmfs/volumes/5da11380-395afa60-2963-842b2b688783 5da11380-395afa60-2963-842b2b688783 true vfat 299712512 117432320

___________________________________________________________________________________________________________________________

[root@vmware04:/dev/disks] esxcli storage core device smart get -d naa.5000c500b702bf3b

Parameter Value Threshold Worst

---------------------------- ----------------- --------- -----

Health Status IMPENDING FAILURE N/A N/A

Media Wearout Indicator N/A N/A N/A

Write Error Count 1228 N/A N/A

Read Error Count 20226778 N/A N/A

Power-on Hours N/A N/A N/A

Power Cycle Count N/A N/A N/A

Reallocated Sector Count N/A N/A N/A

Raw Read Error Rate N/A N/A N/A

Drive Temperature 46 N/A N/A

Driver Rated Max Temperature N/A N/A N/A

Write Sectors TOT Count N/A N/A N/A

Read Sectors TOT Count N/A N/A N/A

Initial Bad Block Count N/A N/A N/A

kidboyadm · ‎12-20-2019

I try this and i recive this error:

Running VMFS Checker version 2.1 in default mode

Initializing LVM metadata, Basic Checks will be done

ERROR: IO failed: Input/output error

Initializing LVM metadata..|

LVM magic not found at expected Offset,

It might take long time to search in rest of the disk.

VMware ESX Question:

Do you want to continue (Y/N)?

0) _Yes

1) _No

Select a number from 0-1: 0

ERROR: IO failed: Input/output error

ERROR: Failed to Initialize LVM Metadata

VOMA failed to check device : IO error

Total Errors Found: 0

Kindly Consult VMware Support for further assistance

scott28tt · ‎12-20-2019

Moderator: Moved to vSphere Storage

-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog

kidboyadm · ‎12-21-2019

The disk mounted as read only, i tri write somethin in vmfs and i recive this erros. There is some kind of fsck in vmware console ?

NathanosBlightc · ‎12-23-2019

If you really ensure about the Read-Only VMFS datastore, please look at this thread in the community

Please mark my comment as the Correct Answer if this solution resolved your problem

continuum · ‎12-23-2019

Hi

please read Create a VMFS-Header-dump using an ESXi-Host in production | VM-Sickbay

and create a headerdump as explained - O may be able to help/

I can deal with I/O errors

Ulli

________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

All

VMFS Problem