Hi Paul, I recently installed some shiny new SATA drives, and haven't been able to boot into BDI since -- the 2.6.16.20-rtai kernel seems not to recognize them. Any idea how I could fix that? I can boot slax with a 2.6.16 kernel, or bdi 4.51 anaconda, and those both give me access to the BDI partition on the new drive. Thanks, Matt
Hi Matt On Monday 02 April 2007 03:38, Matt Timmermans wrote:
I recently installed some shiny new SATA drives, and haven't been able to boot into BDI since -- the 2.6.16.20-rtai kernel seems not to recognize them.
I recently added a SATA drive to my desktop/dev system over christmas and it appeared as /dev/sda*. Must admit, the boot partition is still on an IDE drive - Another box that uses all SCSI drives boots OK, so based on the assumption that SATA emulates SCSI, I would have expected the current BDI-4 kernel to work.
Any idea how I could fix that? I can boot slax with a 2.6.16 kernel, or bdi 4.51 anaconda, and those both give me access to the BDI partition on the new drive.
A couple of questions - Was this a fresh install with grub being installed in the MBR or was it copied over from an IDE partition wholesale ? MoBo specs and chipset ? (The JMicron chipset needs 2.6.18 or later to work properly, although I don't think that is an issue here.) Regards, Paul.
I recently added a SATA drive to my desktop/dev system over christmas and it appeared as /dev/sda*. Must admit, the boot partition is still on an IDE drive - Another box that uses all SCSI drives boots OK, so based on the assumption that SATA emulates SCSI, I would have expected the current BDI-4 kernel to work.
Oh, that's encouraging. I'm getting a kernel panic because it can't find /dev/sda2 to mount the root FS. If the modules are there, though, maybe I can get it to work with an initrd.
A couple of questions - Was this a fresh install with grub being installed in the MBR or was it copied over from an IDE partition wholesale ?
I replicated the partition from the old IDE drive and made a GRUB boot disk. When it didn't work, I put an upgraded kernel and modules from the DBI 4.51 next to the old ones in /boot and /lib so I can try booting either kernel.
MoBo specs and chipset ? (The JMicron chipset needs 2.6.18 or later to work properly, although I don't think that is an issue here.)
It's an Asus P4C800 with intel 875P: http://www.asus.com/products4.aspx?l1=3&l2=12&l3=30&model=176&modelmenu=1 I'm going to see if I can figure out how to get that initrd thing working. Cheers, Matt
On Monday 02 April 2007 15:07, Matt Timmermans wrote:
Oh, that's encouraging. I'm getting a kernel panic because it can't find /dev/sda2 to mount the root FS. If the modules are there, though, maybe I can get it to work with an initrd.
I kinda wondered if that was what you'd done.. The problem is the initrd.img doesn't contain all the modules needed run SATA or SCSI drives..
I'm going to see if I can figure out how to get that initrd thing working.
`mkinitrd -o /boot/initrd.img-2.6.16.20-rtai 2.6.16.20-rtai` should do it. The problem is how to run the command when the system won't boot.. If you can boot from either the BDI-4 CD or another partition, then try mounting the BDI-4 partition. With the partition mounted, try chrooting in to the mount point and running mkinitrd." Regards, Paul.
participants (2)
-
Matt Timmermans -
Paul