Archlinux 升级内核报错

2017-05-30 22:54:48 +08:00
 Gehrman

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...

事务成功完成.

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

4441 次点击
所在节点    Linux
15 条回复
4ever911
2017-05-31 00:22:55 +08:00
哈哈,那我还是不要更新了。。。
showgood163
2017-05-31 01:20:09 +08:00
两台 ARCH

升级的时候都是这个提示

实际没问题。
cinhoo
2017-05-31 01:22:43 +08:00
ERROR: file not found: `fsck.btrfs'
不是这个问题吗?
4ever911
2017-05-31 01:27:52 +08:00
我刚才升级了,没报错
Suddoo
2017-05-31 08:23:37 +08:00
笔记本和台式机都是 arch,昨天晚上升级的,并没有什么问题。
![]( https://ooo.0o0.ooo/2017/05/31/592e0c7ec5e03.png
)
Gerhman
2017-05-31 08:39:35 +08:00
@cinhoo 眼瞎没看到那条,回去看看 Thx
@4ever911
@showgood163
@Suddoo
应该就是 btrfs 那报的错了
cd707
2017-05-31 08:45:37 +08:00
btrfs 没有 fsck 工具,所以不用理它 archlinux 的 wiki 有说明
strahe
2017-05-31 09:29:55 +08:00
昨晚升级的 没报错
reus
2017-05-31 09:47:23 +08:00
不用理的,我这样好几年了。
另外不要用 btrfs,看 gentoo 的手册的这一段: https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Disks#Creating_file_systems

A next 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!
showgood163
2017-05-31 11:33:59 +08:00
@Gerhman 才注意到你也用的 btrfs。升级的时候由于有配色方案并且没有看到红色块,这种提示一般都是直接无视掉的。

@reus 我自己的机子和服务器一样都用 brtfs,服务器有过系统崩溃记录,然而,自用的机子没遇到过问题(大概一年了吧)。关于内核的话,arch 更新算比较勤快了。
reus
2017-05-31 11:37:56 +08:00
@showgood163 用 zfs 吧,至少稳定
showgood163
2017-05-31 11:52:23 +08:00
@reus 感谢提醒。找个机会换掉吧。
mlyy
2017-05-31 12:37:44 +08:00
yaourt -S btrfs-progs
momocraft
2017-05-31 13:21:03 +08:00
我也在几台不关键服务器和自己桌面用过 btrfs,有过不明原因的崩溃,没有遇过永久损伤。

btrfs 确实不能说是时间检验过的 FS,不过 snapshot 备份极其方便,而且桌面系统坏掉的影响有限,我觉得自己机器用一下还是不错的。
Gerhman
2017-06-01 09:13:56 +08:00
@mlyy 这个装了提示确实没了

@reus 看来 V2EX 被 btrfs 坑过的人还不少啊,下次换系统得考虑下换掉了

这是一个专为移动设备优化的页面(即为了让你能够在 Google 搜索结果里秒开这个页面),如果你希望参与 V2EX 社区的讨论,你可以继续到 V2EX 上打开本讨论主题的完整版本。

https://www.v2ex.com/t/364799

V2EX 是创意工作者们的社区,是一个分享自己正在做的有趣事物、交流想法,可以遇见新朋友甚至新机会的地方。

V2EX is a community of developers, designers and creative people.

© 2021 V2EX