VMware最新的dist-upgrade后,Ubuntu 14.04.4 LTS挂起启动


15

我跑apt-get dist-upgrade如下:

Calculating upgrade... Done
The following NEW packages will be installed:
  linux-headers-3.19.0-51 linux-headers-3.19.0-51-generic
  linux-image-3.19.0-51-generic linux-image-extra-3.19.0-51-generic
The following packages will be upgraded:
  linux-generic-lts-vivid linux-headers-generic-lts-vivid
  linux-image-generic-lts-vivid
3 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 65.1 MB of archives.
After this operation, 288 MB of additional disk space will be used.

Setting up linux-image-generic-lts-vivid (3.19.0.51.36) ...
Setting up linux-headers-3.19.0-51 (3.19.0-51.57~14.04.1) ...
Setting up linux-headers-3.19.0-51-generic (3.19.0-51.57~14.04.1) ...
Setting up linux-headers-generic-lts-vivid (3.19.0.51.36) ...
Setting up linux-generic-lts-vivid (3.19.0.51.36) ...

之后,Ubuntu 14.04.4 x64 LTS无法正确启动,并在此屏幕上挂起:

在此处输入图片说明

这会在我尝试的所有VM上发生。我可以通过创建/还原快照来重现它。

更新:这是/var/log/boot.log通过GRUB中的高级启动选项启动以前的内核之后的内容:

 * Stopping Read required files in advance                               [ OK ]
 * Starting Mount filesystems on boot                                    [ OK ]
 * Starting Populate /dev filesystem                                     [ OK ]
 * Starting Populate and link to /run filesystem                         [ OK ]
 * Stopping Populate /dev filesystem                                     [ OK ]
 * Stopping Populate and link to /run filesystem                         [ OK ]
 * Stopping Track if upstart is running in a container                   [ OK ]
 * Starting Initialize or finalize resolvconf                            [ OK ]
 * Starting Signal sysvinit that the rootfs is mounted                   [ OK ]
 * Starting mount available cgroup filesystems                           [ OK ]
 * Starting set console keymap                                           [ OK ]
 * Starting Signal sysvinit that virtual filesystems are mounted         [ OK ]
 * Starting Signal sysvinit that virtual filesystems are mounted         [ OK ]
 * Starting Bridge udev events into upstart                              [ OK ]
 * Starting Signal sysvinit that remote filesystems are mounted          [ OK ]
 * Stopping set console keymap                                           [ OK ]
 * Starting Clean /tmp directory                                         [ OK ]
 * Stopping Clean /tmp directory                                         [ OK ]
 * Starting Signal sysvinit that local filesystems are mounted           [ OK ]
 * Starting device node and kernel event manager                         [ OK ]
 * Starting D-Bus system message bus                                     [ OK ]
 * Starting flush early job output to logs                               [ OK ]
 * Stopping Mount filesystems on boot                                    [ OK ]
 * Stopping flush early job output to logs                               [ OK ]
 * Starting load modules from /etc/modules                               [ OK ]
 * Starting cold plug devices                                            [ OK ]
 * Starting log initial device creation                                  [ OK ]
 * Starting SystemD login management service                             [ OK ]
 * Stopping load modules from /etc/modules                               [ OK ]
 * Starting system logging daemon                                        [ OK ]
 * Starting mDNS/DNS-SD daemon                                           [ OK ]
 * Starting bluetooth daemon                                             [ OK ]
 * Starting Reload cups, upon starting avahi-daemon to make sure remote q[ OK ]are populated
 * Stopping Reload cups, upon starting avahi-daemon to make sure remote q[ OK ]are populated
 * Starting Bridge file events into upstart                              [ OK ]
 * Starting Uncomplicated firewall                                       [ OK ]
 * Starting configure network device security                            [ OK ]
 * Starting configure network device                                     [ OK ]
 * Starting configure network device security                            [ OK ]
 * Starting Mount network filesystems                                    [ OK ]
 * Starting Failsafe Boot Delay                                          [ OK ]
 * Stopping Failsafe Boot Delay                                          [ OK ]
 * Stopping Mount network filesystems                                    [ OK ]
 * Starting System V initialisation compatibility                        [ OK ]
 * Starting modem connection manager                                     [ OK ]
 * Starting configure network device security                            [ OK ]
 * Starting configure network device                                     [ OK ]
 * Starting userspace bootsplash                                         [ OK ]
 * Starting network connection manager                                   [ OK ]
 * Stopping userspace bootsplash                                         [ OK ]
 * Starting Send an event to indicate plymouth is up                     [ OK ]
 * Stopping Send an event to indicate plymouth is up                     [ OK ]
 * Starting Bridge socket events into upstart                            [ OK ]
Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd
 * Starting AppArmor profiles                                                                [ OK ]
 * Setting up X socket directories...                                                        [ OK ]
 * Stopping System V initialisation compatibility                        [ OK ]
 * speech-dispatcher disabled; edit /etc/default/speech-dispatcher
 * Starting System V runlevel compatibility                              [ OK ]
 * Starting Restore Sound Card State                                     [ OK ]
 * Starting regular background program processing daemon                 [ OK ]
 * Starting anac(h)ronistic cron                                         [ OK ]
 * Starting save kernel messages                                         [ OK ]
 * Starting configure network device security                            [ OK ]
 * Starting CPU interrupts balancing daemon                              [ OK ]
 * Starting Restore Sound Card State                                     [fail]
 * Starting crash report submission daemon                               [ OK ]
 * Stopping save kernel messages                                         [ OK ]
 * Stopping anac(h)ronistic cron                                         [ OK ]
 * Stopping Restore Sound Card State                                     [ OK ]
 * Starting automatic crash report generation                            [ OK ]
 * Starting cups-browsed - Bonjour remote printer browsing daemon        [ OK ]
 * Starting configure virtual network devices                            [ OK ]
