>
> The hardware is a Tyan 1U rackmount, 2.4 P4, 1GB DDR, two 120GB IDE
> disks in
> RAID1 (Promise FastTrack controller onboard). Hardware
worked before
> for months, no problem. All fans ok, so overheating does
not seem like
> a possibility. The only changed variable is the upgrade from RH9 to
> FC1. However, same behaviour with very different kernels, that also
> confuses me. Some quirk with glibc maybe?
>
> Anyone here experiencing something similar? Any thoughts? Before i
> switch back to RH9 and see if it helps..
>
> Thanks in advance
>
>
Promise Fastrack RAID is your culprit.
Forget using any parallel ATA RAID product made from Promise with
Linux.
I've been round and round this subject, and the best they give you
is source code, but how can you build the source when there's no drive
recognized. I recommend going to 3WARE for any ATA RAID (SATA or
parallel) with Linux.
I hear that Promise SATA is supported in the kernel by default, but if
you've got what I think you've got, you're probably want to use the
on-motherboard Promise RAID chipsets. This server is best relegated
to becoming a Windows server if you want RAID with the Promise
chipset.
Select your hardware carefully.....
I'm not crazy about these controllers too, but nevertheless i can't forget that
it worked just fine before with RH9, with whatever kernel i'd throw in it.
Just as long as you compile Promise's partial source code of the driver using
the new kernel's source, and then make sure you have a properly created initrd
image for module loading on boot. Just like i do now with FC1.
I have two other identical machines using this controller with no problem,
difference is that they still run RH9.
And this also happens with the same exact kernels used when running RH9, still
there on /boot...
For this, i do not think Promise controller is the culprit. It was there
before.
BC
--
fedora-list mailing list
fedora-list(a)redhat.com
To unsubscribe:
http://www.redhat.com/mailman/listinfo/fedora-list
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.