I'm running Debian Buster and ran the usual check for updates etc. commands

When I did the system update I hit this error

update-initramfs: Generating /boot/initrd.img-4.19.0-22-amd64
pigz: abort: write error on <stdout> (No space left on device)
E: mkinitramfs failure cpio 141 pigz 28
update-initramfs: failed for /boot/initrd.img-4.19.0-22-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
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

so it looks like I'm running out of space and it could be the linux image(s) I have taking up space? Is that correct?

What is the best way to remove some of the old ones safely?

Or am is mis-reading this?

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Linux question
By: Avon to All on Sun Dec 18 2022 02:11 pm

update-initramfs: Generating /boot/initrd.img-4.19.0-22-amd64
pigz: abort: write error on <stdout> (No space left on device)
E: mkinitramfs failure cpio 141 pigz 28
update-initramfs: failed for /boot/initrd.img-4.19.0-22-amd64 with 1.
so it looks like I'm running out of space and it could be the linux image(s) I have taking up space? Is that correct?
What is the best way to remove some of the old ones safely?

Yup, check if you have more than 1 kernel image, and if you have many you can remove the old ones.

uname -r should tell you the running kernel version, and dpkg -l <pipe> grep image should tell you how many linux-image's are loaded, and you can "apt remove" the ones that you dont use (not the running kernel), and that should free up some space.



...����
--- SBBSecho 3.15-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

so it looks like I'm running out of space and it could be the linux image(s) I have taking up space? Is that correct?

What is the best way to remove some of the old ones safely?

Try apt autoremove or apt-get auto-remove. <- something similar, run apt or apt-get withour arguments to get a list of available commands.

Or am is mis-reading this?

No, that is not a good error. :( I hope you can get enough free space to update your initramfs.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Hello Avon!

On 18 Dec 2022, Avon said the following...

so it looks like I'm running out of space and it could be the linux image(s) I have taking up space? Is that correct?

I think it looks so, yes. You might want to try:

apt autoremove

...to see if that offers to remove some of the older kernels.

Best regards
Zip

--- Mystic BBS v1.12 A48 2022/07/15 (Linux/64)
* Origin: Star Collision BBS, Uppsala, Sweden (21:1/202)

Avon wrote (2022-12-18):

I'm running Debian Buster and ran the usual check for updates etc.
commands

When I did the system update I hit this error

update-initramfs: Generating /boot/initrd.img-4.19.0-22-amd64
pigz: abort: write error on <stdout> (No space left on device)

so it looks like I'm running out of space and it could be the linux image(s) I have taking up space? Is that correct?

What is the best way to remove some of the old ones safely?

Your boot partition is full. Try

$ apt list 'linux-image*'
or
$ dpkg -l 'linux-image*'
or
$ ls -la /boot

to list the installed linux images.

If autormove doesn't work, try to remove them manually

$ apt purge linux-image-<insert version here>


⁂

---
* Origin: War is Peace. Freedom is Slavery. Ignorance is Strength. (21:3/102)

On Sun, 18 Dec 2022 11:17:28 +0100
"Oli" <oli@21:3/102> wrote:

Avon wrote (2022-12-18):

I'm running Debian Buster and ran the usual check for updates etc. commands

When I did the system update I hit this error

update-initramfs: Generating /boot/initrd.img-4.19.0-22-amd64
pigz: abort: write error on <stdout> (No space left on device)

so it looks like I'm running out of space and it could be the
linux image(s) I have taking up space? Is that correct?

What is the best way to remove some of the old ones safely?

Your boot partition is full. Try

$ apt list 'linux-image*'
or
$ dpkg -l 'linux-image*'
or
$ ls -la /boot

to list the installed linux images.

If autormove doesn't work, try to remove them manually

$ apt purge linux-image-<insert version here>

I would manually remove enough to ensure the new kernel initramfs can
be installed on the boot device and then reboot successfully before
trying an autoremove, otherwise you could be left in a bad way. I don't
like automatic stuff when things are broken.
--
End Of The Line BBS - Plano, TX
telnet endofthelinebbs.com 23

I'm running Debian Buster and ran the usual check for updates etc. commands

When I did the system update I hit this error

update-initramfs: Generating /boot/initrd.img-4.19.0-22-amd64
pigz: abort: write error on <stdout> (No space left on device)
E: mkinitramfs failure cpio 141 pigz 28
update-initramfs: failed for /boot/initrd.img-4.19.0-22-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
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

so it looks like I'm running out of space and it could be the linux image(s) I have taking up space? Is that correct?

What is the best way to remove some of the old ones safely?

Or am is mis-reading this?

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

Well Start with sudo apt auto-remove

This will get rid of unused dependencies.

Then sudo apt clean

this will clear the cache.

Aside from that you will have to find things taking up space you want to remove. If this is on a pi with SD might be time to back it up and reflash to a larger card. you can use DD to back up to am image and again to put it on a larger card, or even better flash it to a HDD/SSD and use that.

If your on PC then you can just add more space to your install.

I'm sure there is some super advanced Linux guy on here that will be more assistance.

I would be happy to let you pick my brain if you like. I have a Teamspeak server @ voice.clawfest.com. No password I typically get on daily around 5:30ish CST and stay on till I go to bed usually around ~10ish.

|23|04Dr|16|12Claw
|16|14Sysop |12Noverdu |14BBS |04(|14Noverdu.com|04)
|10Standard Ports for SSH/Telnet Web/HTTP://|14Noverdu.com:808
|20|15fsxNet/MRC Chat/Registered Doors!/50Nodes/No Time Use! Stay On!|16|07

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Noverdu BBS (21:1/210)

I'm running Debian Buster and ran the usual check for updates etc.

I find sometimes it can be worth checking what kind of logs are being generated and if they're being rotated properly. Often non standard packages will create logging and still drop it into /var/log but not age it out.

If you're running anything like NTOP you might also want to check on its database. They can get quite out of hand. I did have NTOP specifically with a database size over 2Gb at one stage...

ST

--- Mystic BBS v1.12 A47 2021/12/24 (Linux/64)
* Origin: Storm BBS (21:2/108)

Run as sudo: apt autoremove

----
Thanks!
Orbitman (Allen)
Orbit BBS, Opp, AL USA
orbitbbs.ddns.net:7210

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/32)
* Origin: Orbit BBS-Opp, AL. USA | orbitbbs.ddns.net:7210 (21:2/131)