Date: Wed, 29 Nov 2006 09:54:37 -0800 From: Chuck Swiger <cswiger@mac.com> To: Grant Peel <gpeel@thenetnow.com> Cc: freebsd-questions@freebsd.org Subject: Re: CAM Status SCSI Error Message-ID: <F28DB66F-8449-4B0D-8FB0-07B808DDCDA9@mac.com> In-Reply-To: <009401c7136d$0417a550$6501a8c0@GRANT> References: <009401c7136d$0417a550$6501a8c0@GRANT>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F28DB66F-8449-4B0D-8FB0-07B808DDCDA9>