ATARAID, IDE RAID 0, installing grub problem

Rroet

Hi,

I have ATARAID 0

running, configuring Gentoo onto it was an adventure on it's own :lol:

, but now I have a problem.

I can't get GRUB installed. It can't find my RAID 0 drive and get installed.
Please help. none of the "root (hdx,x)" devices work.

lx · Posted: Wed Jun 05, 2002 5:25 pm Post subject:

Sounds similar to this:
https://forums.gentoo.org/viewtopic.php?t=4092
then this has got something to do with it as well
https://forums.gentoo.org/viewtopic.php?p=249
_________________
"Remember there's a big difference between kneeling down and bending over.", Frank Zappa

Rroet · Posted: Wed Jun 05, 2002 5:30 pm Post subject:

ph317 · n00b Joined: 02 Jun 2002 Posts: 43

I have gentoo running good on a striped ataraid. Mine's the Promise 20276 on an ASUS A7V333 - 2x40G drives in a stripe, making one big raid disk.

It was a pain and I can't recount all of it, but here's some general things:

1) don't mount /dev into your chroot, you shouldn't need it there for anything

2) Set bios to boot the ataraid controller first, so that bios things of your array as 0x80 (bios disk 0).

3) Build a custom kernel (I used mine in a custom gentoo installer cd, as well as on the final system), make sure the ataraid stuff is compiled in hard (not modules), and that you use devfs.

4) For grub - when you get to the end of the install, isntalling Grub, don't do what install.txt says. Set up the menu.lst correctly, assuming hd0 works correctly to access the device. Install GRUB onto a floppy, and reboot from the floppy. From the grub> prompt on the floppy, then do "root (hd0,0)" and "setup(hd0)", using your own valid root/boot partition number. After that reboot off of HDD, and it should be able to find the boot partition, and do the menu, and boot your kernel just fine.

5) kernel root mount - However, with all of that alone, the kernel will still panic being unable to mount the root device. For some reason, even with devfs and non-modular kernel, adding "root=/dev/ataraid/disc0/partX" to the kernel's boot options will not work. The *only* thing that worked for me was to use the hex method, like "root=7206" - where 0x72 is hex for 114 (major number for ataraid), and 0x06 was partition 6, my root. Be sure to set this option in your kernel boot line in menu.lst before you do the grub-floppy-bootstrap thing in (4) above.

lx · Posted: Wed Jun 05, 2002 10:58 pm Post subject:

Spades · n00b Joined: 18 Apr 2002 Posts: 12

For some reason the device names for ataraid are different during boot. Instead of /dev/ataraid/discX/partX use /dev/ataraid/dXpX for the root device.

Buzzz · Posted: Fri Jun 07, 2002 6:47 pm Post subject:

I also use ataraid and I ran into the same kind of trouble. I now use lilo as bootmanager. At the point where the installation documentation starts with installing grub, I did a "emerge lilo".
I created a /etc/lilo.conf as follows:

ryandlugosz · Guest

I've been working with linux for a long time now & I wasn't about to make gentoo boot properly on an ata raid from promise using grub. As per the post above's suggestion, I used the old tried-and-true lilo instead & it worked right away!

One note though, in his lilo.conf, he uses boot=/dev/ataraid/disc0

this did not work correctly for me, however - you need to use boot=/dev/ataraid/disc0/disc

could be that something changed since july when he posted it.

-Ryan[/quote]