SOLVED Kernel Panic

[mpadilla2]

The comand to reinstall glibc....had to add on the packages directory cause that was missing in the comand thenktor posted. Also expanded the command like he said to what version of glibc was in the directory. So like I said it started to work and then threw that error.

[mpadilla2]

Specifically the command was:

Code: Select all

spkg --root=/mnt/sda1 -u --reinstall /mnt/sda1/var/slapt-get/patches/packages/glibc-2.13-x86_64-6_slack13.37.txz

[mpadilla2]

I studied the link more that I provided in my original post until I understood what was going on. I then did the steps to change fstab and lilo config to use UUID and it works! I got the system to boot up finally!

Here is the link again in case anyone is wondering:
https://www.slacky.eu/forum/viewtopic.php?f=51&t=34622

I'm wondering why all of a sudden is has to identify the partitions by UUID now though? Sheesh it never had to before.

Anyway, thank you everyone for all of your help!

[Akuna]

Really? That is odd because LiloSetup would have done that automatically for you if you had used it as suggested.
(That is LiloSetup a GUI tool from the system menu, not liloconfig from the command line. Or else lilosetup.py from the command line as advised by mimosa)

[Akuna]

I'm wondering why all of a sudden is has to identify the partitions by UUID now though? Sheesh it never had to before.

Maybe the users moved the partition/disks around? Are those inclosed hard drives or removable?

[mpadilla2]

I did use it from the system menu. It changed lilo conf to uuid only not fstab. No they haven't move the partitions around as they are just users not computer knowledgeable at all. It is one hard drive and not easily removed.

[mimosa]

Which Salix edition is it?

[Akuna]

I did use it from the system menu. It changed lilo conf to uuid only not fstab.

Oops my bad! Sorry I read you too quickly.
No idea why this happened.
If not the users directly, maybe inadvertently by some programs or configuration that switched the partition naming scheme? This is odd indeed...
(Any new packages installed prior to this events? packages from third party repo?)
Anyways, it's great you found a fix.
If this happens to anyone else, we might get more clues.