Kernel panics when booting off SCSI
From: Joel Barker (jobagard-maya_at_yahoo.com)
To: firstname.lastname@example.org Date: Mon, 22 Aug 2005 08:48:58 -0700
I have been using two hard drives, an old IDE mounted at / and a brand new
SCSI mounted on /home. A few days ago the IDE drive died. Fortunately, I had
just copied all the data over to the SCSI drive (/dev/sda1). But when I try
to boot off the SCSI drive, I get the following messags:
Freeing unused kernel memory: 152k freed
NET: Registered protocol family 1
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE2: IDE controller at PCI slot 0000:00:09.0
NFORCE2: chipset revision 162
NFORCE2: not 100% native mode: will probe irqs later
NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
hdc: OPTORITECD-RW CW5201, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
pivot_root: No such file or directory
/sbin/init: 432: cannot open dev/console: No such file
Kernel panic - not syncing: Attempted to kill init!
Here are the commands I'm using in GRUB to boot:
root (hd0,0) <--- this is the scsi disk
kernel /vmlinuz root=/dev/sda1 ro
I tried building a new initrd (mkinitrd) with 'scsi_mod', 'sd_mod' and
'sr_mod' added to /etc/mkinitrd/modules, but no improvement. I then built an
initrd with nearly all the modules from `lsmod` (except a few I was sure
weren't needed, like soundcore) added to /etc/mkinitrd/modules. I got a few
more messages when I tried to boot ("USB Mass Storage support
registered"), but had the exact same error.
I am using Debian 3.1.
/sbin/init exists on both /dev/sda1 and the initrd.
So does /dev/console.
I DID specify the correct kernel version when building the initrd.
If possible, I would like a solution short of recompiling the kernel.
-- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact email@example.com