25 posts were split to a new topic: Missing Codecs | Video playback not works all the time
Welcome to Fedora @louisel
I had to split your topic as it was to long and it was about more than they asked in the title.
Our forum, especially in the ask.fedora section, it is more like a FAQ. Users ask a question and we try to help figure it out. When they get a satisfying answer it is possible to use the option “mark as solution”. This way it gets indicated as a solved question and users can see this with a closed padlock under your title, in front of the Ask fedora Section.
About your problem with the /boot partition, it will be difficult to give you correct information, when you not show us how your hard-drive is sharing the two Linux installations. As Mint also is a Linux distribution it works very similar as Fedora but there are still some differences which can cause you Issues.
If you want to avoid problems that one of the OS ‘s is interfering into the other one, I propose to use Fedora in a VM. This way you can even let run both installations to the same time and it is possible to see the differences of both OS’ s.
An other better option would be that you use an external SDD to run fedora with a separate boot sector. This way you not destroy the other OS’s boot options from grub. It is also possible to swap the disks and you have always a running OS.
I gave you all this detailed information because you mention in the Title that you are new to Linux/Fedora.
1 Like
Hello,thanks for the advice. Unfortunately I don’t know why but the VM I tried didn’t convince me. I tried Fedora 42 KDM and it seemed even in the upgrade process that it lacked some things. I don’t remember well but no after install manip worked correcly for some reason.
Why not for the SSD but I don’t understand exactly how to do that, can you be more precise ?
You mean KDE right? KDE and Gnome are quite different. For the VM I do use Virtual-Machine-Manager. There is quite easy to start a ISO file for first look in to a different linux-version (without creating a vm-disk). If I install mostly I just use the default partitioning option and let Fedora do the rest. 20GB is mostly more as enough for a VM.
The separate SDD is just a External connected SDD drive. While installing you chose explicitly this drive and let everything install automatically from Fedor on it. If you make it this way it will also create a new EFI and /boot partition just for Fedora. In the Computers bios you set the boot option to the external ssd as default. If you not connect it will be the next working and this is your internal one.
Back to the /boot topic.
I also saw on your screenshots that the host-name is displaying a long number, when you share a screen shot of your terminal. This is also not normal. See here User@fedora in Terminal replaced with weird characters
Yes, KDE sorry. Okay for the 20GB and how it’s supposed to work through SDD, I’ll consider it maybe.
Linked to the article you sent :
hostnamectl
Static hostname: (unset)
Transient hostname: 2a01cb0808670f001a5754a6102a22e3.ipv6.abo.wanadoo.fr
Icon name: computer-laptop
Chassis: laptop 💻
Machine ID: 849aa82ba8864e6f9eb8bee234363e5f
Boot ID: fa544eacadc84684a790c3d652f4a5f1
Operating System: Fedora Linux 42 (Workstation Edition)
CPE OS Name: cpe:/o:fedoraproject:fedora:42
OS Support End: Wed 2026-05-13
OS Support Remaining: 1y 2d
Kernel: Linux 6.14.5-300.fc42.x86_64
Architecture: x86-64
Hardware Vendor: HP
Hardware Model: HP Pavilion Laptop 14-ce2xxx
Firmware Version: F.32
Firmware Date: Fri 2024-08-16
Firmware Age: 8month 3w 2d
Input of echo $PS1
❯ echo $PS1
\[\]~\[\] \[\]❯\[\]
I tried changing it through settings like the guy in the article. It seems it worked :
1 Like
Sorry for everything being in French, I’m a bit anxious to change the language in case it also changes the keyboard display. i don’t want losing access just because of a different keyboard layout.
In my “Disks” I noticed that I have two boot partitions :
The first one is very little, with very little space left. It may be what was set up with Windows back then, I kept it intact when I erased windows to only keep Mint. Didn’t format nor changed its size.
The second one is way bigger with much space left. I suppose it was created when I installed Fedora.
What does this mean exactly ? I don’t understand why Fedora would load its boot/update it in the little one, while it got the bigger one for itself ? Or do I misunderstand ?
Anyhow, the “/boot is full” message doesn’t show anymore as of yet, so it’s maybe solved. I don’t know.
boot/efi and /boot they have different purposes. When observing you can see that they are on different file systems.
What was stored on the motherboard In earlier times is now in a separate partition on the hard-disk. How this exactly works is explained here. This prepares your computer on a hardware level for the boot process. This partition can be shared with other Operating Systems.
While /boot is the partition which stores the different kernels, it works already on a software level communicating with the hardware declared in /boot/efi.
Command line tools to check your drivers for /boot/efi are:
fwupdmgr(driver management)efibootmgr(managing the boot sequences for efi boot)
Now the /boot partition is really for each Linux OS independent. Fedora and Linux Mint not use the same Kernels. With
uname -ayou can see the exact version from the kernel and to which Fedora Version it belongs
When updating the Kernel it goes to/bootpartition/directory. That is the reason why the partition for that is bigger.
I hope that this information helps you for the moment to understand the difference between this two /boot/efi and /boot partitions.
2 Likes
Okay ! I think I understand. Means I now have no issues with the boot, isn’t it ?
1 Like
Language, no worries works quite well. It’s quite easy to change the output language for a terminal session though
for a single command
eg. English
LANG=en_US.UTF-8 <command>
German:
LANG=de_DE.UTF-8 <command>
to switch for the session use
export LANG=en-US.UTF-8
and then just the commands.
can you pls post the output of
lsblk -f
sudo efibootmgr
ls -al /boot
1 Like
Nah, it’s because in my encrypted password I put a french symbol that probably isn’t in the english keyboard. Anyways !
I went into Mint Update Manager and erased one old kernel, I only kept the actual one (obviously) and the one before that. I guess it freed memory a bit.
Then, here is the result of the different inputs you gave :
lsblk -f
sudo efibootmgr
ls -al /boot
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
zram0 swap 1 zram0 929d6cce-efdb-4d5d-bcca-ac71fdfac438 [SWAP]
nvme0n1
├─nvme0n1p1 vfat FAT32 783D-0A38 34,9M 64% /boot/efi
├─nvme0n1p2 ext4 1.0 d1761ccf-b660-4486-aa47-9b86fd5006c5 600,2M 31% /boot
├─nvme0n1p3 crypto_L 2 0a05dcbf-ebe0-48b9-bb33-2dc853efe4a7
│ └─luks-0a05dcbf-ebe0-48b9-bb33-2dc853efe4a7
│ btrfs fedora 496fe340-50f9-493f-9e63-89876bcfed04 70,2G 22% /home
│ /
├─nvme0n1p4 ext4 1.0 d2185933-97ce-428e-86d9-e63fb41bd41b
├─nvme0n1p5 ext4 1.0 f092b29c-17c3-42f5-a4bc-ffa9a869175d
└─nvme0n1p6 ext4 1.0 ce6da053-b9c7-4e8e-a756-be8aa85a3c19
[sudo] Mot de passe de louise :
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,3001,2001,0002,3002,2002,2004,0000
Boot0001* Fedora HD(1,GPT,7f463d5a-6feb-42d3-b269-6cf37c80e921,0x800,0x32000)/\EFI\fedora\shimx64.efi
Boot0002* ubuntu HD(1,GPT,7f463d5a-6feb-42d3-b269-6cf37c80e921,0x800,0x32000)/\EFI\ubuntu\shimx64.efi
Boot2001* EFI USB Device RC
Boot3001* Internal Hard Disk or Solid State Disk RC
Boot3002* Internal Hard Disk or Solid State Disk RC
total 309633
dr-xr-xr-x. 8 root root 4096 9 mai 02:20 .
dr-xr-xr-x. 1 root root 180 9 mai 14:49 ..
-rw-r--r--. 1 root root 283136 24 mars 01:00 config-6.14.0-63.fc42.x86_64
-rw-r--r--. 1 root root 285772 2 mai 02:00 config-6.14.5-300.fc42.x86_64
drwx------. 5 root root 1024 1 janv. 1970 efi
drwxr-xr-x. 2 root root 4096 9 mai 02:20 extlinux
drwx------. 3 root root 4096 10 mai 15:42 grub2
-rw-------. 1 root root 176153061 8 mai 18:34 initramfs-0-rescue-849aa82ba8864e6f9eb8bee234363e5f.img
-rw-------. 1 root root 33220633 8 mai 18:35 initramfs-6.14.0-63.fc42.x86_64.img
-rw-------. 1 root root 32659605 8 mai 18:54 initramfs-6.14.5-300.fc42.x86_64.img
drwxr-xr-x. 3 root root 4096 8 mai 18:33 loader
drwx------. 2 root root 16384 8 mai 18:29 lost+found
lrwxrwxrwx. 1 root root 45 8 mai 18:33 symvers-6.14.0-63.fc42.x86_64.xz -> /lib/modules/6.14.0-63.fc42.x86_64/symvers.xz
lrwxrwxrwx. 1 root root 46 8 mai 18:53 symvers-6.14.5-300.fc42.x86_64.xz -> /lib/modules/6.14.5-300.fc42.x86_64/symvers.xz
-rw-r--r--. 1 root root 11588933 24 mars 01:00 System.map-6.14.0-63.fc42.x86_64
-rw-r--r--. 1 root root 11626784 2 mai 02:00 System.map-6.14.5-300.fc42.x86_64
drwxr-xr-x. 9 root root 4096 10 mai 01:00 timeshift
-rwxr-xr-x. 1 root root 16968040 8 mai 18:33 vmlinuz-0-rescue-849aa82ba8864e6f9eb8bee234363e5f
-rwxr-xr-x. 1 root root 16968040 24 mars 01:00 vmlinuz-6.14.0-63.fc42.x86_64
-rw-r--r--. 1 root root 160 24 mars 01:00 .vmlinuz-6.14.0-63.fc42.x86_64.hmac
-rwxr-xr-x. 1 root root 17242472 2 mai 02:00 vmlinuz-6.14.5-300.fc42.x86_64
-rw-r--r--. 1 root root 161 2 mai 02:00 .vmlinuz-6.14.5-300.fc42.x86_64.hmac
The LANG variable changes only the text output not the keyboard layout.
/boot looks good. Mint’s /boot is probably a normal directory in the partition 5 because it’s an ext4 filesystem.
You just need to make sure that the timeshift don’t grow too much. The space is needed when a new kernel in installed.
That part is the mint partition, I know because I had to reupdate grub with it since when I still had windows, I had to recover it since I unmounted it accidentally. I fixed it back then but it seems it lost the mint name, while the fedora partition is called fedora
Good, does it mean my boot partition is normal ? Do I do update refresh then, or will it undo everything we’ve done so far ?
Thanks for the timeshift advice, I’ll make sure it saves at the right place or even on an external drive if possible then
yes, this looks good.
1 Like
I know you’ve gotten all of your problems resolved, but my thoughts, after seeing your disk layout and partition sizes is that you shouldn’t have had problems with your /boot partition. Adding another kernel shouldn’t add much more that another 100MB or so. I didn’t see any files in your ls -al result that weren’t Fedora-related, so I don’t think your Mint installation is using this partition. Maybe look at your mountpoints to see what partition is mounted at /boot the next time you boot Mint. But storing Timeshift data on this partition would likely be a problem if you’re saving more than one snapshot. Like someone else mention, you’re likely going to be okay with adding another kernel to the mix and discontinuing the Timeshift thing on this partition.
On the other hand, I noticed that you have a pretty small EFI partition. Did you say that you had Windows on this same system? I wonder if you had a transition period of time when you uninstalled Windows where your EFI partition was running out of space.
Thanks for your insight, I’m relieved to see that multiple people validate that my booting would be okay from now on.
I know that Mint mounts on nvme0n1p5 because I had to re-update Grub even before I erased windows. I unmounted mint partition by mistake and had to remount + grub update it. I don’t know if it answers your question.
It’s noted for Time shift, I’d definitely be more wary about that. That booting part was never mentioned when I heard of Timeshift in YouTube so I learnt the hard way let’s say.
About the Efi partition :
First I was on windows 10 only.
Second, I was on windows + mint. I had it done by a computer shop near my house since I was anxious about partitioning going wrong.
Then I erased windows just slightly after putting mint back to grub as mentioned upwards. It was much voluntary because I got enough of it and that grub issue was just the drop on the camel’s back lol. So at this moment, it was a Mint only boot, on this week’s Tuesday or so.
Then I tried dual booting fedora on Thursday this week. The install worked but triggered some issues we’re searching about in another discussion because it’s not linked to boot.
All of this in around a month or so lol 
I have no idea of how little or big the EFI partition was before because I was just told not to touch it when I erased windows, so I didn’t take attention. I guess it was little already ?
Having timeshift miss configured seems to cause it to write backups to the /boot.
The partition was filled because of that issue.
You should be able to delete /boot/timeshift and its contents to get the disk space back.
But make sure that timeshift does not write there again.
1 Like
I relaunched the commands into Mint just to give you confirmation :
And it seems what I understood, one part is on efi boot and the other is into the ~5 partition
Yes, I’ll definitely be wary of that now. Thanks for the confirmation. I guess I’ll make sure it’s registered on the main partition or even better, on an external SSD that I’d update every time necessary/once a week or so
Did you delete the files from /boot/timeshift to get the disk space back?
1 Like