☰

我的啟動過程正常嗎？開機需要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

正常開機時間為40s（包括BIOS）。您可能有一些“不太好的”硬體導致此問題。此外，您還必須在啟動時保留許多東西並安裝許多軟體包。但您不必擔心。

答案2

您可以嘗試啟動終端，然後輸入下面的程式碼，並根據您的情況/需求進行修改。

sudo tune2fs -c 50 /dev/hda1

50 應該會使系統每 50 次啟動執行一次 fsck。 50~100被認為是正常的。 hda1 可能是 hda1、hda2、hda3... 或 sda1、sda2、sda3...，取決於您的設定。

您可以透過輸入獲得更多資訊man tune2fs。這向下箭頭帶您瀏覽線上說明頁面。

相關內容