> Large unneeded files can be deleted with "rm".
This is what I ended up doing. The version 25 was in currently use and I
rm'ed all the old version files.
That worked, but I needed to do the same when version 31 appeared.
Fortunately the new version will get into use so rm will work.
Maybe
On Sun 01 Aug 2021 at 21:55:15 (+0200), Kamil Jońca wrote:
> David Christensen writes:
>
> [...]
> >
> > A 500 GB boot partition would be enough for several kernels, etc., on
> > Debian 10 amd64.
>
> OP wrote about 500 _M_ bytes (0.5G), and I can confirm, this is rather
> little, when trying
On 8/1/21 12:55 PM, Kamil Jońca wrote:
David Christensen writes:
[...]
A 500 GB boot partition would be enough for several kernels, etc., on
Debian 10 amd64.
OP wrote about 500 _M_ bytes (0.5G),
Please see:
> On 8/1/21 3:29 PM, David Christensen wrote:
>> I see a typo in my post --
David Christensen writes:
[...]
>
> A 500 GB boot partition would be enough for several kernels, etc., on
> Debian 10 amd64.
OP wrote about 500 _M_ bytes (0.5G), and I can confirm, this is rather
little, when trying updating kernels.
KJ
--
http://stopstopnop.pl/stop_stopnop.pl_o_nas.html
Sorry, Stefan. This was supposed to go to the list.
On 8/2/21 11:02 PM, Marc Shapiro wrote:
On 8/1/21 9:33 PM, Stefan Monnier wrote:
So really think hard before splitting off a filesystem outside of
volume management. I believe it is more likely to cause problems
than it is to avoid
On 8/2/21 12:47 PM, Greg Wooledge wrote:
On Mon, Aug 02, 2021 at 12:43:27PM -0700, David Christensen wrote:
I'd rather not install dracut.
Me too. So why not use lsinitramfs -l ? Why keep reinventing the wheel?
unicorn:~$ lsinitramfs -l /boot/initrd.img-5.10.0-8-amd64 | head -12
drwxr-xr-x
On Mon, Aug 02, 2021 at 12:43:27PM -0700, David Christensen wrote:
> I'd rather not install dracut.
Me too. So why not use lsinitramfs -l ? Why keep reinventing the wheel?
unicorn:~$ lsinitramfs -l /boot/initrd.img-5.10.0-8-amd64 | head -12
drwxr-xr-x 2 root root0 Apr 25
On 8/2/21 11:29 AM, Greg Wooledge wrote:
On Mon, Aug 02, 2021 at 11:11:11AM -0700, David Christensen wrote:
Please post your console session showing how you created
initrd.img-5.10.0-8-amd64.txt.gz.
I didn't. It was created automatically when I installed dracut-core.
Prior to that, it was
On Mon, Aug 02, 2021 at 11:11:11AM -0700, David Christensen wrote:
> On 8/1/21 3:51 PM, Greg Wooledge wrote:
> > On Sun, Aug 01, 2021 at 03:29:07PM -0700, David Christensen wrote:
> > > 2021-08-01 13:52:37 root@dipsy ~
>
> > > # gunzip -c /boot/initrd.img-4.19.0-17-amd64 | cpio -i -d -H newc
> >
On 8/1/21 3:51 PM, Greg Wooledge wrote:
On Sun, Aug 01, 2021 at 03:29:07PM -0700, David Christensen wrote:
2021-08-01 13:52:37 root@dipsy ~
# gunzip -c /boot/initrd.img-4.19.0-17-amd64 | cpio -i -d -H newc
--no-absolute-filenames
246741 blocks
That may not extract the full content of the
On Mon 02 Aug 2021 at 08:04:25 (+0300), Teemu Likonen wrote:
> * 2021-08-01 16:00:24-0400, Greg Wooledge wrote:
>
> > Someone who knows what makes initrd images swell up, please step in
> > and advise. And no, it's not "try using a different compression
> > algorithm". It's something in the
On Sun 01 Aug 2021 at 13:21:11 (+0300), Ilkka Huotari wrote:
> Thanks. I should have said, that also apt-get autoremove fails:
>
> $ sudo apt-get autoremove
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> 0 upgraded, 0 newly installed, 0 to
On 01/08/2021 23:51, Greg Wooledge wrote:
> On Sun, Aug 01, 2021 at 03:29:07PM -0700, David Christensen wrote:
>> 2021-08-01 13:52:37 root@dipsy ~
>> # file /boot/initrd.img-4.19.0-17-amd64
>> /boot/initrd.img-4.19.0-17-amd64: gzip compressed data, last modified: Sun
>> Jul 25 19:43:38 2021, from
> So really think hard before splitting off a filesystem outside of
> volume management. I believe it is more likely to cause problems
> than it is to avoid problems.
All my machines have a separate /boot partition (and everything
else in LVM). These are all "historical accidents", because at
* 2021-08-01 16:00:24-0400, Greg Wooledge wrote:
> Someone who knows what makes initrd images swell up, please step in
> and advise. And no, it's not "try using a different compression
> algorithm". It's something in the *content*.
Initrd image is large when the pairing kernel is compiled with
On Mon, 2 Aug 2021 at 08:33, Andy Smith wrote:
> At this point there will probably be some people who consider
> themselves veterans saying that one must absolutely split things off
> because of various reasons like differing mount options being
> desirable, ability to re-use contents of /home
On Sun, Aug 01, 2021 at 03:29:07PM -0700, David Christensen wrote:
> 2021-08-01 13:52:37 root@dipsy ~
> # file /boot/initrd.img-4.19.0-17-amd64
> /boot/initrd.img-4.19.0-17-amd64: gzip compressed data, last modified: Sun
> Jul 25 19:43:38 2021, from Unix, original size 126331392
Your initrd
Hello,
OP: You are pretty safe deleting (rm) vmlinuz* and initrd* things
from /boot that are related to any kernels you aren't actually
booted into at the time. That can give you back enough space to let
apt finish what it wants to do. Just remember to do:
# update-initramfs -u -k all
On 8/1/21 1:00 PM, Greg Wooledge wrote:
On Sun, Aug 01, 2021 at 12:45:27PM -0700, David Christensen wrote:
On 7/31/21 9:20 PM, Ilkka Huotari wrote:
-rw-r--r-- 1 root root 153M heinä 10 14:22 initrd.img-5.11.0-22-generic
-rw-r--r-- 1 root root 151M heinä 23 13:13
Am Sonntag, 1. August 2021, 22:00:24 CEST schrieb Greg Wooledge:
Try to uninstall old kernels with
aptitude purge ~n5.10.0-7-*
for uninstalling all related packages with "5.10.0-7-" in its name. Do it with
all unneeded kernels.
It will also uninstall headers and modules for that
On Sun, Aug 01, 2021 at 12:45:27PM -0700, David Christensen wrote:
> On 7/31/21 9:20 PM, Ilkka Huotari wrote:
> > -rw-r--r-- 1 root root 153M heinä 10 14:22 initrd.img-5.11.0-22-generic
> > -rw-r--r-- 1 root root 151M heinä 23 13:13 initrd.img-5.11.0-25-generic
> A 500 GB boot partition would
On 7/31/21 9:20 PM, Ilkka Huotari wrote:
Hi,
I'm using Ubuntu 21. My /boot partition size is 500M and it's getting full:
/dev/sda1 446M 352M 61M 86% /boot
What's taking space are mainly these:
-rw-r--r-- 1 root root 153M heinä 10 14:22 initrd.img-5.11.0-22-generic
Ilkka Huotari [2021-08-01 07:20:20] wrote:
> I'm using Ubuntu 21. My /boot partition size is 500M and it's getting full:
Notice that this is a Debian mailing-list, so questions about Ubuntu are
not really "on topic".
AFAIK Ubuntu handles the initrd files and kernels slightly differently
from
On Sunday 01 August 2021 06:57:54 Paul Duncan wrote:
> Hmmm... Thats a little annoying.
>
> Maybe try removing the -22 image manually, like this:
>
> apt-get remove linux-image-5.11.0-22
>
> See if that works. If it doesn't, I'm not sure what else to try -
> other than a re-install - at which I
On 01/08/2021 13:34, didier gaumet wrote:
> Hello,
>
> Disclaimer: I have never tested what is following.
>
> Perhaps another way of keeping two kernels without increasing the size oft
> the /boot partition would be to decrease the size of the initrd files: by
> default they are built with
Paul Duncan wrote:
...
> Hmmm... Thats a little annoying.
>
> Maybe try removing the -22 image manually, like this:
>
> apt-get remove linux-image-5.11.0-22
if that is the kernel that is being run then you risk
putting your system into a completely unbootable state (if
the upgrade failed that
Hello,
Disclaimer: I have never tested what is following.
Perhaps another way of keeping two kernels without increasing the size oft the
/boot partition would be to decrease the size of the initrd files: by default
they are built with allmost all possible modules, but they can be built with
Hmmm... Thats a little annoying.
Maybe try removing the -22 image manually, like this:
apt-get remove linux-image-5.11.0-22
See if that works. If it doesn't, I'm not sure what else to try - other
than a re-install - at which I would make /boot a little bigger :-)
I'm sure others more
On 2021-08-01 at 06:21, Ilkka Huotari wrote:
> Hi Paul,
>
> Thanks. I should have said, that also apt-get autoremove fails:
>
> $ sudo apt-get autoremove
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> 0 upgraded, 0 newly installed, 0 to
Hi Paul,
Thanks. I should have said, that also apt-get autoremove fails:
$ sudo apt-get autoremove
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Hi Ilkka,
Try doing "apt autoremove". This should get rid of all the old, no-longer
used kernels and other software on your system. You should then be able to
get the new stuff on :-)
Best Regards,
Paul.
On Sun, 1 Aug 2021 at 04:36, Ilkka Huotari wrote:
> Hi,
>
> I'm using Ubuntu 21. My
Hi,
I'm using Ubuntu 21. My /boot partition size is 500M and it's getting full:
/dev/sda1 446M 352M 61M 86% /boot
What's taking space are mainly these:
-rw-r--r-- 1 root root 153M heinä 10 14:22 initrd.img-5.11.0-22-generic
-rw-r--r-- 1 root root 151M heinä 23 13:13
32 matches
Mail list logo
