From owner-freebsd-questions@FreeBSD.ORG Mon Mar 31 17:22:52 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 AE6CFC16; Mon, 31 Mar 2014 17:22:52 +0000 (UTC) Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (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 6F554C85; Mon, 31 Mar 2014 17:22:52 +0000 (UTC) Received: by mail-ig0-f171.google.com with SMTP id c1so2542967igq.4 for ; Mon, 31 Mar 2014 10:22:51 -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=xy/5HloazLS4ris+8Ua2LgToahtc4O86NHcpqQMzieI=; b=HAv3h6Y72fV+E1YXJdR775AlpwK12JvywDusRpYS3ytvi7epBa1b4HZZpCDOGOwi9L ExoopJLS81nNOKm1g0x5T/I8oWNWNJu9fEbTyNVAej35MDwErIG9ucSRGG/jHcvF0lyE p8TzEThKqOKDVu/azbu7FshQN6Z9CJ550P+Wk30z6dgwii/7llZdEgou/2066CAvuPkr LfdYyQN4FzhjHgaCPUiIEuHKnmm1QSAq9OIFdInkvUxYEuzxmVadsfqLrUjhPrarEB1q GGVZZKIWDHNlR9GJIAg0EEGkLxqb55LBi5TIqIyHfveDShy0iz92kpzZv3bu8Q5ujTmo rSaQ== MIME-Version: 1.0 X-Received: by 10.42.247.132 with SMTP id mc4mr33220744icb.44.1396286569583; Mon, 31 Mar 2014 10:22:49 -0700 (PDT) Sender: vrwmiller@gmail.com Received: by 10.64.235.212 with HTTP; Mon, 31 Mar 2014 10:22:49 -0700 (PDT) In-Reply-To: <066f01cf4cff$178e0ab0$46aa2010$@FreeBSD.org> References: <024701cf4aa7$f68be1b0$e3a3a510$@FreeBSD.org> <066f01cf4cff$178e0ab0$46aa2010$@FreeBSD.org> Date: Mon, 31 Mar 2014 13:22:49 -0400 X-Google-Sender-Auth: YAp0VOYTccK2wKJcSiz4bq6o6Y8 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 17:22:52 -0000 On Mon, Mar 31, 2014 at 12:34 PM, 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, 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 -- Take care Rick Miller