Date: Sun, 27 Oct 2002 22:21:34 -0500 From: Tom Parquette <tparquet@twcny.rr.com> To: questions@freebsd.org Subject: Corrupt vinum concatenated drive -- Hardware? Message-ID: <3DBCAD3E.7030000@twcny.rr.com>
next in thread | raw e-mail | index | archive | help
I had something happen to my concatenated vinum drive.
Looking at /var/log/messages I think it may be calling out a hardware
problem on one of my drives.
This configuration has been running for a week or so without complaining.
I call myself VERY green with vinum and I would appreciate someone
looking over my sholder.
From messsages:
ad7: READ command timeout tag=0 serv=0 - resetting
ata3: resetting devices .. done
ad7: WRITE command timeout tag=0 serv=0 - resetting
ata3: resetting devices .. done
ad7: WRITE command timeout tag=0 serv=0 - resetting
ata3: resetting devices ..
ad7: removed from configuration
vinum: FreeBSD.p0.s2 is stale by force
vinum: FreeBSD.p0 is corrupt
fatal :FreeBSD.p0.s2 write error, block15846552 for 65536 bytes
FreeBSD.p0.s2: user buffer block 120283440 for 65536 bytes
vinumdrive2: fatal drive I/O error, block 15846552 for 65536 bytes
vinum: drive vinumdrive2 is down
I checked the output from disklabel -r for ad5, 6, and 7. The sizes for
vinum agree with the values for C: (I'm having problems with cut and
paste otherwise I'd provide the actual output.)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DBCAD3E.7030000>