https://bugzilla.novell.com/show_bug.cgi?id=725622
https://bugzilla.novell.com/show_bug.cgi?id=725622#c35
--- Comment #35 from Harald Koenig 2011-10-31 17:05:35 UTC ---
(In reply to comment #34)
found it : you have "noauto" specified for /home in your fstab : so systemd
doesn't try to mount it at startup ...
interesting!! that's from yast2 when creating that setup many releases back
(likely opensuse 11.1).
so I removed the "noauto" and did reboot -- but first again with sysvinit ;-)
and surprise: without "noauto" runs into some timeout
service boot.localfs start
Waiting for /dev/mapper/cr_home .............................. timeout!
Checking file systems...
fsck from util-linux 2.20
root2: clean, 6789/1966080 files, 6220530/7864320 blocks
...
/dev on /11.4/dev type none (rw,bind)
failedActivating crypto devices using /etc/crypttab ...
service boot.localfs done
and only later the crypto stuff gets started and /home shows up:
service boot.crypto start
Loading console font lat9w-16.psfu -m trivial G0:loadable
doneLoading keymap i386/qwerty/us.map.gz
doneStart Unicode mode
doneUnlocking cr_home (/dev/system/home)
modprobe: FATAL: Error inserting padlock_sha
(/lib/modules/3.1.0-rc9-1-desktop/kernel/drivers/crypto/padlock-sha.ko): No
such device
cr_home...done
service boot.crypto done
so there seems to be a good reason for the "noauto" -- at least for the
sysvinit case...
now, next reboot with systemd (without "noauto") -- and /home/ got mounted as
expected!
GREAT!!! I'm glad to see/understand what's going on!
except for the sysvinit case ;-))
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.