Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #233923 > unrolled thread

No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

Back to article view | Back to linux.debian.user

Contents

  No space left when: update-initramfs: Generating  /boot/initrd.img-5.10.0-5-amd64 Marco Ippolito <maroloccio@gmail.com> - 2021-04-07 14:30 +0200
    Re: No space left when: update-initramfs: Generating  /boot/initrd.img-5.10.0-5-amd64 Greg Wooledge <greg@wooledge.org> - 2021-04-07 14:40 +0200
    Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64 IL Ka <kazakevichilya@gmail.com> - 2021-04-07 14:50 +0200
    Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64 Stefan Monnier <monnier@iro.umontreal.ca> - 2021-04-07 15:00 +0200
      Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64 Javier Barroso <javibarroso@gmail.com> - 2021-04-07 15:40 +0200
        Re: No space left when: update-initramfs: Generating  /boot/initrd.img-5.10.0-5-amd64 Marco Ippolito <maroloccio@gmail.com> - 2021-04-07 16:10 +0200
      Re: No space left when: update-initramfs: Generating  /boot/initrd.img-5.10.0-5-amd64 Erwan David <erwan@rail.eu.org> - 2021-04-07 15:40 +0200
      Re: No space left when: update-initramfs: Generating  /boot/initrd.img-5.10.0-5-amd64 Marco Ippolito <maroloccio@gmail.com> - 2021-04-07 16:10 +0200
        Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64 Stefan Monnier <monnier@iro.umontreal.ca> - 2021-04-07 17:40 +0200
    Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64 Hans <hans.ullrich@loop.de> - 2021-04-07 15:20 +0200
      Re: No space left when: update-initramfs: Generating  /boot/initrd.img-5.10.0-5-amd64 Marco Ippolito <maroloccio@gmail.com> - 2021-04-07 16:20 +0200
        Re: No space left when: update-initramfs: Generating  /boot/initrd.img-5.10.0-5-amd64 Andrei POPESCU <andreimpopescu@gmail.com> - 2021-04-07 19:50 +0200
          Re: No space left when: update-initramfs: Generating  /boot/initrd.img-5.10.0-5-amd64 Greg Wooledge <greg@wooledge.org> - 2021-04-07 20:10 +0200
            Re: No space left when: update-initramfs: Generating  /boot/initrd.img-5.10.0-5-amd64 David Wright <deblis@lionunicorn.co.uk> - 2021-04-07 20:40 +0200
              Re: No space left when: update-initramfs: Generating  /boot/initrd.img-5.10.0-5-amd64 Marco Ippolito <maroloccio@gmail.com> - 2021-04-08 14:30 +0200
                Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64 David <bouncingcats@gmail.com> - 2021-04-08 15:20 +0200
                  Re: No space left when: update-initramfs: Generating  /boot/initrd.img-5.10.0-5-amd64 Marco Ippolito <maroloccio@gmail.com> - 2021-04-08 15:40 +0200
                    Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64 David <bouncingcats@gmail.com> - 2021-04-09 13:00 +0200
                      Re: No space left when: update-initramfs: Generating  /boot/initrd.img-5.10.0-5-amd64 Marco Ippolito <maroloccio@gmail.com> - 2021-04-10 03:20 +0200
          Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64 Hans <hans.ullrich@loop.de> - 2021-04-07 20:30 +0200
    Re: No space left when: update-initramfs: Generating  /boot/initrd.img-5.10.0-5-amd64 Eduard Bloch <edi@gmx.de> - 2021-04-07 21:30 +0200
      Re: No space left when: update-initramfs: Generating  /boot/initrd.img-5.10.0-5-amd64 Marco Ippolito <maroloccio@gmail.com> - 2021-04-07 23:00 +0200

Page 1 of 2  [1] 2  Next page →

#233923 — No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

Was upgrading from buster to bullseye. Space ran out, UI crashed, restarted in
recovery mode and cleaned up space. Restarted and run:

# dpkg --configure -a
Setting up initramfs-tools (0.139) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.139) ...
update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64
cat: write error: No space left on device
update-initramfs: failed for /boot/initrd.img-5.10.0-5-amd64 with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned
 error exit status 1
 Errors were encountered while processing:
  initramfs-tools

# df -h /boot
Filesystem      Size  Used Avail Use% Mounted on
/dev/nvme0n1p1  236M  233M     0 100% /boot

What do you recommend I do?

Doubt: after this, by default old kernels will be cleaned up in Bullseye Vs
       Buster?

[toc] | [next] | [standalone]

#233925

On Wed, Apr 07, 2021 at 09:20:46AM -0300, Marco Ippolito wrote:
> # df -h /boot
> Filesystem      Size  Used Avail Use% Mounted on
> /dev/nvme0n1p1  236M  233M     0 100% /boot
> 
> What do you recommend I do?

