<?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: Netserver  LC 2000 / RedHat 7.2 Cannot Mount Root FS in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/netserver-lc-2000-redhat-7-2-cannot-mount-root-fs/m-p/2674852#M1243</link>
    <description>See if you can get on the system at all (boot from CD in rescue mode, most likely).&lt;BR /&gt;&lt;BR /&gt;See if it discovered and mounted the root partition correctly.  If not, umount and remount the correct root fs under /mnt&lt;BR /&gt;&lt;BR /&gt;If it didn't mount correctly, thats bad.  You can reboot at this point and try hitting Ctrl-x at the lilo spash screen and booting like:&lt;BR /&gt;&lt;BR /&gt;LILO: linux root=/dev/sda3&lt;BR /&gt;&lt;BR /&gt;(substitue the correct device for your root volume)  &lt;BR /&gt;&lt;BR /&gt;If that boots, check the /etc/lilo.conf and see if it's correct.  Reinstall.&lt;BR /&gt;&lt;BR /&gt;Failing that, you could try a kernel rebuild and a new initrd image.  There was a command to poke in a new device number directly into the kernel if you moved devices, but I can't recall what it was.&lt;BR /&gt;</description>
    <pubDate>Fri, 01 Mar 2002 22:27:20 GMT</pubDate>
    <dc:creator>Eric Ladner</dc:creator>
    <dc:date>2002-03-01T22:27:20Z</dc:date>
    <item>
      <title>Netserver  LC 2000 / RedHat 7.2 Cannot Mount Root FS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/netserver-lc-2000-redhat-7-2-cannot-mount-root-fs/m-p/2674849#M1240</link>
      <description>I Previously posted a question regarding the Netraid 2M and linux file corruption.&lt;BR /&gt;&lt;BR /&gt;The system was running RedHat 6.2 and after building 2.4.18 kernel for it and rebooting I got a kernel panic (mount error 6 - No init found).&lt;BR /&gt;&lt;BR /&gt;Thinking this a foul-up in the os, rather than spending hours searching we went with a re-install with RedHat 7.2.&lt;BR /&gt;&lt;BR /&gt;5 minutes later...same error.&lt;BR /&gt;&lt;BR /&gt;Has anyone had this problem before?&lt;BR /&gt;&lt;BR /&gt;Any help appreciated.</description>
      <pubDate>Fri, 01 Mar 2002 21:15:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/netserver-lc-2000-redhat-7-2-cannot-mount-root-fs/m-p/2674849#M1240</guid>
      <dc:creator>Paul S_1</dc:creator>
      <dc:date>2002-03-01T21:15:17Z</dc:date>
    </item>
    <item>
      <title>Re: Netserver  LC 2000 / RedHat 7.2 Cannot Mount Root FS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/netserver-lc-2000-redhat-7-2-cannot-mount-root-fs/m-p/2674850#M1241</link>
      <description>When you say you re-installed 7.2, you did a cold install off of the CD?&lt;BR /&gt;&lt;BR /&gt;What I'm wondering is if any hardware changes were made to the machine (i.e. cards removed, shuffled, disk devices moved, etc).  &lt;BR /&gt;&lt;BR /&gt;Something as simple as exchanging two scsi cards in a system or adding a drive to your scsi bus can render a machine unbootable.</description>
      <pubDate>Fri, 01 Mar 2002 21:34:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/netserver-lc-2000-redhat-7-2-cannot-mount-root-fs/m-p/2674850#M1241</guid>
      <dc:creator>Eric Ladner</dc:creator>
      <dc:date>2002-03-01T21:34:23Z</dc:date>
    </item>
    <item>
      <title>Re: Netserver  LC 2000 / RedHat 7.2 Cannot Mount Root FS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/netserver-lc-2000-redhat-7-2-cannot-mount-root-fs/m-p/2674851#M1242</link>
      <description>No, we installed a fresh 7.2 installation.&lt;BR /&gt;&lt;BR /&gt;As far as the hardware is concerned, nothing was changed.&lt;BR /&gt;&lt;BR /&gt;It appears that we cannot use a 2.4 kernel on that particular server. There must be a way though, I just cant locate one on the internet.</description>
      <pubDate>Fri, 01 Mar 2002 21:41:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/netserver-lc-2000-redhat-7-2-cannot-mount-root-fs/m-p/2674851#M1242</guid>
      <dc:creator>Paul S_1</dc:creator>
      <dc:date>2002-03-01T21:41:57Z</dc:date>
    </item>
    <item>
      <title>Re: Netserver  LC 2000 / RedHat 7.2 Cannot Mount Root FS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/netserver-lc-2000-redhat-7-2-cannot-mount-root-fs/m-p/2674852#M1243</link>
      <description>See if you can get on the system at all (boot from CD in rescue mode, most likely).&lt;BR /&gt;&lt;BR /&gt;See if it discovered and mounted the root partition correctly.  If not, umount and remount the correct root fs under /mnt&lt;BR /&gt;&lt;BR /&gt;If it didn't mount correctly, thats bad.  You can reboot at this point and try hitting Ctrl-x at the lilo spash screen and booting like:&lt;BR /&gt;&lt;BR /&gt;LILO: linux root=/dev/sda3&lt;BR /&gt;&lt;BR /&gt;(substitue the correct device for your root volume)  &lt;BR /&gt;&lt;BR /&gt;If that boots, check the /etc/lilo.conf and see if it's correct.  Reinstall.&lt;BR /&gt;&lt;BR /&gt;Failing that, you could try a kernel rebuild and a new initrd image.  There was a command to poke in a new device number directly into the kernel if you moved devices, but I can't recall what it was.&lt;BR /&gt;</description>
      <pubDate>Fri, 01 Mar 2002 22:27:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/netserver-lc-2000-redhat-7-2-cannot-mount-root-fs/m-p/2674852#M1243</guid>
      <dc:creator>Eric Ladner</dc:creator>
      <dc:date>2002-03-01T22:27:20Z</dc:date>
    </item>
    <item>
      <title>Re: Netserver  LC 2000 / RedHat 7.2 Cannot Mount Root FS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/netserver-lc-2000-redhat-7-2-cannot-mount-root-fs/m-p/2674853#M1244</link>
      <description>Hello Paul,&lt;BR /&gt;&lt;BR /&gt;After moving to kernel 2.4.x, did you rebuild the initrd file ?&lt;BR /&gt;&lt;BR /&gt;People would suggest you to use mkinitrd, but this is my preferred method to do that :&lt;BR /&gt;&lt;BR /&gt;Let's say the current initrd filename is /boot/initrd-2.4.7-3.img (this is just an example).&lt;BR /&gt;&lt;BR /&gt;cp /boot/initrd-2.4.7-3.img /tmp/initrd.gz&lt;BR /&gt;gunzip /tmp/initrd.gz&lt;BR /&gt;mount -oloop /tmp/initrd /mnt&lt;BR /&gt;cd /mnt&lt;BR /&gt;grep insmod /mnt/linuxrc&lt;BR /&gt;grep modprobe /mnt/linuxrc&lt;BR /&gt;&lt;BR /&gt;  -&amp;gt; you have the list of modules used during the boot steps&lt;BR /&gt;&lt;BR /&gt;Then, go to /lib/modules/2.4.18/... to copy the appropriate modules into /mnt/lib. For example :&lt;BR /&gt;&lt;BR /&gt;cp -p /lib/modules/2.4.18/kernel/fs/ext3/ext3.o /mnt/lib&lt;BR /&gt;cp -p /lib/modules/2.4.18/kernel/fs/jbd/jbd.o /mnt/lib&lt;BR /&gt;&lt;BR /&gt;After that :&lt;BR /&gt;&lt;BR /&gt;cd /boot&lt;BR /&gt;umount /mnt&lt;BR /&gt;gzip /tmp/initrd&lt;BR /&gt;cp /tmp/initrd.gz /boot/initrd-2.4.18.img&lt;BR /&gt;&lt;BR /&gt;Edit your /etc/lilo.conf to reflect the changes.&lt;BR /&gt;&lt;BR /&gt;Launch "lilo" to refresh boot zones.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;If you want an advise : when you build another kernel, it is strongly recommended to keep your old kernel in place, just in case. For example, if I had the following /etc/lilo.conf :&lt;BR /&gt;&lt;BR /&gt;prompt&lt;BR /&gt;timeout=100&lt;BR /&gt;boot=/dev/hda&lt;BR /&gt;map=/boot/map&lt;BR /&gt;install=/boot/boot.b&lt;BR /&gt;message=/boot/message&lt;BR /&gt;&lt;BR /&gt;image=/boot/vmlinuz-2.4.7-3&lt;BR /&gt; label=linux&lt;BR /&gt; initrd=/boot/initrd-2.4.7-3.img&lt;BR /&gt; read-only&lt;BR /&gt; root=/dev/hda5&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;After the changes above, my /etc/lilo.conf would look like this :&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;prompt&lt;BR /&gt;timeout=100&lt;BR /&gt;boot=/dev/hda&lt;BR /&gt;map=/boot/map&lt;BR /&gt;install=/boot/boot.b&lt;BR /&gt;message=/boot/message&lt;BR /&gt;&lt;BR /&gt;image=/boot/vmlinuz-2.4.18&lt;BR /&gt; label=linux&lt;BR /&gt; initrd=/boot/initrd-2.4.18.img&lt;BR /&gt; read-only&lt;BR /&gt; root=/dev/hda5&lt;BR /&gt;&lt;BR /&gt;image=/boot/vmlinuz-2.4.7-3&lt;BR /&gt; label=old&lt;BR /&gt; initrd=/boot/initrd-2.4.7-3.img&lt;BR /&gt; read-only&lt;BR /&gt; root=/dev/hda5&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Good luck.&lt;BR /&gt;&lt;BR /&gt;Kodjo&lt;BR /&gt;</description>
      <pubDate>Sat, 02 Mar 2002 20:44:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/netserver-lc-2000-redhat-7-2-cannot-mount-root-fs/m-p/2674853#M1244</guid>
      <dc:creator>Kodjo Agbenu</dc:creator>
      <dc:date>2002-03-02T20:44:02Z</dc:date>
    </item>
    <item>
      <title>Re: Netserver  LC 2000 / RedHat 7.2 Cannot Mount Root FS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/netserver-lc-2000-redhat-7-2-cannot-mount-root-fs/m-p/2674854#M1245</link>
      <description>While all of your suggestions are appreciated, I think I have discovered the problem.&lt;BR /&gt;&lt;BR /&gt;It seems that booting in 'rescue' mode from the CD, the scsi modules are loaded like so:&lt;BR /&gt;&lt;BR /&gt;sym53c8xx then megaraid&lt;BR /&gt;&lt;BR /&gt;Whereas when booting the system on it's own, the modules are loaded in reverse.&lt;BR /&gt;&lt;BR /&gt;I will remove megaraid from the load process and report my findings. The megaraid can always be loaded after the boot process since this is not the OS partition.&lt;BR /&gt;&lt;BR /&gt;BTW: RedHat 7.2 uses the Grub boot loader rather than Lilo (although lilo is an option during install).&lt;BR /&gt;&lt;BR /&gt;-Paul</description>
      <pubDate>Mon, 04 Mar 2002 16:15:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/netserver-lc-2000-redhat-7-2-cannot-mount-root-fs/m-p/2674854#M1245</guid>
      <dc:creator>Paul S_1</dc:creator>
      <dc:date>2002-03-04T16:15:10Z</dc:date>
    </item>
    <item>
      <title>Re: Netserver  LC 2000 / RedHat 7.2 Cannot Mount Root FS</title>
      <link>https://community.hpe.com/t5/operating-system-linux/netserver-lc-2000-redhat-7-2-cannot-mount-root-fs/m-p/2674855#M1246</link>
      <description>My hunch paid off.&lt;BR /&gt;&lt;BR /&gt;On RedHat 7.2 (or, I am assuming any 2.4 distro) the scsi modules appear to load in the wrong order for this machine.&lt;BR /&gt;&lt;BR /&gt;The 2.4 kernel will load megaraid before your sym53c8xx driver resulting in some sort of conflict (does the megaraid use a sym chipset?). It seems the system will then look to the partition on your array instead of the fixed disk in the system.&lt;BR /&gt;&lt;BR /&gt;I removed the megaraid entry from my modules.conf and built a new initrd image. Reboot and poof, there it was. Maybe using --with=megaraid with mkinitrd will cause this module to load -after- the sym module.&lt;BR /&gt;&lt;BR /&gt;Something to think about if you have an identical system or know of someone having this problem.&lt;BR /&gt;&lt;BR /&gt;Thanks for the suggestions!&lt;BR /&gt;-Paul Slinski</description>
      <pubDate>Mon, 04 Mar 2002 18:11:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/netserver-lc-2000-redhat-7-2-cannot-mount-root-fs/m-p/2674855#M1246</guid>
      <dc:creator>Paul S_1</dc:creator>
      <dc:date>2002-03-04T18:11:17Z</dc:date>
    </item>
  </channel>
</rss>

