From owner-freebsd-bugs@freebsd.org Wed Oct 12 18:10:21 2016 Return-Path: Delivered-To: freebsd-bugs@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 ACB06C0F9EB for ; Wed, 12 Oct 2016 18:10:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9C505D69 for ; Wed, 12 Oct 2016 18:10:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9CIAKv4088207 for ; Wed, 12 Oct 2016 18:10:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 212914] CAM: SATA drives are getting deleted and then re-added after controller rescan Date: Wed, 12 Oct 2016 18:10:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RC1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ken@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Oct 2016 18:10:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212914 --- Comment #2 from Kenneth D. Merry --- The device may be going away for several possible reasons: 1. A CCB is returned with the status CAM_DEV_NOT_THERE or CAM_SEL_TIMEOUT. 2. A CCB is returned with the SCSI ASC/ASCQ 0x25,0x00, Logical Unit Not Supported. 3. Someone is doing an xpt_async(AC_LOST_DEVICE, ...) A device may go away and come back as a result of a rescan if any of the following changes: SCSI Standard Inquiry Data (Full inquiry data, including Vendor, Product, Revision) SCSI page 0x80 serial number The first thing I would look at here is what status is getting returned from the drive in question after a reset. If that all looks good, look at wheth= er someone is issuing a rescan, and whether the device is returning inconsiste= nt results. Those inconsistent results could be buried in the part of the Inq= uiry data that isn't displayed. Standard inquiry data is checksummed along with= the serial number and any change in the checksum will make the device go away a= nd come back. Although this is a SATA drive, obviously the only thing that matters is the SCSI response, because CAM is communicating with it as if it is a SCSI prot= ocol device. --=20 You are receiving this mail because: You are the assignee for the bug.=