Actually this bug report is not about updates stopping working. This is
about not being able to remove a kernel with related packages completely
by usual ways due to a specific reason, if /boot becomes full enough.
There are other bug reports that call for bigger /boot partition or an
automatic
Sorry I was not clear enough.
When I said "Filled with" I meant that they were the files occupying space. I'm
sorry if that gave the idea that the corresponding vmlinuz-* files weren't
present - it was just that in terms of bytes occupied, the initrd files are the
big ones.
As you can see from
Please check out
https://help.ubuntu.com/community/ReportingBugs#Filing_a_general_bug_against_no_particular_package
(and the document in general). Please tell me the URL of the report
thereafter.
You told in #23 that you "Just ran in to this on Ubuntu 20.04", but to
be precise it is not even
Ok, did it.
That's freed up a load of space.
Where would I file the bug about having two sets of kernels?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra
Well, you could search for support in askubuntu.com. I think it may be a
bug that you have two flavors of kernels installed, if you did not
install the other manually. You might need to make a separate bug report
about that; removing the other flavor might be a workaround.
--
You received this
I've not yet found a way to make a USB boot that would allow me to start
the machine in the event of something going wrong. Without a plan to
revert the change, I'm a bit nervous. I know it *should* work fine - but
I don't want to suddenly have an unbootable laptop I can't rescue.
--
You
Hayden, did you try?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra package fails, if /boot is about full
To manage notifications about this bug go to:
Remove the older generic kernel by linux-purge and then try booting the
respective oem kernel via advanced grub menu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a
Oh, the versions do not match. I do not see how removing the hwe kernels
would make it unbootable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra package
Thanks for that advice.
I'm a bit in trepidation about removing the default HWE. How do I protect
myself from having an unbootable system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Hayden Clark, so you use "oem" kernels. If you do not need "generic"
kernels, you can save a lot of space in /boot by deleting all "generic"
kernels. Probably the easiest way to do it in your case is "sudo apt
autoremove linux-generic-hwe-20.04". Check that it does not remove any
"oem" kernels. If
And then I tried "sudo linux-purge --keep=1".
That has tidied up a bit, but there's still not much space?field.comment=And
then I tried "sudo linux-purge --keep=1".
That has tidied up a bit, but there's still not much space.
Now /boot contains:
# du -sh /boot/*
248K
Here is the result of linux-purge --info
My /boot is like this:
# du -sh /boot/*
248K/boot/config-5.10.0-1038-oem
248K/boot/config-5.10.0-1044-oem
248K/boot/config-5.11.0-25-generic
248K/boot/config-5.11.0-27-generic
244K/boot/config-5.8.0-63-generic
48M /boot/efi
8.0M
Could you attach output of "linux-purge --info"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra package fails, if /boot is about full
To manage
Did you run "sudo linux-purge --keep=1"? (or replace "1" by "0" to purge
even more)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra package fails, if /boot
I managed to get some free space back on /boot.
I'm posting this in the hopes that what I did may inform any fixing process.
1) List kernels with `dpkg -l | tail -n +6 | grep -E 'linux-image-[0-9]+'`
2) Delete the oldest initrd with update-initramfs -d -k 5.8.0-59-generic. There
was now 111Mb
I have now run linux-purge. It only freed up 50Mb or so, and no kernels
got removed
** Attachment added: "Directory listing for /boot"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+attachment/5512828/+files/slash-boot-contents-post-linux-purge.txt
--
You received
Ok, more information. Just got warned that /boot is full again.
I have attached a directory listing for /boot.
Where do I find the logs for the update process that's doing this?
** Attachment added: "Directory listing for /boot"
This was a fresh install of 20.04. I enabled encryption as it's a work laptop.
I don't think I have logs - just the failure due to /boot being full on the
update UI.
I then followed the instructions at
https://help.ubuntu.com/community/RemoveOldKernels under "Safely remove old
kernels" so I
Did you upgrade from older release or are the files generated when you
were using 20.04? Can you provide any logs concerning the issue? Do the
extra initrd.img* files match /boot/initrd.img-*.old-dkms, see
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513 ? Or do you
still have the
Just ran in to this on Ubuntu 20.04, with an encrypted root partition. The
partition layout is the one automatically generated when you install and ask
for root partition encryption - I didn't mess with it.
Drive is 512Gb NVME
Machine is a Lenovo Thinkbook 15
Kernel 5.8.0-59-generic
The /boot
** Project changed: initramfs-tools => ubuntu
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra package fails, if /boot is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a
** No longer affects: dpkg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra package fails, if /boot is about full
To manage notifications about
A new attempt to estimate required space in /boot.
** Attachment added: "The modified generate_initramfs function"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+attachment/4970885/+files/generate_initramfs
--
You received this bug notification because you are a
As for the patch, the following test shows that a file stored in /boot
may require significantly more available space than the same file in
/var/tmp, even if blocksize in (partition containing) /var/tmp is
bigger. I don't know what is the best way to estimate how much available
space is needed for
For some reason with my patch mv may fail even if I try to make sure mv
will not be run, if there is not enough space on /boot:
Setting up linux-generic-lts-xenial (4.4.0.97.81) ...
Processing triggers for initramfs-tools (0.103ubuntu4.8) ...
update-initramfs: Generating
There is no bug with that number.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra package fails, if /boot is about full
To manage notifications about this
I think source of the problem here is bug 1501844 and removing a linux-
image-extra package causes update-initramfs to be run. If the kernel
package maintainer scripts were written differently then removing linux-
image and linux-image-extra would not have a problem if /boot was full,
but removing
** Changed in: initramfs-tools (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra package fails, if /boot is
Then not incomplete anymore?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra package fails, if /boot is about full
To manage notifications about this bug
I've recreated this on Ubuntu 16.04 now, it seems that the missing bit
was creating a sufficiently small enough amount of free space on my
/boot partition.
While running 'sudo apt install' did finish the removal and I was able
to continue using apt, I did notice that I had a leftover / abandoned
Tested in 16.04
Lower free space at /boot to 10MB by the following one-liner:
sudo dd if=/dev/zero of=/boot/tmpfile bs=1MB count=$(($(stat -f
--format="%f*%S" /boot)/100-10))
Then remove a linux-image-extra package by apt, e.g.
sudo apt purge linux-image-extra-4.10.0-19-generic
Check
Using the same procedure I was unable to recreate this on Ubuntu 16.04.
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tried recreating this in Ubuntu 17.04 by having three kernels
installed on a /boot partition with only 11M of free space left. I then
used 'sudo apt autoremove' which removed my oldest kernel, including
linux-image-extra-4.10.0-19-generic, and did not run into any issues. Is
this issue specific
patch version 2 is also against (then) current
https://git.launchpad.net/~usd-import-team/ubuntu/+source/initramfs-tools/tree/update-initramfs
** Patch removed: "patch concerning generate_initramfs function in
update_initramfs"
** Tags added: full-boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra package fails, if /boot is about full
To manage notifications about this bug go
This patch is better, because it takes into account the size of possible
existing initramfs file when calculating the needed available free
space.
** Patch added: "version 2 of patch concerning generate_initramfs function in
update_initramfs"
The attachment "patch concerning generate_initramfs function in
update_initramfs" seems to be a patch. If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message
Patch against current https://git.launchpad.net/~usd-import-
team/ubuntu/+source/initramfs-tools/tree/update-initramfs
** Attachment added: "patch concerning generate_initramfs function in
update_initramfs"
Not sure if using dkms, but if so may be related to bug 1515513
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra package fails, if /boot is about full
To
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
** Description changed:
System calls /etc/kernel/postinst.d/initramfs-tools when
purging/removing a linux-image-extra package. That calls "update-
initramfs -c" which needs significant amount of additional disk space in
/boot temporarily. But there is no space left, if /boot is full.
** Description changed:
System calls /etc/kernel/postinst.d/initramfs-tools when
purging/removing a linux-image-extra package. That calls "update-
initramfs -c" which needs significant amount of additional disk space in
/boot temporarily. But there is no space left, if /boot is full.
+
Maybe also dkms may need more space on /boot when updating and backing
up initrd.img?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678187
Title:
Removing a linux-image-extra package fails, if
** Description changed:
System calls /etc/kernel/postinst.d/initramfs-tools when
purging/removing a linux-image-extra package. That calls "update-
initramfs -c" which needs significant amount of additional disk space in
/boot temporarily. But there is no space left, if /boot is full.
** Summary changed:
- dpkg fails to remove a linux-image-extra package, if /boot is about full
+ Removing a linux-image-extra package fails, if /boot is about full
** Description changed:
- "dpkg --purge" calls /etc/kernel/postinst.d/initramfs-tools when
+ System calls
47 matches
Mail list logo
