<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: vCenter Appliance cannot boot due to bad superblock in VMware vCenter™ Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Appliance-cannot-boot-due-to-bad-superblock/m-p/496948#M7359</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Run # journalctl which will give you corrupt volume.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then issue the command # fsck -fyv &amp;lt;volume&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;usually, the volume would be /dev/sda3 or /dev/log_vg/log&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FYI, /dev/sda2 is swap volume.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 05 Aug 2018 00:53:18 GMT</pubDate>
    <dc:creator>Vijay2027</dc:creator>
    <dc:date>2018-08-05T00:53:18Z</dc:date>
    <item>
      <title>vCenter Appliance cannot boot due to bad superblock</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Appliance-cannot-boot-due-to-bad-superblock/m-p/496946#M7357</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Came in this morning and our testlab was down, it's on 6.5. It would respond to ping, but the web client was down. I logged into vcenter directly through the address on the esxi splash page. I found the appliance on this page:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="1.JPG"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/69868i0C6C03E61158FBF6/image-size/large?v=v2&amp;amp;px=999" role="button" title="1.JPG" alt="1.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Googling the error I came across this KB : &lt;A href="https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2081464" title="https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2081464"&gt;"fsck failed" error when starting vCenter Server Appliance (2081464) | VMware KB&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I run the commands they suggest I get the following: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="2.JPG"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/69869i95D00CF09F4F4703/image-size/large?v=v2&amp;amp;px=999" role="button" title="2.JPG" alt="2.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;So I called my Linux guy over and he had me run some commands, giving me the following output: &lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="3.JPG"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/69870i9CB5EF2FA7276981/image-size/large?v=v2&amp;amp;px=999" role="button" title="3.JPG" alt="3.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;He's saying it looks like we should have 4 sda drives from the look of ls /dev/ but that only 3 are showing up when he specifically lists them. Talking to the Storage team, I found out that the Equalogic that the Appliance is on threw some errors last night and had it's issues, but that it recovered fine. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So what I'm hearing from Linux and Storage is that this is basically a perfect storm of errors and I'll need to rebuild (No backups in the Testlab, obviously) from scratch. I was hoping you fine people would have some brilliant ideas/insights to save me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Jan 2017 15:53:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Appliance-cannot-boot-due-to-bad-superblock/m-p/496946#M7357</guid>
      <dc:creator>vmware12</dc:creator>
      <dc:date>2017-01-10T15:53:05Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter Appliance cannot boot due to bad superblock</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Appliance-cannot-boot-due-to-bad-superblock/m-p/496947#M7358</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The symptoms that are displayed are outlined in &lt;A href="https://kb.vmware.com/s/article/2149838"&gt;KB2149838&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you run through the KB, pay attention to the startup messages and if there are any other issues, such as "cannot manually run 'fsck /dev/log_vg/log'," make note.&lt;/P&gt;&lt;P&gt;:# e2fsck -y /dev/log_vg/log &lt;/P&gt;&lt;P&gt;:# reboot&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This should resolve your issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 04 Aug 2018 03:14:07 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Appliance-cannot-boot-due-to-bad-superblock/m-p/496947#M7358</guid>
      <dc:creator>mikelacroix</dc:creator>
      <dc:date>2018-08-04T03:14:07Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter Appliance cannot boot due to bad superblock</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Appliance-cannot-boot-due-to-bad-superblock/m-p/496948#M7359</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Run # journalctl which will give you corrupt volume.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then issue the command # fsck -fyv &amp;lt;volume&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;usually, the volume would be /dev/sda3 or /dev/log_vg/log&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FYI, /dev/sda2 is swap volume.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 05 Aug 2018 00:53:18 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Appliance-cannot-boot-due-to-bad-superblock/m-p/496948#M7359</guid>
      <dc:creator>Vijay2027</dc:creator>
      <dc:date>2018-08-05T00:53:18Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter Appliance cannot boot due to bad superblock</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Appliance-cannot-boot-due-to-bad-superblock/m-p/496949#M7360</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;were you able to fix this??&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Aug 2018 08:42:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Appliance-cannot-boot-due-to-bad-superblock/m-p/496949#M7360</guid>
      <dc:creator>Vijay2027</dc:creator>
      <dc:date>2018-08-08T08:42:50Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter Appliance cannot boot due to bad superblock</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Appliance-cannot-boot-due-to-bad-superblock/m-p/496950#M7361</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This most likely isn't an issue anymore. It was posted ~1 year ago but I figured I'd give an answer regardless of whether it's still relevant. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Aug 2018 09:48:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Appliance-cannot-boot-due-to-bad-superblock/m-p/496950#M7361</guid>
      <dc:creator>mikelacroix</dc:creator>
      <dc:date>2018-08-08T09:48:15Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter Appliance cannot boot due to bad superblock</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Appliance-cannot-boot-due-to-bad-superblock/m-p/2925296#M46201</link>
      <description>&lt;P&gt;I faced the same issue today, and googling this page helped me alot,&amp;nbsp;&lt;/P&gt;&lt;P&gt;i first try to run e2fsck /dev/sda1&amp;nbsp; this gives me no error&lt;/P&gt;&lt;P&gt;then i try to run e2fsck /dev/sda2 this shows me bad super block but i was unable to fix it&lt;/P&gt;&lt;P&gt;then i run e2fsck -y /dev/sda2 nothing happen&lt;/P&gt;&lt;P&gt;by running journalctl command and scrolling till last i found that /dev/sda3 is corrupted,&amp;nbsp;&lt;/P&gt;&lt;P&gt;e2fsck -y /dev/sda3&amp;nbsp;&lt;/P&gt;&lt;P&gt;this command fixed my issue&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 23 Aug 2022 09:57:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Appliance-cannot-boot-due-to-bad-superblock/m-p/2925296#M46201</guid>
      <dc:creator>AbdulBasitKhan</dc:creator>
      <dc:date>2022-08-23T09:57:19Z</dc:date>
    </item>
  </channel>
</rss>

