Hello kex, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu9 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1547844 Title: systemd-fsckd does not allow fsck to finish Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd package in Debian: Fix Released Bug description: during normal boots, fsck runs fine with small partitions. But I have two big partitions and systemd seems to abort fsck somewhere between 5 to 10 minutes from start. This results in the partition being checked again at every boot. After manual run in recovery mode, everything is OK again. See e.g. sudo tune2fs -l /dev/mapper/xpcvg-home tune2fs 1.42.12 (29-Aug-2014) Filesystem volume name: <none> Last mounted on: /home Filesystem UUID: db583624-afb4-41cb-8b2d-640bee2de61b Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent sparse_super large_file uninit_bg Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 65536000 Block count: 262144000 Reserved block count: 13107200 Free blocks: 183474571 Free inodes: 65167292 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 961 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 RAID stride: 128 RAID stripe width: 384 Filesystem created: Mon Jul 25 12:23:50 2011 Last mount time: Sat Feb 20 09:34:41 2016 Last write time: Sat Feb 20 09:34:41 2016 Mount count: 166 Maximum mount count: 157 Last checked: Sun Nov 29 14:02:12 2015 Check interval: 15552000 (6 months) Next check after: Fri May 27 15:02:12 2016 Lifetime writes: 1113 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 First orphan inode: 65143018 Default directory hash: half_md4 Directory Hash Seed: ea4a0233-d8af-4c51-9302-140a4affacdf Journal backup: inode blocks journalctl says: helmi 20 09:30:21 xpc systemd-fsck[720]: /dev/mapper/xpcvg-home has been mounted 165 times without being checked, check forced. helmi 20 09:34:40 xpc systemd-fsck[720]: fsck: Warning... fsck.ext4 for device /dev/mapper/xpcvg-home exited with signal 13. helmi 20 09:34:40 xpc systemd-fsck[720]: fsck failed with error code 8. helmi 20 09:34:40 xpc systemd-fsck[720]: Ignoring error. helmi 20 09:34:40 xpc systemd[1]: Started File System Check on /dev/mapper/xpcvg-home. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu9 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 20 14:20:24 2016 InstallationDate: Installed on 2012-12-22 (1154 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic root=UUID=a21f1300-e2a3-44c9-a667-86fc6184627b ro nomdmonddf nomdmonisw libata.noacpi=1 irqpoll all_generic_ide=1 ide-pci-generic.all-generic-ide=1 usbcore.autosuspend=-1 usbcore.old_scheme_first=1 libata.force=8:1.5G xhci_hcd.quirks=262144 SourcePackage: systemd UpgradeStatus: Upgraded to wily on 2015-10-23 (119 days ago) dmi.bios.date: 08/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAXIMUS VI EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIEXTREME:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1547844/+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
