kernel: integrity: Couldn‘t parse dbx signatures: -74

原创已于 2024-03-28 21:21:28 修改 · 1.1k 阅读

9 ·

本内容遵循CC 4.0 BY-SA版权协议

GEO检测

标签

#linux #ubuntu

于 2024-03-20 08:50:58 首次发布

linux 同时被 2 个专栏收录

532 篇文章

订阅专栏

37 篇文章

订阅专栏

现象：

Ubuntu 22.04.3 安装 OK，启动直接进入系统。

22.04.4 安装出现标题错误，此时，在进入系统的过程中，会出现信息，大意是：“Ctrl +C 取消文件系统检查”。

'UEFI 启动，在安装系统等时，需要向 BIOS中写入数据；如，在某台实体电脑上：OS 会在 BIOS里写入数据校验信息，22.04.3 写入成功，因此，不再需要进行文件系统检查。而 22.04.4 写入失败，因此，在启动过程中，OS默认就要进行文件系统了。

解决：

1. 有人说，升级 BIOS可以解决。

2. 有人说：可以无视它。

3. 还有人说：xxx

'UEFI capsule updates not available or [not] enabled in firmware setup': ThinkPad X230

https://github.com/fwupd/fwupd/issues/3584

/sys/firmware/efi/esrt/: does not exist.

/sys/firmware/efi/efivars/: exists.

And the message I get on boot is 'could not parse dbx signatures' (as against what I said it was above; sorry).

------

hughsie commented Nov 21, 2022

couldn't parse dbx signatures: -74" appears during the boot

That looks like the system BIOS doesn't know what to do with the new dbx contents. Maybe you could update the BIOS using an ISO file to see if that unlocks LVFS and dbx updates?

[ 1.204448] integrity: Couldn't parse dbx signatures: -74

https://ubuntuforums.org/showthread.php?t=2486089

Re: Will Not Start After Update

Go into your UEFI BIOS and disable SecureBoot.

This will not help with some computers. With those the EFI checks the files within the EFI partition and thinks that some of them are not secure...

For those, boot from an Ubuntu 2.04.2 LiveUSB and post the results of:
Code:
sudo efibootmgr -v

Couldn't parse dbx signatures : -74

https://github.com/hakuna-m/wubiuefi/issues/243

kernel: integrity: Couldn't parse dbx signatures: -74

https://bbs.archlinux.org/viewtopic.php?id=277394

The dbx database is not longer considered valid. Usually Windows machines gets updated via Windows Update, so Linux isn't able to read the UEFI dbx. There are ways to update bios via Linux, but I don't recommend you to mess with your bios. Just turn secure boot off (is not working anyway) and ignore that message.
Also you can try crossover or VM booting windows. Just a recent idea, not sure.