私のシステムには次の設定がインストールされています。
mercurial@providence:~$ neofetch
_,met$$$$$gg. mercurial@providence
,g$$$$$$$$$$$$$$$P. --------------------
,g$$P" """Y$$.". OS: Debian GNU/Linux 10 (buster) x86_64
,$$P' `$$$. Host: XPS L501X A08
',$$P ,ggs. `$$b: Kernel: 4.19.0-6-amd64
`d$$' ,$P"' . $$$ Uptime: 7 mins
$$P d$' , $$P Packages: 2883 (dpkg)
$$: $$. - ,d$$' Shell: bash 5.0.3
$$; Y$b._ _,d$P' Resolution: 1366x768
Y$$. `.`"Y$$$$P"' DE: MATE
`$$b "-.__ WM: Metacity (Marco)
`Y$$ WM Theme: TraditionalOk
`Y$$. Theme: Clearlooks [GTK2/3]
`$$b. Icons: gnome [GTK2/3]
`Y$$b. Terminal: mate-terminal
`"Y$b._ Terminal Font: Monospace 10
`""" CPU: Intel i5 M 460 (4) @ 2.534GHz
GPU: NVIDIA GeForce GT 420M
GPU: Intel Core Processor
Memory: 1062MiB / 3683MiB
mercurial@providence:~$ uname -a
Linux providence 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) x86_64 GNU/Linux
今問題は、システムの起動時間が長すぎるということです。以下はスタートプロットです。
mercurial@providence:~$ systemd-analyze
Startup finished in 38.520s (kernel) + 26.496s (userspace) = 1min 5.017s
graphical.target reached after 26.478s in userspace
https://svgshare.com/i/FNK.svg
いくつかの問題を解決しようとしましたが、入ることができませんでした。
私の起動ログは次のとおりです。
Gave up waiting for suspend/resume device
Debian: clean, 934549/7528448 files, 9966424/30091008 blocks
[ OK ] Started Set console font and keymap.
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[ OK ] Started Create Volatile Files and Directories.
Starting Update UTMP about System Boot/Shutdown...
Starting Network Time Synchronization...
[ OK ] Started Update UTMP about System Boot/Shutdown.
[ OK ] Started udev Kernel Device Manager.
Starting Show Plymouth Boot Screen...
[ OK ] Started Load AppArmor profiles.
Starting Raise network interfaces...
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Reached target Local Encrypted Volumes.
[ OK ] Started Forward Password Requests to Plymouth Directory Watch.
[ OK ] Started Network Time Synchronization.
[ OK ] Reached target System Time Synchronized.
[ OK ] Created slice system-systemd\x2dbacklight.slice.
Starting Load/Save Screen Backlight Brightness of backlight:intel_backlight...
[ OK ] Started Load/Save Screen Backlight Brightness of backlight:intel_backlight.
[ OK ] Started Raise network interfaces.
Starting Load/Save Screen Backlight Brightness of leds:dell::kbd_backlight...
[ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[ OK ] Started Load/Save Screen Backlight Brightness of leds:dell::kbd_backlight.
Starting Load/Save RF Kill Switch Status...
[ OK ] Started Load/Save RF Kill Switch Status.
Starting Show Plymouth Boot Screen...
Starting Tell Plymouth To Write Out Runtime Data...
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[ OK ] Started Show Plymouth Boot Screen.
Starting Tell Plymouth To Write Out Runtime Data...
Starting Show Plymouth Boot Screen...
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Found device ST9500420AS 7.
Activating swap /dev/disk/by-uuid/c0198c37-f28b-41f5-bb0f-37d575e86896...
[ OK ] Activated swap /dev/disk/by-uuid/c0198c37-f28b-41f5-bb0f-37d575e86896.
[ OK ] Reached target Swap.
[ OK ] Reached target System Initialization.
[ OK ] Started Trigger anacron every hour.
[ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Listening on CUPS Scheduler.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Started Daily apt download activities.
[ OK ] Started CUPS Scheduler.
[ OK ] Reached target Paths.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Started Daily rotation of log files.
[ OK ] Started Daily man-db regeneration.
[ OK ] Listening on UUID daemon activation socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
[ OK ] Started CUPS Scheduler.
[ OK ] Started Manage Sound Card State (restore and store).
Starting Save/Restore Sound Card State...
Starting System Logging Service...
[ OK ] Started Run anacron jobs.
Starting Bluetooth service...
Starting Avahi mDNS/DNS-SD Stack...
[ OK ] Started Regular background program processing daemon.
Starting Modem Manager...
Starting Accounts Service...
Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down...
Starting Deferred execution scheduler...
Starting Disk Manager...
[ OK ] Started D-Bus System Message Bus.
Starting Network Manager...
Starting WPA supplicant...
Starting Login Service...
[ OK ] Started Daily apt upgrade and clean activities.
[ OK ] Reached target Timers.
[ OK ] Started System Logging Service.
[ OK ] Started Save/Restore Sound Card State.
[ OK ] Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down.
[ OK ] Started Deferred execution scheduler.
[ OK ] Started Login Service.
[ OK ] Started WPA supplicant.
[ OK ] Started Avahi mDNS/DNS-SD Stack.
[ OK ] Started Bluetooth service.
[ OK ] Reached target Bluetooth.
[ OK ] Started Make remote CUPS printers available locally.
[ OK ] Reached target Sound Card.
Starting Authorization Manager...
Starting Hostname Service...
[ OK ] Started Network Manager.
Starting Network Manager Wait Online...
[ OK ] Reached target Network.
Starting Permit User Sessions...
[ OK ] Started Unattended Upgrades Shutdown.
[ OK ] Started Permit User Sessions.
Starting Hold until boot process finishes up...
Starting Light Display Manager...
[ OK ] Started Hostname Service.
Starting Network Manager Script Dispatcher Service...
[ OK ] Started Network Manager Script Dispatcher Service.
[ OK ] Started Authorization Manager.
[ OK ] Started Accounts Service.
これについて少し検索してみると、GAVE UP WAITING FOR...これをターゲットにする人がいたので参考にしてください。
mercurial@providence:~$ sudo update-initramfs -u -k all
update-initramfs: Generating /boot/initrd.img-4.19.0-6-amd64
cryptsetup: ERROR: Couldn't resolve device
UUID=fee92c6d-7b60-4014-a66b-c48cd9094162
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
integration and avoid this warning.
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau
I: The initramfs will attempt to resume from /dev/sda7
I: (UUID=c0198c37-f28b-41f5-bb0f-37d575e86896)
I: Set the RESUME variable to override this.
update-initramfs: Generating /boot/initrd.img-4.19.0-5-amd64
cryptsetup: ERROR: Couldn't resolve device
UUID=fee92c6d-7b60-4014-a66b-c48cd9094162
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
integration and avoid this warning.
W: Possible missing firmware /lib/firmware/nvidia/gv100/acr/ucode_load.bin for module nouveau
I: The initramfs will attempt to resume from /dev/sda7
I: (UUID=c0198c37-f28b-41f5-bb0f-37d575e86896)
I: Set the RESUME variable to override this.
それは/dev/sda7私のスワップファイルです。
mercurial@providence:~$ sudo fdisk -l
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Disk model: ST9500420AS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc8000000
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 170128349 169921502 81G 7 HPFS/NTFS/exFAT
/dev/sda3 170144408 337927335 167782928 80G 7 HPFS/NTFS/exFAT
/dev/sda4 337930238 976769023 638838786 304.6G f W95 Ext'd (LBA)
/dev/sda5 337930240 727652351 389722112 185.9G 83 Linux
/dev/sda6 727654400 968382463 240728064 114.8G 83 Linux
/dev/sda7 968384512 976769023 8384512 4G 82 Linux swap / Solaris
mercurial@providence:~$ ls -la /dev/disk/by-uuid
total 0
drwxr-xr-x 2 root root 160 Oct 7 23:45 .
drwxr-xr-x 7 root root 140 Oct 7 23:45 ..
lrwxrwxrwx 1 root root 10 Oct 7 23:46 129C98019C97DE13 -> ../../sda3
lrwxrwxrwx 1 root root 10 Oct 7 23:46 3D9D2B1C080C3A89 -> ../../sda2
lrwxrwxrwx 1 root root 10 Oct 7 23:46 480488312682F440 -> ../../sda1
lrwxrwxrwx 1 root root 10 Oct 7 23:46 aec68856-488a-4c50-aa05-01af59b3ae0b -> ../../sda6
lrwxrwxrwx 1 root root 10 Oct 7 23:46 c0198c37-f28b-41f5-bb0f-37d575e86896 -> ../../sda7
lrwxrwxrwx 1 root root 10 Oct 7 23:46 d96d4546-92a2-49bf-b9d0-c00348d42395 -> ../../sda5
どうすればハーフあたり10秒未満でより早く始めることができますか？
ベストアンサー1
デフォルトでは、仮想ボックス内でスワップを無効にして削除した後、同じ問題が発生し、UUIDが混乱しました。これにより、タイムアウトの問題と依存関係のエラーが発生し、起動するたびにファイルシステムを強制的に確認できます。したがって、UUIDを更新する必要があります。
スワップパーティションが削除された場合（たとえば、意図的にHDからSSDに移行する場合）、ファイルは完全に/etc/initramfs-tools/conf.d/resume空白または読み取られなければなりませんRESUME=。 UUID番号を削除してください。RESUME=NONE無効です。スワップを使用するかどうかにかかわらず、回避策は次のとおりです。
トラブルシューティングのために（オプション）：
sudo cat /var/log/boot.log
正しいパーティション UUIDS をリストします。
sudo blkid -c /dev/null -o list
次の3つのファイルがblkidにリストされている正しいUUID設定を持っていることを確認し、正しいUUIDで上書きします。
/etc/fstab [for me swap was incorrect]
/etc/default/grub [for me RESUME=UUID was incorrect]
/boot/grub/grub.cfg [for me RESUME=UUID was incorrect]
次に、初期のRamファイルシステムを更新します。
update-initramfs -u
上記の3つのファイルを編集すると、cryptsetup: error: couldn't resolve deviceupdate-initramfsを実行したときにエラーが永久に解決されました。
これにより、UUIDを追加する必要はありませんが、/etc/initramfs-tools/conf.d/resumeまだ問題がある場合は、次のUUIDを追加するか、RESUME=UUID=c0198c37-f28b-41f5-bb0f-37d575e86896スワップRESUME=ファイルを使用しない場合は設定することをお勧めします。
次に、次を実行します。
update-initramfs -u
また、起動プロセスを高速化する/etc/default/grubに設定されていることを確認してください。GRUB_TIMEOUT=0ここで説明した内容がすべて終了したら、起動時に最後のファイルシステムチェックを一度実行しますが、1分30秒ではなく10秒で起動します。