Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 2 Jun 2000 23:26:37 -0600
From:      "Kenneth D. Merry" <ken@kdm.org>
To:        John <papalia@udel.edu>
Cc:        Mike Smith <msmith@FreeBSD.ORG>, John Lengeling <johnl@raccoon.com>, freebsd-scsi@FreeBSD.ORG
Subject:   Re: Dying connection?
Message-ID:  <20000602232637.B7954@panzer.kdm.org>
In-Reply-To: <4.3.1.2.20000603011132.00ad6e80@mail.udel.edu>; from papalia@udel.edu on Sat, Jun 03, 2000 at 01:15:04AM -0400
References:  <Your <4.3.1.2.20000602012826.00ad4e90@mail.udel.edu> <200006020538.WAA01381@mass.cdrom.com> <4.3.1.2.20000602013902.00ae1330@mail.udel.edu> <20000601235026.A98092@panzer.kdm.org> <4.3.1.2.20000603003152.00adfbd0@mail.udel.edu> <20000602223457.A7354@panzer.kdm.org> <4.3.1.2.20000603004007.00ae3100@mail.udel.edu> <20000602224404.A7506@panzer.kdm.org> <4.3.1.2.20000603011132.00ad6e80@mail.udel.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jun 03, 2000 at 01:15:04 -0400, John wrote:
> > > And does that ultimately take
> > > into account all errors encountered since the drive left the factory, but
> > > before I configure the "pass" device?
> >
> >It includes all remapped blocks since the drive left the factory.  The pass
> >device doesn't affect it.
> >
> >You'll probably want to make sure you've got read and write reallocation
> >turned on for the drive.  To check it:
> >
> >{panzer:/usr/home/ken:1:0} camcontrol modepage da1 -m 1
> >AWRE (Auto Write Reallocation Enbld):  1
> >ARRE (Auto Read Reallocation Enbld):  1
> >[ ... ]
> >
> >Those two parameters should be set to 1.  They tell the drive to
> >automatically remap a bad block to a spare sector when it finds the block
> >on either a read or a write.
> 
> Ahhhhhhhh. Very interesting.  Crash courses in learning tend to teach a 
> lot.  I'm curious though about the variable EER (Enable Early 
> Recovery).  From a cursory interpretation of the variable name, it would 
> make sense to be set on.  From a realism stance though, should it be? (Mine 
> is currently 0).

I don't know what it does, I'd suggest looking at the SCSI draft specs at
www.t10.org, specifically at the block command specifications.

> So now, with all this information at hand, does this still point to 
> possible hard drive going back in terms of the original SCSI Bus error 
> which I was receiving? Even if it doesn't, i can definitely say the 
> experience has taught a lot :)

It could be, although I would still say you need to check your cabling and
termination, just in case.  And make sure you have a backup.  Then if your
drive goes out, you haven't lost much.  (That's a good policy whether or
not you think your drive is having trouble.)

Ken
-- 
Kenneth Merry
ken@kdm.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000602232637.B7954>