Purge one or more of your kernel images.

[toc] | [prev] | [next] | [standalone]

#233926 — Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Multipart message — attachments visible in raw view] — view raw

>
>
> # df -h /boot
> Filesystem      Size  Used Avail Use% Mounted on
> /dev/nvme0n1p1  236M  233M     0 100% /boot
>
> What do you recommend I do?
>

1. Autoremove old automatically installed stuff

$ apt purge --autoremove

2. Check packages:

$ dpkg-query --show -f='${Installed-Size}\t${Package}\t${Status}\n' | sort
-nr | head

This will give you the biggest packages (latest field should show if they
are really installed).
Find the one you do not need  (old kernel probably, but be sure not to
delete the current kernel: check "uname -r" !)

Then, purge them:
apt purge "package name"



>
> Doubt: after this, by default old kernels will be cleaned up in Bullseye Vs
>        Buster?
>
>
AFAIK yes, when you call "autoremove" , but one prev. kernel left untouched.

see
/etc/apt/apt.conf.d/01autoremove-kernels
or something like this

[toc] | [prev] | [next] | [standalone]

#233927 — Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

> What do you recommend I do?

Other than purging old kernels, I also recommend you check

    /etc/initramfs-tools/initramfs.conf

where `MODULES=dep` and `COMPRESS=lzma` have made a big difference for
me (more or less shrunk the initrd images by a factor 3-4).

> Doubt: after this, by default old kernels will be cleaned up in Bullseye Vs
>        Buster?

I don't think APT ever cleans up old kernels for you (at least in its
default configuration).


        Stefan

[toc] | [prev] | [next] | [standalone]

#233929 — Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Multipart message — attachments visible in raw view] — view raw

El mié., 7 abr. 2021 14:58, Stefan Monnier <monnier@iro.umontreal.ca>
escribió:

> > What do you recommend I do?
>
> Other than purging old kernels, I also recommend you check
>
>     /etc/initramfs-tools/initramfs.conf
>
> where `MODULES=dep` and `COMPRESS=lzma` have made a big difference for
> me (more or less shrunk the initrd images by a factor 3-4).
>

Thanks I will test!

>
> > Doubt: after this, by default old kernels will be cleaned up in Bullseye
> Vs
> >        Buster?
>
> I don't think APT ever cleans up old kernels for you (at least in its
> default configuration).
>

Recently that was fixed at unstable [1]

I found a interesting manpage for this issue [2]

Regards

[1] https://blog.jak-linux.org/2021/02/18/apt-2.2/
[2] https://manpages.debian.org/stretch/byobu/purge-old-kernels.1.en.html

>
>
>         Stefan
>
>

[toc] | [prev] | [next] | [standalone]

#233931

> Recently that was fixed at unstable [1]

I thought I had noticed a warning about this clean-up, but it does not happen
during the upgrade so I run out of space.

> I found a interesting manpage for this issue [2]

Good catch. Functionality now in apt and purge-old-kernels got deprecated.

[toc] | [prev] | [next] | [standalone]

#233930

Le 07/04/2021 à 14:58, Stefan Monnier a écrit :
>> What do you recommend I do?
> 
> Other than purging old kernels, I also recommend you check
> 
>      /etc/initramfs-tools/initramfs.conf
> 
> where `MODULES=dep` and `COMPRESS=lzma` have made a big difference for
> me (more or less shrunk the initrd images by a factor 3-4).
> 
>> Doubt: after this, by default old kernels will be cleaned up in Bullseye Vs
>>         Buster?
> 
> I don't think APT ever cleans up old kernels for you (at least in its
> default configuration).
> 
> 
>          Stefan
> 
> 

I also found that firmware need space, especially amd64 graphics firmware.

[toc] | [prev] | [next] | [standalone]

#233932

> where `MODULES=dep` and `COMPRESS=lzma` have made a big difference for
> me (more or less shrunk the initrd images by a factor 3-4).

Thank you.

Why did you choose lzma Vs xz or zstd, by the way? Measured diff?

> > Doubt: after this, by default old kernels will be cleaned up in Bullseye Vs
> >        Buster?
> I don't think APT ever cleans up old kernels for you (at least in its
> default configuration).

Read something about it during the upgrade.. was checking here.

[toc] | [prev] | [next] | [standalone]

#233942 — Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

>> where `MODULES=dep` and `COMPRESS=lzma` have made a big difference for
>> me (more or less shrunk the initrd images by a factor 3-4).
> Thank you.
> Why did you choose lzma Vs xz or zstd, by the way? Measured diff?

