From owner-freebsd-stable@freebsd.org Sun Jul 19 18:07:57 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 093489A6700 for ; Sun, 19 Jul 2015 18:07:57 +0000 (UTC) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "neonpark.inter-sonic.com", Issuer "StartCom Class 2 Primary Intermediate Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C20CF1F9B; Sun, 19 Jul 2015 18:07:56 +0000 (UTC) (envelope-from peo@intersonic.se) X-Virus-Scanned: amavisd-new at Intersonic AB Message-ID: <55ABE76C.8050001@intersonic.se> Date: Sun, 19 Jul 2015 20:07:40 +0200 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org CC: James Gritton Subject: Re: jail: /etc/rc: cannot create /dev/null: Operation not supported References: <20150715215253.Horde._Uobbflf4-5sp0TjL7DgCrc@webmail.bsdlabs.com> <55A93AE0.6050204@intersonic.se> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jul 2015 18:07:57 -0000 On 2015-07-18 18:29, James Gritton wrote: > On 2015-07-17 11:26, Per olof Ljungmark wrote: >> On 2015-07-17 01:41, James Gritton wrote: >>> On 2015-07-15 13:52, Per olof Ljungmark wrote: >>>> FreeBSD 10.2-PRERELEASE #0 r284949 >>>> >>>> The jail can be started, but when /etc/rc is executed: >>>> >>>> root@mar:/ # sh -x /etc/rc >>>> + stty status ^T >>>> /etc/rc: cannot create /dev/null: Operation not supported >>>> + trap : 2 >>>> + trap 'echo '\''Boot interrupted'\''; exit 1' 3 >>>> + HOME=/ >>>> + PATH=/sbin:/bin:/usr/sbin:/usr/bin >>>> + export HOME PATH >>>> + [ '' = autoboot ] >>>> + autoboot=no >>>> + _boot=quietstart >>>> + /sbin/sysctl -n vfs.nfs.diskless_valid >>>> /etc/rc: cannot create /dev/null: Operation not supported >>>> ... >>>> >>>> I have done the procedure several times before but never saw this one >>>> before and don't know how to get around it. >>>> >>>> Ideas anyone? Any recent changes that can show up like the above? >>>> >>>> Thanks! >>> >>> If it's trying to create /dev/null, I assume that the jail's /dev isn't >>> mounted when /etc/rc is running. Do you have mount.devfs set in the >>> jail.conf, or jail_foo_devfs_enable in rc.conf (depending on your >>> configuration)? For that matter, can you tell if the jail's /dev is >>> mounted? >> >> Yes, it's mounted. >> >> Because I can set up jails with an identical procedure on other boxes we >> run I suspect something is wrong with the install so I am starting from >> scratch with this one. >> >> While doing that, I am trying to sort another problem, namely to boot >> zfs on root on a HP Proliant with a P410 controller, but that is another >> story. >> >> You know, if it was easy it would not be interesting... >> >> Thanks! > > So maybe a little late since you're starting over, but another possibility > is the devfs ruleset. If something went wrong in setting that up, you > could well have a devfs mounted that shows no devices. True, although I did check the rulesets. However, since this is a box that will go into production I did not want to take any chances in case we missed something that might show up in other places later.