I use to have Ubuntu installed on a 64gb SSD… But then it needed more capacity.
So I cloned the SSD into one with 128gb capacity using the "Disks" application on Ubuntu (that comes pre-installed when you use the Ubuntu live boot (from usb in my case))
Now when I boot up, I get a screen I didn't get before and have to wait a few more minutes than normal. The screen I get is:
If I press the "del" (delete) button, it shows some details about what it's doing:
I don't know what this means and it would be helpful is someone could explain this behaviour and how to fix it.
(After waiting a few more minutes, the computer boots up as normal and working as expected. The SSD is successfully cloned)
update 1:
my /etc/fstab
file looks like:
~$ cat /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/sda5 during installation
UUID=6b1b7475-bcd1-426b-b60d-5488f952ef1a / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=bcd1-426b /boot/efi vfat umask=0077 0 1
/swapfile
the output of the command sudo lsblk -o UUID,NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL,MODEL
is:
~$ sudo lsblk -o UUID,NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL,MODEL
[sudo] password for user:
UUID NAME FSTYPE SIZE MOUNTPOINT LABEL MODEL
loop0 squashfs 143.8M /snap/code/52
loop2 squashfs 15.3M /snap/deno/15
loop3 squashfs 55.4M /snap/core18/1944
loop4 squashfs 217.9M /snap/gnome-3-34-1804/60
loop5 squashfs 219M /snap/gnome-3-34-1804/66
loop6 squashfs 163.3M /snap/gitkraken/167
loop7 squashfs 149.8M /snap/code/53
loop8 squashfs 161.1M /snap/gitkraken/168
loop9 squashfs 125.9M /snap/docker/471
loop10 squashfs 97.9M /snap/core/10577
loop11 squashfs 64.4M /snap/gtk-common-themes/1513
loop12 squashfs 95.8M /snap/rpi-imager/137
loop13 squashfs 95.8M /snap/rpi-imager/150
loop14 squashfs 31.1M /snap/snapd/10707
loop15 squashfs 97.9M /snap/core/10583
loop16 squashfs 64.8M /snap/gtk-common-themes/1514
loop17 squashfs 51M /snap/snap-store/518
loop18 squashfs 51M /snap/snap-store/498
loop19 squashfs 31.1M /snap/snapd/10492
loop20 55.5M /snap/core18/1988
sda 223.6G CT240BX500SSD1
174D-C0A1 ├─sda1 vfat 512M
├─sda2 1K
6b1b7475-bcd1-426b-b60d-5488f952ef1a └─sda5 ext4 223.1G /
sdb 465.8G WDC_WDS500G2B0A-00SM50
C0FB-211B ├─sdb1 vfat 100M
├─sdb2 16M
C27AFBDE7AFBCD63 ├─sdb3 ntfs 465.2G
1A20494E20493255 └─sdb4 ntfs 505M
i see that there is no match for bcd1-426b
.
Best Answer
My wild guess is that it might be trying to mount an additional drive or partition that is not there, and it is waiting for a timeout.
Look at the
/etc/fstab
file and try to spot items there that you think are not valid. In case of doubt, feel free to amend your question.Update:
I'm almost certain that the unique IDs of disks or partitions are different now than what your cloned system used to use.
The following command will reveal the current UUIDs of disks and partitions:
You might need to update the problematic entry in
/etc/fstab
with its current UUID.