在 BIOS 模式下安装 Ubuntu，无法再访问 BIOS

Question

稍等片刻，然后将其标记为题外话。我不敢相信这与 Ubuntu 无关，因为一切都发生在我安装 Ubuntu 之后。

有了这个，我将继续解释正在发生的事情：

我下载并安装了最新版本的 Ubuntu。我想要一个 BIOS 模式，因为我更喜欢这种方式并完成了安装过程。然后我安装了 GNOME 并重新启动。在这一切之后，我无法访问我的 bios。

这已经不是第一次发生了。它发生在过去，我解决了使用辅助硬盘在引导修复中切换引导分区的问题，但现在我不能再这样做了，因为该驱动器上没有 Windows 分区。

这是我的驱动器：

Disk /dev/sdb: 119,2 GiB, 128035676160 bytes, 250069680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xcaa3841c

Device     Boot Start       End   Sectors   Size Id Type
/dev/sdb1  *     2048 250068991 250066944 119,2G 83 Linux

当我尝试引导修复时，在该过程结束时，它说我必须在分区列表的开头创建一个 500mb 的分区，以便 grub 可以正常工作，但是嘿，这是另一个问题：

GParted 停止工作。如果我尝试启动它，这是错误：

Created symlink /run/systemd/system/-.mount ? /dev/null.
Created symlink /run/systemd/system/mnt-Archive.mount ? /dev/null.
Created symlink /run/systemd/system/mnt-Linux\x20Games.mount ? /dev/null.
Created symlink /run/systemd/system/run-user-1000.mount ? /dev/null.
Created symlink /run/systemd/system/tmp.mount ? /dev/null.
/usr/sbin/gpartedbin: error while loading shared libraries: libgtkmm-2.4.so.1: cannot open shared object file: No such file or directory
Removed /run/systemd/system/-.mount.
Removed /run/systemd/system/mnt-Archive.mount.
Removed /run/systemd/system/mnt-Linux\x20Games.mount.
Removed /run/systemd/system/run-user-1000.mount.
Removed /run/systemd/system/tmp.mount.

我想提一下：

• 是的，我确定我正在使用右键进入 bios
• 不，没有 bios 启动画面
• 不，如果我向垃圾邮件DEL发送进入 bios的密钥，则不会发生任何事情
• 是的，关键工作正常
• 是的，我试图拔掉每个驱动器
• 是的，我尝试重置 CMOS
• 是的，我在 BIOS 模式下安装了操作系统，我通过终端进行了检查。

这是引导修复的输出

这是消息警报，说我需要创建一个分区才能正确启动：

[The OS now in use - Ubuntu 17.04] 的启动文件离磁盘很远。您的 BIOS 可能无法检测到它们。您可能希望在创建/boot分区（EXT4，>200MB，磁盘开始）后重试。这可以通过 gParted 等工具执行。然后通过【Boot Repair】的【Separate /boot partition:】选项选择这个分区。( https://help.ubuntu.com/community/BootPartition )

Answer 1

自从从 BIOS 切换到 EFI 以来，我已经看到很多关于 EFI 拒绝启动其设置实用程序的报告。我没有足够密切地跟踪这些以识别模式（例如，特定的固件供应商或主板/计算机品牌是否比其他品牌有更多的问题？），但这绝对是固件错误，而不是操作系统错误。也就是说，它可能由操作系统对固件设置（例如引导顺序）所做的更改触发。在您的情况下，不寻常的事情是您已经完成了 BIOS/CSM/legacy-mode 安装，这意味着操作系统安装不应进行此类更改。我的猜测是，您在固件本身中从 EFI 模式启动更改为 BIOS 模式启动已导致错误显现；或者也许改变一些其他固件设置做到了。

有多种方法可以解决此问题，例如：

• You can unplug your hard disk and boot the computer. This normally causes it to launch the setup utility.
• If you boot Ubuntu in EFI mode (say, the installer booted in this way), typing sudo systemctl reboot --firmware-setup in a shell should reboot into the firmware setup utility.
• Some EFI-mode (but not BIOS-mode) boot managers provide an option to boot into the firmware setup utility. GRUB has this functionality, but I'm not sure if it's enabled by default in Ubuntu, and as you're using the BIOS-mode version, this point is moot. You can, though, use my rEFInd boot manager on a USB flash drive or CD-R (there are download images for both on the page to which I've just linked). The option should appear on the second row of (smaller) icons. You can also use rEFInd to boot your regular installation to EFI mode to use systemctl, if you like.

Note that Boot Repair is very unlikely to solve the problem, since it's caused by issues in the firmware before GRUB (or anything else provided by Ubuntu) takes control of the computer.

Once you're in the setup utility, using the option to reset the firmware to its defaults is likely to fix the problem, but I can't promise that. Given your configuration, you'd need to either switch the CSM back on or add an EFI-mode boot loader to the disk to get booting again, and either procedure runs at least some risk of re-creating the problem.

As this is a firmware bug, looking for an update from the manufacturer is worth doing. If there is no update, I recommend you report the bug; manufacturers can't fix bugs if they don't know they exist.

Note that this case illustrates one advantage of booting in EFI mode: There are ways to get into the firmware setup utility from the boot manager or OS. EFI-mode booting is also usually a little bit faster, it's less restrictive on large (over-2TiB) disks, it supports Secure Boot, it's the native boot mode on modern hardware (meaning it's less likely to create confusion, as described on this page of mine), and it has some other minor advantages over BIOS-mode booting. For these reasons, I generally recommend EFI-mode installations on new hardware unless there's a compelling reason to do a BIOS-mode install.

You can safely ignore the complaint about boot files residing far from the start of the disk. That's been a recurring problem with BIOSes, with the definition of "far" changing over time. Your disk is only 119.2 GiB, with the caveat that you've shown output for /dev/sdb but not /dev/sda, so if /dev/sda is bigger and the boot loader is installed there, it could be an issue. On most modern computers, I'd expect the BIOS (or EFI's CSM) to be able to read up to 2 TiB, so any disk smaller than that should be OK.

I suspect that your GParted problems are unrelated to anything else, but they are troubling. They could indicate a disk that's failing -- but it's more likely random filesystem corruption, particularly if the computer has hung or completely crashed at any point. I strongly recommend you look into this, but as I suspect it's a separate issue from your main problem, I won't provide advice on this here.