From owner-freebsd-questions  Tue Mar 17 12:40:41 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA04050
          for freebsd-questions-outgoing; Tue, 17 Mar 1998 12:40:41 -0800 (PST)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA03879
          for <freebsd-questions@FreeBSD.ORG>; Tue, 17 Mar 1998 12:40:15 -0800 (PST)
          (envelope-from dwhite@gdi.uoregon.edu)
Received: from localhost (dwhite@localhost)
          by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id MAA01165;
          Tue, 17 Mar 1998 12:40:05 -0800 (PST)
          (envelope-from dwhite@gdi.uoregon.edu)
Date: Tue, 17 Mar 1998 12:40:05 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Greg Pavelcak <gpavelcak@philos.umass.edu>
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: Reverting to non-multi-sector mode problem
In-Reply-To: <0EPX00MIEYLQSE@pobox1.oit.umass.edu>
Message-ID: <Pine.BSF.3.96.980317123830.994Z-100000@gdi.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 16 Mar 1998, Greg Pavelcak wrote:

> I recently got a new hard drive. It's a Maxtor Diamondmax 3.2G UDMA 
> (my mobo does not support UDMA, oh well). It seems to work OK. Here's
> what dmesg says at boot: 
> 
> 
> wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa
> wdc0: unit 0 (wd0): <Maxtor 83240D3>, 32-bit, multi-block-16
> wd0: 3090MB (6328665 sectors), 6697 cyls, 15 heads, 63 S/T, 512 B/S
> 
> But after a while, I get a message like this:
> 
> wd0s1e: reverting to non-multi sector mode reading fsbn 40816 of 
> 40656-40895 (wd0s1 bn 405360; cn 25 tn 59 sn 18)wd0: 
> status 51<rdy,seekdone,err> error 4<abort>
> 
> Is this something I should worry about? As I said, it seems to be
> working, but I never see this with my other disk.

I seem to remember another Maxtor having the same problem.  I don't think
it's anything important, but you should change the flags on wdc0 to
0x800080ff to disable multi-block-IO on that drive.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major



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