bad disk discovery

[Scott Long]

Hi,

If your situation is accurate and the disk is not responding properly to regular
commands then it’s unlikely that it will respond to SMART commands either.
Sometimes these situations are caused by a bad cable, bad controller, or
buggy software/firmware, and only rarely will the standard statistics in SMART
pick up these kinds of errors.  SMART is better at tracking wear rates and
error rates on the physical media, both HDD and SSD, but even then it’s hard
for it to be accurately predictive or even accurately diagnostic.  For your case,
I recommend that you describe your hardware and software configuration in
more detail, and look for physical abnormalities in the cabling and connections.
Once that is ruled and and the rest of us know what kind of hardware you’re
dealing with, we might be able to make better commendations.

Scott

> On Dec 7, 2015, at 11:07 AM, prateek sethi <prateekrootkey at gmail.com> wrote:
> 
> Hi ,
> 
> Is there any way or tool to find out that a disk which is not responding
> properly is really bad or not? Sometimes I have seen that there is lot of
> CDB error for a drive and system reboot makes every thing fine. What can be
> reasons for such kind of scenarios?
> 
> I know smartctl is the one which can help. I have some couple of question
> regarding this .
> 
> 1. What if disk does not support smartctl?
> 2. How I can do smartest use of smartctl command like which parameters can
> tell that the disk is actually bad?
> 3. What other test I can perform to make it sure that disk has completely
> gone?
> 
> 
> Please tell me correct place to ask this question if I am asking at wrong
> place.
> _______________________________________________
> freebsd-scsi at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-scsi
> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe at freebsd.org"