From Newsgroup: comp.sys.raspberry-pi

Ah the joy of patch-Tuesday. Or patch-Thursday in my case. So assorted
Windows machines updated I thought I'd better check some Linux machines.
The other week a colleague texted me and pointed out a nasty SSH
regression being exploited. So I sat in Lyon Airport waiting for the
gate to be announced and updated my Pi ZeroW gateway and some VMs. I
just did the SSH updates. It's cool being able to control your machines
from a distance but using the laptop and a phone with roaming data is
asking for something to take you offline when you don't want. Today was
time to catch up with other updates....

All was fine apart from the Pi Zero W which gave an error when running update-initramfs claiming there was no space on the device when doing

"update-initramfs: Generating /boot/initrd.img-6.6.31+rpt-rpi-v7l"

There was plenty of space on the device so I tried again. No luck.
Various ideas tried but it failed at the same place every time. I pulled
out another SDcard, wrote the image to it, put in the Pi, booted and
then did an update and upgrade. It failed again at the same place. So it wasn't the SDcard that was misbehaving. I flailed about miserably
wondering what it was till I found this webpage.

https://hillenius.net/post/nospaceleft/

I followed that and sure enough, it fixed everything. What I don't yet understand is what I had done to get to this place. And if it's just
started for me, are other people going to find themselves in the same situation real soon now?

I run '2024-03-15-raspios-bookworm-armhf-lite.img' with a few tweaks to
place logs etc. on the ram disk and I've been running apt update etc. on
that since end of May. Whatever, after today's update it was not going
to work unless I followed those changes to initramfs-tools.

Hopefully this may help the next Pi user who gets bitten by this.


--- Synchronet 3.19b-Win32 NewsLink 1.113

From Newsgroup: comp.sys.raspberry-pi

On 11/07/2024 at 18:37, mm0fmf wrote:

Ah the joy of patch-Tuesday. Or patch-Thursday in my case. So assorted Windows machines updated I thought I'd better check some Linux machines.
The other week a colleague texted me and pointed out a nasty SSH
regression being exploited. So I sat in Lyon Airport waiting for the
gate to be announced and updated my Pi ZeroW gateway and some VMs. I
just did the SSH updates. It's cool being able to control your machines
from a distance but using the laptop and a phone with roaming data is
asking for something to take you offline when you don't want. Today was
time to catch up with other updates....

All was fine apart from the Pi Zero W which gave an error when running update-initramfs claiming there was no space on the device when doing

"update-initramfs: Generating /boot/initrd.img-6.6.31+rpt-rpi-v7l"

There was plenty of space on the device so I tried again. No luck.
Various ideas tried but it failed at the same place every time. I pulled
out another SDcard, wrote the image to it, put in the Pi, booted and
then did an update and upgrade. It failed again at the same place. So it wasn't the SDcard that was misbehaving. I flailed about miserably
wondering what it was till I found this webpage.

https://hillenius.net/post/nospaceleft/

I followed that and sure enough, it fixed everything. What I don't yet understand is what I had done to get to this place. And if it's just
started for me, are other people going to find themselves in the same situation real soon now?

I run '2024-03-15-raspios-bookworm-armhf-lite.img' with a few tweaks to place logs etc. on the ram disk and I've been running apt update etc. on that since end of May. Whatever, after today's update it was not going
to work unless I followed those changes to initramfs-tools.

Hopefully this may help the next Pi user who gets bitten by this.

We've known about this for ages: change MODULES=most to MODULES=dep in /etc/initramfs-tools/initramfs.conf
--
Chris Elvidge, England
PORK IS NOT A VERB

--- Synchronet 3.19b-Win32 NewsLink 1.113

From Newsgroup: comp.sys.raspberry-pi

On 11/07/2024 19:58, Chris Elvidge wrote:

On 11/07/2024 at 18:37, mm0fmf wrote:

Ah the joy of patch-Tuesday. Or patch-Thursday in my case. So assorted
Windows machines updated I thought I'd better check some Linux
machines. The other week a colleague texted me and pointed out a nasty
SSH regression being exploited. So I sat in Lyon Airport waiting for
the gate to be announced and updated my Pi ZeroW gateway and some VMs.
I just did the SSH updates. It's cool being able to control your
machines from a distance but using the laptop and a phone with roaming
data is asking for something to take you offline when you don't want.
Today was time to catch up with other updates....

All was fine apart from the Pi Zero W which gave an error when running
update-initramfs claiming there was no space on the device when doing

"update-initramfs: Generating /boot/initrd.img-6.6.31+rpt-rpi-v7l"

There was plenty of space on the device so I tried again. No luck.
Various ideas tried but it failed at the same place every time. I
pulled out another SDcard, wrote the image to it, put in the Pi,
booted and then did an update and upgrade. It failed again at the same
place. So it wasn't the SDcard that was misbehaving. I flailed about
miserably wondering what it was till I found this webpage.

https://hillenius.net/post/nospaceleft/

I followed that and sure enough, it fixed everything. What I don't yet
understand is what I had done to get to this place. And if it's just
started for me, are other people going to find themselves in the same
situation real soon now?

I run '2024-03-15-raspios-bookworm-armhf-lite.img' with a few tweaks
to place logs etc. on the ram disk and I've been running apt update
etc. on that since end of May. Whatever, after today's update it was
not going to work unless I followed those changes to initramfs-tools.

Hopefully this may help the next Pi user who gets bitten by this.

We've known about this for ages: change MODULES=most to MODULES=dep in /etc/initramfs-tools/initramfs.conf

Who's "we"?
--- Synchronet 3.19b-Win32 NewsLink 1.113

From Newsgroup: comp.sys.raspberry-pi

On 11.07.2024 um 18:37 Uhr mm0fmf wrote:

There was plenty of space on the device so I tried again. No luck.

Please run
df -h

You storage can be split up into multiple partitions and if /boot is on
its own partition, this one might be full while the partition for /
still has enough space left.
--
kind regards
Marco

Send spam to 1720715867muell@cartoonies.org

--- Synchronet 3.19b-Win32 NewsLink 1.113

From Newsgroup: comp.sys.raspberry-pi

On 13/07/2024 06:17, Marco Moock wrote:

On 11.07.2024 um 18:37 Uhr mm0fmf wrote:

There was plenty of space on the device so I tried again. No luck.

Please run
df -h

You storage can be split up into multiple partitions and if /boot is on
its own partition, this one might be full while the partition for /
still has enough space left.

Thanks for your comments Marco. I was thinking /boot was full at first.
The image is a standard raspbian one with the default partitioning on a
8GB card and there's 4.4GB free. /boot is mounted on / and only
/boot/firmware is a separate 512mb partition that's 85% free still.

Changing to MODULES=dep fixed it. I'm not sure where the out of space
was occurring as the initrd images are now about 6.5MB and before nearer
10MB. There are 2 kernels and theres a v6, v7, v7l and v8 version which
if you tot up all inird and kernel images is only 112MB so even if it
was writing temporary files to /boot/firmware there would still be
plenty of space.

Anyway I don't believe I'm the only Pi Zero user with an almost
off-the-shelf Raspian image who has had this problem, hence the reason
for posting.


--- Synchronet 3.19b-Win32 NewsLink 1.113