>
> I recently had this happen to me on an 8 x 1 TB RAID-5 array on a
> Highpoint RocketRAID 2340 controller. For some unknown reason two drives
> developed unreadable sectors within hours of each other. To make a long
> story short, the way I "fixed" this was to:
>
Not FreeBSD related, s
Ryan Coleman wrote:
> Jun 4 23:02:28 testserver kernel: ar0: 715425MB RAID5 (stripe 64 KB)> status: READY
> Jun 4 23:02:28 testserver kernel: ar0: disk0 READY using ad13 at
ata6-slave
> Jun 4 23:02:28 testserver kernel: ar0: disk1 READY using ad16 at
ata8-master
> Jun 4 23:02:28 testserver ke
Tuc at T-B-O-H.NET wrote:
Ryan Coleman wrote:
Ryan Coleman wrote:
Oh, I completely forgot to ask...
Does the RAID still operate even though one disk is bad?
A year later, and I finally decided to buy a few more disks
off ebay to see if my final theory is right. I win (hopefully)
>
>
> > Ryan Coleman wrote:
> >>> Ryan Coleman wrote:
> >
> > Oh, I completely forgot to ask...
> >
> > Does the RAID still operate even though one disk is bad?
> >
> > After all, that is the purpose of RAID-5. stripe, with parity. One
> > fails, the other two (or N) keep right on going...
> >
>
> Ryan Coleman wrote:
>>> Ryan Coleman wrote:
> Ryan Coleman wrote:
>>> Oh, I completely forgot to ask...
>>>
>>> Does the RAID still operate even though one disk is bad?
>>>
>>> After all, that is the purpose of RAID-5. stripe, with parity. One
>>> fails, the other two (or N) keep right on go
Ryan Coleman wrote:
Ryan Coleman wrote:
Ryan Coleman wrote:
Oh, I completely forgot to ask...
Does the RAID still operate even though one disk is bad?
After all, that is the purpose of RAID-5. stripe, with parity. One
fails, the other two (or N) keep right on going...
Or, is it a RAID-5 card
Ryan Coleman wrote:
Ryan Coleman wrote:
and my tech said "that's a bad sign, you're toast"
and left me hanging.
Knowing you spanned the drives without parity or backup, there is no
need for me to review the errors.
I agree with your tech. Unless there is a miracle (or you outsource the
> Ryan Coleman wrote:
>>> Ryan Coleman wrote:
>
> Oh, I completely forgot to ask...
>
> Does the RAID still operate even though one disk is bad?
>
> After all, that is the purpose of RAID-5. stripe, with parity. One
> fails, the other two (or N) keep right on going...
>
> Or, is it a RAID-5 card t
> Ryan Coleman wrote:
>>> Ryan Coleman wrote:
Is there a way to figure out what order drives were supposed to go in
for
a RAID 5? Using a hex tool?
>>> Do you mean that you physically unplugged them, and they were not
>>> labeled?
>>>
>>> What kind of disk controller is it?
>
>> It'
Ryan Coleman wrote:
Ryan Coleman wrote:
Oh, I completely forgot to ask...
Does the RAID still operate even though one disk is bad?
After all, that is the purpose of RAID-5. stripe, with parity. One
fails, the other two (or N) keep right on going...
Or, is it a RAID-5 card that you put into
Ryan Coleman wrote:
Ryan Coleman wrote:
Is there a way to figure out what order drives were supposed to go in
for
a RAID 5? Using a hex tool?
Do you mean that you physically unplugged them, and they were not labeled?
What kind of disk controller is it?
It's a HighPoint pATA controller, one
> Ryan Coleman wrote:
>> Is there a way to figure out what order drives were supposed to go in
>> for
>> a RAID 5? Using a hex tool?
>
> Do you mean that you physically unplugged them, and they were not labeled?
>
> What kind of disk controller is it?
>
> Technically, AFAIK, the order should not m
Ryan Coleman wrote:
Is there a way to figure out what order drives were supposed to go in for
a RAID 5? Using a hex tool?
Do you mean that you physically unplugged them, and they were not labeled?
What kind of disk controller is it?
Technically, AFAIK, the order should not matter. The stripe
13 matches
Mail list logo
