FreeBSD 10 custom bootonly ISO error

[Rick Miller]

Fixed, see thread below...


On Mon, Mar 31, 2014 at 1:22 PM, Rick Miller <vmiller at hostileadmin.com>wrote:

>
> On Mon, Mar 31, 2014 at 12:34 PM, <dteske at freebsd.org> wrote:
>
>>
>>
>> > -----Original Message-----
>> > From: Rick Miller [mailto:vmiller at 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 at 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
>> > > > [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/
>> > >
>> >
>> > I regenerated the ISO using "-V FREEBSD_INSTALL" and "-volset
>> > FREEBSD_INSTALL", neither of which produced a result beyond the original
>> > error.  Thoughts?
>> >
>>
>> My bad, it appears to be camel-case "FreeBSD_Install". See lines 205-212
>> of
>>
>> http://svnweb.freebsd.org/base/head/release/Makefile?revision=262505&view=ma
>> rkup
>>
>>
>
> I assumed caps was the correct syntax based on something found in the
> archives that suggests this[1], but using "FreeBSD_Install" failed as well.
>
> [1]
> http://lists.freebsd.org/pipermail/freebsd-amd64/2013-April/015251.html
>

I chose to generate the iso the same way it is done in release/Makefile as
opposed to running mkisofs on it and the resulting ISO booted as expected.

Thanks for the help, Devin.

-- 
Take care
Rick Miller