From owner-freebsd-scsi@freebsd.org Tue Dec 8 16:20:51 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 360519D4750 for ; Tue, 8 Dec 2015 16:20:51 +0000 (UTC) (envelope-from stephen.mcconnell@avagotech.com) Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::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 11BFC1F5B for ; Tue, 8 Dec 2015 16:20:50 +0000 (UTC) (envelope-from stephen.mcconnell@avagotech.com) Received: by pfbg73 with SMTP id g73so14635938pfb.1 for ; Tue, 08 Dec 2015 08:20:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=avagotech.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=coCg5xU4j7BrZi4H7VUew/eAxF1LSn/97NMMyLClPTI=; b=UiPjVrggTA0VxEE6JYbPpw+WJESZhzh4lDbqKBUCckzZL2wnj8FModGK5js/hr1FK9 n+gJK3AvrTEbYBYIP0y617M3Vs6jKWuzGkcZNnw9Rz1ShL4Ttjvc5GRrQq5qp+Jit44G +ULYc3pLFifdaJ5NqvFPL5aHS5VDbZnQZzr4I= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=coCg5xU4j7BrZi4H7VUew/eAxF1LSn/97NMMyLClPTI=; b=mndtCeVmO87sH9eUQE1YPAtunIPCbDfUiT1MUyAkHWJQ5L86JssiQQ+4B6kcUnlr+4 ykTJqYZCaTgM18jrzByFFnl6yd9+rjfDG6cIbpRThy9zQH9uNtjgIUsgcOhWOnHYKwxW GPMkW7a/alBkMJ80d/Qv9QQQZ3XL6H2R/Q7+pp3dZxlgYd9nmo7PdGPTBuLernAG+yXV fAndo8cwLF5N+0hKByUT/zMTwXE7nzNbPRMBQxQja8HkNl8dwlUluoBMhk35CwEVcsVV xR2pYCakAle1dsiTVGEHpkd1WCPbf29uaRKhVzZ/ABRGHuqA8dQH+Geal8RT12/DgMDF E1Sw== X-Gm-Message-State: ALoCoQlGUCPJ9ISMmrtq04IXE73R1qScgaG9hAAGPnxccFRa7j449ZpufvMfwuMzzIgn6yND1nTpmxZ1hFQ01ExjC7BvyKxRg1zh6wxiuoFLaOMaKhlHm30= X-Received: by 10.98.14.26 with SMTP id w26mr6107849pfi.110.1449591650313; Tue, 08 Dec 2015 08:20:50 -0800 (PST) From: Stephen Mcconnell References: <6A7832F8-53EB-4641-8EF6-E0E6175EB52D@yahoo.com> In-Reply-To: MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQJO1PHZ3S5C87fllREIl8yX+V/IRAJvH4HyAm7AR3ACs4vlkAGgDtQvnXxyjhA= Date: Tue, 8 Dec 2015 09:20:48 -0700 Message-ID: <48445286cfa5082c78581b2c1e8afb66@mail.gmail.com> Subject: RE: bad disk discovery To: prateek sethi , Michael Jung Cc: freebsd-scsi@freebsd.org, owner-freebsd-scsi@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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: Tue, 08 Dec 2015 16:20:51 -0000 Try looking through the system log to see if there is any debug output from the mps driver, or you can send it to me and I'll take a look. It might give us a clue as to what's going on. Steve McConnell > -----Original Message----- > From: owner-freebsd-scsi@freebsd.org [mailto:owner-freebsd- > scsi@freebsd.org] On Behalf Of prateek sethi > Sent: Tuesday, December 08, 2015 9:05 AM > To: Michael Jung > Cc: freebsd-scsi@freebsd.org; owner-freebsd-scsi@freebsd.org > Subject: Re: bad disk discovery > > Yes, I have tried that one but issue is still there. Other disk are > working fine > with the same configuration that means firmware should not be a problem. > > > On Tue, Dec 8, 2015 at 6:56 PM, Michael Jung wrote: > > > On 2015-12-08 08:00, prateek sethi wrote: > > > >> Hi Scott, > >> Thanks for the your quick response. > >> > >> I have different set of hardware . So that's why I want to know how I > >> can debug it myself . Is there anyway or procedure using that I can > >> findout about the situation or the reason for CDB errors or disk > >> command > failure? > >> > >> Right now I am giving detail about the setup where I am getting this > >> issue . > >> > >> I am using LSI SAS2008 controller and connected with supermicro > >> Enclosure with freebsd 9.3. 16 different disks are there but only one > >> disk is having problem. That means contoller and cable are fine. > >> > >> Faulty disk info are like:-. > >> > >> *smartctl output is:-* > >> > >> smartctl -x /dev/da23 > >> > >> =3D=3D=3D START OF INFORMATION SECTION =3D=3D=3D > >> Vendor: SEAGATE > >> Product: ST3600057SS > >> Revision: 000B > >> Rotation Rate: 15000 rpm > >> Form Factor: 3.5 inches > >> Logical Unit id: 0x5000c5007725173f > >> Serial number: 6SL8YLPC0000N5030DY7 > >> Device type: disk > >> Transport protocol: SAS > >> Local Time is: Tue Dec 8 18:20:45 2015 IST > >> *device is NOT READY (e.g. spun down, busy)* > >> > >> *Logs:-* > >> > >> Dec 8 14:12:01 N1 kernel: da23 at mps0 bus 0 scbus0 target 148 lun 0 > >> Dec 8 14:12:01 N1 kernel: da23: Fixed > >> Direct Access SCSI-5 device Dec 8 14:12:01 N1 kernel: da23: Serial > >> Number 6SL8YLPC0000N5030DY7 Dec 8 14:12:01 N1 kernel: da23: > >> 600.000MB/s transfers Dec 8 14:12:01 N1 kernel: da23: Command > >> Queueing enabled Dec 8 14:12:01 N1 kernel: da23: *Attempt to query > >> device size failed: NOT READY, Logical unit not ready, cause n* Dec > >> 8 14:12:01 N1 kernel: ses1: da23,pass26: Element descriptor: 'Slot > >> 24' > >> Dec 8 14:12:01 N1 kernel: ses1: da23,pass26: SAS Device Slot > >> Element: 1 Phys at Slot 23 > >> > >> *driver versions:-* > >> > >> > >> dev.mps.0.firmware_version: 15.00.00.00 > >> dev.mps.0.driver_version: 16.00.00.00-fbsd > >> > >> > >> > >> > >> > >> > >> On Tue, Dec 8, 2015 at 3:15 AM, Scott Long > wrote: > >> > >> 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 commenda= tions. > >>> > >>> Scott > >>> > >>> > On Dec 7, 2015, at 11:07 AM, prateek sethi > >>> > > >>> 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@freebsd.org mailing list > >>> > https://lists.freebsd.org/mailman/listinfo/freebsd-scsi > >>> > To unsubscribe, send any mail to > >>> > "freebsd-scsi-unsubscribe@freebsd.org > >>> " > >>> > >>> > >>> _______________________________________________ > >> 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= " > >> > > > > > > Have you simply moved the drive to another slot - does the problem > > follow the drive? > > Unlikely but it could be a backplane issue. > > > > I don't know about version 15 firmware, I have always used version 16 > > firmware with 9.x to match the driver version. > > > > > _______________________________________________ > 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"