From owner-freebsd-questions Tue Aug 18 13:04:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17919 for freebsd-questions-outgoing; Tue, 18 Aug 1998 13:04:21 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from galois.tf.or.jp (ppp142121.asahi-net.or.jp [202.213.142.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17904 for ; Tue, 18 Aug 1998 13:04:13 -0700 (PDT) (envelope-from tfuruya@ppp142121.asahi-net.or.jp) Received: from galois.tf.or.jp (localhost.tf.or.jp [127.0.0.1]) by galois.tf.or.jp (8.8.8/3.6W-ht5t-fry@asahi-net-98073004) with ESMTP id EAA05880; Wed, 19 Aug 1998 04:17:27 +0900 (JST) Message-Id: <199808181917.EAA05880@galois.tf.or.jp> To: thelab@nmarcom.com Cc: freebsd-questions@FreeBSD.ORG Cc: Tetsuro FURUYA Subject: Re: wd0 interrupt From: Tetsuro FURUYA In-Reply-To: Your message of "Tue, 18 Aug 1998 10:19:41 -0400 (EDT)" References: X-Mailer: Mew version 1.54 on Emacs 19.28.1, Mule 2.3 X-fingerprint: F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 X-URL: http://sodan.komaba.ecc.u-tokyo.ac.jp/~tfuruya/ Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 19 Aug 1998 04:17:27 +0900 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm T.Furuya. In Message-ID: The Lab wrote: > > From /var/log/messages: > > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 520MB (1065456 sectors), 1057 cyls, 16 heads, 63 S/T, 512 B/S > wdc0: unit 1 (wd1): > wd1: 4110MB (8418816 sectors), 14848 cyls, 9 heads, 63 S/T, 512 B/S > npx0 flags 0x1 on motherboard > npx0: 387 emulator > wd0: interrupt timeout: > wd0: status 58 error 0 > > Can anyone tell me what the last two lines mean, exactly, and what i can > do to prevent it if it's a really bad thing? Your system does not seem to hangup. So, this is rather good. But this makes problem difficult to solve. When the sector on wd0 is broken, the last two error messages will appear in /var/log/messages. So, If you can check the secter is really broken or not, it will help solve this problem, for example, check the disk by windows scandisk or norton utilities, or write to all of vacant disk area and read all file. They say that the recent eide disks are implemented the automatic remapping function, in this case, so even if the sectors are actually broken, they are substituted, no bad secters may be found. If you cannot access that disk after the error message, probably, wd driver does no work well. So, check /usr/src/sys/i386/isa/wd.c, and find out the lines such as du->dk_timeout = 1 + 3; and increase the value. There are several views that the failure of disk is cause by the heat or the unstable power supply. Tetsuro Furuya ======================================================================== TEL: 048-852-3520 FAX: 048-858-1597 || E-Mail: 8==------ ht5t-fry@asahi-net.or.jp , tfu@ff.iij4u.or.jp * || pgp-fingerprint: \|/ pub Tetsuro FURUYA Key fingerprint = F1 BA 5F C1 C2 48 1D C7 AE 5F 16 ED 12 17 75 38 ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message