Date: Thu, 29 May 2003 14:26:43 EST From: Andrea Venturoli <ml.ventu@flashnet.it> To: freebsd-questions@freebsd.org Subject: Is my HD broken? Message-ID: <200305291226.h4TCQi1W004100@soth.ventu>
next in thread | raw e-mail | index | archive | help
>From daily security mails of a FreeBSD 4.7 server I manage, I got, 9 days ago:
> (da3:sym0:0:3:0): READ(10). CDB: 28 0 3 93 83 48 0 0 10 0
> (da3:sym0:0:3:0): HARDWARE FAILURE info:393834f asc:40,85
> (da3:sym0:0:3:0): Diagnostic failure: ASCQ = Component ID
> vinum: vinum0.p1.s0 is crashed by force
> vinum: vinum0.p1 is faulty
> fatal:vinum0.p1.s0 read error, block 59474697 for 8192 bytes
> vinum0.p1.s0: user buffer block 59474432 for 8192 bytes
> vinum: vinum0.p1.s0 is stale by force
I did vinum start vinum0.p1 and everything went as good as expected.
Yesterday I got it once more:
> (da3:sym0:0:3:0): READ(10). CDB: 28 0 4 3c a1 c8 0 0 10 0
> (da3:sym0:0:3:0): HARDWARE FAILURE info:43ca1c8 asc:40,85
> (da3:sym0:0:3:0): Diagnostic failure: ASCQ = Component ID
> vinum: vinum0.p1.s0 is crashed by force
> vinum: vinum0.p1 is faulty
> fatal:vinum0.p1.s0 read error, block 70558089 for 8192 bytes
> vinum0.p1.s0: user buffer block 70557824 for 8192 bytes
> vinum: vinum0.p1.s0 is stale by force
I'm doing vinum start right now and I'm quite sure it will work ok.
However, I'm a little worried: can my disk be broken?
It's pretty new and still under warranty, so I'd like to change it before anything breaks badly, *if it is*.
Can I possibly blame the controller (it's a Tekram DC-390U2W)? Wouldn't it be strange, since it's always the same HD
(out of 4) that shows this problem?
Any diagnostic tool I can use?
bye & Thanks
av.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305291226.h4TCQi1W004100>