Starting VirtualBox kernel modules * Stopping cold plug devices          [ OK ]
 * Stopping log initial device creation                                  [ OK ]
 * Starting save udev log and update rules                               [ OK ]
 * Stopping save udev log and update rules                               [ OK ]
 ...done.

您最有可能注意到以下这一行:Starting Restore Sound Card State在为Ubuntu使用VM时,请尝试禁用虚拟声音界面并重新启动。上面的内核升级很可能破坏了他们的驱动程序。
Flatron '16

这发生在更新之前。但是我现在还是禁用它。没有解决。
亚历山大·蔡特勒

嗯,您可以尝试从这里使用最新的内核:kernel.ubuntu.com/~kernel-ppa/mainline/daily/current看看是否可行。如果没有正确的内核日志,我将无法说出是什么引起了问题(cat /var/log/kern.log)。也许还会查看文件夹中的压缩内核日志。
Flatron

@Flatron我创建了一个包含有问题时间的kern.log的pastebin:pastebin.com/iYDjfcxU
Alexander Zeitler

昨天有一个安全更新,我怀疑Bug#1548985与它有关。
Gunnar Hjalmarsson '16

Answers:


11

在Ubuntu论坛上,至少有一个线程显示我的问题是由最新的Ubuntu内核更新(linux-image-extra-3.19.0-51-generic)引起的:

http://ubuntuforums.org/showthread.php?t=2314723

更新:

@alexmurray在https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1550090提交了一个错误(已经确认)。

如果您受到影响,请在那儿投票(请不要在此处创建“我也”答案)。

更新:

固定3.19.0-51.58~14.04.1


10

我遇到了同样的问题,并恢复为较早的内核。

  1. 坚持Shift启动并选择高级选项,然后选择一个较旧的内核(请注意最新的内核是什么)。这将允许您进入Ubuntu桌面。

  2. 从那里打开突触包管理器。找到linux-image-3.19.0-51-generic(或您已安装的最新内核)。

  3. 右键单击并选择“标记为删除”。

  4. 应用并重新启动。


1
同样的问题,内核版本完全相同。在VMWare Workstation内部的VM上运行。此解决方案解决了它。
psyklopz

1
受到此错误影响的用户应在启动板上将其标记为影响他们。 bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1550090
psyklopz

0

我没有保存启动文本信息的记录,但是有类似的问题(Windows 7 64位主机VMware Workstation 12 Player),最初使用的是我使用了一段时间的15.10 Wily Werewolf VM。安装最新更新几天后,我的VM无法启动并卡在黑屏上。我试图通过从以前使用的.iso中创建一个新的14.04.3 LTS VM来解决此问题。该来宾VM正常运行,直到我对其进行更新,然后它也无法启动。因此,我再次尝试了新安装的15.10 guest虚拟机,并确信这似乎是最新更新中的原因(因为我尝试的2个VM具有不同的内核-我需要更高版本的内核才能具有USB 3.0功能)。

By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.