<?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: Server Booting Failed in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/server-booting-failed/m-p/4058517#M64820</link>
    <description>That sounds really bad. If your /usr is a different file system, is not mounting, maybe because a file system problem/corruption. You should run fsck.&lt;BR /&gt;&lt;BR /&gt;If you don't have a separate file system for /usr, then you should boot in emergency or rescue mode using the installation CD to verify your file systems and data.</description>
    <pubDate>Wed, 22 Aug 2007 08:59:47 GMT</pubDate>
    <dc:creator>Ivan Ferreira</dc:creator>
    <dc:date>2007-08-22T08:59:47Z</dc:date>
    <item>
      <title>Server Booting Failed</title>
      <link>https://community.hpe.com/t5/operating-system-linux/server-booting-failed/m-p/4058516#M64819</link>
      <description>My server boot failed and the boot message display interpreter "/bin/sh" not found&lt;BR /&gt;file link resolves to "/usr/bin/sh"&lt;BR /&gt;FAIL *&lt;BR /&gt;</description>
      <pubDate>Wed, 22 Aug 2007 08:44:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/server-booting-failed/m-p/4058516#M64819</guid>
      <dc:creator>Leandro Mainardi</dc:creator>
      <dc:date>2007-08-22T08:44:44Z</dc:date>
    </item>
    <item>
      <title>Re: Server Booting Failed</title>
      <link>https://community.hpe.com/t5/operating-system-linux/server-booting-failed/m-p/4058517#M64820</link>
      <description>That sounds really bad. If your /usr is a different file system, is not mounting, maybe because a file system problem/corruption. You should run fsck.&lt;BR /&gt;&lt;BR /&gt;If you don't have a separate file system for /usr, then you should boot in emergency or rescue mode using the installation CD to verify your file systems and data.</description>
      <pubDate>Wed, 22 Aug 2007 08:59:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/server-booting-failed/m-p/4058517#M64820</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2007-08-22T08:59:47Z</dc:date>
    </item>
    <item>
      <title>Re: Server Booting Failed</title>
      <link>https://community.hpe.com/t5/operating-system-linux/server-booting-failed/m-p/4058518#M64821</link>
      <description>1.Go to rescue mode using the RHEL installation CD with the boot option:&lt;BR /&gt;&lt;BR /&gt;linux rescue&lt;BR /&gt;&lt;BR /&gt;if vg00 not getting mounted automaically.&lt;BR /&gt;&lt;BR /&gt;2.Try to activate the volume groups by running the commands below:&lt;BR /&gt;&lt;BR /&gt;lvmdiskscan&lt;BR /&gt;vgchange -ay&lt;BR /&gt;&lt;BR /&gt;3.If vg00 is acitaved   Further fsck test can be done using:&lt;BR /&gt;&lt;BR /&gt;tune2fs -l /dev/vg00/lv01 | grep Block&lt;BR /&gt;&lt;BR /&gt;Take note of the Block size.&lt;BR /&gt;&lt;BR /&gt;e2fsck -b &lt;BLOCK_SIZE&gt; -n /dev/vg00/lv01&lt;BR /&gt;&lt;/BLOCK_SIZE&gt;</description>
      <pubDate>Wed, 22 Aug 2007 22:54:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/server-booting-failed/m-p/4058518#M64821</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2007-08-22T22:54:01Z</dc:date>
    </item>
  </channel>
</rss>

