From owner-freebsd-stable Wed Oct 25 6:55:38 2000 Delivered-To: freebsd-stable@freebsd.org Received: from yez.hyperreal.org (unknown [212.85.16.153]) by hub.freebsd.org (Postfix) with SMTP id 0A38937B479 for ; Wed, 25 Oct 2000 06:55:30 -0700 (PDT) Received: (qmail 1747 invoked by uid 1001); 25 Oct 2000 13:55:05 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 25 Oct 2000 13:55:05 -0000 Date: Wed, 25 Oct 2000 06:55:05 -0700 (PDT) From: Brian Behlendorf X-Sender: brian@yez.hyperreal.org To: Elliot Finley Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 4.1.1 and ad0 write errors. In-Reply-To: <39fdc3f2.122211392@mail.afnetinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Oct 2000, Elliot Finley wrote: > You can see what access mode your drives are using by typing 'sysctl > hw.atamodes'. You can downgrade the access mode of your drives by > using 'sysctl -w hw.atamodes'. See 'man ad' for details. yez# sysctl hw.atamodes hw.atamodes: pio,---,---,---, > I've downgraded the access mode on my drive from dma to pio and it > seems to be running fine, albeit a little slower. Sounds like there's nothing to downgrade to. :/ It also looks like I'm getting some general disk corruption at this point; needed to fsck -y this morning to get it to boot, and it nuked a lot of stuff from /usr, causing me to make world again (kinda fun to do while giving a presentation, yay!). I'm still seeing those messages, as well as crap like Oct 25 06:39:46 yez /kernel: ad0: timeout waiting for DRQ - resetting Oct 25 06:39:46 yez /kernel: ata0: resetting devices .. done Oct 25 06:45:27 yez /kernel: ad0: WRITE command timeout tag=0 serv=0 - resetting Oct 25 06:45:27 yez /kernel: ata0: resetting devices .. done I suspect it's more a bad disk now, though, if others aren't seeing exactly this. It's RELENG_4 cvsup'd as of this morning. Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message