[SOLVED] Slackware 14.2 - Kernel panic after installing vmware tools

ilesterg · 12-17-2016, 03:47 PM

Hi!

I took some time installing my very first Slackware VM and it hurts me that vmware tools broke it

Boot:
Kernel panic - Unable to mount root fs on unknown-block(251,1)

Attached are some info.
* boot message showing the kernel panic
* contents of my boot dir
* lilo config
* some info on my installation

My slackware is using lvm. This is my simple layout:

Code:

/dev/sda1 - boot
/dev/sda2 - LVM
/dev/slackware/lv_root
/dev/slackware/lv_swap

I managed to get the first 3 screenshot by running the slackware install disk, activating the volume group (vgchange -a y /dev/slackware) mounting the root logical volume, then chrooting.

I really don't know how to proceed with this. I was following this article and I read that I should run lilo after the installation, but it was already too late. Also, I noticed that the initrd.gz file was just updated so I'm guessing my vmware tools installation did it.

Please bear with me, I'm only using Slackware for a week.

Thanks!

Ztcoracat · 12-17-2016, 06:53 PM

Hi:

I'd be very surprised if the VM tools broke your system.

It's more likely that after a 'kernel upgrade' and not running LILO is what generated kernel panic. I'm not sure but it may be that the driver for you fs is not there or something is missing in the initrd.

I recently forgot to run LILO after a kernel upgrade and my Slackware 14.2 wouldn't boot. However; I didn't have kernel panic-

One of our Moderators; astrogeek and Mr. frankbell helped me. Hope this thread helps you.

http://www.linuxquestions.org/questi...nd-4175595311/

Gerard Lally · 12-17-2016, 07:08 PM

1) What is the name of your Volume Group - slackware or vgslack?

2) Did you create your initrd.gz with the -L option?

ilesterg · 12-17-2016, 07:17 PM

I did have a kernel update days ago (slakpkg update to be more accurate) and I didn't need to rebuild anything.

It was today after installing kde plasma 5 then rebooting then I decided to install vmware tools.

Sorry my vg is vgslack, slackware was just a typo.

Yes I did use -L option but that was during installation. After that I did not do anything kernel related except perhas this vmware tools install. I'm did try to run mkinitrd inside chroot but it appears that it needs 4.4.14 libs which I'm guessing were not loaded.

Ztcoracat · 12-22-2016, 07:54 PM

Did the link I posted help?

Still have kernel panic?

Common causes of kernel panic include things like faulty RAM or malfunctioning peripherals, drivers or software plugins, or even badly written programs.
http://g33kinfo.com/info/archives/492

I'd just do a fresh installation unless you have another kernel to boot:-

Ztcoracat · 12-22-2016, 07:58 PM

https://wiki.archlinux.org/index.php/Kernel_Panics

ilesterg · 01-03-2017, 12:15 AM

This was a VM. I reinstalled Slack, installed VMware Tools then made sure to reran lilo, rebooted, and it booted up successfully. It would have been good to fix that without reinstalling Slack tho.

Marking as solved.

Ztcoracat · 01-03-2017, 03:17 PM

Quote:

It would have been good to fix that without reinstalling Slack tho.

Agreed. Glad it's working for you now and kernel panic is a thing of the past.