Date: Fri, 28 Feb 1997 13:07:33 -0600 (CST) From: David Kelly <dkelly@HiWAAY.net> To: questions@freebsd.org Subject: Is this a failing HD? Message-ID: <199702281907.NAA22738@fly.HiWAAY.net>
next in thread | raw e-mail | index | archive | help
The following messages appeared today on one of my FreeBSD systems. Is this
a symptom of a failing HD or was there something broken in -current as of
Feb 5? Wouldn't think -current was broken as this is system was up for over
20 trouble free days.
Sitting in the room I heard a HD spinning up and down and up. Noticed
messages on the console. System seemed ok, so I tried "find / -name junk".
Kernel panic 12 sometime after find moved over to a SCSI drive. Swap is on
the problem drive.
PeeCee: {1005} uname -a
FreeBSD PeeCee.tbe.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Wed Feb 5
13:06:39 CST 1997 dkelly@PeeCee.tbe.com:/usr/src/sys/compile/PEECEE
i386
clipped from dmesg:
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <Conner Peripherals 510MB - CP3541>
wd0: 486MB (996912 sectors), 989 cyls, 16 heads, 63 S/T, 512 B/S
I don't believe this is an IDE HD that has a power saving mode. Have
been running FreeBSD on it for a couple of years.
>From /var/log/message:
Feb 28 11:14:00 PeeCee /kernel: wd0a: wdstart: timeout waiting to give
command writing fsbn 304 of 304-319 (wd0 bn 304; cn 0 tn 4 sn 52)wd0:
status 80<busy> error 0
Feb 28 11:14:38 PeeCee /kernel: wd0: interrupt timeout:
Feb 28 11:14:39 PeeCee /kernel: wd0: status 58<rdy,seekdone,drq> error
1<no_dam>
Feb 28 11:15:16 PeeCee /kernel: wd0: interrupt timeout:
Feb 28 11:15:17 PeeCee /kernel: wd0: status 58<rdy,seekdone,drq> error
1<no_dam>
Feb 28 11:16:27 PeeCee /kernel: wd0a: wdstart: timeout waiting to give
command writing fsbn 16 of 16-19 (wd0 bn 16; cn 0 tn 0 sn 16)wd0: status
80<busy> error 1 <no_dam>
Feb 28 11:16:31 PeeCee /kernel: wd0: wdunwedge failed:
Feb 28 11:16:31 PeeCee /kernel: wd0: status 50<rdy,seekdone> error 0
Feb 28 11:16:31 PeeCee /kernel: wd0a: wdstart: timeout waiting for DRQ
writing fsbn 17 of 16-19 (wd0 bn 17; cn 0 tn 0 sn 17)wd0: status
50<rdy,seekdone> error 0
Feb 28 11:17:51 PeeCee /kernel: wd0: wdunwedge failed:
Feb 28 11:18:13 PeeCee /kernel: wd0: status 50<rdy,seekdone> error 0
Feb 28 11:18:13 PeeCee /kernel: wd0: wdunwedge failed:
Feb 28 11:18:13 PeeCee /kernel: wd0: status 50<rdy,seekdone> error 0
Feb 28 11:27:52 PeeCee /kernel: wd0: wdunwedge failed:
Feb 28 11:27:57 PeeCee /kernel: wd0: status 50<rdy,seekdone> error 0
Feb 28 11:36:41 PeeCee /kernel: wd0a: wdstart: timeout waiting to give
command writing fsbn 304 of 304-319 (wd0 bn 304; cn 0 tn 4 sn 52)wd0:
status 80<busy> error 1<no_dam>
Feb 28 11:36:50 PeeCee /kernel: wd0: wdunwedge failed:
Feb 28 11:36:50 PeeCee /kernel: wd0: status 50<rdy,seekdone> error 0
Feb 28 11:36:50 PeeCee /kernel: wd0a: wdstart: timeout waiting for DRQ
writing fsbn 305 of 304-319 (wd0 bn 305; cn 0 tn 4 sn 53)wd0: status
80<busy> error 0
There were several others in the logs but these were the first. Others only
differ in fsbn and bounce between status 50 and 58.
--
David Kelly N4HHE, dkelly@tomcat1.tbe.com (wk), dkelly@hiwaay.net (hm)
======================================================================
The human mind ordinarily operates at only ten percent of its
capacity -- the rest is overhead for the operating system.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702281907.NAA22738>