Slow boot time after cloning disk and resizing partitions
1
I recently replaced an SSD with a larger SSD. I used Clonezilla to clone the old disk to the new one. After that I used GParted Live to resize the existing partition, pushing the swap partition to the end of the disk. I also updated from Ubuntu 16.04 to 18.04.
After successfully finishing above steps I notices that the boot time became much longer. I found a few similar threads (linked below) and tried what is suggested there. However, the boot time did not reduce to the amount before the disk change.
Here is my original /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
I already replaced the UUID of the swap partition by looking into the blkid command output:
/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"
I also commented out the /dev/disk/by-id/usb-.. since I believe this was the USB stick which I booted GParted Live from. No idea why it is still defined there.
# /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
The /var/log/boot.log shows the following:
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-byx2did-usbx2dGeneric_USB_Flash_Diskx2d0:0.device.
[DEPEND] Dependency failed for /mnt/usb-Generic_USB_Flash_Disk-0:0.
[ TIME ] Timed out waiting for device dev-disk-byx2duuid-3a0c2581x2d52f2x2d4c92x2d9c4ax2d09d3f0258c05.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.
...
The systemd-analyze command tells:
Startup finished in 36.037s (kernel) + 10.847s (userspace) = 46.885s
graphical.target reached after 10.835s in userspace
What can I do to improve the boot time?
Update
I looked into /var/log/boot.log again today and found this output - notice the time-out when searching for a device!:
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-byx2did-usbx2dGeneric_
[** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[*** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ ***] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ **] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[ *] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[ **] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[ ***] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[*** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[* ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[*** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
...
[ TIME ] Timed out waiting for device dev-disk-byx2did-usbx2dGeneric_USB_Flash_Diskx2d0:0.device.
[DEPEND] Dependency failed for /mnt/usb-Generic_USB_Flash_Disk-0:0.
[ TIME ] Timed out waiting for device dev-disk-byx2duuid-3a0c2581x2d52f2x2d4c92x2d9c4ax2d09d3f0258c05.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.
...
Related
- Slow boot time after resizing partitions. Editing fstab did not work
- Slow boot - “a start job is running for dev-disk-by…”
- Timed out waiting for device dev-disk-byx2duuid-C829x2dC4C1.device
- A start job is running for dev-disk-by x2duuid-ad0b043bx2d404c… .device (7s / 1min 30s)
ubuntu boot fstab gparted timeout
asked Jan 23 at 19:20
JJDJJD
2922722
add a comment |
1
I recently replaced an SSD with a larger SSD. I used Clonezilla to clone the old disk to the new one. After that I used GParted Live to resize the existing partition, pushing the swap partition to the end of the disk. I also updated from Ubuntu 16.04 to 18.04.
After successfully finishing above steps I notices that the boot time became much longer. I found a few similar threads (linked below) and tried what is suggested there. However, the boot time did not reduce to the amount before the disk change.
Here is my original /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
I already replaced the UUID of the swap partition by looking into the blkid command output:
/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"
I also commented out the /dev/disk/by-id/usb-.. since I believe this was the USB stick which I booted GParted Live from. No idea why it is still defined there.
# /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
The /var/log/boot.log shows the following:
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-byx2did-usbx2dGeneric_USB_Flash_Diskx2d0:0.device.
[DEPEND] Dependency failed for /mnt/usb-Generic_USB_Flash_Disk-0:0.
[ TIME ] Timed out waiting for device dev-disk-byx2duuid-3a0c2581x2d52f2x2d4c92x2d9c4ax2d09d3f0258c05.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.
...
The systemd-analyze command tells:
Startup finished in 36.037s (kernel) + 10.847s (userspace) = 46.885s
graphical.target reached after 10.835s in userspace
What can I do to improve the boot time?
Update
I looked into /var/log/boot.log again today and found this output - notice the time-out when searching for a device!:
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-byx2did-usbx2dGeneric_
[** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[*** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ ***] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ **] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[ *] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[ **] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[ ***] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[*** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[* ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[*** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
...
[ TIME ] Timed out waiting for device dev-disk-byx2did-usbx2dGeneric_USB_Flash_Diskx2d0:0.device.
[DEPEND] Dependency failed for /mnt/usb-Generic_USB_Flash_Disk-0:0.
[ TIME ] Timed out waiting for device dev-disk-byx2duuid-3a0c2581x2d52f2x2d4c92x2d9c4ax2d09d3f0258c05.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.
...
Related
- Slow boot time after resizing partitions. Editing fstab did not work
- Slow boot - “a start job is running for dev-disk-by…”
- Timed out waiting for device dev-disk-byx2duuid-C829x2dC4C1.device
- A start job is running for dev-disk-by x2duuid-ad0b043bx2d404c… .device (7s / 1min 30s)
ubuntu boot fstab gparted timeout
asked Jan 23 at 19:20
JJDJJD
2922722
add a comment |
1
1
1
I recently replaced an SSD with a larger SSD. I used Clonezilla to clone the old disk to the new one. After that I used GParted Live to resize the existing partition, pushing the swap partition to the end of the disk. I also updated from Ubuntu 16.04 to 18.04.
After successfully finishing above steps I notices that the boot time became much longer. I found a few similar threads (linked below) and tried what is suggested there. However, the boot time did not reduce to the amount before the disk change.
Here is my original /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
I already replaced the UUID of the swap partition by looking into the blkid command output:
/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"
I also commented out the /dev/disk/by-id/usb-.. since I believe this was the USB stick which I booted GParted Live from. No idea why it is still defined there.
# /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
The /var/log/boot.log shows the following:
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-byx2did-usbx2dGeneric_USB_Flash_Diskx2d0:0.device.
[DEPEND] Dependency failed for /mnt/usb-Generic_USB_Flash_Disk-0:0.
[ TIME ] Timed out waiting for device dev-disk-byx2duuid-3a0c2581x2d52f2x2d4c92x2d9c4ax2d09d3f0258c05.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.
...
The systemd-analyze command tells:
Startup finished in 36.037s (kernel) + 10.847s (userspace) = 46.885s
graphical.target reached after 10.835s in userspace
What can I do to improve the boot time?
Update
I looked into /var/log/boot.log again today and found this output - notice the time-out when searching for a device!:
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-byx2did-usbx2dGeneric_
[** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[*** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ ***] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ **] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[ *] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[ **] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[ ***] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[*** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[* ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[*** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
...
[ TIME ] Timed out waiting for device dev-disk-byx2did-usbx2dGeneric_USB_Flash_Diskx2d0:0.device.
[DEPEND] Dependency failed for /mnt/usb-Generic_USB_Flash_Disk-0:0.
[ TIME ] Timed out waiting for device dev-disk-byx2duuid-3a0c2581x2d52f2x2d4c92x2d9c4ax2d09d3f0258c05.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.
...
Related
- Slow boot time after resizing partitions. Editing fstab did not work
- Slow boot - “a start job is running for dev-disk-by…”
- Timed out waiting for device dev-disk-byx2duuid-C829x2dC4C1.device
- A start job is running for dev-disk-by x2duuid-ad0b043bx2d404c… .device (7s / 1min 30s)
ubuntu boot fstab gparted timeout
asked Jan 23 at 19:20
JJDJJD
2922722
I recently replaced an SSD with a larger SSD. I used Clonezilla to clone the old disk to the new one. After that I used GParted Live to resize the existing partition, pushing the swap partition to the end of the disk. I also updated from Ubuntu 16.04 to 18.04.
After successfully finishing above steps I notices that the boot time became much longer. I found a few similar threads (linked below) and tried what is suggested there. However, the boot time did not reduce to the amount before the disk change.
Here is my original /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
I already replaced the UUID of the swap partition by looking into the blkid command output:
/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"
I also commented out the /dev/disk/by-id/usb-.. since I believe this was the USB stick which I booted GParted Live from. No idea why it is still defined there.
# /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
The /var/log/boot.log shows the following:
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-byx2did-usbx2dGeneric_USB_Flash_Diskx2d0:0.device.
[DEPEND] Dependency failed for /mnt/usb-Generic_USB_Flash_Disk-0:0.
[ TIME ] Timed out waiting for device dev-disk-byx2duuid-3a0c2581x2d52f2x2d4c92x2d9c4ax2d09d3f0258c05.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.
...
The systemd-analyze command tells:
Startup finished in 36.037s (kernel) + 10.847s (userspace) = 46.885s
graphical.target reached after 10.835s in userspace
What can I do to improve the boot time?
Update
I looked into /var/log/boot.log again today and found this output - notice the time-out when searching for a device!:
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-byx2did-usbx2dGeneric_
[** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[*** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ ***] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ **] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[ *] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[ **] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[ ***] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[*** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[* ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
[** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[*** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (2 of 2) A start job is running for dev-disk-byx2duuid-3a0c2581x2d5
[ *** ] (1 of 2) A start job is running for dev-disk-byx2did-usbx2dGeneric_
...
[ TIME ] Timed out waiting for device dev-disk-byx2did-usbx2dGeneric_USB_Flash_Diskx2d0:0.device.
[DEPEND] Dependency failed for /mnt/usb-Generic_USB_Flash_Disk-0:0.
[ TIME ] Timed out waiting for device dev-disk-byx2duuid-3a0c2581x2d52f2x2d4c92x2d9c4ax2d09d3f0258c05.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.
...
Related
- Slow boot time after resizing partitions. Editing fstab did not work
- Slow boot - “a start job is running for dev-disk-by…”
- Timed out waiting for device dev-disk-byx2duuid-C829x2dC4C1.device
- A start job is running for dev-disk-by x2duuid-ad0b043bx2d404c… .device (7s / 1min 30s)
ubuntu boot fstab gparted timeout
ubuntu boot fstab gparted timeout
asked Jan 23 at 19:20
JJDJJD
2922722
asked Jan 23 at 19:20
JJDJJD
2922722
edited 2 days ago
JJD
asked Jan 23 at 19:20
JJDJJD
2922722
asked Jan 23 at 19:20
JJDJJD
2922722
asked Jan 23 at 19:20
JJDJJD
2922722
2922722
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
1
I suspect that there is a 'resume' file
/etc/initramfs-tools/conf.d/resume
which points to the UUID that is no longer found. You can modify that file to point to the correct UUID for the swap partition, and run
sudo update-initramfs -u
See comments #16 and #17 in the following link to a bug report,
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1763611
There is a difference between your case and the case in the bug report,
- in your case you are using a swap partition
- in the case of the bug report a swap file is used (so there is no swap partition, that should be pointed to).
answered Jan 24 at 15:49
sudodussudodus
1,46326
Yes, there is aresumefile with a UUID which matches the UUID3a0c2581-52f2-4c92-9c4a-09d3f0258c05of the swap partition in the original /etc/fstab which posted in my question.
– JJD
Jan 24 at 16:48
Good luck with modifying thatresumefile :-)
– sudodus
Jan 24 at 16:50
I replaced the UUID and executed the update command. Outputupdate-initramfs: Generating /boot/initrd.img-4.15.0-43-generic. I will reboot now.
– JJD
Jan 24 at 16:52
1
1. Are you using the ethernet (wired network) or the wifi or both? 2. Snaps are application programs, that are installed in a special way. They do not share the common libraries, and if I understand correctly, they can run in their own environment (at least to some degree). See this tutorial link
– sudodus
Jan 24 at 19:05
1
It can be difficult to troubleshoot problems afterdo-release-upgrade. I have no idea right now, but hope to come back later. Maybe you have better luck at the Ubuntu Forums, where the helpers are prepared for longer dialogues to help you try different methods, so start a thread there (at the Ubuntu Forums) with a good title and description of your problem, computer hardware and operating system (version of Ubuntu and that you have upgraded viado-release-upgrade).
– sudodus
Jan 28 at 12:52
|
show 9 more comments
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f496298%2fslow-boot-time-after-cloning-disk-and-resizing-partitions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
I suspect that there is a 'resume' file
/etc/initramfs-tools/conf.d/resume
which points to the UUID that is no longer found. You can modify that file to point to the correct UUID for the swap partition, and run
sudo update-initramfs -u
See comments #16 and #17 in the following link to a bug report,
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1763611
There is a difference between your case and the case in the bug report,
- in your case you are using a swap partition
- in the case of the bug report a swap file is used (so there is no swap partition, that should be pointed to).
answered Jan 24 at 15:49
sudodussudodus
1,46326
Yes, there is aresumefile with a UUID which matches the UUID3a0c2581-52f2-4c92-9c4a-09d3f0258c05of the swap partition in the original /etc/fstab which posted in my question.
– JJD
Jan 24 at 16:48
Good luck with modifying thatresumefile :-)
– sudodus
Jan 24 at 16:50
I replaced the UUID and executed the update command. Outputupdate-initramfs: Generating /boot/initrd.img-4.15.0-43-generic. I will reboot now.
– JJD
Jan 24 at 16:52
1
1. Are you using the ethernet (wired network) or the wifi or both? 2. Snaps are application programs, that are installed in a special way. They do not share the common libraries, and if I understand correctly, they can run in their own environment (at least to some degree). See this tutorial link
– sudodus
Jan 24 at 19:05
1
It can be difficult to troubleshoot problems afterdo-release-upgrade. I have no idea right now, but hope to come back later. Maybe you have better luck at the Ubuntu Forums, where the helpers are prepared for longer dialogues to help you try different methods, so start a thread there (at the Ubuntu Forums) with a good title and description of your problem, computer hardware and operating system (version of Ubuntu and that you have upgraded viado-release-upgrade).
– sudodus
Jan 28 at 12:52
|
show 9 more comments
1
I suspect that there is a 'resume' file
/etc/initramfs-tools/conf.d/resume
which points to the UUID that is no longer found. You can modify that file to point to the correct UUID for the swap partition, and run
sudo update-initramfs -u
See comments #16 and #17 in the following link to a bug report,
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1763611
There is a difference between your case and the case in the bug report,
- in your case you are using a swap partition
- in the case of the bug report a swap file is used (so there is no swap partition, that should be pointed to).
answered Jan 24 at 15:49
sudodussudodus
1,46326
Yes, there is aresumefile with a UUID which matches the UUID3a0c2581-52f2-4c92-9c4a-09d3f0258c05of the swap partition in the original /etc/fstab which posted in my question.
– JJD
Jan 24 at 16:48
Good luck with modifying thatresumefile :-)
– sudodus
Jan 24 at 16:50
I replaced the UUID and executed the update command. Outputupdate-initramfs: Generating /boot/initrd.img-4.15.0-43-generic. I will reboot now.
– JJD
Jan 24 at 16:52
1
1. Are you using the ethernet (wired network) or the wifi or both? 2. Snaps are application programs, that are installed in a special way. They do not share the common libraries, and if I understand correctly, they can run in their own environment (at least to some degree). See this tutorial link
– sudodus
Jan 24 at 19:05
1
It can be difficult to troubleshoot problems afterdo-release-upgrade. I have no idea right now, but hope to come back later. Maybe you have better luck at the Ubuntu Forums, where the helpers are prepared for longer dialogues to help you try different methods, so start a thread there (at the Ubuntu Forums) with a good title and description of your problem, computer hardware and operating system (version of Ubuntu and that you have upgraded viado-release-upgrade).
– sudodus
Jan 28 at 12:52
|
show 9 more comments
1
1
1
I suspect that there is a 'resume' file
/etc/initramfs-tools/conf.d/resume
which points to the UUID that is no longer found. You can modify that file to point to the correct UUID for the swap partition, and run
sudo update-initramfs -u
See comments #16 and #17 in the following link to a bug report,
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1763611
There is a difference between your case and the case in the bug report,
- in your case you are using a swap partition
- in the case of the bug report a swap file is used (so there is no swap partition, that should be pointed to).
answered Jan 24 at 15:49
sudodussudodus
1,46326
I suspect that there is a 'resume' file
/etc/initramfs-tools/conf.d/resume
which points to the UUID that is no longer found. You can modify that file to point to the correct UUID for the swap partition, and run
sudo update-initramfs -u
See comments #16 and #17 in the following link to a bug report,
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1763611
There is a difference between your case and the case in the bug report,
- in your case you are using a swap partition
- in the case of the bug report a swap file is used (so there is no swap partition, that should be pointed to).
answered Jan 24 at 15:49
sudodussudodus
1,46326
answered Jan 24 at 15:49
sudodussudodus
1,46326
answered Jan 24 at 15:49
sudodussudodus
1,46326
answered Jan 24 at 15:49
sudodussudodus
1,46326
1,46326
Yes, there is aresumefile with a UUID which matches the UUID3a0c2581-52f2-4c92-9c4a-09d3f0258c05of the swap partition in the original /etc/fstab which posted in my question.
– JJD
Jan 24 at 16:48
Good luck with modifying thatresumefile :-)
– sudodus
Jan 24 at 16:50
I replaced the UUID and executed the update command. Outputupdate-initramfs: Generating /boot/initrd.img-4.15.0-43-generic. I will reboot now.
– JJD
Jan 24 at 16:52
1
1. Are you using the ethernet (wired network) or the wifi or both? 2. Snaps are application programs, that are installed in a special way. They do not share the common libraries, and if I understand correctly, they can run in their own environment (at least to some degree). See this tutorial link
– sudodus
Jan 24 at 19:05
1
It can be difficult to troubleshoot problems afterdo-release-upgrade. I have no idea right now, but hope to come back later. Maybe you have better luck at the Ubuntu Forums, where the helpers are prepared for longer dialogues to help you try different methods, so start a thread there (at the Ubuntu Forums) with a good title and description of your problem, computer hardware and operating system (version of Ubuntu and that you have upgraded viado-release-upgrade).
– sudodus
Jan 28 at 12:52
|
show 9 more comments
Yes, there is aresumefile with a UUID which matches the UUID3a0c2581-52f2-4c92-9c4a-09d3f0258c05of the swap partition in the original /etc/fstab which posted in my question.
– JJD
Jan 24 at 16:48
Good luck with modifying thatresumefile :-)
– sudodus
Jan 24 at 16:50
I replaced the UUID and executed the update command. Outputupdate-initramfs: Generating /boot/initrd.img-4.15.0-43-generic. I will reboot now.
– JJD
Jan 24 at 16:52
1
1. Are you using the ethernet (wired network) or the wifi or both? 2. Snaps are application programs, that are installed in a special way. They do not share the common libraries, and if I understand correctly, they can run in their own environment (at least to some degree). See this tutorial link
– sudodus
Jan 24 at 19:05
1
It can be difficult to troubleshoot problems afterdo-release-upgrade. I have no idea right now, but hope to come back later. Maybe you have better luck at the Ubuntu Forums, where the helpers are prepared for longer dialogues to help you try different methods, so start a thread there (at the Ubuntu Forums) with a good title and description of your problem, computer hardware and operating system (version of Ubuntu and that you have upgraded viado-release-upgrade).
– sudodus
Jan 28 at 12:52
Yes, there is a
resume file with a UUID which matches the UUID 3a0c2581-52f2-4c92-9c4a-09d3f0258c05 of the swap partition in the original /etc/fstab which posted in my question.– JJD
Jan 24 at 16:48
Yes, there is a
resume file with a UUID which matches the UUID 3a0c2581-52f2-4c92-9c4a-09d3f0258c05 of the swap partition in the original /etc/fstab which posted in my question.– JJD
Jan 24 at 16:48
Good luck with modifying that
resume file :-)– sudodus
Jan 24 at 16:50
Good luck with modifying that
resume file :-)– sudodus
Jan 24 at 16:50
I replaced the UUID and executed the update command. Output
update-initramfs: Generating /boot/initrd.img-4.15.0-43-generic. I will reboot now.– JJD
Jan 24 at 16:52
I replaced the UUID and executed the update command. Output
update-initramfs: Generating /boot/initrd.img-4.15.0-43-generic. I will reboot now.– JJD
Jan 24 at 16:52
1
1
1. Are you using the ethernet (wired network) or the wifi or both? 2. Snaps are application programs, that are installed in a special way. They do not share the common libraries, and if I understand correctly, they can run in their own environment (at least to some degree). See this tutorial link
– sudodus
Jan 24 at 19:05
1. Are you using the ethernet (wired network) or the wifi or both? 2. Snaps are application programs, that are installed in a special way. They do not share the common libraries, and if I understand correctly, they can run in their own environment (at least to some degree). See this tutorial link
– sudodus
Jan 24 at 19:05
1
1
It can be difficult to troubleshoot problems after
do-release-upgrade. I have no idea right now, but hope to come back later. Maybe you have better luck at the Ubuntu Forums, where the helpers are prepared for longer dialogues to help you try different methods, so start a thread there (at the Ubuntu Forums) with a good title and description of your problem, computer hardware and operating system (version of Ubuntu and that you have upgraded via do-release-upgrade).– sudodus
Jan 28 at 12:52
It can be difficult to troubleshoot problems after
do-release-upgrade. I have no idea right now, but hope to come back later. Maybe you have better luck at the Ubuntu Forums, where the helpers are prepared for longer dialogues to help you try different methods, so start a thread there (at the Ubuntu Forums) with a good title and description of your problem, computer hardware and operating system (version of Ubuntu and that you have upgraded via do-release-upgrade).– sudodus
Jan 28 at 12:52
|
show 9 more comments
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f496298%2fslow-boot-time-after-cloning-disk-and-resizing-partitions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
