Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!ns.saard.net!news.camtech.com.au!news.adelaide.on.net!news.ade.connect.com.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.cis.okstate.edu!newsfeed.ksu.ksu.edu!news.physics.uiowa.edu!math.ohio-state.edu!uwm.edu!lll-winken.llnl.gov!nntp.coast.net!news-res.gsl.net!news.gsl.net!sgigate.sgi.com!news.tamu.edu!mbreed
From: mbreed@cs.tamu.edu (Michael B. Reed)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Filesystem dying a slow painful death
Date: 23 Jun 1996 20:11:34 GMT
Organization: Texas A&M Department of Computer Engineering, College Station, TX
Lines: 106
Message-ID: <4qk8dm$mtf@news.tamu.edu>
NNTP-Posting-Host: photon.cs.tamu.edu
Recently, I found myself in the unlucky situation of having to replace
my motherboard. I managed to find a MB that was very close to the
original (about the only difference is that the BIOS is from Award;
the old one used an AMI BIOS).
The system was working fine after reassembling the other components on
the new MB. Last night, I put all the components back in the case,
exactly as I had assembled them on my desktop.
Unfortunately, something happened in the meantime, and now the wd0
device complains of timeouts at the end of the device probe sequence,
and I'm also getting hard and soft errors on the device left and
right. These errors are shown below; hopefully, this is useful info,
and I'm not just dropping core here. :)
The following are the results of the device probes, taken from
/var/log/messages, to illustrate the system configuration. The
only thing that doesn't show here is that the CPU is an i486DX/50.
(These have been edited to break at 75 cols. or so.)
-----
FreeBSD 2.1.0-RELEASE #0: Mon Jun 5 00:08:11 CDT 1995
root@dunn-163.dorms.tamu.edu:/usr/src/sys/compile/CUSTOM
CPU: i486DX (486-class CPU)
real memory = 8650752 (8448K bytes)
avail memory = 7303168 (7132K bytes)
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color <16 virtual consoles, flags=0x0>
sio0 at 0x3f8-0x3ff irq 4 flags 0x80 on isa
sio0: type 16550A
sio1: probe test 3 failed
sio1 not found at 0x2f8
lpt0 at 0x3bc-0x3c3 irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: NEC 72065B
fd0: 1.44MB 3.5in
fd1: 1.2MB 5.25in
ft0: Colorado tape
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <ST51080A>
wd0: 1033MB (2116800 sectors), 2100 cyls, 16 heads, 63 S/T, 512 B/S
matcd - Matsushita (Panasonic) CD-ROM Driver by FDIV, Version 1(26) 18-Oct-95
matcdc0 at 0x230-0x233 on isa
matcdc0 Host interface type 0
matcd0: [CR-5630.75]
1 3C5x9 board(s) on ISA found at 0x300
ep0 at 0x300-0x30f irq 10 on isa
ep0: aui/bnc/utp[*UTP*] address 00:20:af:53:43:f1 irq 10
npx0 on motherboard
npx0: INT 16 interface
BIOS Geometries:
0:03ff0f3f 0..1023=1024 cylinders, 0..15=16 heads, 1..63=63 sectors
0 accounted for
wd0s1: type 0x6, start 63, end = 122975, size 122913 : OK
wd0s2: type 0x5, start 122976, end = 799343, size 676368 : OK
wd0s3: type 0xa5, start 799344, end = 2116799, size 1317456 : OK
wd0s5: type 0x6, start 123039, end = 737855, size 614817 : OK
wd0<extended>: type 0x5, start 737856, end = 799343, size 61488 : OK
wd0s6: type 0x4, start 737919, end = 799343, size 61425 : OK
wd0a: wdstart: timeout waiting to give command reading fsbn 64 of 64-79
(wd0 bn 64; cn 0 tn 1 sn 1)wd0: status 0 error 0
-----
The last line shows the timeout that I mentioned earlier. Next comes
the messages that describe the typical soft and hard errors I get.
I've only included one of each, but they usually come in groups of
five or more.
-----
Jun 23 13:51:06 dunn-163 /kernel: wd0s3f: soft error writing fsbn 1067542
of 1067536-1067551 (wd0s3 bn 1292822; cn 1282 tn 8 sn 62)wd0: status
50<seekdone> error 10<no_id>
Jun 23 13:51:06 dunn-163 /kernel: wd0s3f: hard error writing fsbn 1067553
of 1067552-1067679 (wd0s3 bn 1292833; cn 1282 tn 9 sn 10)wd0: status
51<seekdone,err> error 10<no_id>
-----
Plus I get the occasional gem like the following:
-----
Jun 23 13:51:30 dunn-163 /kernel: free inode /usr/56464 had 160 blocks
-----
Last of all, when I issued a shutdown command, the system suffered a
panic:
-----
mode = 0140666 inum = 20 fs = /
panic: ffs_valloc : dup alloc
-----
fsck reports nothing amiss at boot time. I'm not too concerned with
the fate of this particular installation, as I was going to rework it
anyhow. For now, though, the system is in mothballs to avoid doing
having anything else happen to it - I hope. :P
Any help is greatly appreciated.
--
-Brad Reed mbreed@tamu.edu http://www.cs.tamu.edu/people/mbreed/
TAMU Prisoner, August 31, 1992 - December 20, 1996