Piete Brooks <[EMAIL PROTECTED]> writes:
> Exec summary: will raid1 code cause read error sectors to be
> re-vectored ? Full gory details: I am having problems with some new
> disks, in that sectors are going bad. I kind of didn't expect this
> on `new' disks, but maybe I'm just not used to having so many
> sectors !
> So far, the problems have always been in `unused' areas of disk, so
> every once in a while I read all my disks, and process the errors I
> spot. I have a perl script which seeks to the suspect sector on the
> other RAID1 disk, reads the data it has, then seeks to the sector on
> the suspect disk, tries a read, and if that fails, writes the data
> from the other disk.
[...]
> Another disk works fine for a while, then reports: SCSI disk error :
> host 1 channel 0 id 3 lun 0 return code = 28000002 [valid=0] Info
> fld=0xbe7e, Current sd08:30: sense key Hardware Error Additional
> sense indicates Mechanical positioning error scsidisk I/O error: dev
> 08:30, sector 48766
> until I power cycle it, at which point it works
> just fine. Is this a common failure mode ?
Piete,
Common failure modes with SCSI disks are cables longer than specified
(especially with a bunch of disks like in a RAID), improper
termination and intermittant connecting connectors.
Johannes Niess
