Adam PAPAI writes: > Greg Oster wrote: > > Adam PAPAI writes: > > > >>Hello misc, > >> > >>I have an IBM xSeries 335 machine with Dual Xeon processor and 2x73GB > >>SCSI Seagate Barracuda 10K rpm disc. I run OpenBSD 3.8 on it. > >> > >>When I'm creating the raid array (raidctl -iv raid0), I get the > >>following error message: > >> > >>sd0(mpt0:0:0): Check Condition (error 0x70) on opcode 0x28 > >> SENSE KEY: Media Error > >> INFO: 0x224c10c (VALID flag on) > >> ASC/ASCQ: Read Retries Exhausted > >> SKSV: Actual Retry Count: 63 > >>raid0: IO Error. Marking /dev/sd0d as failed. > >>raid0: node (Rod) returned fail, rolling backward > >>Unable to verify raid1 parity: can't read stripe. > >>Could not verify parity. > > > > > > Is this early in the initialization or late in the initialization? > > > > Try doing: > > > > dd if=/dev/rsd0d of=/dev/null bs=10m > > > > and see if you get the same error message... > > > # dd if=/dev/rsd0d of=/dev/null bs=10m > 6977+1 records in > 6977+1 records out > 73160687104 bytes transferred in 1043.771 secs (70092636 bytes/sec) > # dd if=/dev/rsd1d of=/dev/null bs=10m > 6977+1 records in > 6977+1 records out > 73160687104 bytes transferred in 1027.051 secs (71233712 bytes/sec) > # > > This means no hdd error..
Well... no hdd error for this set of reads... Hmmmmm.... What if you push both drives at the same time: dd if=/dev/rsd0d of=/dev/null bs=10m & dd if=/dev/rsd1d of=/dev/null bs=10m & ? (Were the drives "warm" when you did this test, and/or when the original media errors were reported? Does a 'raidctl -iv raid0' work now or does it still trigger an error? ) > Then probably the raidFrame has the problem I guess.. RAIDframe doesn't know anything about SCSI controllers or SCSI errors... all it knows about are whatever VOP_STRATEGY() happens to return to it from the underlying driver... > I have to use /altroot on /dev/sd1a then, or is there a patch for > raidframe to fix this? There is no patch for RAIDframe to fix this. There is either a problem with the hardware (most likely), some sort of BIOS configuration issue (is it negotiating the right speed for the drive?), or (less likely) a mpt driver issue. Once you figure out what the real problem is and fix it, RAIDframe will work just fine :) Later... Greg Oster
