From owner-freebsd-stable@FreeBSD.ORG  Sun Nov 16 22:11:51 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 11957AAA
 for <freebsd-stable@freebsd.org>; Sun, 16 Nov 2014 22:11:51 +0000 (UTC)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (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 C18A8F6
 for <freebsd-stable@freebsd.org>; Sun, 16 Nov 2014 22:11:50 +0000 (UTC)
Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD))
 (envelope-from <lists@opsec.eu>) id 1Xq82x-000Dnh-Bf
 for freebsd-stable@freebsd.org; Sun, 16 Nov 2014 23:11:51 +0100
Date: Sun, 16 Nov 2014 23:11:51 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: freebsd-stable@freebsd.org
Subject: Re: aacraid drives missing after update 10.0 -> 10.1 ?
Message-ID: <20141116221151.GG44537@home.opsec.eu>
References: <20141116213910.GF44537@home.opsec.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20141116213910.GF44537@home.opsec.eu>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Nov 2014 22:11:51 -0000

Hi!

> The raid controller: Adaptec 6405E

Replacing it with an Adaptec ASR8405 and the drives are back alive.

Any ideas why this happens ? That behaviour is very unexpected.

aacraid0: <Adaptec RAID Controller> port 0xb000-0xb0ff mem 0xf7400000-0xf74fffff,0xf7580000-0xf75803ff irq 16 at device 0.0 on pci6
aacraid0: Enable Raw I/O
aacraid0: Enable 64-bit array
aacraid0: using MSI-X interrupts (32 vectors)
aacraid0: New comm. interface type2 enabled
aacraid0: ASR8405, aacraid driver 3.2.5-1
aacraidp0 on aacraid0
aacraidp1 on aacraid0
aacraidp2 on aacraid0
aacraidp3 on aacraid0

da0 at aacraidp1 bus 0 scbus1 target 0 lun 0
da0: <ATA HGST HUS724020AL MJ6O> Fixed Direct Access SCSI-6 device 
da0: Serial Number       PK1B31P8H5DD2V
da0: 300.000MB/s transfers
da0: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C)
da1 at aacraidp1 bus 0 scbus1 target 1 lun 0
da1: <ATA HGST HUS724020AL MJ6O> Fixed Direct Access SCSI-6 device 
da1: Serial Number       PK1B31P8H5L97P
da1: 300.000MB/s transfers
da1: 1907729MB (3907029168 512 byte sectors: 255H 63S/T 243201C)

-- 
pi@opsec.eu            +49 171 3101372                         6 years to go !