Hey everyone! I'm new to Linux and I've been enjoying Linux Mint Cinnamon for a few days now. I made a bit of a blunder during installation by choosing my 1TB HDD instead of my 250GB SSD. After reinstalling on the SSD and formatting the HDD, I've started experiencing a major slowdown during boot. After the GRUB menu and the Linux Mint logo, my system hangs for about 2 minutes before showing an emergency mode screen and then continuing to boot up normally.
From my research, I suspect this might be caused by an error in my fstab file due to the HDD reformat. Below are the outputs of my fstab file and some block device info:
```bash
# /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).
#
#
# / was on /dev/sdb3 during installation
UUID=1c382ad5-a31b-4ca5-bb8e-0c36358c6512 / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda2 during installation
UUID=745C-ACA6 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
```
When checking with `lsblk`, I noticed this entry for my HDD:
```bash
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 ext4 1.0 HDD 719a52c1-9dcd-42fb-b340-8d03260c521a 846.9G 2% /run/timeshift/7589/backup
/media/jake/HDD
sdb
├─sdb1
├─sdb2 vfat FAT32 F75A-E4D3
└─sdb3 ext4 1.0 1c382ad5-a31b-4ca5-bb8e-0c36358c6512 193G 10% /
```
The line in the fstab related to `/boot/efi` appears to be pointing to a UUID that no longer exists. Is it correct to think this is causing my boot delay? How should I go about fixing this issue? If it helps, I've noticed an `efi` folder at `/boot/`, but it's empty.
3 Answers
It sounds like you’re on the right track! The entry for `/boot/efi` might still be referencing the old UUID from your previous installation. Try mounting the current EFI partition first to see if it has the right content. Use this command:
```bash
sudo mount UUID=F75A-E4D3 /boot/efi ; ls /boot/efi
```
If everything looks good there, swap that outdated UUID in your fstab with the new one, run `grub-install` and `update-grub`, then reboot to see if your boot time improves. Don’t comment out the line, as the EFI partition is essential for booting in the long run! Also, I'm curious about what sdb1 is; it could be worth looking into that if you don’t recognize it.
Checking your logs is a smart move too! Run this in the terminal:
```bash
journalctl -xr -p err
```
It may give you hints if your EFI partition is causing any errors. If you're feeling cautious, you can modify your fstab to change that final '1' to '0', which should prevent the system from checking that partition during boot, but only after verifying through the logs. Don’t forget to revert changes to fstab properly later!
What's showing up in the entry for "sdb2 vfat FAT32 F75A-E4D3"? That could give insight into whether it’s correctly set up for your system. If it looks empty or not as expected, it might further confirm that something went wrong during the reinstallation process.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures