poweroff or reboot hangs

[Pavol Domin]

After the upgrade to 15.04, poweroff or reboot hangs, the last message is
quotaoff.sh[PID]... done

It hangs if executed by clicking from the menu, as well as with the 'poweroff', 'reboot', or 'halt' commands from the terminal.
In debug console, in the journalctl -f output, this one error can be seen

Failed umounting /tmp

and the last messages before the freeze are like

Starting Final Step
Starting Power-Off
Shutting Down

I can still switch vt, but cannot type.

After some time, kernel writes:
info: task systemd-shutdow:1 blocked for more than 120 seconds.

ctrl-alt-del does nothing. the only ways to bring server down seem to be alt-sysrq or powerbutton.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: systemd 219-7ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Jun 20 22:17:59 2015
InstallationDate: Installed on 2011-09-16 (1373 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-21-generic root=/dev/mapper/vg00-lv_ubuntu_root ro
SourcePackage: systemd
UpgradeStatus: Upgraded to vivid on 2015-06-19 (1 days ago)
dmi.bios.date: 02/23/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2102
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q-PRO
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.:bvr2102:bd02/23/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Pavol Domin (pavol-domin)]

The bug still exists in 15.10. It cannot be reproduced if booted with init=/sbin/upstart: its clearly systemd related problem.

[Dimitri John Ledkov (xnox)]

Can you still reproduce this with 16.04 xenial?
Do you use hardware/fakeraid as provided by your motherboard? E.g. Intel Matrix Raid?

as part of https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1722491 there is currently mdadm update available from xenial-proposed and zesty-proposed that might resolve this issue.

To test that solution please perform the following:

1) Install mdadm from xenial-proposed/zesty-proposed
   - See https://wiki.ubuntu.com/Testing/EnableProposed
   - Or download & install packages from
xenial
https://launchpad.net/ubuntu/+source/mdadm/3.4-4ubuntu0.1/+build/13596415
zesty
https://launchpad.net/ubuntu/+source/mdadm/3.3-2ubuntu7.5/+build/13596431

2) $ sudo apt install dracut-core

3) $ sudo systemctl enable mdadm-shutdown.service

4) $ sudo systemctl start mdadm-shutdown.service

After this the expectation is for shutdown/reboots to perform clean a shutdown, maintaining the raid array in a synced state, such that it comes up clean.

Please let me know if above resolves shutdown/reboot issues for you.

Regards,

Dimitri.

[Dimitri John Ledkov (xnox)]

Just a quick clarification, first boot/shutdown will still not be clean, but subsequent ones (those that are booted with the updated mdadm package) should be clean.

[Launchpad Janitor (janitor)]

[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]