Hey everyone! I'm a newbie fresh into using Linux Mint Cinnamon, and it's been pretty amazing. I made a bit of a mistake during installation—I accidentally installed it on my 1TB HDD instead of my 250GB SSD. After realizing this, I reinstalled it on the SSD and formatted the HDD. I never even booted from the HDD. However, I've noticed my system is taking quite a while to boot. It hangs at the Linux Mint logo for about 2 minutes before showing some emergency mode text and then finally boots up. I think this might be related to my fstab file since I reformatted the secondary HDD. Here's the relevant output from my fstab and lsblk commands. I suspect this line in my fstab could be causing the problem: "UUID=745C-ACA6 /boot/efi vfat umask=0077 0 1"—since that UUID seems non-existent now. Is this likely the issue? How do I properly edit the fstab file to fix it? By the way, I noticed there's an empty efi folder at /boot/. Any guidance would be super helpful!
3 Answers
Before editing the fstab, I'd recommend checking the logs. You can do this by running `journalctl -xr -p err` in the terminal. This will help you check for any errors related to the EFI partition. If everything looks fine, you could change that trailing '1' in the fstab line to '0', which stops it from checking that partition at boot. But definitely check the logs first to make sure you’re not missing any important issues!
It sounds like you've pinpointed the issue correctly! The line referencing `UUID=745C-ACA6` in your fstab is likely causing the delay because that UUID doesn't exist anymore. First, try manually mounting what you believe to be the correct EFI partition. Use this command: `sudo mount UUID=F75A-E4D3 /boot/efi; ls /boot/efi` to check if it's okay. If it is, you can go ahead and change that problematic line in the fstab to match the new UUID. After editing, don't forget to run `grub-install` and `update-grub` to ensure everything is in sync. Just be cautious—don't comment out that line permanently since you'll need the EFI partition in the future!
Good call on the fstab! I'm curious about what’s going on with `sdb2`. It looks like it's formatted as FAT32 (`vfat`), but you should double-check its contents. If it wasn't meant to be there or it doesn't contain anything useful, that could be another potential issue to sort out. Maybe consider investigating it further and ensure it's properly set up as your EFI partition?
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