From owner-freebsd-questions@freebsd.org Thu Nov 5 21:04:53 2015 Return-Path: Delivered-To: freebsd-questions@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 47108A2718A for ; Thu, 5 Nov 2015 21:04:53 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0D76E1ADE for ; Thu, 5 Nov 2015 21:04:52 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-13-119.dynamic.qsc.de [92.195.13.119]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id 6438A27873; Thu, 5 Nov 2015 21:59:05 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id tA5Kx4eQ002563; Thu, 5 Nov 2015 21:59:04 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Thu, 5 Nov 2015 21:59:04 +0100 From: Polytropon To: Motty Cc: freebsd-questions@freebsd.org Subject: Re: /dev/da* getting /dev/pass* instead Message-Id: <20151105215904.0c3855fb.freebsd@edvax.de> In-Reply-To: <563B9E0E.6040809@gmail.com> References: <563B9E0E.6040809@gmail.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Nov 2015 21:04:53 -0000 On Thu, 5 Nov 2015 10:21:02 -0800, Motty wrote: > Hi All, > I don't get /dev/da0 instead I get /dev/pass0, on FreeBSD 10.2 Jbod > PROMISE 2U-SAS-12-D2 BP 0107, LSI card. This is not fully correct: You don't get the "pass" devices instead of the "da" devices, but you get the "pass" devices _without_ the corresponding "da" devices. See this example: % camcontrol devlist at scbus0 target 0 lun 0 (pass0,cd0) [...] at scbus4 target 0 lun 0 (da3,pass4) You always get "pass" devices (even for SCSI scanners), but in your case, the "da" devices are missing. In your listing, > at scbus0 target 8 lun 0 (pass0) > at scbus0 target 9 lun 0 (pass1) > at scbus0 target 10 lun 0 (pass2) > at scbus0 target 11 lun 0 (pass3) > at scbus0 target 12 lun 0 (pass4) > at scbus0 target 13 lun 0 (pass5) > at scbus0 target 14 lun 0 (pass6) > at scbus0 target 15 lun 0 (pass7) > at scbus0 target 16 lun 0 (pass8) > at scbus0 target 17 lun 0 (pass9) > at scbus0 target 18 lun 0 (pass10) > at scbus0 target 19 lun 0 (pass11) You can see the the devices being connected to the SCSI bus (even if it's not "real SCSI") properly, but the "da" driver has not been loaded for them. The reason? Maybe the controller you're using, "PROMISE 2U-SAS-12-D2 BP 0107, LSI card" (as you wrote) is not configured to represent the devices as "normal" hard disks to the operating system? Additional question: Have you loaded the driver that supports your card (mfi, mpr, mpt, mps etc.) in /boot/loader.conf? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...