From owner-freebsd-scsi@freebsd.org Thu Dec 3 19:49:30 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 F2916A405E8 for ; Thu, 3 Dec 2015 19:49:30 +0000 (UTC) (envelope-from lidl@pix.net) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.pix.net", Issuer "Pix.Com Technologies, LLC CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B79EA1CFA for ; Thu, 3 Dec 2015 19:49:30 +0000 (UTC) (envelope-from lidl@pix.net) Received: from torb.pix.net (torb.pix.net [192.168.16.32]) (authenticated bits=0) by hydra.pix.net (8.15.2/8.15.2) with ESMTPA id tB3JnRx5086424; Thu, 3 Dec 2015 14:49:27 -0500 (EST) (envelope-from lidl@pix.net) To: freebsd-scsi@freebsd.org From: Kurt Lidl Subject: Adaptec 5805 and SAS disks not attaching Message-ID: <56609CC7.6020005@pix.net> Date: Thu, 3 Dec 2015 14:49:27 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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: Thu, 03 Dec 2015 19:49:31 -0000 I recently got a used server, that has an Adaptec 5805 raid controller in it. I bought a couple of enterprise SAS disks. After sorting out the mounting hardware for the machine, I booted a stock FreeBSD 10.2 memory stick on the machine. However, the disks don't attach as daX devices. I have tried configuring the drives as "JBOD", and get the same results. I have tried configuring the drives with neither a RAID or JBOD on them, so the controller can just pass them through to the OS. (It's my intention to run ZFS on the drives.) root@:~lidl # camcontrol devlist at scbus0 target 6 lun 0 (pass0) at scbus0 target 7 lun 0 (pass1) at scbus9 target 0 lun 0 (pass2,ses0) at scbus10 target 0 lun 0 (da0,pass3) Any ideas or obvious gotchas? The controller attaches like this: aac0: mem 0xfba00000-0xfbbfffff irq 26 at device 0.0 on pci7 aac0: Enabling 64-bit address support aac0: Enable Raw I/O aac0: Enable 64-bit array aac0: New comm. interface enabled aac0: Adaptec 5805, aac driver 2.1.9-1 aacp0 on aac0 aacp1 on aac0 aacp2 on aac0 Thanks for any insight. -Kurt