Yes. I confirm that. After change in bios from raid to ahci computer is rebooting and swithing off normally. Wysłano z mojego smartfona Samsung Galaxy. -------- Oryginalna wiadomość --------Od: Tobias Alke Data: 22.04.2017 08:53 (GMT+01:00) Do: Temat: [Bug 1619844] Re: [Xenial] shutdown/reboot hangs at "Reached target Shutdown" I think i have a specification to this issue. First, my system with the same problem at shutdown/reboot, but only in a very special case: Fresh install of Ubuntu Server 16.04.2 LTS CPU: Intel Xeon E3-1245v6 (Kabylake) Mainboard: MSI C236A Workstation/Server Mainboard (model: 7998-012R; latest BIOS: v2.7) RAM: 4x TRANSCEND 8GB DDR4 2133 ECC-DIMM 2Rx8 1Gx72 288P 512Mx8/CL15 (model: TS1GLH72V1H) SSD: 2x Samsung Basic MZ-7KE256BW 850 Pro interne SSD 256GB HDD: 2x Western Digital Red 4TB NAS (model: WDBMMA0040HNC-ERSN) Description of the special case with the shutdown/reboot issue: The problem only reveals when RAID-Mode auf the MSI Mainboard is enabled. After resetting to AHCI-Mode, the problem is over an the server works fine. It seems, that's a problem with the "Intel® C236 Chipset" or more specific a driver problem with intel based components on the different systems. -- You received this bug notification because you are subscribed to the bug report. 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