From owner-freebsd-current@freebsd.org Tue Sep 15 10:05:22 2015 Return-Path: Delivered-To: freebsd-current@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 CAD91A044BF; Tue, 15 Sep 2015 10:05:22 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (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 8561611A7; Tue, 15 Sep 2015 10:05:21 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtp (envelope-from ) id <1Zbn70-0043pG-0u>; Tue, 15 Sep 2015 12:05:18 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (envelope-from ) id <1Zbn6z-000uaj-R8>; Tue, 15 Sep 2015 12:05:17 +0200 Date: Tue, 15 Sep 2015 12:05:17 +0200 From: "O. Hartmann" To: Stefano Garzarella Cc: freebsd-current , freebsd-hackers@freebsd.org, Luigi Rizzo Subject: Re: nanoBSD boot problem (on USB stick or as a HD) Message-ID: <20150915120517.39c691ce@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: References: Organization: FU Berlin X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Sep 2015 10:05:22 -0000 On Tue, 15 Sep 2015 11:31:36 +0200 Stefano Garzarella wrote: > Hi all, > I created a nanoBSD image for my gsoc project (ptnetmap on bhyve). > > I would like to boot this image on USB stick or in the hypervisor as a HD. > I have some problem because if I set NANO_DRIVE="da0" (for USB boot) > in the nanoBSD configuration file, the boot from USB stick works well, > but when I try to boot the same image in the hypervisor as a HD, > I have the following mountroot error: > > Trying to mount root from ufs:/dev/da0s1a [ro]... > mountroot: waiting for device /dev/da0s1a ... > Mounting from ufs:/dev/da0s1a failed with error 19. > > Loader variables: > vfs.root.mountfrom=ufs:/dev/da0s1a > vfs.root.mountfrom.options=ro > > mountroot> > > > At this point I need to manually specify "ufs:/dev/ad0s1a" to properly mount > the root. > > Can you help me? > There is some tricks to avoid this mountroot error? > > Thanks, > Stefano Garzarella > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Check your /etc/fstab. I guess the device for "/" is still /dev/da0s1a. I had to patch the nanoBSD scripts to target that issue and booting from UEFI systems, but my solution is not very transparent. Using labels would be more convenient and would be much more GPT/UEFI friendly. regards, Oliver