LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-14-2014, 04:11 PM   #1
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484
Blog Entries: 15

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
Kernel Panic: could not find kernel image


Hi:

My 64-bit AMD desktop is in kernel panic mode.

I tried using the Live Slackware DVD and at the prompt I typed:
mount /dev/sda1 /mnt. The konsole than returned: Could not find kernel image. So I tried typing huge.s to see if it would boot the kernel.

Do I have to complete a fresh installation of Slackware?

The screen went to black and than displayed this message:

Last edited by Ztcoracat; 02-24-2015 at 07:45 PM.
 
Old 12-14-2014, 04:49 PM   #2
number22
Member
 
Registered: Sep 2006
Location: Earth
Distribution: Slackware 14.1 Slackware64-current multilib
Posts: 278
Blog Entries: 7

Rep: Reputation: Disabled
mismatch kernel and glibc or missing file system modules to read disk.

you probably trying boot from older Slackware cd/dvd to boot later versions Slackware root disk.
 
Old 12-14-2014, 04:55 PM   #3
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
Here's some more details about the circumstances:

This desktop has 2 hard drives.
The 500 GB HDD Western Digital is what I installed Slackware to over the summer.
The new drive that I just installed last week is a Seagate 1 TB HDD and I installed Debian on it.

The first installation of Debian failed. It would take me to a log-in, I'd log in the screen flashed black and
took me directly back to log-in again. Due to the failure I re-installed Debian again and the second install worked properly.

Before I installed Debian I edited the lilo.conf file with a argument letting LILO know about Debian:
Code:
other = /dev/sdb
lablel = debian
I didn't have sound at the first boot of Debian nor at all the other previous boots either.
I booted into Slackware yesterday and the video's would play for a minute but crash.
After rebooting into Slackware I'm stuck in kernel panic mode.
I put the Slackware DVD in the CDROM drive and shut down the tower.

Once the Slackware DVD boots I don't know what to try at this point.
 
Old 12-14-2014, 04:57 PM   #4
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
Quote:
Originally Posted by number22 View Post
mismatch kernel and glibc or missing file system modules to read disk.

you probably trying boot from older Slackware cd/dvd to boot later versions Slackware root disk.
The Live Slackware DVD I'm booting with is Slackware 14.1-

Can anything be done at this point or do I need to re-install?
 
Old 12-14-2014, 04:59 PM   #5
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 3,340

Rep: Reputation: Disabled
Quote:
Originally Posted by Ztcoracat View Post
I tried using the Live Slackware DVD and at the prompt I typed:
mount /dev/sda1 /mnt. The konsole than returned: Could not find kernel image.
That's not the Linux console, it's the bootloader prompt. You can specify the name of one of the kernel images on the DVD and various parameters, but you cannot run commands.

Have you tried booting the system by following the onscreen instructions? Those that start with "In a pinch, you can boot your system from here..."?

If you type huge.s root=/dev/sda1 rdinit= ro (note the space after rdinit=), the bootloader will load the "huge.s" kernel from the DVD, which in turn will try to mount /dev/sda1 as the root file system. If you installed Slackware to a partition other than /dev/sda1, modify the command line accordingly.
 
Old 12-14-2014, 05:16 PM   #6
number22
Member
 
Registered: Sep 2006
Location: Earth
Distribution: Slackware 14.1 Slackware64-current multilib
Posts: 278
Blog Entries: 7

Rep: Reputation: Disabled
Quote:
Originally Posted by Ztcoracat View Post
The Live Slackware DVD I'm booting with is Slackware 14.1-

Can anything be done at this point or do I need to re-install?
Maybe your disk has older version Slackware, it is best and easy just reinstall with new Slackware.

Live DVD is not same as installation DVD, if you arleady has live DVD then you already has a working slackware, you just need lsblk to see all disk, and then use mount command to chose disk to mount.
 
Old 12-14-2014, 05:30 PM   #7
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
Quote:
Originally Posted by Ser Olmy View Post
That's not the Linux console, it's the bootloader prompt. You can specify the name of one of the kernel images on the DVD and various parameters, but you cannot run commands.

Have you tried booting the system by following the onscreen instructions? Those that start with "In a pinch, you can boot your system from here..."?

If you type huge.s root=/dev/sda1 rdinit= ro (note the space after rdinit=), the bootloader will load the "huge.s" kernel from the DVD, which in turn will try to mount /dev/sda1 as the root file system. If you installed Slackware to a partition other than /dev/sda1, modify the command line accordingly.

If I recall correctly it's kernel 3.10. but I don't remember the extension-
I haven't booted the system by following the onscreen instructions because the on screen instructions take me directly into a fresh installation.

Do you mean that there should not be a space after rdinit= it should look like this instead?
Code:
huge.s root=/dev/sda1 rdinit=ro
 
Old 12-14-2014, 05:35 PM   #8
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 3,340

