topic Re: ESXi 7.0.3 VMFS-6 Unable to mount datastore ( JBC inconsistency errors ) in VMware vSphere™ Discussions

topic Re: ESXi 7.0.3 VMFS-6 Unable to mount datastore ( JBC inconsistency errors ) in VMware vSphere™ Discussions https://communities.vmware.com/t5/VMware-vSphere-Discussions/ESXi-7-0-3-VMFS-6-Unable-to-mount-datastore-JBC-inconsistency/m-p/2894593#M41720 <P>I resolved this by booting the ESXi server off a Linux Live CD and used vmfs6-tools to mount the filesystem and copy the required data, luckily retaining 100%.</P><P>Turns out issue was due to a faulty SSD drive and not VMWare. Still it is not helpful to be unable to mount and access the VMFS6 data without having to boot an alternative operating system.</P><P> </P> Mon, 21 Feb 2022 14:20:16 GMT WhiteSea 2022-02-21T14:20:16Z ESXi 7.0.3 VMFS-6 Unable to mount datastore ( JBC inconsistency errors ) https://communities.vmware.com/t5/VMware-vSphere-Discussions/ESXi-7-0-3-VMFS-6-Unable-to-mount-datastore-JBC-inconsistency/m-p/2885972#M41204 <P>Hi,</P><P>I recently ( and unfortunately ) upgraded my ESXi server to 7.0.3 ... which was then pulled. Having upgraded I have been experiencing random crashes of the ESXi server. This looks to have caused a corruption in one of my VMFS-6 datastores. A voma check lists a number of lock issues but ultimately I think the 4 JBC inconsistency errors shown are the reason for the filesystem not mounting</P><P> </P><P><SPAN>Running VMFS Checker version 2.1 in check mode<SPAN class="">               </SPAN></SPAN></P><P><SPAN>Initializing LVM metadata, Basic Checks will be done<SPAN class="">         </SPAN></SPAN></P><P><SPAN><SPAN class="">                                                             </SPAN></SPAN></P><P><SPAN>Checking for filesystem activity</SPAN></P><P><SPAN>Performing filesystem liveness check..|Scanning for VMFS-6 host activity (4096 bytes/HB, 1024 HBs).</SPAN></P><P><SPAN><SPAN class="">         </SPAN>Scsi 2 reservation successful<SPAN class="">                       </SPAN></SPAN></P><P><SPAN>Phase 1: Checking VMFS header and resource files<SPAN class="">             </SPAN></SPAN></P><P><SPAN><SPAN class="">   </SPAN>Detected VMFS-6 file system (labeled:'VMFS-2TBa') with UUID:60568465-a8e23e74-8eca-a0369fcfbc38, Version 6:82</SPAN></P><P><SPAN><SPAN class="">   </SPAN>Found stale lock [type 10c00002 offset 11698176 v 234, hb offset 4096000</SPAN></P><P><SPAN>gen 161, mode 1, owner 61aa6e60-dc12f1be-594b-a0369fcfbc38 mtime 8353</SPAN></P><P><SPAN>num 0 gblnum 0 gblgen 0 gblbrk 0]</SPAN></P><P><SPAN><SPAN class="">   </SPAN>Found stale lock [type 10c00002 offset 15794176 v 64, hb offset 4096000</SPAN></P><P><SPAN>gen 211, mode 1, owner 61cf03d5-bdd708c1-ccb3-a0369fcfbc38 mtime 5487</SPAN></P><P><SPAN>num 0 gblnum 0 gblgen 0 gblbrk 0]</SPAN></P><P><SPAN><SPAN class="">   </SPAN>Found stale lock [type 10c00002 offset 16080896 v 52, hb offset 4096000</SPAN></P><P><SPAN>gen 161, mode 1, owner 61aa6e60-dc12f1be-594b-a0369fcfbc38 mtime 8391</SPAN></P><P><SPAN>num 0 gblnum 0 gblgen 0 gblbrk 0]</SPAN></P><P><SPAN><SPAN class="">   </SPAN>Found stale lock [type 10c00002 offset 32776192 v 20, hb offset 4096000</SPAN></P><P><SPAN>gen 183, mode 1, owner 61b5ef88-5f9c65cf-dfd2-a0369fcfbc38 mtime 1076828</SPAN></P><P><SPAN>num 0 gblnum 0 gblgen 0 gblbrk 0]</SPAN></P><P><SPAN><SPAN class="">   </SPAN>Found stale lock [type 10c00007 offset 734175232 v 132, hb offset 4100096</SPAN></P><P><SPAN>gen 29, mode 1, owner 61cf2ee4-900f1726-6c59-a0369fcfbc38 mtime 91</SPAN></P><P><SPAN>num 0 gblnum 0 gblgen 0 gblbrk 0]</SPAN></P><P><SPAN>Phase 2: Checking VMFS heartbeat region <SPAN class="">                     </SPAN></SPAN></P><P><SPAN><SPAN class="">   </SPAN>Stale HB state with zero journal address <SPAN class="">                 </SPAN></SPAN></P><P><SPAN>Phase 3: Checking all file descriptors. <SPAN class="">                     </SPAN></SPAN></P><P><SPAN><SPAN class="">   </SPAN>Found stale lock [type 10c00001 offset 7577600 v 54, hb offset 4096000</SPAN></P><P><SPAN>gen 211, mode 1, owner 61cf03d5-bdd708c1-ccb3-a0369fcfbc38 mtime 4914</SPAN></P><P><SPAN>num 0 gblnum 0 gblgen 0 gblbrk 0]</SPAN></P><P><SPAN><SPAN class="">   </SPAN>Found stale lock [type 10c00001 offset 7593984 v 50, hb offset 4096000</SPAN></P><P><SPAN>gen 119, mode 2, owner 00000000-00000000-0000-000000000000 mtime 4908</SPAN></P><P><SPAN>num 1 gblnum 0 gblgen 0 gblbrk 0]</SPAN></P><P><SPAN><SPAN class="">   </SPAN>Found stale lock [type 10c00001 offset 7602176 v 513, hb offset 4096000</SPAN></P><P><SPAN>gen 211, mode 1, owner 61cf03d5-bdd708c1-ccb3-a0369fcfbc38 mtime 4842</SPAN></P><P><SPAN>num 0 gblnum 0 gblgen 0 gblbrk 0]</SPAN></P><P><SPAN>..</SPAN></P><P><SPAN>..</SPAN></P><P><SPAN>..</SPAN></P><P><SPAN>Phase 4: Checking pathname and connectivity.<SPAN class="">                 </SPAN></SPAN></P><P><SPAN>Phase 5: Checking resource reference counts.<SPAN class="">                 </SPAN></SPAN></P><P><SPAN><SPAN class=""> </SPAN>ON-DISK ERROR: JBC inconsistency found: (13,0) allocated in bitmap, but never used</SPAN></P><P><SPAN><SPAN class=""> </SPAN>ON-DISK ERROR: JBC inconsistency found: (13,1) allocated in bitmap, but never used</SPAN></P><P><SPAN><SPAN class=""> </SPAN>ON-DISK ERROR: JBC inconsistency found: (13,2) allocated in bitmap, but never used</SPAN></P><P><SPAN><SPAN class=""> </SPAN>ON-DISK ERROR: JBC inconsistency found: (13,3) allocated in bitmap, but never used</SPAN></P><P><SPAN><SPAN class="">                                                             </SPAN></SPAN></P><P><SPAN>Total Errors Found: <SPAN class="">          4</SPAN></SPAN></P><P>Does anyone know how to fix these errors. The "fix" option of voma does nothing. To say I am pissed at VMWare for this 7.0.3 release is an understatement.</P> Sat, 01 Jan 2022 14:34:45 GMT https://communities.vmware.com/t5/VMware-vSphere-Discussions/ESXi-7-0-3-VMFS-6-Unable-to-mount-datastore-JBC-inconsistency/m-p/2885972#M41204 WhiteSea 2022-01-01T14:34:45Z Re: ESXi 7.0.3 VMFS-6 Unable to mount datastore ( JBC inconsistency errors ) https://communities.vmware.com/t5/VMware-vSphere-Discussions/ESXi-7-0-3-VMFS-6-Unable-to-mount-datastore-JBC-inconsistency/m-p/2894590#M41719 <P>Hello!</P><P>If you are still having issues, checking the Knowledge Base might offer solutions. <BR />You can also find a list of known issues and existing workarounds. For example this one <A href="https://kb.vmware.com/s/article/86281" target="_blank">https://kb.vmware.com/s/article/86281</A></P><P>Have you been able to find a solution? </P> Mon, 21 Feb 2022 13:57:36 GMT https://communities.vmware.com/t5/VMware-vSphere-Discussions/ESXi-7-0-3-VMFS-6-Unable-to-mount-datastore-JBC-inconsistency/m-p/2894590#M41719 Marcela2 2022-02-21T13:57:36Z Re: ESXi 7.0.3 VMFS-6 Unable to mount datastore ( JBC inconsistency errors ) https://communities.vmware.com/t5/VMware-vSphere-Discussions/ESXi-7-0-3-VMFS-6-Unable-to-mount-datastore-JBC-inconsistency/m-p/2894593#M41720 <P>I resolved this by booting the ESXi server off a Linux Live CD and used vmfs6-tools to mount the filesystem and copy the required data, luckily retaining 100%.</P><P>Turns out issue was due to a faulty SSD drive and not VMWare. Still it is not helpful to be unable to mount and access the VMFS6 data without having to boot an alternative operating system.</P><P> </P> Mon, 21 Feb 2022 14:20:16 GMT https://communities.vmware.com/t5/VMware-vSphere-Discussions/ESXi-7-0-3-VMFS-6-Unable-to-mount-datastore-JBC-inconsistency/m-p/2894593#M41720 WhiteSea 2022-02-21T14:20:16Z