Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

Hi,
I'm running a P4P800 Deluxe with 4 Maxtor 200GB disks as RAID 0+1. One disk  
failed and was replaced by the same type. But the synchronization of this  
new disk fails every time I try to start it (doesn't matter if I use the  
controller bios or the Via raid tool). Synchronization of the other disk on  
the same channel works properly.
Already changed the Master/Slave settings on the disks of the channel and  
checked the cable.
I'm using the latest via drivers for the 6410 and the 1019 BIOS on the  
board.
 
Any ideas?
 
Thanks in advance
Timo

Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

You have checked the new hd using Maxtor disk utility?
 
"Timo Lamm" <dastas@gmx.net> wrote in message
news3lhu1$jhq$01$1@news.t-online.com...
> Hi,
> I'm running a P4P800 Deluxe with 4 Maxtor 200GB disks as RAID 0+1. One
disk
> failed and was replaced by the same type. But the synchronization of this
> new disk fails every time I try to start it (doesn't matter if I use the
> controller bios or the Via raid tool). Synchronization of the other disk
on
> the same channel works properly.
> Already changed the Master/Slave settings on the disks of the channel and
> checked the cable.
> I'm using the latest via drivers for the 6410 and the 1019 BIOS on the
> board.
>
> Any ideas?
>
> Thanks in advance
> Timo
>
>

Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

This is where raid vendors need to splash out on some diagnostic s/w.
I suggest a google on raid 1 failures, but at the end of the day you can:
- guess based on google results,
- backup the files and rebuild the raid from scratch starting with a new  
raid volume,
- hassle the vendor.
 
I would do all 3 and work on #2 pending results of #3.
 
This makes borked raid 1 #4 in 2 weeks.
 
 
"Timo Lamm" <dastas@gmx.net> wrote in message  
news3lhu1$jhq$01$1@news.t-online.com...
> Hi,
> I'm running a P4P800 Deluxe with 4 Maxtor 200GB disks as RAID 0+1. One  
> disk failed and was replaced by the same type. But the synchronization of  
> this new disk fails every time I try to start it (doesn't matter if I use  
> the controller bios or the Via raid tool). Synchronization of the other  
> disk on the same channel works properly.
> Already changed the Master/Slave settings on the disks of the channel and  
> checked the cable.
> I'm using the latest via drivers for the 6410 and the 1019 BIOS on the  
> board.
>
> Any ideas?
>
> Thanks in advance
> Timo
>

Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

You should be aware that a raid built with a specific manu.controler is
specific to that controler.
ie another manu raid controler may not even see the raid, if it does data
corruption / loss may result. Nore is it likely anothers raid diagnostics
software will diagnose any other than their own controllers raid
 
"Mercury" <me@spam.com> wrote in message news3qsbs$pr$1@lust.ihug.co.nz...
> This is where raid vendors need to splash out on some diagnostic s/w.
> I suggest a google on raid 1 failures, but at the end of the day you can:
> - guess based on google results,
> - backup the files and rebuild the raid from scratch starting with a new
> raid volume,
> - hassle the vendor.
>
> I would do all 3 and work on #2 pending results of #3.
>
> This makes borked raid 1 #4 in 2 weeks.
>
>
> "Timo Lamm" <dastas@gmx.net> wrote in message
> news3lhu1$jhq$01$1@news.t-online.com...
> > Hi,
> > I'm running a P4P800 Deluxe with 4 Maxtor 200GB disks as RAID 0+1. One
> > disk failed and was replaced by the same type. But the synchronization
of
> > this new disk fails every time I try to start it (doesn't matter if I
use
> > the controller bios or the Via raid tool). Synchronization of the other
> > disk on the same channel works properly.
> > Already changed the Master/Slave settings on the disks of the channel
and
> > checked the cable.
> > I'm using the latest via drivers for the 6410 and the 1019 BIOS on the
> > board.
> >
> > Any ideas?
> >
> > Thanks in advance
> > Timo
> >
>
>

Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

