Date: 14 Mar 2000 14:52:59 -0500 From: Chris Shenton <cshenton@uucom.com> To: freebsd-questions@freebsd.org Subject: Dump reports read errors on SCSI disk Message-ID: <lfwvn5gwh0.fsf@Samizdat.uucom.com>
next in thread | raw e-mail | index | archive | help
Been noticing that "dump" (run nightly from Amanda) has been reporting read errors on a 9GB Seagate Barracuda (SCSI UW on Adaptec 2940[W?]): DUMP: 73.47% done, finished in 0:23 DUMP: read error from /dev/rda0s1h: Input/output error: [block 10833238]: count=5120 DUMP: read error from /dev/rda0s1h: Input/output error: [sector 10833241]: count=512 DUMP: read error from /dev/rda0s1h: Input/output error: [block 10839330]: count=7168 DUMP: read error from /dev/rda0s1h: Input/output error: [sector 10839336]: count=512 DUMP: 77.29% done, finished in 0:20 DUMP: 83.79% done, finished in 0:14 DUMP: read error from /dev/rda0s1h: Input/output error: [block 11640074]: count=3072 DUMP: read error from /dev/rda0s1h: Input/output error: [sector 11640076]: count=512 DUMP: 90.27% done, finished in 0:08 DUMP: 97.41% done, finished in 0:02 DUMP: DUMP: 3273041 tape blocks DUMP: finished in 5206 seconds, throughput 628 KBytes/sec DUMP: level 0 dump on Tue Mar 14 05:14:40 2000 Does this indicate my drive is toast, or getting toasted? Is there a way to map out defective sectors (I thought SCSI did this by itself)? I'll try and track the errors: if the sector/block are not consistent from run to run could it be a termination problem? Thanks. 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?lfwvn5gwh0.fsf>