[SOLVED] Kernel Panic: could not find kernel image
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
First all, how many hard disks you are planning to use, how is each disk partitioned?
physical disk 1 from bios, usually called /dev/sda
physical disk 2 from bios, usually called /dev/sdb
your dvd player might be called /dev/sdc or /dev/cdrom
partition1 on first disk; called /dev/sda1
partition2 on second disk called /dev/sdb2
Do you even know where is your old Slackware installed at?
if you know, then mount it to /mnt, and find your way to lilo.conf file and then using vi editor find line says
Code:
boot =/dev/sdX #change x to slackware hard disk.
if your kernel is older < 3.10.7 you need to find and change
Code:
image = /boot/vmlinuz
root=/dev/sdx# #slackware partion for /.
label=old_slackware
save these changes and run command
lilo -A /dev/sdx# <active the slackware partion
lilo -M /dev/sdx mbr < update physical disk mbr record
run plain lilo again just make sure every thing is in order, no errors.
Yes, I installed Slackware 14.1 on the Western Digital 500 GB HDD (sda1) in July of 2014 and it was running fine until
yesterday.
I installed Debian on the 1 TB HDD last week.(dev/sdb1)
Did anything in particular happen yesterday? Did you by any chance update either OS (Slackware or Debian)?
It would be helpful to know the exact partition layout of your hard drives. Could you post the output from fdisk -l /dev/sda and fdisk -l /dev/sdb? Just boot from the Slackware DVD, select a language and press Enter at the login prompt. You will then find yourself at a command prompt from where you can run fdisk
I booted w/o the Slackware DVD and typed F11 several times to boot to the 1 TB HDD.
Debian is the first os in the Grub Menu and Slackware is the second choice.
There is no sign of my 500 GB Toshiba HDD and the Slackware I installed on it-
-::-I would like to know what happened to my Slackware os and what hosed it?-::-
Code:
WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 1953525167 976762583+ ee GPT
det@debian:~$
you can't have 2 OS on 2 different disk drive and both called /dev/sda1; when you add additional disk drive; driver letter changes and it might switch order.
never mind I misread your last comments about Slackware on /dev/sdb1
Did anything in particular happen yesterday? Did you by any chance update either OS (Slackware or Debian)?
It would be helpful to know the exact partition layout of your hard drives. Could you post the output from fdisk -l /dev/sda and fdisk -l /dev/sdb? Just boot from the Slackware DVD, select a language and press Enter at the login prompt. You will then find yourself at a command prompt from where you can run fdisk
I updated Debian a few days ago and upon doing so I got this error:
Code:
unreliable CPU thermal sensor mointoring disabled
The 2 GB swap and the EXT 4 journaling file system I created for Slackware on sda1 and sda2 is gone:-
Code:
det@debian:~$ fdisk -l/dev/sda1
bash: fdisk: command not found
debiancat@debian:~$ fdisk -l/dev/sda2
bash: fdisk: command not found
The 2 GB swap and the EXT 4 journaling file system I created for Slackware on sda1 and sda2 is gone:-
Code:
det@debian:~$ fdisk -l/dev/sda1
bash: fdisk: command not found
debiancat@debian:~$ fdisk -l/dev/sda2
bash: fdisk: command not found
That error message isn't telling you the drive is gone. It says you can't run the fdisk command, probably due to insufficient privileges. Try: sudo fdisk -l /dev/sda
That error message isn't telling you the drive is gone. It says you can't run the fdisk command, probably due to insufficient privileges. Try: sudo fdisk -l /dev/sda
So, to be clear: ls /dev/sda returns an error?
Using the Debian terminal running that cmd doesn't return anything but this:
Code:
dt@debian:~$ sudo ls /dev/sda
[sudo] password for debiancat:
/dev/sda
dt@debian:~$ sudo fdisk -l /dev/sda
dt@debian:~$ sudo fdisk -l /dev/sda
dt@debian:~$
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.