GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
到
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force"
update-grub
。update-grub
,但没有起作用。然后我将其更改为 GRUB_CMDLINE_LINUX_DEFAULT="acpi=force",这解决了我的问题。 - RedPixeldist-upgrade
后的新内核版本有关? - xjiGRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR
=lsb_release -i -s 2> /dev/null || echo Debian
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force"
GRUB_CMDLINE_LINUX=""
除了这些,我还需要改变其他什么东西才能使它工作吗? - yugantar kumarsudo swapoff -a && systemctl poweroff
作为临时解决办法。
2. 在Xenial-proposed的systemd 229-4ubuntu5软件包中有一个潜在的修复方法。打开系统设置->软件和更新->开发者选项标签,勾选Pre-release (xenial-proposed)旁边的框,输入root密码,刷新缓存。在更新标签下,选择“立即显示更新”关闭系统设置。启动软件更新器并立即安装更新。
3. 如果问题仍然存在,请阅读这些错误报告:https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917以获取日志数据的信息,并按照建议提交新的错误报告。还请阅读错误报告:https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788303。
4. 按照“调试启动/关机问题”部分的说明,在/usr/share/doc/systemd/README.Debian.gz
中检查是否有任何挂起的任务。您需要在每次关机或重启之前启动调试shell,方法是输入:systemctl start debug-shell
。在救援shell ctl+alt+F9
中捕获journalctl -b
的屏幕截图可能会有所帮助。还可以将systemctl list-jobs
和systemctl --failed
的输出以及这些命令的输出都附加到同一个“filename.text”文件中,方法是在命令末尾添加>>filename.text
,例如:journalctl -b >>filename.text
journalctl -xe >>filename.text
systemctl list-jobs >>filename.text
systemctl --failed >>filename.text
lsblk >>filename.text
。所有这些内容将被追加到同一个文件中,供您在下次启动时分析,如果您提交了错误报告,将此文件附加到您的错误报告中可能会有所帮助。
更新
我遇到这些卡顿问题已经有一段时间了,最终我发现我的硬盘开始出现扇区故障等问题。所以,是时候更换新的硬盘并重新安装系统了。我按照Ubuntu的建议,在一个单独的启动硬盘上重新安装了操作系统,将交换分区作为第一个,根目录作为第二个,家目录作为第三个逻辑分区。从技术上讲,sda1是Grub引导程序,sda2是扩展分区,sda5、sda6、sda7分别是交换分区、根目录和家目录;sda3和sda4不存在。自那时以来,这个问题在新安装的硬盘上的操作系统上没有再出现过,大约已经过去了9个多月。我目前正在运行16.04.02 LTS版本,重启或关机时没有任何卡顿问题。之前的操作系统是Win7/Ubuntu双系统安装,交换分区位于硬盘末尾。
我并不是说这个问题与双系统安装、硬盘故障或者分区顺序有关,但在我的情况下,其中一个、两个或者所有这些因素都存在。现在,我不再遭受“Reached Target Shutdown”卡顿问题的困扰。
sudo -H gedit /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
到
GRUB_CMDLINE_LINUX_DEFAULT="acpi=force"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" 在这里移除“quiet”选项 将会在启动过程中显示文本输出,而移除“splash”选项 则会在启动时显示黑屏而不是启动画面。
保存并关闭 Gedit。
然后在终端中更新 Grub:
sudo update-grub
附加信息:
我注意到我还有一个正在运行的“停止作业”,所以我在/etc/systemd/system.conf
中减少了超时时间:
sudo -H gedit /etc/systemd/system.conf
#
并更改以下行中的时间。DefaultTimeoutStartSec=5s
DefaultTimeoutStopSec=5s
sudo systemctl daemon-reload
/etc/systemd/system.conf
中的DefaultTimeoutStartSec
和DefaultTimeoutStopSec
更改为'10':sudo -H gedit /etc/systemd/system.conf
然后进行编辑
DefaultTimeoutStartSec=10s
DefaultTimeoutStoptSec=10s
do-release-upgrade -d
将系统从14.04升级到16.04。echo 1 > /proc/sys/kernel/sysrq
echo b > /proc/sysrq-trigger
这个方法应该有效。也许在第二个命令之前你应该运行sync
。
reboot -f
可能有帮助,但我没有尝试过,因为如果服务器再次挂起,我无法访问它。
你可以检查/var/log/syslog文件。找到打开计算机的地方,并检查之前的行。你可以将它粘贴在这里。
我的syslog:
Apr 29 11:21:48 bow NetworkManager[875]: <warn> [1461907308.0752] dhcp4 (em0): request timed out
Apr 29 11:21:48 bow NetworkManager[875]: <info> [1461907308.0753] dhcp4 (em0): state changed unknown -> timeout
Apr 29 11:21:48 bow NetworkManager[875]: <info> [1461907308.0918] dhcp4 (em0): canceled DHCP transaction, DHCP client pid 2437
Apr 29 11:21:48 bow NetworkManager[875]: <info> [1461907308.0918] dhcp4 (em0): state changed timeout -> done
Apr 29 11:21:48 bow NetworkManager[875]: <info> [1461907308.0929] device (em0): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Apr 29 11:21:48 bow NetworkManager[875]: <warn> [1461907308.0943] device (em0): Activation: failed for connection 'Wired connection 1'
Apr 29 11:21:48 bow NetworkManager[875]: <info> [1461907308.0970] device (em0): state change: failed -> disconnected (reason 'none') [120 30 0]
Apr 29 11:21:48 bow NetworkManager[875]: <info> [1461907308.1062] policy: auto-activating connection 'Wired connection 1'
Apr 29 11:21:48 bow NetworkManager[875]: <info> [1461907308.1101] device (em0): Activation: starting connection 'Wired connection 1' (df58434d-16fc-4036-b1d2-2cae515dbf19)
Apr 29 11:21:48 bow NetworkManager[875]: <info> [1461907308.1108] device (em0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 29 11:21:48 bow NetworkManager[875]: <info> [1461907308.1133] device (em0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 29 11:21:48 bow NetworkManager[875]: <info> [1461907308.1152] device (em0): state change: config -> ip-config (reason 'none') [50 70 0]
Apr 29 11:21:48 bow NetworkManager[875]: <info> [1461907308.1167] dhcp4 (em0): activation: beginning transaction (timeout in 45 seconds)
Apr 29 11:21:48 bow NetworkManager[875]: <info> [1461907308.1221] dhcp4 (em0): dhclient started with pid 2444
Apr 29 11:21:48 bow dhclient[2444]: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 3 (xid=0x6cc9f4a)
Apr 29 11:21:51 bow dhclient[2444]: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 4 (xid=0x6cc9f4a)
Apr 29 11:21:55 bow dhclient[2444]: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 11 (xid=0x6cc9f4a)
Apr 29 11:22:01 bow CRON[2453]: (root) CMD (/usr/local/lib/wifictl)
Apr 29 11:22:01 bow CRON[2450]: (CRON) info (No MTA installed, discarding output)
Apr 29 11:22:06 bow dhclient[2444]: DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 20 (xid=0x6cc9f4a)
.................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
Apr 29 11:23:34 bow rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="860" x-info="http://www.rsyslog.com"] start
Apr 29 11:23:34 bow rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
Apr 29 11:23:34 bow rsyslogd: rsyslogd's groupid changed to 104
Apr 29 11:23:34 bow rsyslogd: rsyslogd's userid changed to 101
Apr 29 11:23:34 bow kernel: [ 0.000000] Initializing cgroup subsys cpuset
Apr 29 11:23:34 bow kernel: [ 0.000000] Initializing cgroup subsys cpu
Apr 29 11:23:34 bow kernel: [ 0.000000] Initializing cgroup subsys cpuacct
Apr 29 11:23:34 bow kernel: [ 0.000000] Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)
lspci
的输出,以帮助进行故障排除。00:00.0 Host bridge: Intel Corporation Atom Processor D2xxx/N2xxx DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller (rev 09)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 02)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation NM10/ICH7 Family SATA Controller [AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
03:00.0 Network controller: Qualcomm Atheros AR9227 Wireless Network Adapter (rev 01)
/etc/default/grub
,在关机前运行sudo swapoff -a
等等... 但是这些方法都对我无效。USB 3.0传统模式
对我有效。我的解决方案在这里 here
但简单来说:
sudo vim /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="noefi"
acpi=force
并更新了内核到4.6.7。 - Gosha U.