It depends on what sort of raid modes are in place. If you are not using raid (e.g. RAID1) as provided by your motherboard firmware, and only use individual devices, it is best to disable raid settings in the bios and use regular acpi setting. I have to do this for example on latest generation of Dell XPS laptops that use "raid" mode on a single nvme drive with OS support drivers that are not available for linux.
Otherwise if you do use RAID controllers with mdadm, e.g. Intel Matrix RAID, DDF, etc. 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. -- 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/1619844 Title: [Xenial] shutdown/reboot hangs at "Reached target Shutdown" Status in systemd package in Ubuntu: Confirmed Bug description: I tried getting more information in the debug-shell but I was unsuccessful in doing so. I was able to switch to the debug shell via ctrl+alt+f9 but I couldn't actually type anything in. I could switch back to the stuck shutdown screen via ctrl+alt+f1, and hitting NumLock would turn the light on my keyboard on and off, but I couldn't do anything else. I captured a journal of the stuck reboot. Interestingly, the journal shows a few more lines after "Reached target Shutdown", which is as far as I get on my screen. This system was installed with Xenial 16.04.1 (never been upgraded) and has had this problem since the very first boot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Sep 3 00:33:19 2016 InstallationDate: Installed on 2016-08-17 (16 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=5f709fed-48c9-4830-87be-acd13f263eb1 ro SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/mariadb.service → /etc/systemd/system/mariadb.service.d/migrated-from-my.cnf-settings.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-404:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1619844/+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
