Beginners Questions • Re: [Software] sda1 Full - how to safely clear it?

Hello again. I'm afraid I'm just going around the houses. apt autoremove just tells me to run apt --fix-broken install, which stops because there is no room in the boot folder.

ulimit -c returns 0 and df -ah --sync returns

Code:

Filesystem                   Size  Used Avail Use% Mounted onsysfs                           0     0     0    - /sysproc                            0     0     0    - /procudev                         7.8G     0  7.8G   0% /devdevpts                          0     0     0    - /dev/ptstmpfs                        1.6G  1.5M  1.6G   1% /run/dev/mapper/debian--vg-root  878G   23G  811G   3% /securityfs                      0     0     0    - /sys/kernel/securitytmpfs                        7.8G     0  7.8G   0% /dev/shmtmpfs                        5.0M   12K  5.0M   1% /run/lockcgroup2                         0     0     0    - /sys/fs/cgrouppstore                          0     0     0    - /sys/fs/pstorebpf                             0     0     0    - /sys/fs/bpfsystemd-1                       -     -     -    - /proc/sys/fs/binfmt_miscmqueue                          0     0     0    - /dev/mqueuetracefs                         0     0     0    - /sys/kernel/tracingdebugfs                         0     0     0    - /sys/kernel/debughugetlbfs                       0     0     0    - /dev/hugepagesfusectl                         0     0     0    - /sys/fs/fuse/connectionsconfigfs                        0     0     0    - /sys/kernel/configramfs                           0     0     0    - /run/credentials/systemd-sysusers.serviceramfs                           0     0     0    - /run/credentials/systemd-sysctl.serviceramfs                           0     0     0    - /run/credentials/systemd-tmpfiles-setup-dev.service/dev/sda1                    455M  450M     0 100% /bootramfs                           0     0     0    - /run/credentials/systemd-tmpfiles-setup.servicebinfmt_misc                     0     0     0    - /proc/sys/fs/binfmt_misctmpfs                        1.6G  2.5M  1.6G   1% /run/user/1000/dev/sr0                     7.3G  7.3G     0 100% /media/cdrom0portal                       0.0K  0.0K  0.0K    - /run/user/1000/doc

Yet another one falls victim to that stupid practice of using a too small a /boot partition while having boatloads of free space on where it should actually be as a located as a directory on your / partition. Using that GD lvm now I notice that junk involved in the problem as I have seen many times. If this was a normal install with a / partition the solution would be simple you boot a live USB mount the / and /boot partitions, then copy the files to the /boot directory located on the /root partition followed by an edit of the /etc/fstab on mounted / to comment out/remove the /boot partition line then reboot with problem solved. As it is you are left with little choice as I do think the reason for that partition is the lvm cannot be booted from that is reason for the partition. The choices left are delete old not in use kernel files in the /boot manually to get the space to allow the --fix-broken to complete and get apt back working, the second backup all your important files nuke the install do fresh install and give the /boot partition a few GB of space so this has no possibility of ever happening again..

Statistics: Posted by RedGreen925 — 2025-01-29 00:56

---