Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 19 Jul 2015 20:07:40 +0200
From:      Per olof Ljungmark <peo@intersonic.se>
To:        freebsd-stable@freebsd.org
Cc:        James Gritton <jamie@freebsd.org>
Subject:   Re: jail: /etc/rc: cannot create /dev/null: Operation not supported
Message-ID:  <55ABE76C.8050001@intersonic.se>
In-Reply-To: <df578da91e74fa5467792d722bb778ba@gritton.org>
References:  <20150715215253.Horde._Uobbflf4-5sp0TjL7DgCrc@webmail.bsdlabs.com> <d21415575fb72f8758734ff9425bd58d@gritton.org> <55A93AE0.6050204@intersonic.se> <df578da91e74fa5467792d722bb778ba@gritton.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55ABE76C.8050001>