[SOLVED] Kernel Panic: could not find kernel image

Ser Olmy · 12-14-2014, 08:25 PM

Well, /dev/sda is clearly there, but fdisk doesn't seem able to access it.

The drive could very well be defective. Try:

Code:

sudo smartctl -a /dev/sda

Ztcoracat · 12-14-2014, 08:29 PM

Quote:

Originally Posted by Ser Olmy

Well, /dev/sda is clearly there, but fdisk doesn't seem able to access it.

The drive could very well be defective. Try:

Code:

sudo smartctl -a /dev/sda

Code:

dt@debian:~$ sudo smartctl -a /dev/sda
[sudo] password for debiancat: 
sudo: smartctl: command not found
det@debian:~$

Ser Olmy · 12-14-2014, 08:33 PM

I guess you don't have smartmontools installed. You could apt-get install smartmontools or use a live distribution like System Rescue CD which has most of these tools included.

Ztcoracat · 12-14-2014, 08:38 PM

Quote:

Originally Posted by Ser Olmy

I guess you don't have smartmontools installed. You could apt-get install smartmontools or use a live distribution like System Rescue CD which has most of these tools included.

I'll have to look and see in the stack of DVD's that I have if I have a System Rescue CD.
I think I do have one-

Code:

det@debian:~$ sudo apt-get install smartmontools 
[sudo] password for debiancat: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package smartmontools
det@debian:~$

Ser Olmy · 12-14-2014, 08:43 PM

Debian certainly has a smartmontools package available, so I don't know why apt-get can't find it.

colorpurple21859 · 12-14-2014, 08:47 PM

run

Code:

sudo apt-get update

then try installing smartmontools

Ztcoracat · 12-14-2014, 08:55 PM

I took a picture of Grub after I typed e for edit so you can see what I have.

Ztcoracat · 12-14-2014, 09:13 PM

Quote:

Originally Posted by colorpurple21859

run

Code:

sudo apt-get update

then try installing smartmontools

Code:

dt@debian:~$ sudo apt-get update
[sudo] password for debiancat: 
Get:1 http://security.debian.org jessie/updates InRelease [84.1 kB]
Get:2 http://security.debian.org jessie/updates/main Sources [14 B]
Get:3 http://security.debian.org jessie/updates/contrib Sources [14 B]
Get:4 http://security.debian.org jessie/updates/main amd64 Packages [14 B]
Get:5 http://security.debian.org jessie/updates/contrib amd64 Packages [14 B]
Get:6 http://security.debian.org jessie/updates/contrib Translation-en [14 B]
Get:7 http://security.debian.org jessie/updates/main Translation-en [14 B]
Fetched 84.2 kB in 5s (15.4 kB/s)     
Reading package lists... Done
debiancat@debian:~$ sudo apt-get install smartmontools
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package smartmontools
dt@debian:~$

colorpurple21859 · 12-14-2014, 09:37 PM

what happens if you unplug the cable to the debian hard drive then try to boot the slackware drive, either directly or with the slackware dvd.

Ztcoracat · 12-14-2014, 09:49 PM

Quote:

Originally Posted by colorpurple21859

what happens if you unplug the cable to the debian hard drive then try to boot the slackware drive, either directly or with the slackware dvd.

I would have to kill the power to the case and unplug the 1 TB drive and I really don't want to do that.
--That would be my last thing on my list I would want to try--
I was very careful when I installed the new 1 TB HDD.

I'm looking for the Rescue CD so I can see if the smartmontools are on the disk.

Ztcoracat · 12-14-2014, 10:20 PM

Booting the 'System Rescue CD' I choose boot into a 64 bit Linux Graphical GUI with other choices.

What can I run for you in the Rescue Terminal in order for you to get the information you need to help me?

@Ser Olmy:
I downloaded the smartmontools from the link you posted; thanks.

Ztcoracat · 12-14-2014, 10:39 PM

The Slackware partition's are there-

Ztcoracat · 12-14-2014, 11:46 PM

Quote:

Originally Posted by Ser Olmy

Well, /dev/sda is clearly there, but fdisk doesn't seem able to access it.

The drive could very well be defective. Try:

Code:

sudo smartctl -a /dev/sda

I tried running the smartcltl cmd after installing the smartmontools-

Code:

det@debian:~$ sudo smartctl -a /dev/sda
[sudo] password for debiancat: 
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16-2-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               /2:0:0:0
Product:              
Compliance:           SPC-5
User Capacity:        600,332,565,813,390,450 bytes [600 PB]
Logical block size:   774843950 bytes
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
det@debian:~$

Ser Olmy · 12-15-2014, 05:13 AM

Quote:

Originally Posted by Ztcoracat

Code:

det@debian:~$ sudo smartctl -a /dev/sda
[sudo] password for debiancat: 
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16-2-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               /2:0:0:0
Product:              
Compliance:           SPC-5
User Capacity:        600,332,565,813,390,450 bytes [600 PB]
Logical block size:   774843950 bytes
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
scsiModePageOffset: response length too short, resp_len=47 offset=50 bd_len=46
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

I think it's fairly safe to say that this drive is history.

colorpurple21859 · 12-15-2014, 05:34 AM

Quote:

I think it's fairly safe to say that this drive is history.

If it was me, I would first recheck cables, then if that doesn't work, try with the debian drive disconnected and lastly with cables installed as orginally before the debian drive was added, before calling the slackware drive dead.tt