From owner-freebsd-questions Fri Aug 25 09:25:31 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id JAA14132 for questions-outgoing; Fri, 25 Aug 1995 09:25:31 -0700 Received: from rflab1.gtri.gatech.edu (rflab1.gtri.gatech.edu [130.207.199.83]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id JAA14120 for ; Fri, 25 Aug 1995 09:25:29 -0700 Received: (from ken@localhost) by rflab1.gtri.gatech.edu (8.6.12/8.6.12) id MAA23842; Fri, 25 Aug 1995 12:25:08 -0400 From: "Kenneth D. Merry" Message-Id: <199508251625.MAA23842@rflab1.gtri.gatech.edu> Subject: Re: Adaptec 2842, Quantum XP34300 problem To: gibbs@freefall.FreeBSD.org (Justin T. Gibbs) Date: Fri, 25 Aug 1995 12:25:07 -0400 (EDT) Cc: questions@freebsd.org In-Reply-To: <199508251444.HAA05513@freefall.FreeBSD.org> from "Justin T. Gibbs" at Aug 25, 95 07:44:00 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1511 Sender: questions-owner@freebsd.org Precedence: bulk > >ahc1: target 0, lun 0 (sd0) timed out > >sd0(ahc1:0:0): BUS DEVICE RESET message queued. > >ahc1: target 0, lun 0 (sd0) timed out > >ahc1: Issued Channel A Bus Reset #1. 1 SCBs aborted > >panic: ahc1: brkadrint, Illegal Host Access at seqaddr = 0x0 > The "brkadrint" is a bug. The messages above it should be enough > to find the problem. Cool....let me know if you track down the problem...I'll be glad to test things out... > > So, I'm not sure whether this is a hardware problem, or a software > >problem, or what. > The grand prixs are very touchy little drives. We had three die with > similar behavior patterns to what you describe here. Although it > may be a driver problem, it sounds like the drive just didn't like it > when you accessed a particular sector. Actually, the drive is an Atlas, not a Grand Prix. (The XP34300 is an Atlas, the XP34301 is a Grand Prix...) Of course, the problem may not be limited to the Grand Prix drives...:( > > I wasn't running the -current ahc1 driver when I did the backup, so > >the error messages aren't as verbose as they might be. So, if anyone has > >any idea how I might at the very least diagnose what kind of problem my > >drive has, and hopefully be able to fsck the entire thing, I'd be very > >grateful. > The overlapped commands errors should not occur with the -current driver. > You should be using that. Thanks for your help. Ken -- Kenneth Merry ken@rflab1.gtri.gatech.edu Disclaimer: I don't speak for GTRI, GT, or Elvis.