☰

我的启动过程正常吗？启动需要 50 秒

tag-icon • tag-icon boot performance fsck
我的启动过程正常吗？启动需要 50 秒

这是我的 boot.log

resume: libgcrypt version: 1.5.0
fsck from util-linux 2.19.1
fsck from util-linux 2.19.1
fsck from util-linux 2.19.1
/dev/sda5: clean, 668102/3276800 files, 4449436/13107200 blocks
/dev/sda2: recovering journal
uhome: recovering journal
/dev/sda2: clean, 3030/74592 files, 200601/297200 blocks (check in 2 mounts)
uhome: clean, 282203/2621440 files, 8705593/10485760 blocks (check after next mount)
Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox
 * Starting AppArmor profiles       [170G 
[164G[ OK ]
 * Setting sensors limits       [170G 
[164G[ OK ]
Invalidating stale software suspend images... done.
 * Starting mDNS/DNS-SD daemon[164G[ OK ]
Starting DECnet... * Starting network connection manager[164G[ OK ]
done.
 * Stopping Failsafe Boot Delay[164G[ OK ]
 * Stopping System V initialisation compatibility[164G[ OK ]
 * Starting System V runlevel compatibility[164G[ OK ]
 * Starting Bumblebee supporting nVidia Optimus cards[164G[ OK ]
 * Starting LightDM Display Manager[164G[ OK ]
 * Starting save kernel messages[164G[ OK ]
 * Starting ACPI daemon[164G[ OK ]
 * Starting anac(h)ronistic cron[164G[ OK ]
 * Starting deferred execution scheduler[164G[ OK ]
 * Starting regular background program processing daemon[164G[ OK ]
 * Starting automatic crash report generation[164G[[31mfail[39;49m]
 * Stopping anac(h)ronistic cron[164G[ OK ]
 * Starting CPU interrupts balancing daemon[164G[ OK ]

fstab 的内容：

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sda5 during installation
UUID=d30f09f8-9580-4a6b-ac31-f69116793f9f /               ext4    errors=remount-ro 0       1
# /boot was on /dev/sda2 during installation
UUID=28309a48-2171-4784-8093-d0e5ca40e6de /boot           ext4    defaults        0       2
# /home was on /dev/sda6 during installation
UUID=4d7ee3e9-bf26-483d-af6e-efcd883126d0 /home           ext4    defaults        0       2
# swap was on /dev/sda10 during installation
UUID=f1a123f0-c81d-4f0a-9d5c-6780cbf8b9dc none            swap    sw              0       0

这是 dmesg 日志：http://paste.ubuntu.com/826319/‘

dmesg 日志显示 6 秒后出现了相当大的波动，它等待了太长时间才在第 24 秒再次启动。

fdisk -l和的输出mount：http://paste.ubuntu.com/826397/

我几乎禁用了所有可以禁用的服务，但启动仍然需要 50 秒。使用 Live USB 启动几乎只需要 25 秒。

启动过程在“resume libcrypt version”行处停止了大约 20 秒。并且每次启动时都会执行这些 fsck。这些 fsck 有必要吗？

编辑：引导图 启动图

答案1

正常启动时间为 40 秒（包括 BIOS）。您可能有一些“不太好”的硬件导致此问题。此外，您还必须在启动时保留许多东西并安装了许多软件包。但您不必担心。

答案2

您可以尝试启动终端，然后输入下面的代码，根据您的情况/需要进行修改。

sudo tune2fs -c 50 /dev/hda1

50 应该使系统每 50 次启动执行一次 fsck。50~100 被视为正常值。hda1 可能是 hda1、hda2、hda3... 或 sda1、sda2、sda3...，具体取决于您的设置。

您可以通过输入获取更多信息man tune2fs。向下箭头带您浏览手册页。

相关内容