Raspberry Pi | libc-bin segmentation fault when using USB-SD adapter

[lpseguin]

Raspberry Pi | libc-bin segmentation fault when using USB-SD adapter

[68wooley]

Something worth trying:

I was running via a microSD to USB-A adaptor and booting from USB. I just re-imaged my card and booted from the internal microSD reader and I no longer have the problem.

If you're booting via USB, might be worth trying. Someone else posted the same issue/solution in the RPi forums:

https://forums.raspberrypi.com/viewtopic.php?t=358967#p2172823

[68wooley]

Does it just require a SD card present or does the system need to be booted from SD card as well?

Good question. I'll test this afternoon and let you know.

[68wooley]

OK - here's what I found:

It seems the issue is tied to the use of a microSD to USB-A adaptor:

• Flashing PiOS to an actual USB-A thumb-drive and booting from that had no issues.
• Flashing PiOS to a SSD in a USB-C enclosure and booting from that via a USB-C to USB-A adaptor had no issues.
• Booting from the microSD card in the USB-A adaptor continued to have problems, even with a second microSD card in the built-in reader.
• Flashing a different microSD card and booting from that via the USB-A adaptor resulted in the same problem.

If anyone wants to investigate further, they're welcome to go for it, but the 'solution' of using the internal reader is simple enough I can't see it being worth anyone's time unless whatever the problem is starts manifesting in other ways.

[MichaIng]

Hmm, a segmentation fault in a native Debian binary could be a filesystem error. Hopefully not an issue with a package/update shipped by the RPi repo. Does the kernel show some errors?

dmesg -l 0,1,2,3

Reinstalling that package does not help, does it?

apt install --reinstall libc-bin

[lpseguin]

Hi!

Here's the output from the cmd:

 dmesg -l 0,1,2,3
[    0.839513] mmc1: Controller never released inhibit bit(s).

 apt install --reinstall libc-bin
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for libc-bin:arm64

[Joulinar]

Can you share following

Architecture | dpkg --print-architecture

[lpseguin]

Can you share following

Architecture | dpkg --print-architecture

arm64

[MichaIng]

Strange error. Not sure whether this means that some meta file (one of /var/lib/dpkg/info/libc-bin.*) is missing, or something else. Searching around, manually unpacking the package onto the system seems to be a solution for this kind of error, but lets try some more common APT issue solutions first:

/boot/dietpi/func/dietpi-set_software apt clean
apt update
apt install --reinstall libc-bin

[lpseguin]

Thanks for the help.
This is a brand new Pi kit I bought so I'm assuming the hardware is not faulty but not so sure anymore.
But my next step was to install the default Raspberry OS and see if similar errors persisted there.

the reinstall didn't work unfortunately:

(...)
All packages are up to date.
root@DietPi4:~# apt install --reinstall libc-bin
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for libc-bin:arm64

[MichaIng]

No need to test RPi OS. This is not some kind of systematic error, but a random one, like it can happen (in very rare cases) that a download you do with any OS is faulty, because some random bit was wrong, despite error-correction mechanisms. It could be also a bad block on the SD card, but then on RPi OS, it might affect a completely different file, remaining unrecognised or leading to a very different error.

The package is btw indeed shipped by the RPi repository. Originally (from your dietpi-update logs) it crashed with a segmentation fault:

Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up libc-bin (2.36-9+rpt2+deb12u3) ...
Segmentation fault
Segmentation fault
dpkg: error processing package libc-bin (--configure):
 installed libc-bin package post-installation script subprocess returned error exit status 139
Errors were encountered while processing:
 libc-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)

However, this package was last updated this Oktober, so it should be fine, otherwise we would have seen many more reports with this error already. So probably indeed a random download error.

So lets try to manually overwrite the content of this package on your system:

cd /tmp
apt download libc-bin
dpkg -x libc-bin_*.deb /
apt install --reinstall ./libc-bin_*.deb
rm ./libc-bin_*.deb

[lpseguin]

Know of a good way to test the entire SD card ?
I reformatted it maybe 5-6 times with 3 different DietPI OS versions and always failed on the same libc-bin error.
It seems more than likely at this point that this would be an hardware failure or as you said more reports would come in about this.

