把最后两行删掉后,启动时间减少一些,还没彻底解决,而且我发现cat /etc/fstab与sudo fdisk -l查到的系统磁盘名不一致,看起来fstab文件存在较严重的问题,前面抓的log中除了俩已经移除的磁盘在开机时会检测外,之前连过电脑的移动硬盘记录也保存下来了,在开机时也会检测,检测这仨不存在的盘浪费不少时间,感觉像是deepin系统的基础功能没有搞好 😢
不过fstab中错误的磁盘分区名被屏蔽了。。。😂
把最后两行删掉后,启动时间减少一些,还没彻底解决,而且我发现cat /etc/fstab与sudo fdisk -l查到的系统磁盘名不一致,看起来fstab文件存在较严重的问题,前面抓的log中除了俩已经移除的磁盘在开机时会检测外,之前连过电脑的移动硬盘记录也保存下来了,在开机时也会检测,检测这仨不存在的盘浪费不少时间,感觉像是deepin系统的基础功能没有搞好 😢
不过fstab中错误的磁盘分区名被屏蔽了。。。😂
sudo cat /var/log/boot.log
请输入密码:
验证成功
Starting ModemManager.service - Modem Manager...
[ OK ] Started fprintd.service - Fingerprint Authentication Daemon.
Starting systemd-hostnamed.service - Hostname Service...
[ OK ] Started virtlogd.service - libvirt logging daemon.
[ OK ] Created slice system-deepin\x2dservice\x2dgroup.slice - Slice /system/deepin-service-group.
Starting dde-dconfig-daemon.service - dde-dconfig-daemon service...
[ OK ] Started deepin-service-group@app.service - deepin-service-manager.
[ OK ] Started udisks2.service - Disk Manager.
[ OK ] Started systemd-hostnamed.service - Hostname Service.
[ OK ] Stopped cups.path - CUPS Scheduler.
Stopping cups.path - CUPS Scheduler...
[ OK ] Started cups.path - CUPS Scheduler.
[ OK ] Closed cups.socket - CUPS Scheduler.
Stopping cups.socket - CUPS Scheduler...
[ OK ] Listening on cups.socket - CUPS Scheduler.
[ OK ] Started ModemManager.service - Modem Manager.
Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
[ OK ] Finished dpkg-db-backup.service - Daily dpkg database backup service.
[ OK ] Started dde-dconfig-daemon.service - dde-dconfig-daemon service.
[ OK ] Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
Starting dde-api-dbus-proxy-v1.service - dde-api-proxy-v1 service...
[ OK ] Started dde-api-dbus-proxy-v1.service - dde-api-proxy-v1 service.
[ OK ] Started NetworkManager.service - Network Manager.
[ OK ] Reached target network.target - Network.
Starting NetworkManager-wait-online.service - Network Manager Wait Online...
Starting cups.service - CUPS Scheduler...
Starting libvirt-guests.service - libvirt guests suspend/resume service...
[ OK ] Finished libvirt-guests.service - libvirt guests suspend/resume service.
[ OK ] Started cups.service - CUPS Scheduler.
[ OK ] Reached target printer.target - Printer Support.
[ OK ] Finished logrotate.service - Rotate log files.
[ OK ] Started vboxdrv.service - VirtualBox Linux kernel module.
Starting vboxautostart-service.service...
Starting vboxballoonctrl-service.service...
[ OK ] Started vboxautostart-service.service.
[ OK ] Started vboxballoonctrl-service.service.
Starting upower.service - Daemon for power management...
[ OK ] Started upower.service - Daemon for power management.
Starting deepin-devicecontrol.service - Deepin Device Control Daemon...
[ OK ] Started deepin-devicecontrol.service - Deepin Device Control Daemon.
[FAILED] Failed to start NetworkManager-wait-online.service - Network Manager Wait Online.
See 'systemctl status NetworkManager-wait-online.service' for details.
[ OK ] Reached target network-online.target - Network is Online.
Starting nmbd.service - Samba NMB Daemon...
[ OK ] Reached target remote-fs-pre.target - Preparation for Remote File Systems.
[ OK ] Reached target remote-fs.target - Remote File Systems.
Starting blk-availability.service - Availability of block devices...
[ OK ] Started cron.service - Regular background program processing daemon.
Starting libvirtd.service - libvirt legacy monolithic daemon...
Starting rpc-statd-notify.service - Notify NFS peers of a restart...
Starting samba-ad-dc.service - Samba AD Daemon...
[ OK ] Started spark-update-notifier.service - Spark Store update notifier.
Starting systemd-user-sessions.service - Permit User Sessions...
Starting vboxweb-service.service...
[ OK ] Finished blk-availability.service - Availability of block devices.
[ OK ] Started rpc-statd-notify.service - Notify NFS peers of a restart.
[ OK ] Started vboxweb-service.service.
[ OK ] Finished systemd-user-sessions.service - Permit User Sessions.
Starting lightdm.service - Light Display Manager...
Starting plymouth-quit-wait.service - Hold until boot process finishes up...
systemd-analyze blame
2min 24ms NetworkManager-wait-online.service
1.603s vboxdrv.service
1.298s plymouth-quit-wait.service
1.003s logrotate.service
816ms NetworkManager.service
795ms apt-daily-upgrade.service
520ms dev-nvme0n1p7.device
482ms deepin-devicecontrol.service
470ms dpkg-db-backup.service
446ms user@1000.service
427ms systemd-udev-trigger.service
409ms udisks2.service
387ms smbd.service
335ms accounts-daemon.service
302ms e2scrub_reap.service
298ms virtlogd.service
283ms upower.service
273ms com.home.appstore.daemon.service
251ms deepin-login-sound.service
249ms winbind.service
244ms polkit.service
229ms deepin-accounts1-daemon.service
227ms run-rpc_pipefs.mount
lines 1-23
看也看不懂,只知道开机很慢。
看也看不懂,只知道开机很慢。
具体仔细看下帖子的正文,已经附带了定位和解决的办法,一步一步操作下就行了, 大概的原因是在更换硬盘时系统内有一些旧盘的残留信息导致每次开机时都去尝试找之前的硬盘
Popular Events
More
系统是从2021年12月安装的,一直使用在线方式升级系统,开机慢的问题从2023年1月一直持续按到现在(2024年1月12日)了,系统也从20.8自动升级到20.9了,依然开机慢;把原机器中的机械仓库盘换成SSD也没有改善。
原来发过一个帖子,问题一直未得到解决,社区有懂这块的大神吗???请指导下,谢谢!🙂 🙂 🙂
之前配置:CPU Ryzen-5700G含集显、内存 海盗船2x16G + 光威2x32G、硬盘 一块西数PCE3.0 1TB + 一块西数HDD 4TB紫盘
当前配置(2024.01.11把HDD紫盘换成SSD):CPU Ryzen-5700G含集显、内存 海盗船2x16G + 光威2x32G、硬盘 一块西数PCE3.0 1TB + 一块梵想PCE3.0 2TB
当前系统:Deepin 20.9 内核版本 5.15.77
**旧帖子链接:**https://bbs.deepin.org/post/253353
-------------------------------😂 感谢各位的支持,拖了一整年的问题终于解决了,下面是复盘与解决流程😊 ---------------------------
问题
启动打印信息:
GRUB引导界面跳转后多按几次F1,可以看到打印信息。
boot log:
执行sudo cat /var/log/boot.log
log中的关键信息:
A start job is running for /dev/disk/by-uuid...............(.. / 1min 30s)
Timed out waiting for device /dev/disk/by-uuid...............
Dependency failed for /..........
Dependency failed for Crayptografy Setup for ..........
Dependency failed for Local Encrypted Volumes ..........
**问题的原因:**更换磁盘、改分区卷名等操作引起
/etc/fstab、/etc/crypttab文件内容未同步到准确的状态。解决流程
Step1:
sudo fdisk -lsudo cat /etc/fstab #针对情况1,确认fstab文件中磁盘的分区UUID、分区信息、文件系统信息等信息是否正确Step2:
sudo vi /etc/fstab #针对情况1,改正fstab中错误的分区UUID或分区信息或文件系统信息、注释或删除不存在的分区UUID对应的信息条目Step3:
sudo cat /etc/crypttab #针对情况2,查询解密流程是否依然会根据残留信息尝试解密Step4:
sudo vi /etc/crypttab #针对情况2,注释或删除残留的解密流程Step5:
sudo rm -rf /root/.deepin-diskmanager-service/xxxxxxxxxxxxxxxxxxxxxx.key #针对情况2,删除残留的加解密keyStep6:
sudo systemctl daemon-reload #重新载入服务文件Step7:
先关机,再重新开机,不建议直接使用reboot感谢
首先,特别感谢坛友的支持,问题解决了一半;
其次,国外有一个帖子也帮了大忙,删除残留的解密流程是通过这个帖子学会的,花了很长时间搜索sdb1_aesE、eb94c921-af43-43d5-8699-481ddf22e239等关键字,就是没找到在哪里,因此我把帖子链接一并附上: https://www.linux.org/threads/when-i-start-my-os-it-takes-long.36078/
反思
该问题似乎在linux上面出现挺多的,更换磁盘、重新分区等都有可能出现该问题,今天花了很多时间搜索,发现deepin、UOS论坛上面都有人反馈该问题,但是之前反馈的似乎都没解决,社区是否可以针对该问题做一个深入的优化呢?这种问题特别影响体验,对于普通小白,往往无从下手,不利于向普通消费群体推广哦。。。