<?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: mount &amp;amp; kernal panic issue in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/mount-amp-kernal-panic-issue/m-p/4440210#M37054</link>
    <description>possible corruption on dm-0 config OR worst raid disk. if you are able to login via console or you have ilo to login remote console ,you can check /etc/fstab for dm-0 group , and seems normal you can try to comment out dm-0 group and boot system if it is able to start. Maybe you can locate the problem.</description>
    <pubDate>Thu, 18 Jun 2009 07:35:04 GMT</pubDate>
    <dc:creator>Hakki Aydin Ucar</dc:creator>
    <dc:date>2009-06-18T07:35:04Z</dc:date>
    <item>
      <title>mount &amp; kernal panic issue</title>
      <link>https://community.hpe.com/t5/operating-system-linux/mount-amp-kernal-panic-issue/m-p/4440208#M37052</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;This is HP itanium 64bit server, suddenly server is rebooted i got some messages like&lt;BR /&gt;mount error22&lt;BR /&gt;please find the attachment.  How to rectify it</description>
      <pubDate>Tue, 16 Jun 2009 07:26:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/mount-amp-kernal-panic-issue/m-p/4440208#M37052</guid>
      <dc:creator>muralikrishna</dc:creator>
      <dc:date>2009-06-16T07:26:02Z</dc:date>
    </item>
    <item>
      <title>Re: mount &amp; kernal panic issue</title>
      <link>https://community.hpe.com/t5/operating-system-linux/mount-amp-kernal-panic-issue/m-p/4440209#M37053</link>
      <description>Hi,&lt;BR /&gt;According to your screen shot what i can say is &lt;BR /&gt;1)your raid device md-0 doesn't have any valid ext file system.&lt;BR /&gt;2)This could mean that maybe md-0 device is curropted&lt;BR /&gt;3)due to /etc/fstab have entry for md-0 it tries to mount md-0 at the boot process but unable to comply with file system type on the /etc/fstab entry due to reason 1.&lt;BR /&gt;&lt;BR /&gt;Hope this is helpful &lt;BR /&gt;Good Luck....!</description>
      <pubDate>Thu, 18 Jun 2009 02:42:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/mount-amp-kernal-panic-issue/m-p/4440209#M37053</guid>
      <dc:creator>Nuwan Alwis</dc:creator>
      <dc:date>2009-06-18T02:42:14Z</dc:date>
    </item>
    <item>
      <title>Re: mount &amp; kernal panic issue</title>
      <link>https://community.hpe.com/t5/operating-system-linux/mount-amp-kernal-panic-issue/m-p/4440210#M37054</link>
      <description>possible corruption on dm-0 config OR worst raid disk. if you are able to login via console or you have ilo to login remote console ,you can check /etc/fstab for dm-0 group , and seems normal you can try to comment out dm-0 group and boot system if it is able to start. Maybe you can locate the problem.</description>
      <pubDate>Thu, 18 Jun 2009 07:35:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/mount-amp-kernal-panic-issue/m-p/4440210#M37054</guid>
      <dc:creator>Hakki Aydin Ucar</dc:creator>
      <dc:date>2009-06-18T07:35:04Z</dc:date>
    </item>
  </channel>
</rss>

