On 5/18/23 4:21 PM, home user wrote:
(f37 stand-alone dual-boot workstation)
During this afternoon's patching (via dnf), a warning GUI popped up saying
/boot is full. It offered me the option to move /boot files to trash, but no
option to delete anything. I tried moving the rescue file to trash, but the
GUI said it couldn't. After the dnf patching finished, I removed the rescue
file via the rm command. But when I rebooted, the rescue option was still in
the grub menu.
I'm comfortable using rm in regular hard drive areas like /home. But I'm
neither a trained nor a professional sys.admin. I'm seriously uneasy about
simply rm-ing files in /boot. What should I clear out of /boot, and what's the
best-practice way?
Please tell me what specific information you need to help me so I can provide
it.
thanks,
Bill.
My /boot went from
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda3 485348 379984 75668 84% /boot
to
/dev/sda3 485348 130396 325256 29% /boot
The output from du -m for /boot dropped from 20 entries, total of 317
to:
-bash.3[boot]: du -m
1 ./lost+found
3 ./grub2/fonts
1 ./grub2/themes/system
3 ./grub2/themes/starfield
3 ./grub2/themes
3 ./grub2/i386-pc
5 ./grub2/locale
12 ./grub2
6 ./efi/EFI/fedora
1 ./efi/EFI/BOOT
7 ./efi/EFI
7 ./efi
1 ./loader/entries
1 ./loader
128 .
-bash.4[boot]:
Great improvement!
I'm marking this thread [SOLVED]. If the problem happens again, I'll open a
new thread.
I thank everyone who tried to help.
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