`lzma` and `xz` should be pretty much identical, it was a toss-up (I
have a preference for `lzip` in that space, but it's not available ;-).

`zstd` should compress significantly less (but is significantly faster
both to compress and to uncompress).  I focused on disk space usage
(but I did notice that uncompression takes a non-negligible amount of
time on my old Thinkpad X30 when the initrd image is large (e.g. with
`modules=most`)).

>> > Doubt: after this, by default old kernels will be cleaned up in
>> >        Bullseye Vs Buster?
>> I don't think APT ever cleans up old kernels for you (at least in its
>> default configuration).
> Read something about it during the upgrade.. was checking here.

Maybe my info is out of date then.


        Stefan

[toc] | [prev] | [next] | [standalone]

#233928 — Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

[Multipart message — attachments visible in raw view] — view raw

Am Mittwoch, 7. April 2021, 14:20:46 CEST schrieb Marco Ippolito:
Hi Marco, 
just get rid of older kernels.


This is may way:


1st, check your running actual kernel:

uname -a

Then check all installed kernel versions:

ls /boot

You will see several kernels. I suppose, apt-get autoremove will not unistall them, so 
just use aptitude with the version you want to uninstall:

aptitude purge ~n4.9.10-amd64-* 

This will uninstall all stuff with "4.9.10-amd64-" in its name, this means kernel, headers 
and maybe selfcompiled kernel modules like the nvidia-stuff.

Please check before saying "Y" what is going to be uninstalled.

Do this with all the kernels, except the one you are actually running.

This is working well for me, so good luck!

Best regards

Hans





> Was upgrading from buster to bullseye. Space ran out, UI crashed, restarted
> in recovery mode and cleaned up space. Restarted and run:
> 
> # dpkg --configure -a
> Setting up initramfs-tools (0.139) ...
> update-initramfs: deferring update (trigger activated)
> Processing triggers for initramfs-tools (0.139) ...
> update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64
> cat: write error: No space left on device
> update-initramfs: failed for /boot/initrd.img-5.10.0-5-amd64 with 1.
> dpkg: error processing package initramfs-tools (--configure):
>  installed initramfs-tools package post-installation script subprocess
> returned error exit status 1
>  Errors were encountered while processing:
>   initramfs-tools
> 
> # df -h /boot
> Filesystem      Size  Used Avail Use% Mounted on
> /dev/nvme0n1p1  236M  233M     0 100% /boot
> 
> What do you recommend I do?
> 
> Doubt: after this, by default old kernels will be cleaned up in Bullseye Vs
>        Buster?


-- 
*Hans-J. Ullrich*
zertifizierter Datenschutzbeauftragter
zertifizierter Datenschutzauditor
zertifizierter Penetrationtester
zertifizierter IT-Security Professionell
zertifizierter IT-Forensik Professionell
zertifizierter Network Vulnerabilty Professionell

[toc] | [prev] | [next] | [standalone]

#233933

> Hi Marco, 

Hi Hans :)

> aptitude purge ~n4.9.10-amd64-* 

Hadn't thought of matching a pattern, thanks.

[toc] | [prev] | [next] | [standalone]

#233949

[Multipart message — attachments visible in raw view] — view raw

On Mi, 07 apr 21, 11:11:55, Marco Ippolito wrote:
> > Hi Marco, 
> 
> Hi Hans :)
> 
> > aptitude purge ~n4.9.10-amd64-* 
> 
> Hadn't thought of matching a pattern, thanks.

While I'm a big fan of aptitude's patterns it's also not installed by 
default. For basic uses 'apt' is fine as well and supports globs:

    apt list --installed linux-image-4*

    apt purge linux-image-4.9.10-?-amd64


(just an example, adjust as needed)

Hope this helps,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

[toc] | [prev] | [next] | [standalone]

#233951

On Wed, Apr 07, 2021 at 08:40:58PM +0300, Andrei POPESCU wrote:
> While I'm a big fan of aptitude's patterns it's also not installed by 
> default. For basic uses 'apt' is fine as well and supports globs:
> 
>     apt list --installed linux-image-4*
> 
>     apt purge linux-image-4.9.10-?-amd64

Remember that you need to quote these globs (at least the special
characters in them), or else one day you *will* get a nasty surprise
when one of them matches a file in your current working directory.

[toc] | [prev] | [next] | [standalone]

#233953

On Wed 07 Apr 2021 at 14:02:58 (-0400), Greg Wooledge wrote:
> On Wed, Apr 07, 2021 at 08:40:58PM +0300, Andrei POPESCU wrote:
> > While I'm a big fan of aptitude's patterns it's also not installed by 
> > default. For basic uses 'apt' is fine as well and supports globs:
> > 
> >     apt list --installed linux-image-4*
> > 
> >     apt purge linux-image-4.9.10-?-amd64
> 
> Remember that you need to quote these globs (at least the special
> characters in them), or else one day you *will* get a nasty surprise
> when one of them matches a file in your current working directory.

