touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #64575
[Bug 1435126] Re: slow boot: systemd-fsck Cannot communicate fsck progress to fsckd: Broken pipe
Didier - the slow boot and those 'cannot communicate' messages happened
several times. However those seem to have gone away now, and boot time
is much better than it was, although still slower than before this
started:
~ $ systemd-analyze
Startup finished in 10.061s (kernel) + 9.968s (userspace) = 20.030s
I'm running from an SSD, and would normally see boot times in the 9-12s
range.
There is nothing in /var/crash related to plymouth.
~ $ systemctl status plymouth-start.service
● plymouth-start.service - Show Plymouth Boot Screen
Loaded: loaded (/lib/systemd/system/plymouth-start.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Mon 2015-03-23 22:10:11 EDT; 10h ago
Process: 321 ExecStartPost=/bin/plymouth show-splash (code=exited, status=0/SUCCESS)
Process: 316 ExecStart=/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid --attach-to-session (code=exited, status=0/SUCCESS)
Main PID: 320 (code=exited, status=0/SUCCESS)
Mar 23 22:10:11 gazp6 systemd[1]: Starting Show Plymouth Boot Screen...
Mar 23 22:10:11 gazp6 systemd[1]: Started Show Plymouth Boot Screen.
I still don't see the Kubuntu logo on startup, but I do see it during
the shutdown process.
I can of course live without the logo on startup and the slightly longer
boot times. The fsck errors are what prompted me to report this.
--
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/1435126
Title:
slow boot: systemd-fsck Cannot communicate fsck progress to fsckd:
Broken pipe
Status in systemd package in Ubuntu:
Incomplete
Bug description:
The computer eventually boots after a long delay. Possibly related,
plymouth does not display the Kubuntu logo, or anything else, during
this time.
The top two entries for systemd-analyze blame are:
30.570s systemd-fsck@dev-disk-by\x2duuid-03562ae0\x2d19b0\x2d4e47\x2d9d17\x2d898cc10e2cf2.service
30.569s systemd-fsck-root.service
The relevant journalct entries seem to be:
Mar 21 22:04:05 gazp6 systemd[1]: Started udev Wait for Complete Device Initialization.
Mar 21 22:04:05 gazp6 systemd[1]: Started Recovery mode menu.
Mar 21 22:04:05 gazp6 systemd[1]: Starting Copy rules generated while the root was ro...
Mar 21 22:04:05 gazp6 systemd[1]: Started Copy rules generated while the root was ro.
Mar 21 22:04:34 gazp6 systemd-fsck[264]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:04:34 gazp6 systemd-journal[263]: Forwarding to syslog missed 28 messages.
Mar 21 22:04:34 gazp6 systemd-fsck[264]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:04:34 gazp6 systemd-fsck[264]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:04:34 gazp6 systemd-fsck[264]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:04:34 gazp6 systemd-fsck[264]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:04:34 gazp6 systemd-fsck[264]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:04:34 gazp6 systemd-fsck[264]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:04:34 gazp6 systemd-fsck[264]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:04:34 gazp6 systemd-fsck[264]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:04:34 gazp6 systemd-fsck[264]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:04:34 gazp6 systemd-fsck[264]: /dev/sda2: 186114/1602496 files (0.2% non-contiguous), 1493144/6400000 blocks
Mar 21 22:04:34 gazp6 systemd[1]: Started File System Check on Root Device.
Mar 21 22:04:34 gazp6 systemd[1]: Starting Remount Root and Kernel File Systems...
Mar 21 22:04:34 gazp6 systemd[1]: Started Remount Root and Kernel File Systems.
Mar 21 22:04:34 gazp6 systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:acpi_video0...
Mar 21 22:04:34 gazp6 systemd[1]: Reached target Local File Systems (Pre).
Mar 21 22:04:34 gazp6 systemd[1]: Starting Local File Systems (Pre).
Mar 21 22:04:34 gazp6 kernel: EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
Mar 21 22:04:34 gazp6 systemd[1]: Starting File System Check on /dev/disk/by-uuid/03562ae0-19b0-4e47-9d17-898cc10e2cf2...
Mar 21 22:04:34 gazp6 systemd[1]: Started Various fixups to make systemd work better on Debian.
Mar 21 22:04:34 gazp6 systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:nv_backlight...
Mar 21 22:04:34 gazp6 systemd[1]: Starting Load/Save Random Seed...
Mar 21 22:04:34 gazp6 systemd[1]: Starting Load/Save RF Kill Switch Status of rfkill0...
Mar 21 22:04:34 gazp6 systemd[1]: Started Rebuild Hardware Database.
Mar 21 22:04:34 gazp6 systemd[1]: Starting Flush Journal to Persistent Storage...
Mar 21 22:04:34 gazp6 systemd[1]: Started Load/Save Screen Backlight Brightness of backlight:acpi_video0.
Mar 21 22:04:34 gazp6 systemd[1]: Started Load/Save Screen Backlight Brightness of backlight:nv_backlight.
Mar 21 22:04:34 gazp6 systemd[1]: Started Load/Save Random Seed.
Mar 21 22:04:34 gazp6 systemd[1]: Started Load/Save RF Kill Switch Status of rfkill0.
Mar 21 22:04:34 gazp6 systemd-fsck[549]: home: Superblock last mount time is in the future.
Mar 21 22:04:34 gazp6 systemd-fsck[549]: (by less than a day, probably due to the hardware clock being incorrectly set) FIXE
D.
Mar 21 22:04:34 gazp6 systemd-fsck[549]: home: Superblock last write time (Sun Mar 22 23:10:17 2015,
Mar 21 22:04:34 gazp6 systemd-fsck[549]: now = Sat Mar 21 22:04:34 2015) is in the future.
Mar 21 22:04:34 gazp6 systemd-fsck[549]: FIXED.
Mar 21 22:04:34 gazp6 systemd-journal[263]: Runtime journal is using 8.0M (max allowed 79.6M, trying to leave 119.4M free of
787.0M available → current limit 79.6M).
Mar 21 22:04:34 gazp6 systemd[1]: Started Flush Journal to Persistent Storage.
Mar 21 22:04:34 gazp6 systemd[1]: Started File System Check Daemon to report status.
Mar 21 22:04:34 gazp6 systemd[1]: Starting File System Check Daemon to report status...
Mar 21 22:04:57 gazp6 kernel: usb 4-1.2.2: USB disconnect, device number 7
Mar 21 22:04:57 gazp6 systemd-udevd[293]: error opening USB device 'descriptors' file
Mar 21 22:04:59 gazp6 kernel: usb 4-1.2.2: new low-speed USB device number 9 using ehci-pci
Mar 21 22:04:59 gazp6 kernel: usb 4-1.2.2: New USB device found, idVendor=046d, idProduct=c05a
Mar 21 22:04:59 gazp6 kernel: usb 4-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Mar 21 22:04:59 gazp6 kernel: usb 4-1.2.2: Product: USB Optical Mouse
Mar 21 22:04:59 gazp6 kernel: usb 4-1.2.2: Manufacturer: Logitech
Mar 21 22:04:59 gazp6 kernel: input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.2/4-1.2.2/4-
1.2.2:1.0/0003:046D:C05A.0005/input/input26
Mar 21 22:04:59 gazp6 kernel: hid-generic 0003:046D:C05A.0005: input,hidraw2: USB HID v1.11 Mouse [Logitech USB Optical Mouse
] on usb-0000:00:1d.0-1.2.2/input0
Mar 21 22:04:59 gazp6 mtp-probe[572]: checking bus 4, device 9: "/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.2/4-1.2.2"
Mar 21 22:04:59 gazp6 mtp-probe[572]: bus: 4, device: 9 was not an MTP device
Mar 21 22:05:04 gazp6 systemd-fsck[549]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:05:04 gazp6 systemd-journal[263]: Forwarding to syslog missed 39 messages.
Mar 21 22:05:05 gazp6 systemd-fsck[549]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:05:05 gazp6 systemd-fsck[549]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:05:05 gazp6 systemd-fsck[549]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:05:05 gazp6 systemd-fsck[549]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:05:05 gazp6 systemd-fsck[549]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:05:05 gazp6 systemd-fsck[549]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:05:05 gazp6 systemd-fsck[549]: Cannot communicate fsck progress to fsckd: Broken pipe
Mar 21 22:05:05 gazp6 systemd-fsck[549]: home: 31963/11231232 files (1.4% non-contiguous), 7639948/44921344 blocks
Mar 21 22:05:05 gazp6 systemd[1]: Started File System Check on /dev/disk/by-uuid/03562ae0-19b0-4e47-9d17-898cc10e2cf2.
Mar 21 22:05:05 gazp6 systemd[1]: Mounting /home...
Mar 21 22:05:05 gazp6 kernel: EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
Mar 21 22:05:05 gazp6 systemd[1]: Mounted /home.
Mar 21 22:05:05 gazp6 systemd[1]: Reached target Local File Systems.
Mar 21 22:05:05 gazp6 systemd[1]: Starting Local File Systems.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu8
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Mar 22 23:20:40 2015
MachineType: System76, Inc. Gazelle Professional
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=9d256b9e-4806-4bc1-8dd9-bde5a24f75dc ro splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/09/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: Not Applicable
dmi.board.name: Gazelle Professional
dmi.board.vendor: System76, Inc.
dmi.board.version: gazp6
dmi.chassis.asset.tag: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: gazp6
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/09/2011:svnSystem76,Inc.:pnGazelleProfessional:pvrgazp6:rvnSystem76,Inc.:rnGazelleProfessional:rvrgazp6:cvnSystem76,Inc.:ct10:cvrgazp6:
dmi.product.name: Gazelle Professional
dmi.product.version: gazp6
dmi.sys.vendor: System76, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1435126/+subscriptions
References