Rep: Reputation: Disabled
Quote:
Originally Posted by Ztcoracat View Post
I haven't booted the system by following the onscreen instructions because the on screen instructions take me directly into a fresh installation.
It mounts your root file system and boots the installed Slackware system using the kernel from the DVD. It does not start the installer.
Quote:
Originally Posted by Ztcoracat View Post
Do you mean that there should not be a space after rdinit= it should look like this instead?
There should definitely be a space after rdinit=. It means "do not use the supplied RAM disk image":
Code:
huge.s root=/dev/sda1 rdinit= ro
 
Old 12-14-2014, 05:43 PM   #9
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
Ok, thanks; Ser Olmy:-

At the bootloader prompt I'll type it the way you've posted it in code tags.

Once it boots the installed Slackware os what should I do from there?
(aside from looking in /var/log to find out what's going on)
 
Old 12-14-2014, 05:48 PM   #10
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 3,340

Rep: Reputation: Disabled
The error message says the kernel can't mount root, so you should check /etc/lilo.conf and make sure the root directive specifies the right partition. It looks like the current setting is /dev/sda2, actually.

If you make any changes to lilo.conf, remember to run lilo afterwards to apply the changes to the bootloader.
 
Old 12-14-2014, 06:20 PM   #11
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
Quote:
Originally Posted by Ser Olmy View Post
The error message says the kernel can't mount root, so you should check /etc/lilo.conf and make sure the root directive specifies the right partition. It looks like the current setting is /dev/sda2, actually.

If you make any changes to lilo.conf, remember to run lilo afterwards to apply the changes to the bootloader.
Booting the Live Slackware DVD now....

I'll post what I see in lilo.conf so you can see it, bb-
 
Old 12-14-2014, 06:24 PM   #12
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 3,340

Rep: Reputation: Disabled
Quote:
Originally Posted by Ztcoracat View Post
Booting the Live Slackware DVD now....
The Slackware DVD does not contain a live system, just the installer.
 
Old 12-14-2014, 06:34 PM   #13
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
I tried to look at the /etc/lilo.conf at the boot prompt but that's not working.
After a few min's it appeared to boot the kernel image and now I'm being asked for info. on the keyboard-
Code:
$ Enter 1 to select a keyboard map.
What am I doing wrong?
 
Old 12-14-2014, 06:41 PM   #14
Ser Olmy
Senior Member
 
Registered: Jan 2012
Distribution: Slackware
Posts: 3,340

Rep: Reputation: Disabled
Then you must have tried to run some sort of command from the boot prompt, which obviously didn't work. Eventually the default kernel booted with no options, leading you straight to the installer. That is not what you wanted.

This is what you need to do:
  1. Boot from the DVD
  2. At the boot prompt, type huge.s root=/dev/sda1 rdinit= ro and press Enter
  3. Wait as the kernel loads and the system boots
  4. Log in and troubleshoot the boot issue
If step 3 doesn't get you to the login prompt, try specifying /dev/sda2 as the root file system. If it still doesn't work, make a note of any error messages and return here.
 
Old 12-14-2014, 07:05 PM   #15
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176Reputation: 1176
Quote:
Originally Posted by Ser Olmy View Post
Then you must have tried to run some sort of command from the boot prompt, which obviously didn't work. Eventually the default kernel booted with no options, leading you straight to the installer. That is not what you wanted.

This is what you need to do:
  1. Boot from the DVD
  2. At the boot prompt, type huge.s root=/dev/sda1 rdinit= ro and press Enter
  3. Wait as the kernel loads and the system boots
  4. Log in and troubleshoot the boot issue
If step 3 doesn't get you to the login prompt, try specifying /dev/sda2 as the root file system. If it still doesn't work, make a note of any error messages and return here.
I tried steps 1-3 and never make it to log in. I also tried /dev/sda2 as well--
After the kernel loads this is what I have:

Code:
No filesystem could mount root tried: reiserts ext3 ext 2 ext4 vfat msdos iso96 60 ntfs romfs
udf jfs sfs ocfs2 btrfs

Kernel panic-not syncing: vfs Unable to mount root fs on unknown-block (8,1)
Call Trace
dum_stack +0x9d/0x1b
panic +0xc2/0x1ba
mount_block_root+0x2aa/0x2bg
Mount_root+0x9d/0xa0
prepare_namespac+0x16c/0x1a4
kernel_init_freeable+0x1d1/0x1df
? do_early_param+0x88/0x88
? rest_init+0x80/0x80
ret_from_fork+0x7c/0xbo
? rest_init+0x80/0x80
The prompt is flashing as well as the lights on the keyboard and the keyboard is temporarily not working.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Vanilla kernel config gives kernel panic: Unable to find VolGroup0 bbcannon Linux - Newbie 1 09-24-2008 03:48 AM
ISOLinux from Debian etch cannot find kernel image (but kernel is in its place)! Why? *Dark Dragon* Debian 4 11-07-2005 09:54 PM
Kernel Panic can not find init image ToeShot Linux - General 5 08-03-2005 02:05 PM
kernel panic error after rebooting new kernel image fiero Linux - General 4 07-13-2005 08:32 AM
kernel-image generates Kernel Panic Osten Debian 1 03-10-2004 12:08 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:01 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration