<?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: Upgrade kernel in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/upgrade-kernel/m-p/3638985#M19876</link>
    <description>Your insmod may need updating (the one used by initrd). As you can see, it was unable to load even the first module necessary to eventually access your root file-system.&lt;BR /&gt;&lt;BR /&gt;The new kernel has QUERY_MODULES removed (don't ask why, normally there would be some kind of compatibility-overlap). So, your&lt;BR /&gt;older `insmod` or `insmod.static` is trying to use the old-method of loading modules.&lt;BR /&gt;&lt;BR /&gt;You may not be able to recover easily. I found that I needed to rebuild the kernel with the necessary SCSI drivers in the&lt;BR /&gt;kernel. This would allow me to boot and mount a root file-system.&lt;BR /&gt;&lt;BR /&gt;Save the previous kernel ".config" file. You must rebuild with the 'loop' device in the kernel as well (or else you can't make a new initrd RAM disk).&lt;BR /&gt;&lt;BR /&gt;Then you can install the new modutils package.&lt;BR /&gt;&lt;BR /&gt;Then you can change back to the previous configuration with `make clean ; make oldconfig`....etc. Rebuild the kernel,&lt;BR /&gt;install and boot happy.&lt;BR /&gt;</description>
    <pubDate>Fri, 30 Sep 2005 07:06:52 GMT</pubDate>
    <dc:creator>Mugilvannan</dc:creator>
    <dc:date>2005-09-30T07:06:52Z</dc:date>
    <item>
      <title>Upgrade kernel</title>
      <link>https://community.hpe.com/t5/operating-system-linux/upgrade-kernel/m-p/3638984#M19875</link>
      <description>I hv just upgrade the RH 3 kernel by installing the kernel-xxx binary file , but when reboot to the new kernel , it pop the below messages , it is strange that it is normal when i doing the same thing to another server ( of course they are different hardware ) , could suggest what is the problem ? thx &lt;BR /&gt;&lt;BR /&gt;Error : /bin/insmod exited abnormally&lt;BR /&gt;loading aaraid.o module&lt;BR /&gt;&lt;BR /&gt;Redhat/Adaptec aaraid driver&lt;BR /&gt;/lib/aacraid.o: init_module:&lt;BR /&gt;hint : insmod errors can be caused by incorrect module parameter including invaild io or irq parameters .&lt;BR /&gt;&lt;BR /&gt;loading aic7xxx.o module&lt;BR /&gt;/lib/aic8xxx.o init_module:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;jdb.o module&lt;BR /&gt;ext3.o module&lt;BR /&gt;&lt;BR /&gt;mounting /proc filesystem&lt;BR /&gt;&lt;BR /&gt;creating block devices&lt;BR /&gt;VFS: cannot open root device "LABEL:/" or&lt;BR /&gt;&lt;BR /&gt;Please append a correct "root=" boot option&lt;BR /&gt;Kernel panic VFS: Unable to mount root</description>
      <pubDate>Fri, 30 Sep 2005 07:03:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/upgrade-kernel/m-p/3638984#M19875</guid>
      <dc:creator>addendum</dc:creator>
      <dc:date>2005-09-30T07:03:08Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade kernel</title>
      <link>https://community.hpe.com/t5/operating-system-linux/upgrade-kernel/m-p/3638985#M19876</link>
      <description>Your insmod may need updating (the one used by initrd). As you can see, it was unable to load even the first module necessary to eventually access your root file-system.&lt;BR /&gt;&lt;BR /&gt;The new kernel has QUERY_MODULES removed (don't ask why, normally there would be some kind of compatibility-overlap). So, your&lt;BR /&gt;older `insmod` or `insmod.static` is trying to use the old-method of loading modules.&lt;BR /&gt;&lt;BR /&gt;You may not be able to recover easily. I found that I needed to rebuild the kernel with the necessary SCSI drivers in the&lt;BR /&gt;kernel. This would allow me to boot and mount a root file-system.&lt;BR /&gt;&lt;BR /&gt;Save the previous kernel ".config" file. You must rebuild with the 'loop' device in the kernel as well (or else you can't make a new initrd RAM disk).&lt;BR /&gt;&lt;BR /&gt;Then you can install the new modutils package.&lt;BR /&gt;&lt;BR /&gt;Then you can change back to the previous configuration with `make clean ; make oldconfig`....etc. Rebuild the kernel,&lt;BR /&gt;install and boot happy.&lt;BR /&gt;</description>
      <pubDate>Fri, 30 Sep 2005 07:06:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/upgrade-kernel/m-p/3638985#M19876</guid>
      <dc:creator>Mugilvannan</dc:creator>
      <dc:date>2005-09-30T07:06:52Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade kernel</title>
      <link>https://community.hpe.com/t5/operating-system-linux/upgrade-kernel/m-p/3638986#M19877</link>
      <description>what do you have into /etc/modules.conf and what RHEL3 update you install?</description>
      <pubDate>Sun, 02 Oct 2005 00:59:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/upgrade-kernel/m-p/3638986#M19877</guid>
      <dc:creator>Vitaly Karasik_1</dc:creator>
      <dc:date>2005-10-02T00:59:35Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade kernel</title>
      <link>https://community.hpe.com/t5/operating-system-linux/upgrade-kernel/m-p/3638987#M19878</link>
      <description>thx Mugilvannan ,&lt;BR /&gt;&lt;BR /&gt;do you mean I need to add the SCSI driver to the new kernel ? &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;thx Vitaly Karasik ,&lt;BR /&gt;&lt;BR /&gt;I didn't run up2date to the server .</description>
      <pubDate>Mon, 03 Oct 2005 02:42:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/upgrade-kernel/m-p/3638987#M19878</guid>
      <dc:creator>addendum</dc:creator>
      <dc:date>2005-10-03T02:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade kernel</title>
      <link>https://community.hpe.com/t5/operating-system-linux/upgrade-kernel/m-p/3638988#M19879</link>
      <description>can you post /etc/modules.conf?</description>
      <pubDate>Mon, 03 Oct 2005 02:54:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/upgrade-kernel/m-p/3638988#M19879</guid>
      <dc:creator>Vitaly Karasik_1</dc:creator>
      <dc:date>2005-10-03T02:54:21Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade kernel</title>
      <link>https://community.hpe.com/t5/operating-system-linux/upgrade-kernel/m-p/3638989#M19880</link>
      <description>alias usb-controller1 ehci-hcd&lt;BR /&gt;alias char-major-188 off&lt;BR /&gt;alias scsi_hostadapter2 aic7xxx&lt;BR /&gt;alias char-major-14 off&lt;BR /&gt;alias block-major-20 off&lt;BR /&gt;alias scsi_hostadapter1 aacraid&lt;BR /&gt;alias scsi_hostadapter megaraid2&lt;BR /&gt;alias eth0 e1000&lt;BR /&gt;alias eth1 e1000</description>
      <pubDate>Mon, 03 Oct 2005 03:27:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/upgrade-kernel/m-p/3638989#M19880</guid>
      <dc:creator>addendum</dc:creator>
      <dc:date>2005-10-03T03:27:10Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade kernel</title>
      <link>https://community.hpe.com/t5/operating-system-linux/upgrade-kernel/m-p/3638990#M19881</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;you could try to append the root= as it says in the diag output and specify the full pathname to the disk /dev/sda1 or if its on cciss /dev/cciss/ccissxxxx,etc..&lt;BR /&gt;&lt;BR /&gt;that may be enough for it to boot, or if you have a recovery floppy boot up to that and then &lt;BR /&gt;remount the filesystem as it will be readonly by default, and make the changes to the modules.conf file, then reboot&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;&lt;BR /&gt;Matt&lt;BR /&gt;</description>
      <pubDate>Fri, 07 Oct 2005 09:22:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/upgrade-kernel/m-p/3638990#M19881</guid>
      <dc:creator>Matt Palmer_2</dc:creator>
      <dc:date>2005-10-07T09:22:13Z</dc:date>
    </item>
  </channel>
</rss>

