2.2.1 upgrade; kernel panic; superblock problem

2.2.1 upgrade; kernel panic; superblock problem

Post by Raymond Doetje » Sun, 21 Feb 1999 04:00:00



You should always have the "old" kernel in a extra lilo.conf section.
Then when lilo comes up, you enter the old setupname.

What you probably forgot was to run lilo. You should always run lilo
even when you overwrite a kernel! You can still make a boot disk mount
the partition and run lilo
that way you don't need to reinstall your system.

Raymond

 
 
 

2.2.1 upgrade; kernel panic; superblock problem

Post by John Burto » Sun, 21 Feb 1999 04:00:00


I wanted to play with changing my kernel but didn;t want to make my machine
unbootable. How do I change lilo.conf so that I can boot my old working
kernel?
Do I just duplicate the lines starting with "image=/vmlinuz"?

>You should always have the "old" kernel in a extra lilo.conf section.
>Then when lilo comes up, you enter the old setupname.

>What you probably forgot was to run lilo. You should always run lilo
>even when you overwrite a kernel! You can still make a boot disk mount
>the partition and run lilo
>that way you don't need to reinstall your system.

>Raymond


 
 
 

2.2.1 upgrade; kernel panic; superblock problem

Post by Timothy Murp » Mon, 22 Feb 1999 04:00:00



>I wanted to play with changing my kernel but didn;t want to make my machine
>unbootable. How do I change lilo.conf so that I can boot my old working
>kernel?
>Do I just duplicate the lines starting with "image=/vmlinuz"?

Yes, except that you must give a different "label" in the two cases,
eg "label=linux.old" and "label=linux".

--
Timothy Murphy  

tel: +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland

 
 
 

1. Problem upgrading Kernel, Kernel Panic.

  I have problem with upgrading kernel. At last I decided to upgrade kernel from antique
 version "Linux-1.1.18" to "Linux-1.1.95". I think I did every steps of compilation correctly
 and no problems were occured. The problem starts after rebooting the system.

   "Kernel panic: VFS: Unable to mount root fs on 03:02"

  Fortunately I builded lilo.config file correctly and I was able to load old version of kernel.
 My lilo.conf file is :

--------------------------------------------------
 LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="cdu31a=0x340"
boot = /dev/hda2
#compact        # faster, but won't work on all systems.
delay = 50
vga = normal    # force sane state
ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /vmlinuz
  root = /dev/hda2
  label = Linux-1.1.18
# Linux bootable partition config begins
image = /usr/src/linux/arch/i386/boot/zImage
  root = /dev/hda2
  label = Linux-1.1.95
# Linux bootable partition config ends
-------------------------------------------------

 I also used 'rdev /usr/src/linux/arch/i386/boot/zImage /dev/hda2'. I made bootable disk with
new Kernel on it. I examined to pass arguments to 'lilo' at boot time. For example:

-------------------------------
LILO
boot:
Linux-1.1.18     Linux-1.1.95

boot: Linux-1.1.95 boot=/dev/hda2 ( or boot=/dev/hda2 )

...................................................................................
...................................................................................
( Some Kernel booting messages )
...................................................................................
...................................................................................
Kernel panic: VFS: Unable to mount root fs on 03:02
(System halted)
------------------------------

 So may be someone can give advice.

2. stat() dangerous?

3. Problem wiht Kernel upgrading, Kernel Panic: ...

4. how do i set modem for full-duplex in Linux?

5. Bad Superblock, kernel panic, help please.

6. mount win98/cdrom drive question

7. HELP - Kernel PANIC - bad SuperBlock

8. Sol-2.5-x86 on Triton-II motherboards

9. 1.1.81 kernel panic (swapper) causing superblock destruction

10. Kernel panic, alternate superblock

11. kernel panic - Bad magic number in superblock

12. kernel panic, unable to read superblock

13. Kernel Panic After upgrade to 2.4.9-34 kernel on RH7.2