Date: Sat, 03 Jun 2000 01:15:04 -0400 From: John <papalia@udel.edu> To: "Kenneth D. Merry" <ken@kdm.org> Cc: Mike Smith <msmith@FreeBSD.ORG>, John Lengeling <johnl@raccoon.com>, freebsd-scsi@FreeBSD.ORG Subject: Re: Dying connection? Message-ID: <4.3.1.2.20000603011132.00ad6e80@mail.udel.edu> In-Reply-To: <20000602224404.A7506@panzer.kdm.org> References: <4.3.1.2.20000603004007.00ae3100@mail.udel.edu> <4.3.1.2.20000603003152.00adfbd0@mail.udel.edu> <4.3.1.2.20000602013902.00ae1330@mail.udel.edu> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > >So you probably don't need to add anything to your kernel config file,
> > > > >unless you don't have the pass(4) driver configured. (You can't
> get the
> > > > >defects list off the drive with camcontrol(8) without it.)
> > > >
> > > > So, to address curiosity, I recompiled with the pass device in the
> > > > kernel. Now, using "camcontrol defects -f phys -P", I get the
> following
> > > > nice long list. Does it mean anything in the end run? Also, from
> within
> > > > the Adaptec SCSI bios, if I run their "media check", all turns up ok.
> > >
> > >The -P argument to the defects subcommand gives you the permanent defect
> > >list, which is created at the factory. It is a list of blocks that were
> > >bad when the disk was manufactured. Your list is fairly short.
> > >
> > >If you use the -G argument, you get the grown defect list, which is the
> > >list if defects that have popped up since the drive left the factory. If
> > >you use both -P and -G, you'll get both lists at the same time.
> >
> > Ah..... ok. My mistake. Retrying, I get:
> >
> > merlin# camcontrol defects -f phys -G
> > Got 0 defects.
> >
> > So now, is that a good thing, or a bad thing?
>
>It's good, probably. You might have defects, but the drive may not have
>remapped them.
>
> > 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).
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 :)
Thanks,
John
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?4.3.1.2.20000603011132.00ad6e80>