On Monday 19 November 2007 12:35:14 am Billy Holmes wrote:
Jeff Cranmer wrote:
Cannot open root device sda3 or unknown block (0,0)
Please append a correct root= boot option.
Here are the available partitions
run make menuconfig in your new kernel dir.
check to ensure ext3 is compiled in. (not sure why it wouldn't be)
ext3 journalling file system support, ext3 extended attributes and ext3 posix
access control lists are all compiled into the kernel.
check to make sure you've got udev or devfs installed properly in both
kernels (maybe one isn't defined in the kernel, and the old kernel had
it). I'd really try to ensure you're running udev and not devfs, but
first things first.
IF SATA:
Make sure the proper SATA options are the same for each kernel. There's
one SATA option that isn't compatible with another SATA option. (it
could be fixed in newer kernels by now)
From dmesg for the current working kernel, I worked out that the drive which
it is having trouble finding is a serial ATA drive, running the sata_nv
driver.
Vendor: ATA Model: WDC WD2500JS-60N Rev: 10.0
Type: Direct-Access ANSI SCSI revision: 05
I disabled all the SATA drivers except for the nvidia one, and have made some
progress.
The kernel now finds the drive, but for some reason puts a little 8MB drive at
sda, and populates the 'real' 250MB drive at sdb, so the kernel still panics
(probably due to fstab wanting to see the main drive at sda, not sdb).
I'd like to get a log of this, but dmesg only shows the log of the kernel that
boots. Does anyone have any suggestions of how to get at the log for a
panicking kernel, or have any suggestions on how to fix this. I suspect the
I may be able to play with fstab and get the new kernel to boot, but I'm
loath to do this, as that will most likely break the kernel that is working,
so if it doesn't simultaneously fix the non-working kernel, I'm toast.
Any suggestions gratefully received.
---
--
[EMAIL PROTECTED] mailing list
