Re: FreeBSD 10 custom bootonly ISO error

Hi all,

I revisited this thread because I've encountered this yet again, but first
wanted to concretely address the issue described below in term of the ISO's
volume label.  mkisoimages.sh[1] changes the label to upper case before
making it.  See line #39 in the reference.

Now, onto the current problem...below this thread...

On Mon, Mar 31, 2014 at 2:20 PM, Rick Miller <vmiller@hostileadmin.com>
wrote:

> Fixed, see thread below...
>
>
> On Mon, Mar 31, 2014 at 1:22 PM, Rick Miller <vmiller@hostileadmin.com>
> wrote:
>
>>
>> On Mon, Mar 31, 2014 at 12:34 PM, <dteske@freebsd.org> wrote:
>>
>>>
>>>
>>> > -----Original Message-----
>>> > From: Rick Miller [mailto:vmiller@hostileadmin.com]
>>> > Sent: Monday, March 31, 2014 7:33 AM
>>> > To: Devin Teske
>>> > Cc: FreeBSD Questions
>>> > Subject: Re: FreeBSD 10 custom bootonly ISO error
>>> >
>>> > On Fri, Mar 28, 2014 at 1:05 PM, <dteske@freebsd.org> wrote:
>>> >
>>> > >
>>> > > > Hi all,
>>> > > >
>>> > > > I will customize the FreeBSD 10 bootonly ISO to perform a
>>> > > non-interactive,
>>> > > > automated OS installation.  The initial ISO was built via
>>> release.sh
>>> > > > and
>>> > > was
>>> > > > successfully tested for boot functionality prior to touching
>>> > > > ${CHROOTDIR}/usr/obj/usr/src/release/bootonly/etc/installerconfig
>>> > > > and running mkisofs on bootonly/ generating a new bootonly ISO.
>>> > > >
>>> > > > NOTE: mkisofs command used: mkisofs -R -no-emul-boot -b boot/cdboot
>>> > > > -o bootonly.iso bootonly
>>> > > >
>>> > > > 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