Date: Fri, 28 Mar 2014 14:36:16 -0400 From: Rick Miller <vmiller@hostileadmin.com> To: Devin Teske <dteske@freebsd.org> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: FreeBSD 10 custom bootonly ISO error Message-ID: <CAHzLAVESAkL3UXEZNz=TwQEYDmZ5Rg_ao8XRFtNpMYd%2BKGvmzg@mail.gmail.com> In-Reply-To: <024701cf4aa7$f68be1b0$e3a3a510$@FreeBSD.org> References: <CAHzLAVHs=2n3xcR7jeiDx-foGsrXzd=t-fOe3y23%2BK4OUpdh-w@mail.gmail.com> <024701cf4aa7$f68be1b0$e3a3a510$@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks, Devin... On Fri, Mar 28, 2014 at 1:05 PM, <dteske@freebsd.org> wrote: > > [ snip ] > > > > Booting the new ISO via a vmware 5.x VM resulted in an error mounting the > > filesystem[1] (see image in reference [1]). Manually entering the "mount > > from" here[2] (cd9660:/dev/cd0) resulted in the system continuing to boot > > into bsdinstall as expected. > > > > The error appears to suggest using /dev/acd0, despite the the first line > in the > > output of bootonly_iso_error.png suggesting the CD-ROM device is actually > > /dev/cd0. I'm inclined to believe I missed a step normally performed > during > > execution of release.sh (such as editing > > bootonly/boot/defaults/loader.conf), but have been unable to ascertain > > what. Any feedback or clues would be greatly appreciated. > > > > [1] http://www.hostileadmin.com/images/bootonly_iso_error.png > > [2] http://www.hostileadmin.com/images/bootonly_iso_cdboot.png > > > > You didn't give the ISO a label. It actually doesn't look for cd0 nor acd0 > but FREEBSD_INSTALL label which ends up in /dev/iso9660/ > Are you referring to a volume label for the ISO via mkisofs -V FREEBSD_INSTALL? -- Take care Rick Miller
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHzLAVESAkL3UXEZNz=TwQEYDmZ5Rg_ao8XRFtNpMYd%2BKGvmzg>