Re: CAM Status SCSI Error
On Nov 28, 2006, at 8:15 PM, Grant Peel wrote: Could not get anywhere with fsck. Kept Saying 'rerun fsck manually' which I did. Got the thing up anmd running using the SCSI verify media Utility in the bios. showned one error when it ran, maked the block as bad. fsck shows all f/s clean now. LOts of verbage found on google, but nothing that explained anything well. Disk is about 2 years old, not under heavy load.FreeBSD 6.1 Should I replace? (Seagate Cheetah SCSI 3 73 GIG). or is this 'normal' once in a while? While bad sectors occur over time, they aren't normal. You should install smartmontools (assuming you run FreeBSD 5.x or later) and have it run a drive self-test, and monitor the counts of bad sectors being reallocated and other errors. If you don't see anything bad and no additional bad sectors appear over the next few weeks, you can probably live with it as an isolated incident. Of course, you should also be prepared to recover your data from backups in case the drive decides to die completely, as it may do just that... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CAM Status SCSI Error
Hi all, Server crashed. /var/log/messages shows this started Tues Afternoon: . Nov 27 23:20:40 defiant kernel: (da0:ahc0:0:0:0): Retries Exhausted Nov 27 23:20:40 defiant kernel: g_vfs_done():da0s1f[READ(offset=48365768704, length=2048)]error = 5 Nov 27 23:25:54 defiant proftpd[863]: defiant.thenetnow.com - MaxInstances (30) reached, new connection denied Nov 27 23:25:55 defiant last message repeated 35 times Nov 27 23:26:21 defiant kernel: (da0:ahc0:0:0:0): READ(10). CDB: 28 0 7 61 69 c7 0 0 4 0 Nov 27 23:26:21 defiant kernel: (da0:ahc0:0:0:0): CAM Status: SCSI Status Error Nov 27 23:26:21 defiant kernel: (da0:ahc0:0:0:0): SCSI Status: Check Condition Nov 27 23:26:21 defiant kernel: (da0:ahc0:0:0:0): MEDIUM ERROR info:76169c9 asc:11,0 Nov 27 23:26:21 defiant kernel: (da0:ahc0:0:0:0): Unrecovered read error field replaceable unit: e4 actual retry count: 142 Could not get anywhere with fsck. Kept Saying 'rerun fsck manually' which I did. Got the thing up anmd running using the SCSI verify media Utility in the bios. showned one error when it ran, maked the block as bad. fsck shows all f/s clean now. LOts of verbage found on google, but nothing that explained anything well. Disk is about 2 years old, not under heavy load.FreeBSD 6.1 Should I replace? (Seagate Cheetah SCSI 3 73 GIG). or is this 'normal' once in a while? -Grant ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"