From owner-freebsd-usb@freebsd.org Wed Feb 8 17:32:22 2017 Return-Path: Delivered-To: freebsd-usb@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 6C0CFCD6AF8 for ; Wed, 8 Feb 2017 17:32:22 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 0B5371C23 for ; Wed, 8 Feb 2017 17:32:22 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.129.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id E87981FE104; Wed, 8 Feb 2017 18:32:16 +0100 (CET) Subject: Re: mount USB device To: Chris Hellberg , freebsd-usb@freebsd.org References: <1485637315.32561.862669136.6A6031BC@webmail.messagingengine.com> From: Hans Petter Selasky Message-ID: Date: Wed, 8 Feb 2017 18:31:38 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <1485637315.32561.862669136.6A6031BC@webmail.messagingengine.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 17:32:22 -0000 On 01/28/17 22:01, Chris Hellberg wrote: > Hi, > > I have a freebsd guest in a VM that receives a USB controller via PCI > passthrough. There was a USB drive inserted in the port when the host > and freebsd guest were booted. I'd like to be able to mount that drive. > The device is detected with usbdevs: > > root@NYCD-5K% usbdevs > addr 1: UHCI root hub, Intel > addr 1: EHCI root hub, Intel > addr 2: product 0x0020, vendor 0x8087 > addr 3: B-READE, GENERICU > root@NYCD-5K% > > However the kernel does not detect the drive (normally there would be > /dev/da0s1 present as well as the block device): > > root@NYCD-5K% ls -la /dev/da* > crw-r----- 1 root operator 0, 73 Jan 27 23:30 /dev/da0 > root@NYCD-5K% > > Fdisk can't get at the device: > > root@NYCD-QFX5100-48S-2:RE:0% fdisk /dev/da0 > fdisk: cannot open disk /dev/da0: Device not configured > root@NYCD-QFX5100-48S-2:RE:0% > > Unfortunately the system does not have the camcontrol binary nor lsusb > nor gpart. There is /usr/sbin/usbd installed on the system but I don't > know if that helps. And unfortunately the system only allows signed > binaries so it's essentially a locked environment from the perspective > of installing any other binaries. > > Any ideas how I can get at the disk. I can easily get everything working > fine if I pull out and reinsert the USB drive. Hi, Some formats don't have a partition label. Did you try to mount /dev/da0 directly ? Are you expecting labels to be present? --HPS