I am more than aware of this - there needs to be industry standardisation on  
the storage / format of raid meta data with the objective that the drives  
and raid configs become h/w vendor independant.
EG pull out a raid array from one manufacturers controller and plug itinto  
anothers and have it work 100% - so long as the two controller implement the  
same raid type and options.
 
The issues that seem to be arising are where a drive in a mirror fails, but  
the 'good' drive that is left is not in fact good. An IBM OEM Adaptec  
contoller failure recently complained of this and the solution provided by  
IBM was a file level backup restore. I have also read 3 other failures that  
sound quite similar, although the controllers offer no evidence. The  
manifestation is failure to recreate the RAID 1 after some % of processing.
 
A good volume in a raid should be able to be scanned and volume format  
errors corrected - meta data that is used by the controller being optionally  
corrected. A bit like a chkdsk /f.
 
Obviously, every manufacturers controller diagnostics will be controller  
specific. More info is needed.
 
"MrGrumpy" <dl@spoofmail.notme> wrote in message  
news:v088e.33787$pA6.26182@newsfe1-win.ntli.net...
> You should be aware that a raid built with a specific manu.controler is
> specific to that controler.
> ie another manu raid controler may not even see the raid, if it does data
> corruption / loss may result. Nore is it likely anothers raid diagnostics
> software will diagnose any other than their own controllers raid
>
> "Mercury" <me@spam.com> wrote in message  
> news3qsbs$pr$1@lust.ihug.co.nz...
>> This is where raid vendors need to splash out on some diagnostic s/w.
>> I suggest a google on raid 1 failures, but at the end of the day you can:
>> - guess based on google results,
>> - backup the files and rebuild the raid from scratch starting with a new
>> raid volume,
>> - hassle the vendor.
>>
>> I would do all 3 and work on #2 pending results of #3.
>>
>> This makes borked raid 1 #4 in 2 weeks.
>>
>>
>> "Timo Lamm" <dastas@gmx.net> wrote in message
>> news3lhu1$jhq$01$1@news.t-online.com...
>> > Hi,
>> > I'm running a P4P800 Deluxe with 4 Maxtor 200GB disks as RAID 0+1. One
>> > disk failed and was replaced by the same type. But the synchronization
> of
>> > this new disk fails every time I try to start it (doesn't matter if I
> use
>> > the controller bios or the Via raid tool). Synchronization of the other
>> > disk on the same channel works properly.
>> > Already changed the Master/Slave settings on the disks of the channel
> and
>> > checked the cable.
>> > I'm using the latest via drivers for the 6410 and the 1019 BIOS on the
>> > board.
>> >
>> > Any ideas?
>> >
>> > Thanks in advance
>> > Timo
>> >
>>
>>
>
>

Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

"Mercury" <me@spam.com> writes:
> The issues that seem to be arising are where a drive in a mirror fails, but  
> the 'good' drive that is left is not in fact good. An IBM OEM Adaptec  
> contoller failure recently complained of this and the solution provided by  
> IBM was a file level backup restore. I have also read 3 other failures that  
> sound quite similar, although the controllers offer no evidence. The  
> manifestation is failure to recreate the RAID 1 after some % of processing.
>
> A good volume in a raid should be able to be scanned and volume format  
> errors corrected - meta data that is used by the controller being optionally  
> corrected. A bit like a chkdsk /f.
>
> Obviously, every manufacturers controller diagnostics will be controller  
> specific. More info is needed.
 
Well, I've been able to recover a failed disk in a software RAID 1
array under Linux, but I've yet to be able to recover a failed disk in
an onboard RAID 1 array under WinXP.  You don't always get what you
pay for!!
 
--  
Forte International, P.O. Box 1412, Ridgecrest, CA  93556-1412
Ronald Cole <ronald@forte-intl.com>      Phone: (760) 499-9142
President, CEO                             Fax: (760) 499-9152
My GPG fingerprint: C3AF 4BE9 BEA6 F1C2 B084  4A88 8851 E6C8 69E3 B00B