Timo Schoeler wrote:
> thus Damian Lubosch spake:
>> Hello!
>>
>> I need some help in building up a RAID 1 with the Intel ICH7 Chipset 
>> Controller. (Intel 82801GB/GR Serial ATA/Raid Controller (ICH7) (rev.
>>  0x01))
>>
>> I already tried it in two different ways: software RAID in NetBSD and
>>  hardware RAID using the onboard controller natively.
>>
>> In hardware RAID the installation system does not recognize the
>> harddrives in RAID-1 mode at all. In software RAID I was following
>> the very good instruction written on 
>> http://www.netbsd.org/guide/en/chap-rf.html step by step, but the
>> system is failing in the execution of the command "raidctl -F
>> component0 raid0" since there are errors like:
>>
>> wd0a: error reading fsbn 268435392 of 268435392-268435519 (wd0 bn 
>> 268435455; cn 266305 tn 0 sn 15), retrying wd0: (id not found) wd1a:
>> error reading fsbn 268435392 of 268435392-268435519 (wd1 bn 
>> 268435455; cn 266305 tn 0 sn 15)wd1: (id not found)
>>
>> after about 85% of the restore-operation.
>>
>> First, I thought that it could be some block/sector error. So I tried
>> a thrid harddrive (of same size/type) and used it in combination with
>> the first and the second harddrive and I had the same error messages.
>>  I also tried to install a clean NetBSD on the third drive and built
>> the RAID on the first two empty drives (now with raidctl -v -i raid0)
>> but with the same result.
>>
>> I attached my dmesg below.
>>
>> I hope someone can help me. Thanks in advance,
>>
>> Damian Lubosch
>>
>> [snip]
>>
>> raid0: IO Error.  Marking /dev/wd1a as failed. wd0a: error reading
>> fsbn 268435392 of 268435392-268435519 (wd0 bn 268435455; cn 266305 tn
>> 0 sn 15)wd0: (id not found)
>>
>> Unable to verify raid1 parity: can't read stripe Could not verify
>> parity raid0: Error re-writing parity!
>
> hi,
>
> have a look a
>
> http://mail-index.netbsd.org/current-users/2005/06/20/0016.html
>
> and
>
> http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/dev/ata/wd.c?rev=1.274.2.8.2.4&content-type=text/x-cvsweb-markup 
>
>
> i had the same problem, maybe your hard drive needs the same workaround?
>
> HTH,
>

Hi Timo!

That worked for me! Never again Seagate disks... Thank you a lot :-)

Damian.