Another Upgrade, Another "Not-syncing" kernel panic

BobNutfield · 06-28-2010, 01:24 PM

I apologize, but I have started this new thread because I do not believe there are many still looking where I originally posted it, and I really need to get this solved so I can do some work. Well, got everything I need, followed all the instructions, and it won't boot. I don't know why I thought it would, no upgrade I have ever tried worked without headaches.

I get a kernel panic, not syncing, which I know is because it can't find the boot partition. When running lilo, I get a warning,
LBA32 addressing assumed.

My lilo.conf:

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/sda
#compact        # faster, but won't work on all systems.
# Standard menu.
message = /boot/boot_message.txt

# Append any additional kernel parameters:
append=" vt.default_utf8=0"
#prompt
timeout = 5
# Normal VGA console
vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0     # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda1
  label = Linux
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends

My /etc/fstab:

Code:

/dev/sda6        swap             swap        defaults         0   0
/dev/sda1        /                ext4        defaults         1   1
/dev/sda5        /home            ext4        defaults         1   2
#/dev/cdrom      /mnt/cdrom       auto        noauto,owner,ro  0   0
/dev/fd0         /mnt/floppy      auto        noauto,owner     0   0
devpts           /dev/pts         devpts      gid=5,mode=620   0   0
proc             /proc            proc        defaults         0   0
tmpfs            /dev/shm         tmpfs       defaults         0   0

I don't see what I did wrong. If anyone can take a look, I would appreciate it.

Thanks
Bob

XGizzmo · 06-28-2010, 02:23 PM

I would have to guess that the /boot/vmlinuz symlink is pointing to the generic kernel.
I which case you need to setup an initrd to get the system to boot. Running the helper
script /usr/share/mkinitrd/mkinitrd_command_generator.sh should help get you started.
Or you need to boot the huge kernel but it is not recommended to run huge kernels beyond
initial setup.

BobNutfield · 06-28-2010, 02:31 PM

Thanks, but I checked that. It is pointing to the huge kernel (as I was running under 13.0). I chrooted into Slack from a live distro to run lilo again, and get an error "permission denied" Tried liloconfig, and it will not reinstall with an error (doesn't say what.)

This is very frustrating. It seems to happen each time I upgrade, following official instructions to the letter.

Thanks for your reply.

Bob

BobNutfield · 06-28-2010, 03:14 PM

I believe that either lilo is not installed or the partition table is cocked up. Running liloconfig from the chroot environment does not work. It will not install lilo. It seems to work until entering the command to install lilo. Then it gives me a message that LILO has returned an error. Attempting to look at the partition table from fdisk -l returns cannot open /proc/partitions

I don't see a way around this one without a reinstall unless someone has an idea.

Bob

BobNutfield · 06-28-2010, 04:00 PM

UPDATE

LILO successfully installed, but still getting a kernel panic. The error asks to correct the "root=" parameter, but it is already correct.

The exact error is:

[QUOTE]Please append a correct "root-" boot option; here are the available options:[
Kernel Panic - not syncing VFS: Unable to mount root fs on unknown-block(3,1)/QUOTE]

Can this be solved?

Bob

BobNutfield · 06-29-2010, 12:44 PM

Well, 156 views and one reply. With the experts that come here, I guess I can assume that this one is a goner. Looks like a reinstall. Oh, well.

Bob

T3slider · 06-29-2010, 02:38 PM

You probably should `mount -o bind /proc/ /path/to/chroot/proc/` so lilo can see the correct information when trying to run (assuming you're chrooting from a LiveCD/install disk). Then chroot into the filesystem and edit lilo.conf and run lilo. The output of `fdisk -l` would be helpful to ensure that your partitions are still valid.

Alternatively you can boot into your system using the kernel on the install disk by passing the arguments displayed on the screen ('in a pinch'). Should be something like

Code:

hugesmp.s root=/dev/sda1 rdinit= ro

Then you can avoid the chroot stuff and just run lilo on your running system.

BobNutfield · 06-29-2010, 02:58 PM

Thanks, T3Slider, but I have already done all that you suggest, reinstalled lilo, pointed directly to the huge kernel.....many other things.

I have no idea what happened. The upgrade went very smoothly until the reboot, obviously.

But, never mind. I am reinstalling now as I write. I will stick with 13.0 for now and download (or purchase) a 13.1 DVD and reinstall again.

Thanks for your help. Have no idea what happened.

Bob