Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all articles
Browse latest Browse all 182126

Trouble in VMFS-unknown version on ESXi 6.5 but it still can be accessed and reached out is vmfs6 by using recovery software

$
0
0

After i reinstall the ESXi , and my SSD can't load the filesystem to vmfs6 ,then i have made a lot of research to repair the filesystem to vmfs6 , but there are need to pay a huge money for a key.Also, i have already tested and passed by voma with 0 error , So , does anyone can help me to repair the filesystem to give me to access the files because i have a lot of important data on a single VM.

 

REPORT 1:

[root@server:~] df -h

          Filesystem   Size   Used Available Use% Mounted on

VMFS-unknown version   0.0B   0.0B      0.0B   0% /vmfs/volumes/SSD 128G

vfat                 249.7M   8.0K    249.7M   0% /vmfs/volumes/238e93e3-dfb17682-5562-ef490f6ff7d6

vfat                 249.7M 143.6M    106.1M  58% /vmfs/volumes/bd4b17e7-3f022a3f-d65c-938d21b31e31

vfat                 285.8M 205.8M     80.0M  72% /vmfs/volumes/495c2082-1ded4d5a-d9f4-74d4356b4eb2

 

REPORT 2(VOMA):

[root@server:/vmfs/volumes] voma -m vmfs -d /vmfs/devices/disks/naa.5707c181005a45cc

Checking if device is actively used by other hosts       

Running VMFS Checker version 2.1 in default mode         

Initializing LVM metadata, Basic Checks will be done     

Phase 1: Checking VMFS header and resource files         

   Detected VMFS-6 file system (labeled:'SSD 128G') with UUID:5aa2a8e4-6d0f985e-f0ef-74d4356b4eb2, Version 6:81

   Found stale lock [type 10c00002 offset 9756672 v 58, hb offset 3637248

gen 127, mode 1, owner 5aa5469e-265dc7e2-b24d-74d4356b4eb2 mtime 524426

num 0 gblnum 0 gblgen 0 gblbrk 0]

Phase 2: Checking VMFS heartbeat region                  

Marking Journal addr (5, 0) in use                       

Phase 3: Checking all file descriptors.                  

   Found stale lock [type 10c00001 offset 34799616 v 172, hb offset 3637248

gen 127, mode 1, owner 5aa5469e-265dc7e2-b24d-74d4356b4eb2 mtime 2719

num 0 gblnum 0 gblgen 0 gblbrk 0]

   Found stale lock [type 10c00001 offset 34807808 v 42, hb offset 3637248

gen 127, mode 1, owner 5aa5469e-265dc7e2-b24d-74d4356b4eb2 mtime 2777

num 0 gblnum 0 gblgen 0 gblbrk 0]

   Found stale lock [type 10c00001 offset 34873344 v 38, hb offset 3637248

gen 127, mode 1, owner 5aa5469e-265dc7e2-b24d-74d4356b4eb2 mtime 2788

num 0 gblnum 0 gblgen 0 gblbrk 0]

   Found stale lock [type 10c00001 offset 34996224 v 48, hb offset 3637248

gen 111, mode 1, owner 5aa54177-0ea4b366-0f31-74d4356b4eb2 mtime 295

num 0 gblnum 0 gblgen 0 gblbrk 0]

   Found stale lock [type 10c00001 offset 35086336 v 67, hb offset 3637248

gen 127, mode 1, owner 5aa5469e-265dc7e2-b24d-74d4356b4eb2 mtime 2706

num 0 gblnum 0 gblgen 0 gblbrk 0]

   Found stale lock [type 10c00001 offset 35094528 v 68, hb offset 3637248

gen 127, mode 1, owner 5aa5469e-265dc7e2-b24d-74d4356b4eb2 mtime 2717

num 0 gblnum 0 gblgen 0 gblbrk 0]

   Found stale lock [type 10c00001 offset 35102720 v 69, hb offset 3637248

gen 127, mode 1, owner 5aa5469e-265dc7e2-b24d-74d4356b4eb2 mtime 2729

num 0 gblnum 0 gblgen 0 gblbrk 0]

   Found stale lock [type 10c00001 offset 35110912 v 70, hb offset 3637248

gen 127, mode 1, owner 5aa5469e-265dc7e2-b24d-74d4356b4eb2 mtime 2754

num 0 gblnum 0 gblgen 0 gblbrk 0]

   Found stale lock [type 10c00001 offset 35119104 v 71, hb offset 3637248

gen 127, mode 1, owner 5aa5469e-265dc7e2-b24d-74d4356b4eb2 mtime 2764

num 0 gblnum 0 gblgen 0 gblbrk 0]

Phase 4: Checking pathname and connectivity.             

Phase 5: Checking resource reference counts.             

                                                         

Total Errors Found:           0


Viewing all articles
Browse latest Browse all 182126

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>