您尚未登录。

#16 2019-08-28 16:34:18

Mr.I
路人丙
所在地: SH
注册时间: 2015-08-29
帖子: 167

Re: 系统无法启动,一直停在LOGO界面

jingmouren 说:

呃 俺只是看到这命令支持ext3和ext4,不知道是不是逻辑的。
分区里的内容用ISO系统看都在

呃,你能用 LiveCD 看到分区里的内容的话,那就说明你前面的那些 LVM 操作应该没有把分区弄坏掉。

你之前的那个 lvreduce 报错是不是像这样的? :

[root@CentOS7-Ansible ~]# lvreduce  -L 10g /dev/vda1
  Path required for Logical Volume "vda1".
  Please provide a volume group name
  Run `lvreduce --help' for more information.

照理说应该就是这个。

如果是的话,那么接下来,你要把启动失败时出现的问题的具体内容告诉我们。
如果不是的话,那么就把你之前运行 lvreduce 时报的错的具体内容 以及 启动失败时出现的那个问题的具体内容告诉我们。

然后我们才能继续帮你。


运维工程师,业余程序员,偶尔写写代码,对 ArchLinux 和 Gnome3 一见钟情 wink

离线

#17 2019-08-28 16:43:52

jingmouren
会员
注册时间: 2014-09-13
帖子: 65

Re: 系统无法启动,一直停在LOGO界面

昨天报的啥错今天已经记不得了
今天启动时报得错已经贴了,就是显示
Failed to mount /boot/efi
in meergency mode. after logging in , type "journalctl-xb" to view system logs. "systemcftl default" to boot into default mode
root...
(..Control-D...).

离线

#18 2019-08-28 17:01:30

Mr.I
路人丙
所在地: SH
注册时间: 2015-08-29
帖子: 167

Re: 系统无法启动,一直停在LOGO界面

那么,现在用 LiveCD 检查一下 /dev/sda1 里面的内容是否正常。

看看是否能够在 LiveCD 环境下正常挂载并读取里面的内容。

如果 EFI 分区里面没有问题的话,贴一下你的 fstab。

--------------------update----------------

看起来你的 EFI 分区应该没有问题,因为你的系统已经引导完毕了,那个错是在引导成功之后才出现的。看着像是 fstab 写坏掉了

最近编辑记录 Mr.I (2019-08-28 17:11:20)


运维工程师,业余程序员,偶尔写写代码,对 ArchLinux 和 Gnome3 一见钟情 wink

离线

#19 2019-08-28 17:34:59

依云
a.k.a. 百合仙子
所在地: 一个等待妹纸出现的地方
注册时间: 2011-08-21
帖子: 5,155
个人网站

Re: 系统无法启动,一直停在LOGO界面

jingmouren 说:

昨天报的啥错今天已经记不得了
今天启动时报得错已经贴了,就是显示
Failed to mount /boot/efi
in meergency mode. after logging in , type "journalctl-xb" to view system logs. "systemcftl default" to boot into default mode
root...
(..Control-D...).

所以你倒是敲 journalctl -xb 啊。

离线

#20 2019-08-28 17:45:16

jingmouren
会员
注册时间: 2014-09-13
帖子: 65

Re: 系统无法启动,一直停在LOGO界面

依云 说:
jingmouren 说:

昨天报的啥错今天已经记不得了
今天启动时报得错已经贴了,就是显示
Failed to mount /boot/efi
in meergency mode. after logging in , type "journalctl-xb" to view system logs. "systemcftl default" to boot into default mode
root...
(..Control-D...).

所以你倒是敲 journalctl -xb 啊。


ISO系统再chroot后 journalctl -xb没内容啊

现在在win,暂时没法贴fstab

最近编辑记录 jingmouren (2019-08-28 17:50:11)

离线

#21 2019-08-28 18:02:40

Mr.I
路人丙
所在地: SH
注册时间: 2015-08-29
帖子: 167

Re: 系统无法启动,一直停在LOGO界面

jingmouren 说:

ISO系统再chroot后 journalctl -xb没内容啊

依云的意思是,在启动失败报那个错的时候敲 journalctl -xb (先要 login)

实际上按照提示内容来就可以了:

in meergency mode. after logging in , type "journalctl-xb" to view system logs.

在紧急模式中,登录后,输入 "journalctl -xb" 来查看系统日志.

最近编辑记录 Mr.I (2019-08-28 18:09:08)


运维工程师,业余程序员,偶尔写写代码,对 ArchLinux 和 Gnome3 一见钟情 wink

离线

#22 2019-08-28 19:36:45

jingmouren
会员
注册时间: 2014-09-13
帖子: 65

Re: 系统无法启动,一直停在LOGO界面

在那个界面
啥也输入不了
倒是按了若干次Ctrl+D后才重启
不知道另有啥方式登进emergency mode

离线

#23 2019-08-28 22:36:49

依云
a.k.a. 百合仙子
所在地: 一个等待妹纸出现的地方
注册时间: 2011-08-21
帖子: 5,155
个人网站

Re: 系统无法启动,一直停在LOGO界面

jingmouren 说:

在那个界面
啥也输入不了
倒是按了若干次Ctrl+D后才重启
不知道另有啥方式登进emergency mode

谁让你一直按的……按一次,然后 root 登录(如果你有 root 密码就输入 root 密码)。应该都有提示的。
从 live 系统 chroot 进去之后,用 journalctl -n 1000 查看最近一千条消息。不够再加。这样找起来累一些但总是可以找到的。
如果你忘记了 root 密码也可以 live 系统进去之后改。

离线

#24 2019-08-29 08:54:35

jingmouren
会员
注册时间: 2014-09-13
帖子: 65

Re: 系统无法启动,一直停在LOGO界面

fstab
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=***                           /boot/efi      vfat    defaults,noatime 0 2
UUID=***  /              ext4    defaults,noatime 0 1
UUID=*** /home          ext2    defaults,noatime 0 2

journalctl
Aug 28 16:15:41 *-pc systemd[1]: Condition check resulted in Commit a transient machine-i>
Aug 28 16:15:41 *-pc systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache>
Aug 28 16:15:41 *-pc systemd[1]: Started Emergency Shell.
Aug 28 16:15:41 *-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 m>
Aug 28 16:15:41 *-pc systemd[1]: Reached target Emergency Mode.
Aug 28 16:15:41 *-pc systemd[1]: Condition check resulted in Rebuild Journal Catalog bein>
Aug 28 16:15:41 *-pc systemd[1]: Condition check resulted in Update is Completed being sk>
Aug 28 16:15:41 *-pc systemd[1]: systemd-modules-load.service: Main process exited, code=>
Aug 28 16:15:41 *-pc systemd[1]: systemd-modules-load.service: Failed with result 'exit-c>
Aug 28 16:15:41 *-pc systemd[1]: Failed to start Load Kernel Modules.
Aug 28 16:15:41 *-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 m>
Aug 28 16:15:41 *-pc systemd[1]: Condition check resulted in FUSE Control File System bei>
Aug 28 16:15:41 *-pc systemd[5281]: emergency.service: Executable /bin/plymouth missing, >
Aug 28 16:15:42 *-pc systemd[1]: Reloading.
Aug 28 16:15:43 *-pc systemd[1]: emergency.service: Succeeded.
Aug 28 16:15:43 *-pc systemd[1]: Stopped Emergency Shell.
Aug 28 16:15:43 *-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 ms>
Aug 28 16:15:43 *-pc systemd[1]: Condition check resulted in Create list of required stat>
Aug 28 16:15:43 *-pc systemd[1]: Condition check resulted in File System Check on Root De>
Aug 28 16:15:43 *-pc systemd[1]: Started Forward Password Requests to Wall Directory Watc>
Aug 28 16:15:43 *-pc systemd[1]: Starting Load Kernel Modules...
Aug 28 16:15:43 *-pc systemd[1]: Stopped target Emergency Mode.
Aug 28 16:15:43 *-pc systemd[1]: Mounting /boot/efi...
Aug 28 16:15:43 *-pc systemd[1]: Started Dispatch Password Requests to Console Directory >
Aug 28 16:15:43 *-pc systemd[1]: Condition check resulted in First Boot Wizard being skip>
Aug 28 16:15:43 *-pc systemd[1]: Condition check resulted in Create System Users being sk>
Aug 28 16:15:43 *-pc systemd[1]: Condition check resulted in Rebuild Hardware Database be>
Aug 28 16:15:43 *-pc systemd[1]: Condition check resulted in Virtual Machine and Containe>
Aug 28 16:15:43 *-pc systemd-modules-load[5299]: Failed to lookup module alias 'crypto_us>
Aug 28 16:15:43 *-pc systemd-modules-load[5299]: Failed to lookup module alias 'vboxsf': >
Aug 28 16:15:43 *-pc systemd-modules-load[5299]: Failed to lookup module alias 'vboxdrv':>
Aug 28 16:15:43 *-pc systemd-modules-load[5299]: Failed to lookup module alias 'vboxnetad>
Aug 28 16:15:43 *-pc systemd-modules-load[5299]: Failed to lookup module alias 'vboxnetfl>
Aug 28 16:15:43 *-pc systemd-modules-load[5299]: Failed to lookup module alias 'vboxpci':>
Aug 28 16:15:43 *-pc systemd-modules-load[5299]: Failed to lookup module alias 'uinput': >
Aug 28 16:15:43 *-pc systemd[1]: systemd-modules-load.service: Main process exited, code=>
Aug 28 16:15:43 *-pc systemd[1]: systemd-modules-load.service: Failed with result 'exit-c>
Aug 28 16:15:43 *-pc mount[5300]: mount: /boot/efi: <E6><9C><AA><E7><9F><A5><E7><9A><84> >
Aug 28 16:15:43 *-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 m>
Aug 28 16:15:43 *-pc systemd[1]: Failed to start Load Kernel Modules.
Aug 28 16:15:43 *-pc systemd[1]: boot-efi.mount: Mount process exited, code=exited, statu>
Aug 28 16:15:43 *-pc systemd[1]: boot-efi.mount: Failed with result 'exit-code'.
Aug 28 16:15:43 *-pc systemd[1]: Failed to mount /boot/efi.
Aug 28 16:15:43 *-pc systemd[1]: Dependency failed for Local File Systems.
Aug 28 16:15:43 *-pc systemd[1]: local-fs.target: Job local-fs.target/start failed with r>
Aug 28 16:15:43 *-pc systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
Aug 28 16:15:43 *-pc systemd[1]: systemd-ask-password-console.path: Succeeded.
Aug 28 16:15:43 *-pc systemd[1]: Stopped Dispatch Password Requests to Console Directory >
Aug 28 16:15:43 *-pc systemd[1]: systemd-ask-password-wall.path: Succeeded.
Aug 28 16:15:43 *-pc systemd[1]: Stopped Forward Password Requests to Wall Directory Watc>
Aug 28 16:15:43 *-pc systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache>
Aug 28 16:15:43 *-pc systemd[1]: Condition check resulted in Commit a transient machine-i>
Aug 28 16:15:43 *-pc systemd[1]: Started Emergency Shell.
Aug 28 16:15:43 *-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 m>
Aug 28 16:15:43 *-pc systemd[1]: Reached target Emergency Mode.
Aug 28 16:15:43 *-pc systemd[1]: Condition check resulted in Rebuild Journal Catalog bein>
Aug 28 16:15:43 *-pc systemd[1]: Condition check resulted in Update is Completed being sk>
Aug 28 16:15:43 *-pc systemd[1]: Condition check resulted in FUSE Control File System bei>
Aug 28 16:15:43 *-pc systemd[5302]: emergency.service: Executable /bin/plymouth missing, >

最近编辑记录 jingmouren (2019-08-29 09:01:49)

离线

#25 2019-08-29 09:54:14

Mr.I
路人丙
所在地: SH
注册时间: 2015-08-29
帖子: 167

Re: 系统无法启动,一直停在LOGO界面

其实你可以直接注释掉 fstab 里面的第一条再重启试试。

----------------------------

不过,还是先看下为什么挂载失败了吧。

那行日志我看到了:

Aug 28 16:15:43 *-pc mount[5300]: mount: /boot/efi: <E6><9C><AA><E7><9F><A5><E7><9A><84> >

但是没有贴全,而且这行日志还是带汉字的

<E6><9C><AA><E7><9F><A5><E7><9A><84>

这段东西是汉字:未知的

楼主你再来一次 journalctl,这次带上 -l 参数,并且把输出的日志重定向到一个文件里,再从文件里读出来。这样一定可以把日志完整地输出出来了

最近编辑记录 Mr.I (2019-08-29 10:02:17)


运维工程师,业余程序员,偶尔写写代码,对 ArchLinux 和 Gnome3 一见钟情 wink

离线

#26 2019-08-29 10:17:51

jingmouren
会员
注册时间: 2014-09-13
帖子: 65

Re: 系统无法启动,一直停在LOGO界面

Aug 29 09:15:20 *-pc systemd[1]: Started Create Static Device Nodes in /dev.
Aug 29 09:15:26 *-pc mtp-probe[331]: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7"
Aug 29 09:15:20 *-pc systemd[1]: Starting udev Kernel Device Manager...
Aug 29 09:15:26 *-pc mtp-probe[319]: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9"
Aug 29 09:15:23 *-pc systemd[1]: Started udev Kernel Device Manager.
Aug 29 09:15:26 *-pc mtp-probe[332]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6"
Aug 29 09:15:23 *-pc systemd-udevd[269]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Aug 29 09:15:26 *-pc mtp-probe[332]: bus: 1, device: 3 was not an MTP device
Aug 29 09:15:31 *-pc systemd-fsck[336]: /dev/sda7:没有问题,964219/9849600 文件,35121375/39321600 块
Aug 29 09:15:24 *-pc systemd-vconsole-setup[261]: /usr/bin/loadkeys failed with exit status 1.
Aug 29 09:15:26 *-pc mtp-probe[319]: bus: 1, device: 6 was not an MTP device
Aug 29 09:15:31 *-pc systemd-fsck[338]: fsck.fat 4.1 (2017-01-24)
Aug 29 09:15:31 *-pc systemd-fsck[338]: /dev/sda1: 708 files, 18006/65536 clusters
Aug 29 09:15:24 *-pc systemd-vconsole-setup[301]: /usr/bin/loadkeys failed with exit status 1.
Aug 29 09:15:26 *-pc mtp-probe[331]: bus: 1, device: 4 was not an MTP device
Aug 29 09:15:31 *-pc mount[391]: mount: /boot/efi: 未知的文件系统类型“vfat”.
Aug 29 09:15:24 *-pc systemd-udevd[257]: Process '/usr/lib/systemd/systemd-vconsole-setup' failed with exit code 1.
Aug 29 09:15:26 *-pc mtp-probe[339]: checking bus 1, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-1"
Aug 29 09:15:24 *-pc systemd-udevd[258]: Process '/usr/lib/systemd/systemd-vconsole-setup' failed with exit code 1.
Aug 29 09:15:26 *-pc mtp-probe[339]: bus: 1, device: 2 was not an MTP device
Aug 29 09:15:24 *-pc systemd-vconsole-setup[306]: /usr/bin/loadkeys failed with exit status 1.
Aug 29 09:15:24 *-pc systemd-udevd[287]: Process '/usr/lib/systemd/systemd-vconsole-setup' failed with exit code 1.
Aug 29 09:15:25 *-pc systemd[1]: Found device WDC_WD10SPZX-24Z10 SYSTEM.
Aug 29 09:15:26 *-pc systemd[1]: Found device WDC_WD10SPZX-24Z10 7.
Aug 29 09:15:26 *-pc systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Aug 29 09:15:26 *-pc systemd[1]: Reached target Local File Systems (Pre).
Aug 29 09:15:26 *-pc systemd[1]: Starting File System Check on /dev/disk/by-uuid/81a2a2d4-2c61-41d0-a060-09d3532ca548...
Aug 29 09:15:26 *-pc systemd[1]: Condition check resulted in Virtual Machine and Container Storage (Compatibility) being skipped.
Aug 29 09:15:26 *-pc systemd[1]: Starting File System Check on /dev/disk/by-uuid/C43F-E4AF...
Aug 29 09:15:27 *-pc systemd[1]: Started File System Check on /dev/disk/by-uuid/81a2a2d4-2c61-41d0-a060-09d3532ca548.
Aug 29 09:15:27 *-pc systemd[1]: Mounting /home...
Aug 29 09:15:27 *-pc systemd[1]: Mounted /home.
Aug 29 09:15:30 *-pc systemd[1]: Started File System Check on /dev/disk/by-uuid/C43F-E4AF.
Aug 29 09:15:30 *-pc systemd[1]: Mounting /boot/efi...
Aug 29 09:15:30 *-pc systemd[1]: boot-efi.mount: Mount process exited, code=exited, status=32/n/a
Aug 29 09:15:32 *-pc kernel: audit: type=1130 audit(1567041332.037:15): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 29 09:15:32 *-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 29 09:15:30 *-pc systemd[1]: boot-efi.mount: Failed with result 'exit-code'.
Aug 29 09:15:32 *-pc kernel: audit: type=1127 audit(1567041332.104:16): pid=397 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
Aug 29 09:15:32 *-pc audit[397]: SYSTEM_BOOT pid=397 uid=0 auid=4294967295 ses=4294967295 msg=' comm="systemd-update-utmp" exe="/usr/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success'
Aug 29 09:15:30 *-pc systemd[1]: Failed to mount /boot/efi.
Aug 29 09:15:30 *-pc systemd[1]: Dependency failed for Local File Systems.
Aug 29 09:15:30 *-pc systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Aug 29 09:15:30 *-pc systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
Aug 29 09:15:30 *-pc systemd[1]: systemd-ask-password-console.path: Succeeded.
Aug 29 09:15:32 *-pc kernel: audit: type=1130 audit(1567041332.200:17): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 29 09:15:32 *-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 29 09:15:30 *-pc systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
Aug 29 09:15:30 *-pc systemd[1]: systemd-ask-password-wall.path: Succeeded.
Aug 29 09:15:30 *-pc systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
Aug 29 09:15:30 *-pc systemd[1]: Reached target Timers.
Aug 29 09:15:30 *-pc systemd[1]: Reached target Network.
Aug 29 09:15:30 *-pc systemd[1]: Reached target Offline System Update (Pre).
Aug 29 09:15:30 *-pc systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Aug 29 09:15:30 *-pc systemd[1]: Started Emergency Shell.
Aug 29 09:15:30 *-pc systemd[1]: Reached target Emergency Mode.
Aug 29 09:15:30 *-pc systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
Aug 29 09:15:30 *-pc systemd[1]: Reached target Paths.
Aug 29 09:15:30 *-pc systemd[1]: Reached target Sockets.
Aug 29 09:15:31 *-pc systemd[1]: Started Flush Journal to Persistent Storage.
Aug 29 09:15:31 *-pc systemd[1]: Starting Create Volatile Files and Directories...
Aug 29 09:15:32 *-pc systemd[1]: Started Create Volatile Files and Directories.
Aug 29 09:15:32 *-pc systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
Aug 29 09:15:32 *-pc systemd[1]: Condition check resulted in Update is Completed being skipped.
Aug 29 09:15:32 *-pc systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Aug 29 09:15:32 *-pc systemd[1]: Started Update UTMP about System Boot/Shutdown.
Aug 29 09:15:32 *-pc systemd[1]: Startup finished in 4.415s (firmware) + 3.850s (loader) + 5.396s (kernel) + 16.540s (userspace) = 30.203s.
Aug 29 09:15:32 *-pc systemd[1]: System is tainted: local-hwclock
Aug 29 09:15:32 *-pc systemd[395]: emergency.service: Executable /bin/plymouth missing, skipping: No such file or directory
Aug 29 09:15:36 *-pc systemd[1]: Reloading.
Aug 29 09:15:36 *-pc systemd[1]: emergency.service: Succeeded.
Aug 29 09:15:36 *-pc systemd[1]: Stopped Emergency Shell.
Aug 29 09:15:36 *-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=emergency comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 29 09:15:36 *-pc systemd[1]: Started Forward Password Requests to Wall Directory Watch.
Aug 29 09:15:36 *-pc systemd[1]: Condition check resulted in Virtual Machine and Container Storage (Compatibility) being skipped.
Aug 29 09:15:36 *-pc systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Aug 29 09:15:36 *-pc systemd[1]: Stopped target Emergency Mode.
Aug 29 09:15:36 *-pc kernel: audit: type=1131 audit(1567041336.787:18): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=emergency comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 29 09:15:36 *-pc systemd[1]: Starting Load Kernel Modules...
Aug 29 09:15:36 *-pc kernel: audit: type=1131 audit(1567041336.790:19): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-lvmetad comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 29 09:15:36 *-pc kernel: audit: type=1130 audit(1567041336.794:20): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Aug 29 09:15:36 *-pc kernel: audit: type=1130 audit(1567041336.800:21): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=emergency comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 29 09:15:36 *-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-lvmetad comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 29 09:15:36 *-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-modules-load comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Aug 29 09:15:36 *-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=emergency comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 29 09:15:36 *-pc systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
Aug 29 09:15:36 *-pc systemd[1]: Condition check resulted in Create list of required static device nodes for the current kernel being skipped.
Aug 29 09:15:36 *-pc mount[419]: mount: /boot/efi: 未知的文件系统类型“vfat”.
Aug 29 09:15:36 *-pc systemd[1]: Stopping LVM2 metadata daemon...
Aug 29 09:15:36 *-pc systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
Aug 29 09:15:36 *-pc systemd[1]: Mounting /boot/efi...
Aug 29 09:15:36 *-pc systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Aug 29 09:15:36 *-pc systemd[1]: Condition check resulted in Create System Users being skipped.
Aug 29 09:15:36 *-pc systemd[1]: lvm2-lvmetad.service: Succeeded.
Aug 29 09:15:36 *-pc systemd[1]: Stopped LVM2 metadata daemon.
Aug 29 09:15:36 *-pc systemd-modules-load[418]: Failed to lookup module alias 'crypto_user': Function not implemented
Aug 29 09:15:36 *-pc systemd-modules-load[418]: Failed to lookup module alias 'vboxsf': Function not implemented
Aug 29 09:15:36 *-pc systemd-modules-load[418]: Failed to lookup module alias 'vboxdrv': Function not implemented
Aug 29 09:15:36 *-pc systemd-modules-load[418]: Failed to lookup module alias 'vboxnetadp': Function not implemented
Aug 29 09:15:36 *-pc systemd-modules-load[418]: Failed to lookup module alias 'vboxnetflt': Function not implemented
Aug 29 09:15:36 *-pc systemd-modules-load[418]: Failed to lookup module alias 'vboxpci': Function not implemented
Aug 29 09:15:36 *-pc systemd-modules-load[418]: Failed to lookup module alias 'uinput': Function not implemented
Aug 29 09:15:36 *-pc systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Aug 29 09:15:36 *-pc systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Aug 29 09:15:36 *-pc systemd[1]: Failed to start Load Kernel Modules.
Aug 29 09:15:36 *-pc systemd[1]: boot-efi.mount: Mount process exited, code=exited, status=32/n/a
Aug 29 09:15:36 *-pc systemd[1]: boot-efi.mount: Failed with result 'exit-code'.
Aug 29 09:15:36 *-pc systemd[1]: Failed to mount /boot/efi.

离线

#27 2019-08-29 10:33:07

Mr.I
路人丙
所在地: SH
注册时间: 2015-08-29
帖子: 167

Re: 系统无法启动,一直停在LOGO界面

jingmouren 说:

Aug 29 09:15:36 *-pc mount[419]: mount: /boot/efi: 未知的文件系统类型“vfat”.

Aug 29 09:15:36 *-pc systemd[1]: Failed to start Load Kernel Modules.
Aug 29 09:15:36 *-pc systemd[1]: boot-efi.mount: Mount process exited, code=exited, status=32/n/a
Aug 29 09:15:36 *-pc systemd[1]: boot-efi.mount: Failed with result 'exit-code'.
Aug 29 09:15:36 *-pc systemd[1]: Failed to mount /boot/efi.

看下你的内核版本,以及:

ls /usr/lib/modules
ls /usr/lib/modules/{你的内核版本}/kernel/fs/fat

最近编辑记录 Mr.I (2019-08-29 10:40:25)


运维工程师,业余程序员,偶尔写写代码,对 ArchLinux 和 Gnome3 一见钟情 wink

离线

#28 2019-08-29 10:55:07

jingmouren
会员
注册时间: 2014-09-13
帖子: 65

Re: 系统无法启动,一直停在LOGO界面

Linux manjaro-gnome 4.19.28-1-MANJARO #1 SMP PREEMPT Sun Mar 10 08:32:42 UTC 2019 x86_64 GNU/Linux

$ls /usr/lib/modules
4.19.28-1-MANJARO  extramodules-4.19-MANJARO

$ ls /usr/lib/modules/4.19.28-1-MANJARO/kernel/fs/fat
fat.ko.xz  msdos.ko.xz  vfat.ko.xz

chroot后
Linux manjaro-gnome 4.19.28-1-MANJARO #1 SMP PREEMPT Sun Mar 10 08:32:42 UTC 2019 x86_64 GNU/Linux
sh-5.0# ls /usr/lib/modules       
ls: cannot access '/usr/lib/modules': No such file or directory
sh-5.0# ls /usr/lib/modules-load.d/
bluez.conf  uinput.conf

注释/etc/fstab /boot/efi也不能启动, 停在Starting TLP system startup/shutdown
log
Aug 29 10:38:55 *-pc systemd[1]: Started OpenNTP Daemon.
Aug 29 10:38:55 *-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=openntpd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 29 10:38:55 *-pc systemd[1]: Reached target Multi-User System.
Aug 29 10:38:55 *-pc kernel: audit: type=1130 audit(1567046335.765:30): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=openntpd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 29 10:38:55 *-pc systemd[1]: Starting TLP system startup/shutdown...
Aug 29 10:38:55 *-pc systemd[1]: Reached target Graphical Interface.
Aug 29 10:38:56 *-pc tlp[594]: Applying power save settings...done.
Aug 29 10:38:56 *-pc tlp[594]: Setting battery charge thresholds...done.
Aug 29 10:38:56 *-pc systemd[1]: Started TLP system startup/shutdown.
Aug 29 10:38:56 *-pc systemd[1]: Startup finished in 4.338s (firmware) + 4.143s (loader) + 5.041s (kernel) + 6min 27.256s (userspace) = 6min 40.779s.
Aug 29 10:38:56 *-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=tlp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Aug 29 10:38:56 *-pc kernel: audit: type=1130 audit(1567046336.572:31): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=tlp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

最近编辑记录 jingmouren (2019-08-29 10:57:30)

离线

#29 2019-08-29 11:12:45

Mr.I
路人丙
所在地: SH
注册时间: 2015-08-29
帖子: 167

Re: 系统无法启动,一直停在LOGO界面

jingmouren 说:

chroot后
Linux manjaro-gnome 4.19.28-1-MANJARO #1 SMP PREEMPT Sun Mar 10 08:32:42 UTC 2019 x86_64 GNU/Linux
sh-5.0# ls /usr/lib/modules       
ls: cannot access '/usr/lib/modules': No such file or directory
sh-5.0# ls /usr/lib/modules-load.d/
bluez.conf  uinput.conf

你系统上的 /usr/lib/modules 直接整个目录都没了?! 你确定你没有找错地方吗,如果真的是整个目录全都没有了,那么基本上就没救了。


jingmouren 说:

注释/etc/fstab /boot/efi也不能启动, 停在Starting TLP system startup/shutdown

这个只是一种存在侥幸心的尝试。比如,如果你的 fstab 刚好在这个位置有问题,那么直接注释掉 EFI 这一行就可以了,因为 EFI 的任务只是引导而已,在完成引导进入系统之后,不挂载也是没关系的。而现在,这个做法已经可以排除掉了。


运维工程师,业余程序员,偶尔写写代码,对 ArchLinux 和 Gnome3 一见钟情 wink

离线

#30 2019-08-29 11:23:40

jingmouren
会员
注册时间: 2014-09-13
帖子: 65

Re: 系统无法启动,一直停在LOGO界面

manjaro-chroot后看确实没/usr/lib/modules了
我也很奇怪,因为pacman -Syu能执行,而且说已经是最新

离线

页脚