On Thu, 2010-10-21 at 22:50 -0400, Bill Nottingham wrote:
Bill Nottingham (notting(a)redhat.com) said:
> Yanko Kaneti (yaneti(a)declera.com) said:
> > On Thu, 2010-10-21 at 10:43 -0400, Bill Nottingham wrote:
> > > I've set up a repo on
r.fp.org:
> > >
http://repos.fedorapeople.org/repos/notting/initscripts-systemd/
> >
> > Didn't automount anything from fstab other than /, not even /home. Even
> > when I logged in on the console with a user that has a home directory
> > there. Manually starting the corresponding *.mount units worked.
>
> It's not supposed to do that through systemd mount units... yet. There's a
> separate service for that.
To elaborate more... what does 'systemctl status fedora-mountall.service'
say?
fedora-mountall.service - Check, mount, and relabel all filesystems
Loaded: loaded (/lib/systemd/system/fedora-mountall.service)
Active: inactive (dead)
CGroup: name=systemd:/systemd-1/fedora-mountall.service
which seems to be caused by
fedora-init-crypto-1.service - Initialize encrypted storage
Loaded: loaded (/lib/systemd/system/fedora-init-crypto-1.service)
Active: failed since [Fri, 22 Oct 2010 08:57:39 +0300; 1min 24s ago]
Process: 1021 (/lib/systemd/fedora-init-crypto 0, code=exited, status=1/FAILURE)
CGroup: name=systemd:/systemd-1/fedora-init-crypto-1.service
# systemctl restart fedora-init-crypto-1.service
on the console just seems to hang
Yanko