systemd: fsck of ext4 filesystem does not show progress
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
When booting following a crash fsck is triggered for the root volume (LVM containing ext4 filesystem). This is correctly announced by systemd/plymouth and remains announced for the duration of the fsck, however the percentage complete is always 0.0% for the entire duration of the check. For those of us with no disk lights this is very off putting.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-5ubuntu1
ProcVersionSign
Uname: Linux 3.19.0-10-generic x86_64
NonfreeKernelMo
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Mar 31 10:10:41 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-06-20 (648 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130618)
MachineType: Intel Corporation 2012 Client Platform
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: systemd
UpgradeStatus: Upgraded to vivid on 2013-11-10 (505 days ago)
dmi.bios.date: 07/30/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: ACRVMBY1.
dmi.board.
dmi.board.name: Latexo FFRD
dmi.board.vendor: Intel Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.
dmi.chassis.type: 9
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: 2012 Client Platform
dmi.product.
dmi.sys.vendor: Intel Corporation
Changed in systemd (Ubuntu): | |
status: | Confirmed → Won't Fix |
Adding a boot with fsck booted with debug on the kernel command line, attaching journalctl -b as requested on IRC.