From owner-freebsd-current@freebsd.org Tue Sep 15 10:48: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 CA064A03046; Tue, 15 Sep 2015 10:48:22 +0000 (UTC) (envelope-from stefanogarzarella@gmail.com) Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6CC631C9A; Tue, 15 Sep 2015 10:48:22 +0000 (UTC) (envelope-from stefanogarzarella@gmail.com) Received: by lahg1 with SMTP id g1so75038285lah.1; Tue, 15 Sep 2015 03:48:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-type; bh=deNpc4Wu9BaPQhqTCqDXTE1uvudJEUriryYU9n2Hifw=; b=LIw0VFYEnj8/DR7ZAfyulEOP+KgWQR000XmcWg4hrBCpNvhyMUbkPpvmS1aPON3nLX 46Z8danRpk56sKMdyyBkKpXk6as6lkOboTsYGjpswApugtUjW4ggwA3Z6kK3tfseWW/Y 7jiJST807uvf6tBf3BgWKagczjcosK+9mTEgRCPa+zj0XC6652jSgWyTcNwelyD2YEc/ y6ov0sid/tBhYPGmRuVMEZPaBfG7YD1XLwLEl3X1AbN/X3LkPTqLxhvwF/qp9RgvG4/7 MHEkQQFSTERRqwdb7xeU72K/aI88qBkDW7bY/t0m/9iE+Vg5DIFdVcgGkCyGJC3SEVEz vt/g== X-Received: by 10.152.28.65 with SMTP id z1mr20178894lag.9.1442314100125; Tue, 15 Sep 2015 03:48:20 -0700 (PDT) MIME-Version: 1.0 References: <20150915120517.39c691ce@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <20150915120517.39c691ce@freyja.zeit4.iv.bundesimmobilien.de> From: Stefano Garzarella Date: Tue, 15 Sep 2015 10:48:10 +0000 Message-ID: Subject: Re: nanoBSD boot problem (on USB stick or as a HD) To: "O. Hartmann" Cc: freebsd-current , freebsd-hackers@freebsd.org, Luigi Rizzo Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 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:48:22 -0000 Hi Oliver, Thank you very much! I solved it setting NANO_LABEL="mylabel". Cheers, Stefano Il giorno mar 15 set 2015 alle 12:05 O. Hartmann < ohartman@zedat.fu-berlin.de> ha scritto: > 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 >