Hi there,

hop you can help

my setup....

I have a win2k server with a 2100s SCSI Raid Card.
it has connected 2 x Fujitsu man3184mc 18.4Gb/sca2 drives
and 1 HP  C1537A tape drive.

i only have raidutil and no storage manager. i only have remote access
at present.

ive been getting 1 drive failing intermitently (twice in two weeks)
and ive rebuilt the array, which seemed to worked fine.

and my backups dont always work (tapeware) the message is "scanning for
device"

how would i go about diagnosing where the problem lies?
ive already checked the log on the card (raidutil -e d0)

and got 1 error of 0c/03 (write error - recommend reassignment)

and 2 of 29/02 (scsi bus reset occured) which seem to be around about
the time of the failed drive.

what do these mean? where do  i go to find out? is there a good reference
out there? or do i just blindly replace things till the problem goes away?

i pefer a more pragmatic approach :-)

Cheers Folks

Regards,


Russ

"Russ Lunn" <russ.lunn@hcsltd.com> wrote in message news:c664tp$igg$1$8300dec7@news.demon.co.uk
> Hi there,
> 
> hope you can help
> 
> my setup....
> 
> I have a win2k server with a 2100s SCSI Raid Card.
> it has connected 2 x Fujitsu man3184mc 18.4Gb/sca2 drives
> and 1 HP  C1537A tape drive.
> 
> i only have raidutil and no storage manager. i only have remote access
> at present.
> 
> ive been getting 1 drive failing intermittently (twice in two weeks)
> and ive rebuilt the array, which seemed to worked fine.
> 
> and my backups dont always work (tapeware) the message is "scanning for
> device"
> 
> how would i go about diagnosing where the problem lies?
> ive already checked the log on the card (raidutil -e d0)
> 
> and got 1 error of 0c/03 (write error - recommend reassignment)

Like it says, it runs into a write error to a sector and it recommends reassignment of that sector.

Your utilitie(s) should have tools to take the necessary action, either
do a reassign bad block or setting bad block reassignment to automatic.
Or you could use the sledgehammer tactic and Low Level Format the drive.

> 
> and 2 of 29/02 (scsi bus reset occured) which seem to be around about
> the time of the failed drive.

That seems drastic for a failed write so maybe the drive hang on 
the write and the driver recovered by resetting the SCSI bus.
In that case the drive may be on it's last feet.

> 
> what do these mean? where do  i go to find out? is there a good reference
> out there? or do i just blindly replace things till the problem goes away?
> 
> i prefer a more pragmatic approach :-)
> 
> Cheers Folks
> 
> Regards,
> 
> 
> Russ