On Wed, Nov 04, 2015 at 09:48:05PM +0000, Patrick O'Callaghan wrote:
On 4 November 2015 at 21:24, Patrick O'Callaghan
<pocallaghan(a)gmail.com>
wrote:
> Does "modprobe -v btrfs" print anything, or does the command fail
>> silently?
>>
> Gives no output. "lsmod|grep btrfs" shows nothing.
>
>> Is this with SELinux enforcing? If so, have you tried with enforcing=0
>> yet? (or run "setenforce 0" as root before trying modprobe and the
other
>> commands.
>
> I tried with enforcing off. No difference.
I'm thinking that the btrfs problem is a red herring. I masked both btrfs
and NFS filesystems in /etc/fstab and rebooted. Now I get a very low-res
KDE login screen (which of course doesn't do any good as /home is not
mounted), but journalctl continues to show errors, in particular:
Unit var-lib-nfs-rpc_pipefs.mount has failed
Also, networking is off. I repeat, all NFS mounts are masked (commented
out).
When I upgraded to F22, all fstab entries that said mount at boot
had to succeed or the boot went to emergency mode. For me it
was an obscure sshfs mount that caused problems.
Are any boot time mounts failing?
--
Jon H. LaBadie jonfu(a)jgcomp.com