I saw this as well on 18.04 during boot. Since
/usr/share/initramfs-tools/scripts/local-premount/btrfs
calls for the scan, you can workaround this issue by dealing with that
file. Since I wasn't using BTRFS regularly, I purged the file through
sudo apt purge btrfs-progs
--
You
Thanks @ufoot . It took quite a while to find that issue, but the
solution was hidden among many people reporting other solutions and
bugs. Remember after the
# chroot ./root
and before the
# update-initramfs -u -k all
You have to edit the file
# /etc/initramfs-tools/initramfs.conf
as noted
I had the grub "error: out of memory" issue after upgrading Ubuntu to
22.04 from 21.10. I used a Live USB of Ubuntu to chroot into my system
and after many trials and failures, I could get past the issue by
changing line 36 in /etc/initramfs-tools/initramfs.conf by using a
different compression
Public bug reported:
I had the grub "error: out of memory" issue after upgrading Ubuntu to
22.04 from 21.10. I used a Live USB of Ubuntu to chroot into my system
and after many trials and failures, I could get past the issue by
changing line 36 in /etc/initramfs-tools/initramfs.conf by using a
I upgraded from 22.04.1 to 22.10. Issue returned as
/usr/sbin/mkinitramfs was changed to default. Had to follow my previous
steps shown after #41 . . . zstd had defaulted to a lower compression
value in /usr/sbin/mkinitramfs at 1 instead of 19. I changed line 196 to
19 compression
zstd)
As with comment #41, #44, and #45, has the decision been made to fix
grub2's memory issues or just the compression level change that was with
initramfs (as I believe it was a choice made to increase Raspberry Pie
boot times)?
--
You received this bug notification because you are a member of
Bringing one the original triage fixes I posted in #41 and #45 after
gathering some information on changes to grub2 for Raspberry Pi that
exposed this issue (i.e., I know the fix to get things to boot), after
upgrading to 22.10, I now have an updated set of events on a specific
kernel.
I still
Hi juliank, I understand completely you want me to have insights related
to verification of the update in lunar-proposed and that I am confusing
you with my #131 post.
I was mentioning that to help people who need the triage, since it is
not possible to say locked out nor without updates until
juliank, edited and removed more notes as you advised. I hope my edits
per your advice help clarify things and help anyone to see if a new bug
is necessary to report. Thanks for your input.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
@madzohan from my comment around #41 above and related workarounds from
there downward, it seems you tried a different compression scheme and
found a smaller size in this case from zstd to xz.
I looked over your settings and options for xz compression, but also
reading the man pages for XZ it
10 matches
Mail list logo
