From owner-freebsd-scsi@freebsd.org  Mon Dec  7 18:07:36 2015
Return-Path: <owner-freebsd-scsi@freebsd.org>
Delivered-To: freebsd-scsi@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 615629B9DA2
 for <freebsd-scsi@mailman.ysv.freebsd.org>;
 Mon,  7 Dec 2015 18:07:36 +0000 (UTC)
 (envelope-from prateekrootkey@gmail.com)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com
 [IPv6:2a00:1450:400c:c09::22a])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 049FC1740
 for <freebsd-scsi@freebsd.org>; Mon,  7 Dec 2015 18:07:36 +0000 (UTC)
 (envelope-from prateekrootkey@gmail.com)
Received: by wmww144 with SMTP id w144so161166345wmw.0
 for <freebsd-scsi@freebsd.org>; Mon, 07 Dec 2015 10:07:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=xwXWvN/YiQRCHuZmYzWalb4mhhztTLMe0O/K4TR8xG0=;
 b=kxz9WNhGnn514G5COhc13y6h+GBNiKw1JAuOr5P7gtxh7sOlf8VfcUYidnXALnVjrY
 JGDHmD7cCWT1CbvH+7eYvcJJoW22nMIbRNpI68wPKNH4mw93E75kz53eQRC2xL/L0DmT
 WhcxWVYl/nVaqdi0ytW/ktMQilELA0wMimYLBYSlJhsvdZyegmnBPkQ/4+SucqQp1rTf
 cHXK1N1BaXgbnWEjngaBLDacT9t5SOImjjWqO/bI00U0A4Z4+tqwA/Pz+NckiNCykFSD
 EcsO/lp6n1n63kqgobT1d7a2LBCW+I9APYK38uYcGGavRH30dJY66HaGBo+/l1oNRd/u
 K4cA==
MIME-Version: 1.0
X-Received: by 10.28.45.216 with SMTP id t207mr23838559wmt.89.1449511654533;
 Mon, 07 Dec 2015 10:07:34 -0800 (PST)
Received: by 10.27.16.7 with HTTP; Mon, 7 Dec 2015 10:07:34 -0800 (PST)
Date: Mon, 7 Dec 2015 23:37:34 +0530
Message-ID: <CABD8d0rTD2Fu9QsqLKREBcA-nndQrUH8F8DWrPh_KQB64qjy1Q@mail.gmail.com>
Subject: bad disk discovery
From: prateek sethi <prateekrootkey@gmail.com>
To: freebsd-scsi@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.20
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-scsi>,
 <mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi/>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
 <mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Dec 2015 18:07:36 -0000

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.