And then I ran sudo apt purge linux-image-5.10.0-16-amd64 linux-image-5.10.0-25-amd64 linux-image-5.10.0-26-amd64 linux-image-5.10.0-27-amd64 linux-image-5.10.0-28-amd64 which ran without any issue (all those configuration files were purged successfully).
However, when I retried running the migration, I received the same error as above (...remove old, unused kernels to free up some space in /boot/.)
Any ideas? Any help would be highly appreciated!
Zmlerf, so if we lookg at df -h | grep "Avail\|boot", do you really have less than 70M available ?
I guess we can also savagely edit the code with nano /usr/lib/python3/dist-packages/yunohost/migrations/0027_migrate_to_bookworm.py and comment / tweak the line but x_x
What’s really confusing is that you had quite a lof of kernels so I would expect removing them to free up more than 70MB
230M total is fine~ish … Some provider only configure 100M total by default sometimes (which is really tight and troublesome especially for people not super familiar with cleaning up old kernels which is not a straightforward / trivial operation)
Hey @rodinux@Aleks - thanks both of you so much for taking the time
As Aleks said, this is indeed not a straightforward operation. And when I run uname -r it returns surprisingly enough 5.10.0-29-amd64 which makes me a bit afraid to decide which kernel/s I should remove
Any help would be, again, truly appreciated
Usually upgrading a kernel need a reboot, then the grub will take the last kernel.
But first it’s necessary know if the begin of the migration have do some changes. It seems have just stopped with this warning…
What do yo see in /etc/apt/sources.list and /etc/apt/sources.list.d/yunohost.list ?
what returns yunohost tools versions ?
If nothing have really begin in the script of migration, you should after doing a sudo update-grub first reboot and see if you are using le last kernel, then clean old ones…
Hello @rodinux
While sudo cat /etc/apt/sources.list shows the following:
# deb cdrom:[Debian GNU/Linux 11 _Bullseye_ - Unofficial amd64 CD Binary-1 20220808-10:55]/ bullseye main non-free
#deb cdrom:[Debian GNU/Linux 11 _Bullseye_ - Unofficial amd64 CD Binary-1 20220808-10:55]/ bullseye main non-free
deb http://ftp.debian.org/debian bullseye main contrib
deb-src http://ftp.debian.org/debian bullseye main contrib
## YunoHost repository
deb http://forge.yunohost.org/debian/ bullseye stable
deb http://security.debian.org/debian-security bullseye-security main contrib non-free
deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free
# bullseye-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
deb http://ftp.debian.org/debian bullseye-updates main contrib non-free
deb-src http://ftp.debian.org/debian bullseye-updates main contrib non-free
# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.
The file /etc/apt/sources.list.d/yunohost.list does not exist.
Running sudo yunohost tools versions returns:
I presume this means the no changes were made by the migration? But tbh, I’m not really sure what does this all mean Should I run sudo update-grub then reboot then run uname -r or should I do something else? Thank you so much for taking the time, this is really kind of you!!
but feel free to write in French 
if you’re more comfortable!
should I try to remove a few others? Is it even normal the total size is 230M???
