From owner-freebsd-scsi@freebsd.org Mon Dec 7 21:47:21 2015 Return-Path: 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 281359B914C for ; Mon, 7 Dec 2015 21:47:21 +0000 (UTC) (envelope-from scott4long@yahoo.com) Received: from nm16-vm6.bullet.mail.gq1.yahoo.com (nm16-vm6.bullet.mail.gq1.yahoo.com [98.137.177.254]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F30D41CFB for ; Mon, 7 Dec 2015 21:47:20 +0000 (UTC) (envelope-from scott4long@yahoo.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1449524705; bh=kBjJPE2lyXDAHvT29Y69twjimbsEg9znUcmDzJ6MUmw=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject; b=g1u/dGLV3CMxtH1nT9wj/ynIdjegRVQtzgNq3sjBjM8I0vmI670b04RNQCwPZmdHt++8tOvi48RL4z+V3W+vgLk3BIqnkJIOyB52AGbCa3bsNZx5gAmrMYyv71m1mCuxY8eykRfLCd0kQXOjHv/b9/eMYUseyZ2KRkLubCWietNbLqba0USTf6TgQKOkEgLsu8KyMn7nKTadcGO7RcdQufKkGPg6q7bhmTo1sgL2N2SEKp7UrnGcdl3uUMID8qilsByeLXVWkgpPqZ7XjDG7Jqj+yazVQBaBxDUzHiIN/xgkXMHz8+36/xQBguxEoIWobr0yqwCOS3kdUnRvrphXMg== Received: from [98.137.12.55] by nm16.bullet.mail.gq1.yahoo.com with NNFMP; 07 Dec 2015 21:45:05 -0000 Received: from [208.71.42.200] by tm15.bullet.mail.gq1.yahoo.com with NNFMP; 07 Dec 2015 21:45:05 -0000 Received: from [127.0.0.1] by smtp211.mail.gq1.yahoo.com with NNFMP; 07 Dec 2015 21:45:05 -0000 X-Yahoo-Newman-Id: 58333.66122.bm@smtp211.mail.gq1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: 6iLGOx0VM1n3eqnUjTu8EMJr1kgkKqPnbWm1mTf8_L82SF. 9QUcUyJtIQnHXf2eBAJ3rdWHuoYZYbMKw1pRWYyrU9PgUbFh6lCIpG6mRDmO ONX_yn.RuNaHnARSuFAaig6BqTVQu_KVSLKfO8HjGWEiNS_OplrzEcmE7Oxv ES0oMAXk4oZuTPSUbH9iUiWzDVyQCOGq94Tcg9th9SooW8Qqb4ROJfFQfUdx GcTdoWwq5Fwe2JjCS7295n4Pq9knfK4LcmjAJ8Ug1v.H_e8ipWN6DDrZOrRY kbpbEjli.O4GLZKHx3OFTe4zx.S2unWljB0OQPJ7eiJgAZIzBagKWLWqnb.3 UPlkTAVQ47Iu3iUT9oU38ZWKCCvYPhDir1.LajlGKfWQKWFHA93ycTkv4WY5 QCwLJmUoZPeewUlHErUTbPiNIJ5v4QGmENkpO36ydl_kMIuoEQZji7HJKZ6v sO4syHDynwqksLU8BW26rXoWcWk70QfxyTwPUaf4cqwikD7XynZt5syK_Q4a DN5P.CifPKCE3wvO19d00cIFTzFPdvDlGCxwCsiUO X-Yahoo-SMTP: clhABp.swBB7fs.LwIJpv3jkWgo2NU8- Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: bad disk discovery From: Scott Long In-Reply-To: Date: Mon, 7 Dec 2015 14:45:17 -0700 Cc: freebsd-scsi@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <6A7832F8-53EB-4641-8EF6-E0E6175EB52D@yahoo.com> References: To: prateek sethi X-Mailer: Apple Mail (2.3096.5) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Dec 2015 21:47:21 -0000 Hi, If your situation is accurate and the disk is not responding properly to = regular commands then it=E2=80=99s 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=E2=80=99s 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=E2=80=99re dealing with, we might be able to make better commendations. Scott > On Dec 7, 2015, at 11:07 AM, prateek sethi = wrote: >=20 > Hi , >=20 > 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? >=20 > I know smartctl is the one which can help. I have some couple of = question > regarding this . >=20 > 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? >=20 >=20 > Please tell me correct place to ask this question if I am asking at = wrong > place. > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to = "freebsd-scsi-unsubscribe@freebsd.org"