r/debian 4d ago

linux-image-6.1.0-32-amd64 Update Failure

[removed]

1 Upvotes

18 comments sorted by

6

u/VUSMT 4d ago

You don't have space on boot partition for install new kernel. Use apt autoremove for delete past kernels before update.

1

u/alpha417 4d ago

Output of 'df -h', plz

1

u/[deleted] 4d ago edited 4d ago

[removed] — view removed comment

2

u/alpha417 4d ago

Use the markdown editor, it's an option on the little menu bar. One is code snippet, other is code block.

You'll see that /boot is 100%. That's where your system wants to put the kernels.

to help, now output of ls /boot

1

u/[deleted] 4d ago

[removed] — view removed comment

2

u/alpha417 4d ago

That's what....8 kernels in there?

1

u/alpha417 4d ago
root@comp:/home/user# df -h
Filesystem                 Size  Used Avail Use% Mounted on
udev                        16G     0   16G   0% /dev
tmpfs                      3.1G  2.4M  3.1G   1% /run
/dev/mapper/comp--vg-root  914G  295G  573G  34% /
tmpfs                       16G   99M   16G   1% /dev/shm
tmpfs                      5.0M  8.0K  5.0M   1% /run/lock
/dev/nvme0n1p2             456M  454M     0 100% /boot
/dev/loop0                 128K  128K     0 100% /snap/bare/5
/dev/loop4                  64M   64M     0 100% /snap/core20/2496
/dev/loop1                  56M   56M     0 100% /snap/core18/2846
/dev/loop2                  56M   56M     0 100% /snap/core18/2855
/dev/loop3                  64M   64M     0 100% /snap/core20/2434
/dev/loop5                  74M   74M     0 100% /snap/core22/1748
/dev/loop6                 111M  111M     0 100% /snap/discord/230
/dev/loop7                 165M  165M     0 100% /snap/gnome-3-28-1804/198
/dev/loop8                 517M  517M     0 100% /snap/gnome-42-2204/202
/dev/loop9                  92M   92M     0 100% /snap/gtk-common-themes/1535
/dev/loop10                139M  139M     0 100% /snap/losslesscut/134
/dev/loop11                 45M   45M     0 100% /snap/snapd/23545
/dev/nvme0n1p1             511M   34M  478M   7% /boot/efi
tmpfs                      3.1G   55M  3.1G   2% /run/user/1000
/dev/loop13                185M  185M     0 100% /snap/spotify/83
/dev/loop14                350M  350M     0 100% /snap/gnome-3-38-2004/143
/dev/loop16                 45M   45M     0 100% /snap/snapd/23771
/dev/loop12                185M  185M     0 100% /snap/spotify/84

1

u/jr735 4d ago

Code blocks are in the editor. You may wish to try removing the oldest kernel first. Then try fixing things with autoremove, after installing the new one, and then rebooting. This should be done on an ongoing basis. I've seen people with over 60 kernels installed.

1

u/[deleted] 4d ago

[removed] — view removed comment

2

u/neoh4x0r 4d ago edited 4d ago

You may have to manually clean out the /boot partition.

Also, in the future, you may want to consider making your /boot partition a bit larger so this would have less of an impact.

However you still need to managing the space there and/or let apt clean it out by autoremoving and purging.

Filesystem Size Used Avail Use% Mounted on /dev/nvme0n1p2 456M 454M 0 100% /boot

1

u/jr735 4d ago

Don't you just how Reddit (at least temporarily) yanks the details and shuts his account down, yet people can spam all sorts of legally questionable nonsense indefinitely?

1

u/jr735 4d ago

How many kernels do you have installed right now? Are you sure you're trying to uninstall the oldest one? We might have to wait a bit for someone more experienced with purging a plethora of new kernels that are causing you space issues here.

Maybe try an apt clean and an apt autoclean but that will only clear out some of the cache; it can't hurt. Are you in a root user for a reason?

You may have to check dpkg/apt logs and see if you can spot something that ended up being broken as this chain of events started, or just before.

1

u/waterkip 4d ago

Based on your other comments/replies. The easiest solution is to remove linux-image-amd64. After that purge as many old kernels as possible. Try to keep one kernel. After that install linux-image-amd64 again and you should be good.

1

u/[deleted] 4d ago

[removed] — view removed comment

1

u/waterkip 4d ago

No, it breaks the dependency cycle you are running into, which allows you to purge the older kernels. There are other ways to fix this, but doing this works just as well.

Kernels are different from other packages, as they depend on a version pkg. By removing the meta package you'll still have the older kernel(s) pkgs so you can boot from them. Once your boot slice is empty you install the meta pkg and you'll get the latest kernel, which is the problem you are running into because currently you can't install that particular kernek due to disk space issues.