技术解析

Archlinux 升级内核报错
0
2021-06-30 12:38:04
idczone

Updating module dependencies. Please wait ...

正在运行后处理挂钩...

Updating linux initcpios

==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'

-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img

==> Starting build: 4.11.3-1-ARCH

-> Running build hook: [base]

-> Running build hook: [udev]

-> Running build hook: [autodetect]

-> Running build hook: [modconf]

-> Running build hook: [block]

-> Running build hook: [filesystems]

-> Running build hook: [keyboard]

-> Running build hook: [fsck]

==> ERROR: file not found: `fsck.btrfs'

==> WARNING: No fsck helpers found. fsck will not be run on boot.

==> Generating module dependencies

==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img

==> WARNING: errors were encountered during the build. The image may not be

complete.

==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'

-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-

fallback.img -S autodetect

==> Starting build: 4.11.3-1-ARCH

-> Running build hook: [base]

-> Running build hook: [udev]

-> Running build hook: [modconf]

-> Running build hook: [block]

==> WARNING: Possibly missing firmware for module: aic94xx

==> WARNING: Possibly missing firmware for module: wd719x

-> Running build hook: [filesystems]

-> Running build hook: [keyboard]

-> Running build hook: [fsck]

==> Generating module dependencies

==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img

==> Image generation successful

错误: 命令未能被正确执行

Arming ConditionNeedsUpdate...

事务成功完成.

不知道它指的是哪个命令未正确执行,实际使用倒是没遇到什么问题


哈哈,那我还是不要更新了。。。

两台 ARCH
升级的时候都是这个提示
实际没问题。

ERROR: file not found: `fsck.btrfs'
不是这个问题吗?

我刚才升级了,没报错

笔记本和台式机都是 arch,昨天晚上升级的,并没有什么问题。
![]( https://ooo.0o0.ooo/2017/05/31/592e0c7ec5e03.png
)

眼瞎没看到那条,回去看看 Thx



应该就是 btrfs 那报的错了

btrfs 没有 fsck 工具,所以不用理它 archlinux 的 wiki 有说明

昨晚升级的 没报错

不用理的,我这样好几年了。
另外不要用 btrfs,看 gentoo 的手册的这一段: https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disksnext generation filesystem that provides many advanced features such as snapshotting, self-healing through checksums, transparent compression, subvolumes and integrated RAID. A few distributions have begun to ship it as an out-of-the-box option, but it is not production ready. Reports of filesystem corruption are common. Its developers urge people to run the latest kernel version for safety because the older ones have known problems. This has been the case for years and it is too early to tell if things have changed. Fixes for corruption issues are rarely backported to older kernels. Proceed with caution when using this filesystem!
不要用 btrfs!

才注意到你也用的 btrfs。升级的时候由于有配色方案并且没有看到红色块,这种提示一般都是直接无视掉的。
我自己的机子和服务器一样都用 brtfs,服务器有过系统崩溃记录,然而,自用的机子没遇到过问题(大概一年了吧)。关于内核的话,arch 更新算比较勤快了。

用 zfs 吧,至少稳定

感谢提醒。找个机会换掉吧。

yaourt -S btrfs-progs

我也在几台不关键服务器和自己桌面用过 btrfs,有过不明原因的崩溃,没有遇过永久损伤。
btrfs 确实不能说是时间检验过的 FS,不过 snapshot 备份极其方便,而且桌面系统坏掉的影响有限,我觉得自己机器用一下还是不错的。

这个装了提示确实没了
看来 V2EX 被 btrfs 坑过的人还不少啊,下次换系统得考虑下换掉了

数据地带为您的网站提供全球顶级IDC资源
在线咨询
专属客服