Thanks for the info. I don't actually want to use RAID, real or otherwise,
on this machine. I'm more interested in just making the system recognize
the two IDE channels that the "raid" chip controls, and allowing me to use
them for a boot harddrive.
I've attached the complete output from lspci. However, I believe the
following line is the one of interest:
0000:04:06.0 Mass storage controller: Integrated Technology Express, Inc.
IT/ITE
8212 Dual channel ATA RAID controller (PCI version seems to be IT8212,
embedded
seems (rev 11)
On 6/12/06, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
First off, its not a real raid, its a fake raid. Search for SATA raid
linux on google, you'll see that 95% of raid controllers are not really
raid controllers. Certain Intel, Adataptec and 3ware are real
controllers.
All the RAID chip on the mobo does (for Windows) is make it appear as a
logical volume. You're much better off using SW RAID, there may be an
'ataraid' driver to support the BIOS' fakeraid chip, but I wouldn't
recommend it. I'd use SW RAID1 if I were you.
Also, you may want to run lspci from command line to show us what kind of
RAID you are talking about (chipset-wise).
Justin.
On Mon, 12 Jun 2006, ChadDavis wrote:
> I have a Gigabyte mother board that has second and third IDE channels
that
> are controlled by an onboard RAID chip. The chip is a Gigabyte deal I
> think. In the bios, I can configure the RAID controller to simply view
the
> channels as IDE/ATA ( the chip only supports harddrives ). I moved my
> harddrive over to the second channel and tried to boot. The boot
seeemed to
> be going okay until the root file system was mounted and then the boot
hung.
>
> Here's my guesses about what is going on.
>
> 1) I assume that the bios boot processing works fine because it has
> nothing to do with linux, it just goes and gets the boot stuff from the
> harddrive.
>
> 2) the kernel is in memory becuase it was done in step one
>
> 3) when the kernel, linux itself, tries to read the harddrive ( after
> mounting the root file system ) it can't do it
>
> 4) my guess is that linux needs a driver to control their proprietary
> chip? Does this sound accurate to those more knowledgeable than myself?
>
> Please let me know if my guesses about what is happening seem on the
mark.
> Also, please give advice on how to proceed.
>
> Chad
>
On 6/12/06, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
First off, its not a real raid, its a fake raid. Search for SATA raid
linux on google, you'll see that 95% of raid controllers are not really
raid controllers. Certain Intel, Adataptec and 3ware are real
controllers.
All the RAID chip on the mobo does (for Windows) is make it appear as a
logical volume. You're much better off using SW RAID, there may be an
'ataraid' driver to support the BIOS' fakeraid chip, but I wouldn't
recommend it. I'd use SW RAID1 if I were you.
Also, you may want to run lspci from command line to show us what kind of
RAID you are talking about (chipset-wise).
Justin.
On Mon, 12 Jun 2006, ChadDavis wrote:
> I have a Gigabyte mother board that has second and third IDE channels
that
> are controlled by an onboard RAID chip. The chip is a Gigabyte deal I
> think. In the bios, I can configure the RAID controller to simply view
the
> channels as IDE/ATA ( the chip only supports harddrives ). I moved my
> harddrive over to the second channel and tried to boot. The boot
seeemed to
> be going okay until the root file system was mounted and then the boot
hung.
>
> Here's my guesses about what is going on.
>
> 1) I assume that the bios boot processing works fine because it has
> nothing to do with linux, it just goes and gets the boot stuff from the
> harddrive.
>
> 2) the kernel is in memory becuase it was done in step one
>
> 3) when the kernel, linux itself, tries to read the harddrive ( after
> mounting the root file system ) it can't do it
>
> 4) my guess is that linux needs a driver to control their proprietary
> chip? Does this sound accurate to those more knowledgeable than myself?
>
> Please let me know if my guesses about what is happening seem on the
mark.
> Also, please give advice on how to proceed.
>
> Chad
>