Steve & Dee McInerney wrote:
Have you considered:All,
First off I have not yet been able to successfully get RH8 up on a FastTrack TX2 system. But I have had some minor success in getting close.
In the interests of helping us all slowly get there: I'll share what I've got so far.
1)Installing the system without the mirror, creating a mirror in the bios, and then switching over to the ataraid devices.
2)Installing the system onto a single drive while the mirror is active. Switching to F2 at the end and copying the contents of the 1st drive to the 2nd. Then loading the module, and mounting the ataraid device, and reinstalling your boot loader onto the ataraid device.
3)Creating 2 individual drives in the promise bios, and using software raid. This is what I do.
1. 1st off, you will need a RH8 system elsewhere, or the ability to get certain RH8 files
Specifically, create a floppy disk (or similar) with:
ataraid.o & pdcraid.o from the redhat rpm "kernel-BOOT-2.4.18-14"
You will also need "MAKEDEV" from /dev.
as well as (easist) the contents of /etc/makedev.d
Are you sure mknod /tmp/ataraid/d0 (and c0p1...) doesn't work. Or "mknod /tmp/d0 b 114 0", "mknod /tmp/d0p1 b 114 1"
2. Boot of the RH8 install CD. at the boot prompts, type in your normal "append" string.
for my system this is:
linux ide0=0x1f0,0x3f6,14 ide1=0x170,0x376,15 ide2=0x9400,0x9002,10 ide3=0x8800,0x8402,10
3. Wait a while while the red hat install boots and starts 4. Skip over the CD checking
5. Should now start booting X.... 6. With X now up, press CTRL-ALT-F2 to drop to a console
7. I'll give the commands I used, but the gist is to install the raid modules, and create the missing devices.
mkdir /tmp/a mount /dev/fd0 /tmp/a ln -s /tmp/a/makedev.d /etc/makedev.d insmod /tmp/a/ataraid.o insmod /tmp/a/pdcraid.o /tmp/a/makedev ataraid
8. At this point you can now mount and manipulate your existing /dev/ataraid/d0px partitions. Unf this is about as far as I've been able to successfully get.
The RH installer won't recognise the partitions as existing - for either upgrading or installing
I tried dropping to the shell and mounting the existing partitions under /mnt/sysimage (which is where the RH upgrader expects them to be), unf this causes a fatal error and a nearly immediate reboot. sigh.
I'm thinking that somehow we need to get past the GUI disk partitioner's, and then we should be cruising. Unf the author(s) of the GUI have made our lives difficult by not allowing us to specify non-std partitions. :-(
We may be able to get past by messing around with Kickstart or similar - still looking....
Your issue is the installer doesn't know what to do with the ataraid devices. You'd need to modify a bunch of code in the installer. Then you'd need to deal with the fact that the installer will want to use the actual disks as well.
