upgrade problem

fastestOS · 12-17-2008, 07:16 AM

My machine was 12.1 when I decided to try 12.2
I have tried the upgrade method, followed the instructions
in the UPGRADE.TXT. The upgrade of packages went smooth
then I hit telinit 3(the last step from UPGRADE.TXT).

At the prompt I edit the /etc/inittab file,
set the default runlevel to 4 so I can see KDE not the console prompt anymore.
And then I reboot.

Upon rebooting the loading stopped at the line
"Loading Unicode Table etc.. etc.." (sorry I forgot the exact words here but it's one of the last lines to load before arriving to the KDE as I remembered). Due to this I edit another file the /etc/lilo.conf (because I have read something in the UPGRADE.TXT that says "make sure the paths in /etc/lilo.conf point to a valid kernel and then type lilo to reinstall lilo" and for some reason I thought I still have the OLD kernel) so I changed the line image = /boot/vmlinuz to image = /boot/vmlinuz-generic-smp-2.6.27.7-smp. After that I typed lilo to reinstall it.

I reboot once more hoping I have changed the right line then
it gave me more problem the KERNEL PANIC.

"No filesystem could mount root..etc etc..."
Kernel Panic, root could not mount at block (08...)

My system then gets hanged, I can't type nor
switch console. I can't run slackware anymore.
It's kernel panic everytime I reboot.

I'm so worried about it please lend me a hand.
It was all because of my stupid "daredevil" attitude.
Thanks in advance. Hoping for your help here.

Ilgar · 12-17-2008, 07:29 AM

If it was stuck just before loading KDM then LILO must have been OK (as loading the kernel is the very first thing). So I'd recommend that you boot with the installation CD, mount your Slackware partition and 'chroot' into it, take back the changes you made to lilo.conf and re-run 'lilo' to save it. Then reboot the system and we can see what other errors you get.

In addition to UPGRADE.TXT, it's a good idea to see CHANGES_AND_HINTS.TXT as well. Maybe you'll find a clue there.

fastestOS · 12-17-2008, 07:46 AM

thanks for the help friend
it's back to normal now.

I've followed your advice but I used a
live OS instead.

Thanks again for the help.
My box now runs 12.2 SMOOTHLY!!!

brianL · 12-17-2008, 07:52 AM

You'll need an initrd to boot from the generic-smp kernel. Change that line back to just image = /boot/vmlinuz, then get this:
http://www.slackware.com/~alien/tool...d_generator.sh
run it as root, it will tell you the command to enter for a suitable initrd. See the README.initrd for more details.

onebuck · 12-17-2008, 08:10 AM

Hi,

Quote:

Originally Posted by fastestOS

thanks for the help friend
it's back to normal now.

I've followed your advice but I used a
live OS instead.

Thanks again for the help.
My box now runs 12.2 SMOOTHLY!!!

You could have used the 'Slackware® install cd/dvd' to boot then mount the partition in question. Then chroot to the crippled system that was mounted to allow you to make necessary changes.

Just a note for those who might search and find your post as reference;

Quote:

example;

The easiest way would be to use the install cd1 to boot the system as if you were going to install.
After you get to the login then from the cli (command line);

Code:

~#mkdir /slacktemp                   #temporary mount point
~#mount /dev/your_device /slacktemp  #this is the device you installed to
~#chroot /slacktemp                  #change to yours
~#cd /slacktemp/etc                  #change to directory with lilo.conf 
~#vi lilo.conf                       #edit lilo.conf, if need be
~#lilo -v -t -b /dev/your_device     #sda, hda this will only test 
~#lilo -v -b /dev/your_device        #this will write MBR to your_device

You should now be able to re-boot your system.

Lufbery · 12-17-2008, 08:17 AM

Onebuck,

Although I haven't yet needed the emergency recovery instructions you provided, they're potentially very helpful! Thank you.

-Drew

shadowsnipes · 12-17-2008, 11:45 AM

For recent Slackware upgrades and problem fixes please see the HowTos in my signature.