New Harddrive + grub = problems

[JoeDuncan]

Ok, this is the story:

I bought a new hardrive (Maxtor DiamondMax 9 Plus 160 GB IDE ATA/133) and a new PCI controller card to use it (Promise Ultra 133 TX2).

I have a dual boot, Windows 2000/Gentoo system.

I installed the card, booted to Windows 2000, installed the driver, shutdown, hooked up the drive and rebooted to Windows 2000. Windows detected the drive no problem, but could not format it. No problem, I figured I'd format it in Linux.

So, I rebooted into Linux, but my kernel didn't have the driver for the card. The card showed up in dmesg, proc /cat/pci and lspci, and it worked in Win2000, so I know the hardware is ok.

I re-configured the kernel to use the CONFIG_BLK_DEV-PDC202XX_NEW (driver for the promise card) option and I re-compiled the kernel (2.4.28-gentoo-r8).

There were no errors in the compile and this is like the 10th time I've recompiled the kernel for this box, so I know what I'm doing in this respect.

After re-compiling the kernel I copied it over to /boot, along with the System.map and config files. I didn't change the kernel number or file name, so I didn't edit grub.conf.

When I rebooted, however, all I got after the BIOS screens was:

GRUB

And nothing else, it just sat there.

The Ultra 133 TX2 is not a RAID card, and I'm not trying to setup RAID, I just need more storage. Also, I'm not planning on switching to the 2.6 kernel any time soon, my system is (well was) working perfectly fine as it is, and I don't have the time to spend right now reconfiguring everything else for a 2.6 kernel, I just need to get the system booting and the drive working.

Any ideas?

Thanks!

[Matrix905]

Hey

I have the same card the 133 TX2 by promise however when I had HDDs attached to it Gentoo had problems using the HDDs attached to it however, after I moved my optical drives on to the Promise card and the HDDs on to the main IDE chains then everything was working fine. Also you might want to check in BIOS that the drive you're actually booting off is the one that GRUB is configured to boot off of. If your BIOS is set to another drive then GRUB won't find your kernel.

Hope this helps some

- M -

[JoeDuncan]

Ok, but if I'm getting the "GRUB" message, then the BIOS must be trying to boot from the drive that has grub installed correct?

This is also the same drive that grub should be booting from, so how come grub can't find it's own drive?

If it was a problem with finding the kernel, shouldn't I at least get the OS selection screen and be able to select an OS before it fails to find the kernel?

Thanks!