最近、SSDをより大きなSSDに交換しました。 Clonezilla を使用して、古いディスクを新しいディスクに複製しました。その後、私は GParted Live を使用して既存のパーティションのサイズを変更し、スワップパーティションをディスクの最後にプッシュしました。 Ubuntu 16.04から18.04にもアップデートしました。
上記の手順を正常に完了した後、起動時間がはるかに長くなったことに気づきました。私はいくつかの同様のスレッド(以下にリンクされています)を見つけ、そこで提案されているものを試しました。ただし、起動時間は、ディスク交換前の時間には短縮されませんでした。
これが私のオリジナル/etc/fstab
です。
# /etc/fstab: static file system information.
#
# Use 'blkid' 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>
# / was on /dev/sda1 during installation
UUID=e15b2ef7-c32d-46f5-a3a8-4bdc60285b4e / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=3a0c2581-52f2-4c92-9c4a-09d3f0258c05 none swap sw 0 0
/dev/disk/by-id/usb-Generic_USB_Flash_Disk-0:0 /mnt/usb-Generic_USB_Flash_Disk-0:0 auto nosuid,nodev,nofail,x-gvfs-show 0 0
blkidコマンドの出力を調べて、UUID
パーティションのswap
をすでに置き換えました。
/dev/sda1: UUID="e15b2ef7-c32d-46f5-a3a8-4bdc60285b4e" TYPE="ext4" PARTUUID="000d7e8b-01"
/dev/sda5: LABEL="swap" UUID="839f9d78-77b2-491d-808d-8cd551a9eeef" TYPE="swap" PARTUUID="000d7e8b-05"
/dev/disk/by-id/usb-..
もコメントアウトしました。これは、これがGParted Liveを起動したUSBスティックであると考えているためです。なぜそれがまだそこに定義されているのか分かりません。
# /etc/fstab: static file system information.
#
# Use 'blkid' 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>
# / was on /dev/sda1 during installation
UUID=e15b2ef7-c32d-46f5-a3a8-4bdc60285b4e / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
# UUID=3a0c2581-52f2-4c92-9c4a-09d3f0258c05 none swap sw 0 0
UUID=839f9d78-77b2-491d-808d-8cd551a9eeef none swap sw 0 0
# /dev/disk/by-id/usb-Generic_USB_Flash_Disk-0:0 /mnt/usb-Generic_USB_Flash_Disk-0:0 auto nosuid,nodev,nofail,x-gvfs-show 0 0
/var/log/boot.log
は以下を示します。
Starting Tell Plymouth To Write Out Runtime Data...
[ OK ] Started Braille Device Support.
[ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Starting Load/Save RF Kill Switch Status...
[ OK ] Started Braille Device Support.
[ OK ] Started Load/Save RF Kill Switch Status.
[ OK ] Reached target Sound Card.
[ OK ] Started Braille Device Support.
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[ OK ] Started Raise network interfaces.
[ TIME ] Timed out waiting for device dev-disk-by\x2did-usb\x2dGeneric_USB_Flash_Disk\x2d0:0.device.
[DEPEND] Dependency failed for /mnt/usb-Generic_USB_Flash_Disk-0:0.
[ TIME ] Timed out waiting for device dev-disk-by\x2duuid-3a0c2581\x2d52f2\x2d4c92\x2d9c4a\x2d09d3f0258c05.device.
[DEPEND] Dependency failed for /dev/disk/by-uuid/3a0c2581-52f2-4c92-9c4a-09d3f0258c05.
[DEPEND] Dependency failed for Swap.
[ OK ] Reached target System Initialization.
[ OK ] Listening on UUID daemon activation socket.
[ OK ] Listening on PC/SC Smart Card Daemon Activation Socket.
[ OK ] Started Daily apt download activities.
...
systemd-analyzeコマンドは次のことを伝えます。
Startup finished in 36.037s (kernel) + 10.847s (userspace) = 46.885s
graphical.target reached after 10.835s in userspace
起動時間を改善するにはどうすればよいですか?
今日再び/var/log/boot.log
を調べたところ、この出力が見つかりました-デバイスを検索するときにtime-outに注意してください!:
Starting Tell Plymouth To Write Out Runtime Data...
[ OK ] Started Braille Device Support.
[ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Starting Load/Save RF Kill Switch Status...
[ OK ] Started Braille Device Support.
[ OK ] Started Load/Save RF Kill Switch Status.
[ OK ] Reached target Sound Card.
[ OK ] Started Braille Device Support.
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[ OK ] Started Raise network interfaces.
[* ] (1 of 2) A start job is running for dev-disk-by\x2did-usb\x2dGeneric_
[** ] (1 of 2) A start job is running for dev-disk-by\x2did-usb\x2dGeneric_
[*** ] (1 of 2) A start job is running for dev-disk-by\x2did-usb\x2dGeneric_
[ *** ] (2 of 2) A start job is running for dev-disk-by\x2duuid-3a0c2581\x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-by\x2duuid-3a0c2581\x2d5
[ ***] (2 of 2) A start job is running for dev-disk-by\x2duuid-3a0c2581\x2d5
[ **] (1 of 2) A start job is running for dev-disk-by\x2did-usb\x2dGeneric_
[ *] (1 of 2) A start job is running for dev-disk-by\x2did-usb\x2dGeneric_
[ **] (1 of 2) A start job is running for dev-disk-by\x2did-usb\x2dGeneric_
[ ***] (2 of 2) A start job is running for dev-disk-by\x2duuid-3a0c2581\x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-by\x2duuid-3a0c2581\x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-by\x2duuid-3a0c2581\x2d5
[*** ] (1 of 2) A start job is running for dev-disk-by\x2did-usb\x2dGeneric_
[** ] (1 of 2) A start job is running for dev-disk-by\x2did-usb\x2dGeneric_
[* ] (1 of 2) A start job is running for dev-disk-by\x2did-usb\x2dGeneric_
[** ] (2 of 2) A start job is running for dev-disk-by\x2duuid-3a0c2581\x2d5
[*** ] (2 of 2) A start job is running for dev-disk-by\x2duuid-3a0c2581\x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-by\x2duuid-3a0c2581\x2d5
[ *** ] (1 of 2) A start job is running for dev-disk-by\x2did-usb\x2dGeneric_
...
[ TIME ] Timed out waiting for device dev-disk-by\x2did-usb\x2dGeneric_USB_Flash_Disk\x2d0:0.device.
[DEPEND] Dependency failed for /mnt/usb-Generic_USB_Flash_Disk-0:0.
[ TIME ] Timed out waiting for device dev-disk-by\x2duuid-3a0c2581\x2d52f2\x2d4c92\x2d9c4a\x2d09d3f0258c05.device.
[DEPEND] Dependency failed for /dev/disk/by-uuid/3a0c2581-52f2-4c92-9c4a-09d3f0258c05.
[DEPEND] Dependency failed for Swap.
[ OK ] Reached target System Initialization.
[ OK ] Listening on UUID daemon activation socket.
[ OK ] Listening on PC/SC Smart Card Daemon Activation Socket.
...
「再開」ファイルがあると思います
/etc/initramfs-tools/conf.d/resume
これは、もう見つからないUUIDを指します。そのファイルを変更して、スワップパーティションの正しいUUIDをポイントし、実行することができます。
Sudo update-initramfs -u
バグレポートへの次のリンクのコメント#16と#17を参照してください。
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1763611
あなたのケースとバグレポートのケースには違いがあります、