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 < ohart...@zedat.fu-berlin.de> ha scritto: > On Tue, 15 Sep 2015 11:31:36 +0200 > Stefano Garzarella <stefanogarzare...@gmail.com> 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 > > _______________________________________________ > > email@example.com mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscr...@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 > _______________________________________________ firstname.lastname@example.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"