I still had the same error with the manual download you suggested:

root@DietPi4:/tmp# apt download libc-bin
Get:1 https://archive.raspberrypi.org/debian bookworm/main arm64 libc-bin arm64 2.36-9+rpt2+deb12u3 [531 kB]
Fetched 531 kB in 1s (598 kB/s)

Note, selecting 'libc-bin' instead of './libc-bin_2.36-9+rpt2+deb12u3_arm64.deb'
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for libc-bin:arm64

[MichaIng]

Another report of this with RPi OS on Pi-hole forum, the only other result of this exact error on DuckDuckGo: https://discourse.pi-hole.net/t/pi-hole-not-fully-installing-failing-at-libc-bin/66946

There a simple

dpkg --reconfigure -a

helped. This is the step that failed on the initial package upgrade (according to the part of the log I posted) and as well for the user on the Pi-hole forum. Not sure how it can prevent the package reinstall from even reaching the point where it would run this step, with this strange "No file name for" error, but worth to try.

Google throws out one second match, this time Ubuntu: ros2/ros2#1352
A very rare thing it seems, which can happen with APT packages. Interesting that you are able to replicate this even with different DietPi images.

Rufus can do bad block tests on SD cards. However, for this is needs to overwrite and read back every bit of the SD card. And sometimes it does not even find something on one run, while there are bad blocks for sure. Doing multiple runs not only takes much time but further decreases the life span of the card, so I do not recommend it. As long as you do not see I/O errors in dmesg -l 0,1,2,3, the SD card should be fine. The question remains where this error is coming from, but lets see whether the reconfiguration above helps, rendering the question obsolete for now.

[lpseguin]

Hi again and happy new year!

After coming back home the pi was throwing bin errors and wouldn't even finish booting up in a usable state.
I took the time to flash the default Raspberry 64 bit light OS and it booted fine.
But I got the exact same libc-bin error after doing apt update -> apt upgrade.

Reflashed DietPI and tried out the configure option and it's throwing out the same error as before:

root@DietPi:~# sudo dpkg --configure -a
Setting up libc-bin (2.36-9+rpt2+deb12u3) ...
Segmentation fault
Segmentation fault
dpkg: error processing package libc-bin (--configure):
 installed libc-bin package post-installation script subprocess returned error exit status 139
Errors were encountered while processing:
 libc-bin

Still getting the same Controller never released inhibit bits error message in dmesg.
Same error message popped up at bootup in the default Raspberry OS too.

[Joulinar]

does it mean you have the same error with plain RPI OS as you have on DietPi? If yes, we might need to report to RPI developer.

[lpseguin]

does it mean you have the same error with plain RPI OS as you have on DietPi? If yes, we might need to report to RPI developer.

Yes exact same Segmentation Faults and exit codes

[Joulinar]

@MichaIng any idea if this is something to report to RPI or Debian repository?

[68wooley]

Folks,

I don't have a solution for you, but I wanted to let you know I'm having the same issue with libc-bin trying to install XFS on a Pi 5 running Pi OS Lite (64Bit) (bookworm).

I'll let you know if I find a solution.

[lpseguin]

Something worth trying:

I was running via a microSD to USB-A adaptor and booting from USB. I just re-imaged my card and booted from the internal microSD reader and I no longer have the problem.

If you're booting via USB, might be worth trying. Someone else posted the same issue/solution in the RPi forums:

https://forums.raspberrypi.com/viewtopic.php?t=358967#p2172823

Thanks a lot I was in the same situation and putting the MicroSD card in the internal Pi reader fixed the libc-bin error and the update is now working.

[Joulinar]

Does it just require a SD card present or does the system need to be booted from SD card as well?

[MichaIng]

Very strange. The error sounds more like if the package was compiled with wrong (too new for RPi 4, i.e. RPi 5 only) instruction set. Not good to know it's for whatever reason USB adapters, and indeed an issue with the RPi OS package itself.

[MichaIng]

Did someone test to use switch to dwc2 driver or disable UAS (for the USB-SD adapter)?