From owner-freebsd-questions@FreeBSD.ORG Mon Mar 31 14:32:33 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BCA9959C; Mon, 31 Mar 2014 14:32:33 +0000 (UTC) Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7F8956DD; Mon, 31 Mar 2014 14:32:33 +0000 (UTC) Received: by mail-ig0-f170.google.com with SMTP id uq10so3395700igb.1 for ; Mon, 31 Mar 2014 07:32:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=13c/t22gu0yO/qYLWXeBaI6D/N+Rk/rIZ+selRP/sjk=; b=kQTRLXSqpnjrJodfwSNSiC6kXMcT6PFrSJEA3xJzIXn2nH0UnIN77dISZENrqh9l5S JSlnjfhe/CxDNld7pEnbN1qj95PqFvy6xxr2ZncfiS0KpZH3+5dA3MaWXlPhxzS2VyKB u/Ti8nAUwo/VnPfvxRRN7wHP/uIf5ynO2XTKNJW3mWKCVPA8pIQQ/Enxtz74NMKIo5RN RmFx+HjkgTegn3UWdQIZWoST5rPUZp6qyToQy/r+J8X/ZP/i1PRNyGNyCu0wDUh+qlly 2OIgEu8HYHBs+DgzX3u+JsQwTFr/syEd/a7zipVuM7K8Fd4QU0il+tYfXtA+liL5LF5c RlWg== MIME-Version: 1.0 X-Received: by 10.42.16.199 with SMTP id q7mr31844227ica.16.1396276352848; Mon, 31 Mar 2014 07:32:32 -0700 (PDT) Sender: vrwmiller@gmail.com Received: by 10.64.235.212 with HTTP; Mon, 31 Mar 2014 07:32:32 -0700 (PDT) In-Reply-To: <024701cf4aa7$f68be1b0$e3a3a510$@FreeBSD.org> References: <024701cf4aa7$f68be1b0$e3a3a510$@FreeBSD.org> Date: Mon, 31 Mar 2014 10:32:32 -0400 X-Google-Sender-Auth: S54_256XXqmQ1HlNIau4H6mHifs Message-ID: Subject: Re: FreeBSD 10 custom bootonly ISO error From: Rick Miller To: Devin Teske Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2014 14:32:33 -0000 On Fri, Mar 28, 2014 at 1:05 PM, 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? -- Take care Rick Miller