-
-
Notifications
You must be signed in to change notification settings - Fork 495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Raspberry Pi | libc-bin segmentation fault when using USB-SD adapter #6824
Comments
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 |
Hi! Here's the output from the cmd:
|
Can you share following Architecture | |
arm64 |
Strange error. Not sure whether this means that some meta file (one of /boot/dietpi/func/dietpi-set_software apt clean
apt update
apt install --reinstall libc-bin |
Thanks for the help. the reinstall didn't work unfortunately:
|
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
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 |
Know of a good way to test the entire SD card ? I still had the same error with the manual download you suggested:
|
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 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 |
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. Reflashed DietPI and tried out the configure option and it's throwing out the same error as before:
Still getting the same Controller never released inhibit bits error message in dmesg. |
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 |
@MichaIng any idea if this is something to report to RPI or Debian repository? |
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. |
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. |
Does it just require a SD card present or does the system need to be booted from SD card as well? |
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. |
Good question. I'll test this afternoon and let you know. |
OK - here's what I found: It seems the issue is tied to the use of a microSD to USB-A adaptor:
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. |
Did someone test to use switch to |
I'm following because I'm encountering the same issue. In my case it's because I messed up the SD reader somehow, either by pushing it in at an angle or perhaps backwards. I can't boot or read from the SD but can from the same card in a USB adapter. I have a new RPi4 on the way (ordered before I discovered the physical damage), but it would be nice to get this board working with the USB adapter. In January you asked if anyone had tested dwc2 or disabling UAS for the USB-SD adapter. If you can point me in the right direction to try that with Dietpi, I'm game. Since the box is solely for pihole, it's not doing me any good right now without being able to install pihole on this new SD card. |
To disable UAS: echo 'blacklist uas' > /etc/modprobe.d/disable-uas.conf To switch to G_CONFIG_INJECT 'dtoverlay=dwc2' 'dtoverlay=dwc2' /boot/config.txt If you have no other USB drive to boot from and hence no way to actually boot this RPi 4: Do you have another Linux system to access the ext4 filesystem and edit those files there? Else, with a new image, you could use an automation script: Access the FAT setup partition and create a file named #!/bin/dash
echo 'blacklist uas' > /etc/modprobe.d/disable-uas.conf
reboot respectively: #!/bin/dash
echo 'dtoverlay=dwc2' >> /boot/config.txt
reboot or with both commands. Assure to use Unix/LF file endings (instead of Windows/CR LF)! Proper editors should habe the option to change this. Then try to boot it. This script executes at early boot stage, which is hopefully reached. If not, then there is no other way than accessing the ext4 filesystem from another Linux system. |
I wish I'd been about 10 minutes more patient. I (obviously not knowing what I'm doing) manually inserted |
I didn't try disabling UAS because a number of posts I read suggested it might not be configured as a module and blacklisting it might not have an effect. In any event the SD card is now not bootable in the Pi although I can read it fine in Linux. I might give up on this broken board and setup the new one that's allegedly arriving today according to Amazon. |
modinfo uas See the file path, else it would show "builtin". Neither But quite possible that the RPi/kernel simply does not support your USB-SD adapter, like OP and the RPi forum thread are indicating as well. Just worth an attempt to switch driver and UAS. |
Thanks. I can't get the RPi to boot from USB still, and now I have to go out so can't mess with it anymore tonight. I'll just put the working dietpi card in the new SD slot when the new board arrives. Thanks for the info and assistance. |
Thank you for saving me my time. Yes, same Issue. Package libc-bin error on USB-A MicroSD Adapter. Both Raspberry OS 64 and DietPi latest iso same error. I was afraid that my hardware was broken. Now, just removed the SD Card from Adapter and booted from on-Board SD Card Reader. Everything works. Thanks a lot!! |
Hit the same issue on my raspbian install after switching the card to an SD Card reader (which reduced GPS interference). I also ended up with an unbootable SD Card. Adding |
Hey! I just found out about this page, and now I know that I'm not alone. I have faced this issue for like 1 year. I boot Armbian (Debian Bookworm-based) using microsd card to USB adapter, and I always got libc segmentation fault when using Today I reinstalled Armbian 23.11.1 (still Bookworm based) and it works without any libc problems, until I do a EDIT: I think I found the solution. Just download the Edit 2: I think one of these patches caused the problem, but I don't know which one did:
(from https://metadata.ftp-master.debian.org/changelogs//main/g/glibc/glibc_2.36-9+deb12u7_changelog) |
@raspiduino So it is not an RPi but some ARM set-top box in your case? And the latest Debian build of Does it work as well when you use the older build from Debian snapshots here? https://snapshot.debian.org/archive/debian/20240429T204458Z/pool/main/g/glibc/libc-bin_2.36-9%2Bdeb12u6_arm64.deb |
I think so. I think a common thing between us is we all booting from SD-to-USB adapter.
Yes. It's a quadcore ARM Cortex-A53 set-top box. It boots Armbian from SD-to-USB adapter.
Yes it works. |
Guys, the latest version of the package contains quite a lot of fixes, including some crashes. Can you test again upgrading it? |
DietPi version
G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=24
G_DIETPI_VERSION_RC=1
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
Distro version
bookworm 0
Kernel version
Linux DietPi4 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
SBC model
RPi 4 Model B (aarch64)
Power supply used
[5.1V 3.0A, Black, UL Listed]
SD card used
SanDisk ultra
Bug report ID
20d1f2ae-a76d-4003-888a-051aa39f901a
Steps to reproduce
Expected behaviour
Actual behaviour
Extra details
Bug report of that one is : 5d5c4461-2ef7-4e4e-8a66-286367b0279c
The text was updated successfully, but these errors were encountered: