The "VFS: Kernel panic unable to mount root fs 08:00" says it's trying
to mount /dev/sda as root. But your root is /dev/sda2, which is 08:02.
You may be able to get your system up when booting from the scsi disk, or
if that doesn't work, from the boot floppy you made when upgrading by, at
the LILO prompt, typing
linux root=/dev/sda2
Another possibility is that your root really isn't /dev/sda2. Do you
have two scsi disks? If you do, maybe they have somehow gotten exchanged
so that the root is now on, say, /dev/sdb2, in which case "linux
root=/dev/sdb2" could work. But then I don't know why the kernel
panic message complained of 08:00 instead of 08:02, and I don't know why
2.4.2-2 would get the disk order different from 2.2.10. Maybe someone
better informed than either of us can explain it if that turns out to be
what happened.
The official way to get rid of old files in /boot and /usr/src is, if
they're from an rpm, to remove the rpm ("rpm -e ..."). For example, if
you still have /usr/src/linux-2.2.10, it and its contents come mainly from
kernel-headers-2.2.10... and kernel-source-2.2.10..., which you can remove
with rpm. The unofficial way is to just delete what you think you're not
using, and hope you're right. Maybe move them elsewhere before deleting
them to verify that they really aren't being used. It seems to me that if
you actually deleted something vital from /boot, the boot process wouldn't
get far enough for the kernel to panic.
On Thu, 29 Nov 2001, Jeanne Ilchuk wrote:
> I'm in the process of upgrading about 10 Linux servers
> from various RH installations that are greater than or
> equal to 6.0 (most of the kernels are variations of
> 2.2, ie 2.2.10; 2.2.13 etc)
>
> ALL of the servers are Penguin servers running redhat.
> The first 4 went (sort of) smoothly.
>
> Last week's attempt had the aix7xxx driver bug, so I
> put that off for now. The server I tried to upgrade
> this week has SCSI devices with the ncr538xx devices
> at PCI bus 0 device 13 (whatever that means). In
> addition, the floppy drive was bad and we changed
> the floppy device and also added an extra 128M
> memory, for a total of 256M. At first, the memory
> would not load until I added the append statement
> (below), and which was commented out before/during
> the upgrade.
>
> When I booted the system after the upgrade, I got a
> "VFS: Kernel panic unable to mount root fs 08:00....."
> (or something close to that); then the system just hung.
>
> At this point, I reset the server and booted off the
> 2.2.10 boot disk. It refuses to boot the new kernel
> boot disk I made while upgrading; I get the same
> kernel panic. So I now have a 7.1 os with a very
> old kernel. If I do a lilo -q -v the output points
> to /dev/fdo 2.2.10
>
> Here's my /etc/lilo.conf file:
> [root@localhost]# cat /etc/lilo.conf
> boot=/dev/sda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=30
> verbose=3
> #compact
> #append="mem=256M"
> message=/boot/message
> #linear
> default=linux
>
> image=/boot/vmlinuz-2.4.2-2
> label=linux
> read-only
> root=/dev/sda2
>
> image=/boot/vmlinuz-backup
> label=backup
> root=/dev/sda2
> read-only
>
>
> THIS LOOKS LIKE I'M OPERATING THE RIGHT KERNEL,
> with the right parameters; why won't it boot?
>
> One last question; my 24M /boot partition ran out
> of space during the upgrade, so I deleted the old
> boot images and other files. Might that have
> something to do with this mess? How do you officially
> get rid of old files in /boot and also /usr/src/linux/
> ??
>
> Thanks in advance.
>
> -Jeanne
>
>
>
> _______________________________________________
> Seawolf-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/seawolf-list
>
--
Steven Yellin
_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
