Sure, it says: Requires=basic.target Wants=system.slice Before=multi-user.target shutdown.target graphical.target checkfs.service local-fs.target After=system.slice basic.target cryptdisks-early.service mdadm-raid.service systemd-udevd.service mountdevsubfs.service systemd-journald.socket multipath-tools-boot.service
I don't use LVM though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1431107 Title: ordering cycles with early boot images on lvm2.service Status in systemd package in Ubuntu: Incomplete Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do "systemctl status apparmor", I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable "acpi_osi=Windows 2012" SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp