manjaro (arch)安装完成后重启报错：Root device mounted successfully, but sbininit does not exist

最新推荐文章于 2025-11-10 02:22:27 发布

原创

最新推荐文章于 2025-11-10 02:22:27 发布 · 5k 阅读

11 ·

CC 4.0 BY-SA版权

在安装manjaro (arch) 后重启遇到错误：Root device mounted successfully, but /sbin/init does not exist。这是因为/usr被挂载到单独的分区导致的。解决方法包括不将/usr单独分区，或者通过修改init文件添加正确钩子。不单独分区的理由包括避免重装系统时的复杂性，而保持与/在一起。若仍希望分开，需处理引导和hook等，可以参考manjaro官方解决方案。" 131347376,8665662,kubelet CPU 绑核调整无需重启主机解决方案,"['kubelet', 'kubernetes']

manjaro (arch) 安装完成后重启报错：Root device mounted successfully, but /sbin/init does not exist.

前言

这个问题是我的大佬同学赖拐发现的，估计也有很多和他一样被鸟叔带入门linux的童鞋吧？哈哈，只能说实在可惜第三版出的时间太过久远（八年前），据说第四版已经出啦（今年十一），大家有能力去支持一下吧～

问题

言归正传，错误应该是在我们开开心心装好manjaro之后重启，本以为可爱的plasma-kde出现，结果出来了黑不溜秋的报错提示：

ERROR: Root device mounted successfully, but /sbin/init does not exist.

sh:can't access tty; job control turned off

[rootfs /]#

**实际上真正的原因是我们把/usr挂载在了单独的分区上。**具体的原因可以参考stackexchange的一篇问答，很有价值。这里稍作引用

As @Leiaz very correctly pointed out in the comments, /sbin in Arch (and by extension, Manjaro) is now a symlink to /usr/bin. This means that unless /usr is mounted, /usr/sbin/init will not exist. You therefore need to make sure that /usr is mounted by the initial ramdisk. That’s what the Arch wiki quote in your OP means:

If you keep /usr as a separate partition, you must adhere to the following requirem

最低0.47元/天解锁文章