And I'm a big fan of -s with commands like these, so that
you know what's going to be changed. Then recall the command
and remove the -s.

I'm also a big fan of   mv -i   rather than rm, for similar
reasons. Remove the files only when you're sure the system
still works without them.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#233986

> And I'm a big fan of -s with commands like these, so that
> you know what's going to be changed. Then recall the command
> and remove the -s.

Where would I put the -s please?

[toc] | [prev] | [next] | [standalone]

#233989 — Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

On Thu, 8 Apr 2021 at 22:23, Marco Ippolito <maroloccio@gmail.com> wrote:

> > And I'm a big fan of -s with commands like these, so that
> > you know what's going to be changed. Then recall the command
> > and remove the -s.

> Where would I put the -s please?

Explanation of how to find the answer:
He was talking about 'apt' commands.
If you read 'man apt' it hints that it is a front-end to
various 'apt-*' commands like 'apt-get'.
The hints look like "apt-get(8)" which is a reference
to the 'apt-get' man page in Section 8, which can
be read using the command:
  man 8 apt-get
And if you read that man page, you can find an
explanation of the -s option when used with a
'apt-get' command.

[toc] | [prev] | [next] | [standalone]

#233990

> > Where would I put the -s please?
> 
> Explanation of how to find the answer:
> He was talking about 'apt' commands.
> If you read 'man apt' it hints that it is a front-end to
> various 'apt-*' commands like 'apt-get'.
> The hints look like "apt-get(8)" which is a reference
> to the 'apt-get' man page in Section 8, which can
> be read using the command:
>   man 8 apt-get
> And if you read that man page, you can find an
> explanation of the -s option when used with a
> 'apt-get' command.

Gotcha. I like the long option names there, almost all of which are immediately
suggestive of what the change of behaviour might be:

    --simulate, --just-print, --dry-run, --recon, --no-act

Especially: --simulate and --dry-run (for users of rsync and other commands
that use the same long option name)

[toc] | [prev] | [next] | [standalone]

#234016 — Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

On Thu, 8 Apr 2021 at 23:33, Marco Ippolito <maroloccio@gmail.com> wrote:

> Gotcha. I like the long option names there, almost all of which are immediately
> suggestive of what the change of behaviour might be:
>
>     --simulate, --just-print, --dry-run, --recon, --no-act

Yes, and my impression/guess is that because 'apt' docs describe it
as being basically a front end with more convenient defaults for
interactive use, what happens when 'apt' is given these (or other
similar) options that it does not recognise as its own as documented
in the 'apt' man page, it behaves the same as if it handed these
options off to whatever command it runs as its back-end.
So 'apt -s install ...' behaves like 'apt-get -s install ...'.
I don't know if that's literally how it is implemented, but it's
the general behaviour that I would expect. 'apt' is still under
development so the details of it's behaviour might change
between releases.

[toc] | [prev] | [next] | [standalone]

#234065

> Yes, and my impression/guess is that because 'apt' docs describe it
> as being basically a front end with more convenient defaults for
> interactive use, what happens when 'apt' is given these (or other
> similar) options that it does not recognise as its own as documented
> in the 'apt' man page, it behaves the same as if it handed these
> options off to whatever command it runs as its back-end.

I wonder if documentation for options like -s belongs only in apt-get, both in
apt-get and apt or something else. Currenly, the option is accepted by apt but
not documented in the man page I have on my system for apt.

[toc] | [prev] | [next] | [standalone]

#233952 — Re: No space left when: update-initramfs: Generating /boot/initrd.img-5.10.0-5-amd64

Am Mittwoch, 7. April 2021, 19:40:58 CEST schrieb Andrei POPESCU:
Hi Andrei,

yes, you casn do this also with using apt. However, I forgot how to do this, 
it was a litttle bit more complicated.

The syntax was something like "apt-get --purge remove `somestring` " or 
similar. Apt was then using regexp, and the string had to be put in backticks 
or ticks whatever. 

Really, maybe google is telling more. I just forgot, how to do it. 

Last time I used it many years ago and my history is not that long. :-)

Best regards

Hans 

> On Mi, 07 apr 21, 11:11:55, Marco Ippolito wrote:
> > > Hi Marco,
> > 
> > Hi Hans :)
> > 
> > > aptitude purge ~n4.9.10-amd64-*
> > 
> > Hadn't thought of matching a pattern, thanks.
> 
> While I'm a big fan of aptitude's patterns it's also not installed by
> default. For basic uses 'apt' is fine as well and supports globs:
> 
>     apt list --installed linux-image-4*
> 
>     apt purge linux-image-4.9.10-?-amd64
> 
> 
> (just an example, adjust as needed)
> 
> Hope this helps,
> Andrei

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web