R
Rod Speed
Colonel Blip said:
Yes, tho I'd personally boot a BART PE CD with Everest
on it just so the raid doesnt start chucking a wobbly about
one of the raid drives being missing etc.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Yes, tho I'd personally boot a BART PE CD with Everest
on it just so the raid doesnt start chucking a wobbly about
one of the raid drives being missing etc.
F
Folkert Rienstra
Rod Speed said:Yes, tho I'd personally boot a BART PE CD with Everest
on it just so the raid doesnt start chucking a wobbly about
one of the raid drives being missing etc.
It will do that anyway if it's hardware/firmware RAID, clueless.
More than one, so it appears.
C
Colonel Blip
Hello, Arno!
You wrote on 25 Feb 2006 16:08:13 GMT:
AW> You should. That is the point of RAID1, after all. If this does not
AW> wotk, you should throw away the controller and get one that works.
AW> And this should still work with the OS on the RAID array as well.
AW> The only possible problem I see with OS on the array is that if
AW> you remove one drive from the RAID and connect it to a regular
AW> controller, your BIOS could decide to boot from the single
AW> drive instead of from the (degraded, but functionsl) RAID array.
They are RAID0, not RAID1. Also, my system can boot off of 3 different
partitions each containing winxp; 2 of them are on the raid drives but the
3rd once is on my root IDE drive so it should boot fine. I'm just not sure
how it will deal with ONE drive on the RAID0 controller, whether it will
even see it or if it will somehow put garbage on the drive.
The more I think about this, since I regularly back up my array, even if
data is destroyed on the drive in the test I have full image backups to
restore it.
Thanks,
Colonel Blip.
E-mail: (e-mail address removed)
You wrote on 25 Feb 2006 16:08:13 GMT:
AW> You should. That is the point of RAID1, after all. If this does not
AW> wotk, you should throw away the controller and get one that works.
AW> And this should still work with the OS on the RAID array as well.
AW> The only possible problem I see with OS on the array is that if
AW> you remove one drive from the RAID and connect it to a regular
AW> controller, your BIOS could decide to boot from the single
AW> drive instead of from the (degraded, but functionsl) RAID array.
They are RAID0, not RAID1. Also, my system can boot off of 3 different
partitions each containing winxp; 2 of them are on the raid drives but the
3rd once is on my root IDE drive so it should boot fine. I'm just not sure
how it will deal with ONE drive on the RAID0 controller, whether it will
even see it or if it will somehow put garbage on the drive.
The more I think about this, since I regularly back up my array, even if
data is destroyed on the drive in the test I have full image backups to
restore it.
Thanks,
Colonel Blip.
E-mail: (e-mail address removed)
C
Colonel Blip
Hello, Rod!
You wrote on Sun, 26 Feb 2006 05:57:42 +1100:
Good thought. Can't recall if I've already created one some time back. If
not, easy enuf to do.
Thanks,
Colonel Blip.
E-mail: (e-mail address removed)
RS> Yes, tho I'd personally boot a BART PE CD with Everest
RS> on it just so the raid doesnt start chucking a wobbly about
RS> one of the raid drives being missing etc.
You wrote on Sun, 26 Feb 2006 05:57:42 +1100:
Good thought. Can't recall if I've already created one some time back. If
not, easy enuf to do.
Thanks,
Colonel Blip.
E-mail: (e-mail address removed)
RS> Yes, tho I'd personally boot a BART PE CD with Everest
RS> on it just so the raid doesnt start chucking a wobbly about
RS> one of the raid drives being missing etc.
R
Rod Speed
It will do that anyway if it's hardware/firmware RAID, clueless.
Thanks for that completely superfluous proof that you have
never ever had a ****ing clue about anything at all, ever.
C
Colonel Blip
Hello, Rod!
You wrote on Sun, 26 Feb 2006 05:57:42 +1100:
I just bit the bullet and disconnected one drive and rebooted. Bios message
gave me 3 choices; power down and fix the drive; destroy the array; or
continue booting. I chose the latter. However, one can not see the drive
when that choice is made.
As it turns out there is a Via Raid tool that comes with the motherboard so
I installed and ran it. It shows one drive in danger of losing data and
which drive in the array so I least I know the culprit in this case.
Since I keep good backups and may just let it run to failure and then go to
warranty repair if it lasts less than warranty time.
Thanks,
Colonel Blip.
E-mail: (e-mail address removed)
RS> Yes, though I'd personally boot a BART PE CD with Everest
RS> on it just so the raid doesnt start chucking a wobbly about
RS> one of the raid drives being missing etc.
You wrote on Sun, 26 Feb 2006 05:57:42 +1100:
I just bit the bullet and disconnected one drive and rebooted. Bios message
gave me 3 choices; power down and fix the drive; destroy the array; or
continue booting. I chose the latter. However, one can not see the drive
when that choice is made.
As it turns out there is a Via Raid tool that comes with the motherboard so
I installed and ran it. It shows one drive in danger of losing data and
which drive in the array so I least I know the culprit in this case.
Since I keep good backups and may just let it run to failure and then go to
warranty repair if it lasts less than warranty time.
Thanks,
Colonel Blip.
E-mail: (e-mail address removed)
RS> Yes, though I'd personally boot a BART PE CD with Everest
RS> on it just so the raid doesnt start chucking a wobbly about
RS> one of the raid drives being missing etc.
R
Rod Speed
Colonel Blip said:Hello, Rod!
You wrote on Sun, 26 Feb 2006 05:57:42 +1100:
I just bit the bullet and disconnected one drive and rebooted. Bios
message gave me 3 choices; power down and fix the drive; destroy the
array; or continue booting. I chose the latter. However, one can not see
the drive when that choice is made.
OK, you clearly could have destroyed the array since you had
it imaged, run everest on the drives when there is no raid.
As it turns out there is a Via Raid tool that comes with the
motherboard so I installed and ran it. It shows one drive in danger of
losing data and which drive in the array so I least I know the culprit in
this case.
I'd rather see the SMART data when you have a situation
where two drives appear to have gone bad at the same
time, one in the RAID and one not in the RAID.
Thats a bit suspicious, tho its certainly possible and one of the
bads is a maxtor which dont like running inadequately cooled.
Since I keep good backups and may just let it run to failure and then go
to warranty repair if it lasts less than warranty time.
I wouldnt myself with the drive in a raid0 and one
other drive looking rather dubious with lots of
reallocated sectors and it being a maxtor.
Thanks,
Thanks for the washup, too rare in my opinion.
C
Colonel Blip
Hello, Rod!
You wrote on Sun, 26 Feb 2006 05:57:42 +1100:
One final point (I think <g>) on this. I created a BartPE boot and gave this
a try. Unfortunately neither drive in the array is recognized.
Thanks,
Colonel Blip.
E-mail: (e-mail address removed)
RS> Yes, tho I'd personally boot a BART PE CD with Everest
RS> on it just so the raid doesnt start chucking a wobbly about
RS> one of the raid drives being missing etc.
You wrote on Sun, 26 Feb 2006 05:57:42 +1100:
One final point (I think <g>) on this. I created a BartPE boot and gave this
a try. Unfortunately neither drive in the array is recognized.
Thanks,
Colonel Blip.
E-mail: (e-mail address removed)
RS> Yes, tho I'd personally boot a BART PE CD with Everest
RS> on it just so the raid doesnt start chucking a wobbly about
RS> one of the raid drives being missing etc.
R
Rod Speed
Colonel Blip said:Hello, Rod!
You wrote on Sun, 26 Feb 2006 05:57:42 +1100:
One final point (I think <g>) on this. I created a BartPE boot and
gave this a try. Unfortunately neither drive in the array is recognized.
OK, thanks for that feedback.