<?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: Kernel Panic in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/5091465#M49442</link>
    <description>Friends, &lt;BR /&gt;&lt;BR /&gt;I had to reinstall the OS because, my HDD was in a very bad shape. &lt;BR /&gt;&lt;BR /&gt;Thanks for that valuable solution, I think I had a chance to know more about Kernel Panic</description>
    <pubDate>Mon, 11 Feb 2008 10:30:19 GMT</pubDate>
    <dc:creator>Jees Joy</dc:creator>
    <dc:date>2008-02-11T10:30:19Z</dc:date>
    <item>
      <title>Kernel Panic</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/5091460#M49437</link>
      <description>Hi Friends, &lt;BR /&gt;&lt;BR /&gt;Please help me in this, I have RHEL ES1; today it crashed and now when it boots it is showing the following error:&lt;BR /&gt;&lt;BR /&gt;umount /inird/proc failed 2&lt;BR /&gt;Kernel Panic; no init found. Try passing init=option to kernel &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Please help me gurus</description>
      <pubDate>Thu, 07 Feb 2008 09:51:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/5091460#M49437</guid>
      <dc:creator>Jees Joy</dc:creator>
      <dc:date>2008-02-07T09:51:52Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel Panic</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/5091461#M49438</link>
      <description>That could be caused by several reasons. Cause this was a crash, the first thing to verify is the disk and file system integrity. As you cannot boot from disk, you should start from the CD rom in rescue mode, verify your disks and file systems.</description>
      <pubDate>Thu, 07 Feb 2008 12:35:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/5091461#M49438</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2008-02-07T12:35:04Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel Panic</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/5091462#M49439</link>
      <description>ES1?&lt;BR /&gt;&lt;BR /&gt;anyway, doesn't look good. try booting from the install cd and check if you can mount your filesystems on the disk.&lt;BR /&gt;&lt;BR /&gt;might need to do a fsck.</description>
      <pubDate>Fri, 08 Feb 2008 08:58:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/5091462#M49439</guid>
      <dc:creator>dirk dierickx</dc:creator>
      <dc:date>2008-02-08T08:58:23Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel Panic</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/5091463#M49440</link>
      <description>first suggetion..&lt;BR /&gt;&lt;BR /&gt;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;BR /&gt;&lt;BR /&gt;=================second one== I  have not tried this myself===&lt;BR /&gt;&lt;BR /&gt;Your system disk is no longer bootable.&lt;BR /&gt;&lt;BR /&gt;To fix that I have the following suggestions:&lt;BR /&gt;&lt;BR /&gt;use grub in rescue mode to try and re-establish boot capabilities.&lt;BR /&gt;&lt;BR /&gt;This procedure covers two disk mirroing but provides the basics.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;1. boot redhat cd 1&lt;BR /&gt;2. enter "linux rescue" at isolinux prompt&lt;BR /&gt;3. no networking, mount drives&lt;BR /&gt;4. at shell prompt, type "grub"&lt;BR /&gt;5. find /grub/stage1&lt;BR /&gt;6. root (hd0,0)&lt;BR /&gt;7. setup (hd0)&lt;BR /&gt;8. root (hd1,0)&lt;BR /&gt;9. root (hd1)&lt;BR /&gt;10. klingon deathgrip&lt;BR /&gt;&lt;BR /&gt;Otherwise back up data and configuration and reinstall the OS.&lt;BR /&gt;&lt;/BLOCK_SIZE&gt;</description>
      <pubDate>Fri, 08 Feb 2008 21:11:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/5091463#M49440</guid>
      <dc:creator>skt_skt</dc:creator>
      <dc:date>2008-02-08T21:11:15Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel Panic</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/5091464#M49441</link>
      <description>Thank you friends for that valuable advice; my disk was in a very bad situation to recover; so I had to reinstall it.</description>
      <pubDate>Mon, 11 Feb 2008 10:20:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/5091464#M49441</guid>
      <dc:creator>Jees Joy</dc:creator>
      <dc:date>2008-02-11T10:20:43Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel Panic</title>
      <link>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/5091465#M49442</link>
      <description>Friends, &lt;BR /&gt;&lt;BR /&gt;I had to reinstall the OS because, my HDD was in a very bad shape. &lt;BR /&gt;&lt;BR /&gt;Thanks for that valuable solution, I think I had a chance to know more about Kernel Panic</description>
      <pubDate>Mon, 11 Feb 2008 10:30:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/kernel-panic/m-p/5091465#M49442</guid>
      <dc:creator>Jees Joy</dc:creator>
      <dc:date>2008-02-11T10:30:19Z</dc:date>
    </item>
  </channel>
</rss>

