RAID 0 troubles

[sparka]

First off, let me state that I am dual booting Windows XP and Linux (with GRUB)

Well, currently I'm trying to create a RAID 0 (striping) array on two 160gb SATA drives merely for storage (not booting) on ports 3 and 4.

The problem I'm having is that the computer tries to boot from the RAID array or something like that and GRUB complains with an error 5.
Deleting the array works fine, and GRUB loads perfectly.

Any ideas on what could be causing this??
Thanks

 

[Fullmetal Chocobo]

Originally posted by: sparka
First off, let me state that I am dual booting Windows XP and Linux (with GRUB)

Well, currently I'm trying to create a RAID 0 (striping) array on two 160gb SATA drives merely for storage (not booting) on ports 3 and 4.

The problem I'm having is that the computer tries to boot from the RAID array or something like that and GRUB complains with an error 5.
Deleting the array works fine, and GRUB loads perfectly.

Any ideas on what could be causing this??
Thanks

There should be options for making the array bootable (or not). Also, have you checked the boot priority in your BIOS after creating the array?

PS -- RAID 0 for a storage array is a very bad choice. If you must combine the drives, atleast use JBOD. If you don't need the size (ie: if you have 2 200gb hds, and you don't need a 400gb partition), then just store data on the drives seperately, no RAID.

 

[sparka]

Thanks for the reply,

JBOD fails as well with the same error.
What's weird is that the boot priority shows the array as last.
Basically it is the same boot order with the addition of the array at the bottom

My thoughts are that as the array is added, the hard drive names (/dev/hda, /dev/hdb) are altered, therefore making GRUB point to a location that doesn't exist.

Suggestions??
Thanks

 

[Fullmetal Chocobo]

Originally posted by: sparka
Thanks for the reply,

JBOD fails as well with the same error.
What's weird is that the boot priority shows the array as last.
Basically it is the same boot order with the addition of the array at the bottom

My thoughts are that as the array is added, the hard drive names (/dev/hda, /dev/hdb) are altered, therefore making GRUB point to a location that doesn't exist.

Suggestions??
Thanks

Did you check the boot settings for the RAID controller? Also have you checked for bugs with that mobo / chipset regarding RAID? And are you using the most current BIOS available for the board?

 

[sparka]

Yes, i've checked the RAID boot settings
There isn't really known issues concerning my motherboard and RAID
Yes, My BIOS is the latest revision

 

[Fullmetal Chocobo]

Do you haev INT13 enabled or disabled? (and does the mobo RAID controller support it?)

EDIT: Is your boot drive in SATA port 1? Or is it IDE?

 

[sparka]

INT13?
I couldn't find anything even related to that in my BIOS. Any ideas on where to find it?
And my boot drive is IDE

Thanks

EDIT: My BIOS is phoenix awardbios if that makes a difference

To the poster below: Thanks for pointing that out, I understand now and am trying to use a JBOD array instead.

 

[amdskip]

Let me again point out what someone already mentioned. DO NOT USE RAID 0 for storage. Raid 0 is for speed increases only, not storage.

 

[Cr0nJ0b]

If your controller is like mine, you can set the RAID group as bootable...or not. Make sure it's not set to bootable...and of course make sure that your primary is set as the first boot device.

 

[Fullmetal Chocobo]

OP, can you post a link to your mobo (or the manual, specifically), and I'll dig through there...

 

[sparka]

Yes, my raid controller does allow an array to be bootable or not, i've already tried that.
I have it selected as not bootable, but rebooting the computer changes it to bootable for some unknown reason.

As for the link to my motherboard manual:
Epox 9NPA+ Ultra

Thanks for all your help guys!