LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Debian
User Name
Password
Debian This forum is for the discussion of Debian Linux.

Notices


Reply
  Search this Thread
Old 07-21-2006, 11:08 AM   #1
czezz
Member
 
Registered: Nov 2004
Distribution: Slackware/Solaris
Posts: 924

Rep: Reputation: 43
kernel panic


I have an old HP NetServer E60 with SCSI: Adaptec aic7895 ultra scasi adapter and DEBIAN on board.

I was trying to move disk (/dev/sda) from that old HP to much more newer machine HP Proliabt ML 150 with SCSI Adaptec AIC 79xx PCI-X SCSI HBA DRIVER Rev.1.3.10.

...but when I connected it to the newer machine during booting I saw:
Code:
VFS: Cannot open root device "802" or 08:02
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 08:02
What cause that problem and what does it mean ?
Is that incompatibile SCSI controller or lack of driver/module inside kernel ?


PS.
here is /etc/fstab of it:
Code:
/dev/sda2       /               reiserfs        defaults        0       0
/dev/sda1       none            swap    sw                      0       0
proc            /proc           proc    defaults                0       0
/dev/fd0        /floppy         auto    user,noauto             0       0
/dev/cdrom      /cdrom          iso9660 ro,user,noauto          0       0

that may be useful:
Code:
# cat /etc/apt/sources.list
deb http://ftp.pl.debian.org/debian/ stable main
deb-src http://ftp.pl.debian.org/debian/ stable main
deb http://security.debian.org/ stable/updates main

# uname -a
Linux myserver 2.4.24 #1 SMP Sat Jan 31 11:00:37 CET 2004 i686 unknown

Last edited by czezz; 07-21-2006 at 11:18 AM.
 
Old 07-21-2006, 12:43 PM   #2
jonaskoelker
Senior Member
 
Registered: Jul 2004
Location: Denmark
Distribution: Ubuntu, Debian
Posts: 1,524

Rep: Reputation: 47
As the error message says, append the proper "root=" argument when booting the kernel.

That means:
  • Go edit your /etc/lilo.conf or your /boot/grub/menu.lst (depending on which you use).
  • change root=/dev/hda1 to root=/dev/sda2 (most likely).
And you're done.

If you use lilo, it may be nontrivial to boot with an alternative root= parameter, so you may have to revert to your old configuration in order to boot.

If my procedure doesn't work, describe why, and post the relevant config file.
 
Old 07-21-2006, 01:47 PM   #3
czezz
Member
 
Registered: Nov 2004
Distribution: Slackware/Solaris
Posts: 924

Original Poster
Rep: Reputation: 43
jonaskoelker,
please take a look at my 1st post where /etc/fstab is listed:

Code:
/dev/sda2       /               reiserfs        defaults        0
and here is what stands in /etc/lilo.conf
Code:
# more /etc/lilo.conf
lba32
boot=/dev/sda
root=/dev/sda2
install=/boot/boot-menu.b
map=/boot/map
delay=20
default=Linux
image=/vmlinuz
        label=Linux
        read-only
#       restricted
#       alias=1

image=/vmlinuz.old
        label=LinuxOLD
        read-only
        optional
#       restricted
#       alias=2
Basicly this drive boots with no problem at old server.
When I put it to a new one ( NO changing configuration), then I see errors as I mention.

This is SCSI drive so no reason for using /dev/hda1 as u sugested.
It is alredy set as /dev/sda
 
Old 07-22-2006, 08:18 AM   #4
jonaskoelker
Senior Member
 
Registered: Jul 2004
Location: Denmark
Distribution: Ubuntu, Debian
Posts: 1,524

Rep: Reputation: 47
Your lilo.conf looks fine. That leaves me out of ideas. Sorry.
 
Old 07-22-2006, 09:55 AM   #5
Dutch Master
Senior Member
 
Registered: Dec 2005
Posts: 1,686

Rep: Reputation: 124Reputation: 124
Lilo doesn't look that fine... The boot option refers to the disk, not a partition But I'm using Grub, no real experience with Lilo

Last edited by Dutch Master; 07-22-2006 at 09:58 AM.
 
Old 07-23-2006, 06:18 AM   #6
czezz
Member
 
Registered: Nov 2004
Distribution: Slackware/Solaris
Posts: 924

Original Poster
Rep: Reputation: 43
Ok I figured out that issue.
The problem was with kernel that hasn't support other AIC SCSI controler. I have recompiled kernel adding Adaptec AIC79xx U320 support. And that's all.
 
  


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
Kernel 2.4 in Zipslack (Waring: unable to open an initial console | Kernel Panic...) kurtamos Linux - General 2 05-10-2006 12:58 PM
kernel panic: try passing init= option to kernel...installation with Red Hat 9 kergen Linux - Hardware 1 09-30-2004 03:28 AM
Kernel panic puts me in a panic theeeg Linux - Software 2 07-31-2004 04:46 PM
kernel panic (narius panic) narius Linux - Newbie 3 06-20-2002 03:56 PM
Kernel panic making me panic! Linux_N0oby Linux - Software 19 05-29-2002 12:31 AM

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

All times are GMT -5. The time now is 03:29 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