Error loading shared library libgcc_s.so.1

Hi, I just did an OperWRT upgrade from 18.06 to 19.07 on a NAS device, Zyxel NSA310.
Then I installed Samba and created a new user for one of the Samba shares. When I try to log in via ssh with this new user, this error comes up after entering the password:

Error loading shared library libgcc_s.so.1: Permission denied (needed by /bin/ash)
Error relocating /bin/ash: __aeabi_idiv: symbol not found
Error relocating /bin/ash: __aeabi_dadd: symbol not found
Error relocating /bin/ash: __aeabi_i2d: symbol not found
Error relocating /bin/ash: __aeabi_uidivmod: symbol not found
Error relocating /bin/ash: __aeabi_dcmpgt: symbol not found
Error relocating /bin/ash: __aeabi_d2lz: symbol not found
Error relocating /bin/ash: __aeabi_dcmplt: symbol not found
Error relocating /bin/ash: __aeabi_idivmod: symbol not found
Error relocating /bin/ash: __aeabi_uldivmod: symbol not found
Error relocating /bin/ash: __aeabi_dcmple: symbol not found
Error relocating /bin/ash: __aeabi_dcmpge: symbol not found
Error relocating /bin/ash: __aeabi_d2f: symbol not found
Error relocating /bin/ash: __aeabi_dsub: symbol not found
Error relocating /bin/ash: __aeabi_d2iz: symbol not found
Error relocating /bin/ash: __aeabi_dcmpeq: symbol not found
Error relocating /bin/ash: __aeabi_f2d: symbol not found
Error relocating /bin/ash: __aeabi_ddiv: symbol not found
Error relocating /bin/ash: __aeabi_l2d: symbol not found
Error relocating /bin/ash: __aeabi_dmul: symbol not found
Error relocating /bin/ash: __aeabi_uidiv: symbol not found
Error relocating /bin/ash: __aeabi_ui2d: symbol not found
Error relocating /bin/ash: __aeabi_d2uiz: symbol not found
Error relocating /bin/ash: __aeabi_ldivmod: symbol not found

Could anybody give some advice? I'm not sure how to debug further...
The new user has its own home directory with the proper permissions and /bin/ash as shell.

Combined with the error messages below, the term upgrade kind of triggers me here. How did you upgrade? Using sysupgrade and the sysupgrade image or some other way (involving opkg)?

It was a straightforward sysupgrade, done from Luci, using this image.

Please, execute "ls -l /lib" and post the results here.

Well, I did a reinstall and now everything works ok, that error is gone.
I don't know if it was caused by the upgrade or some mistake when I did the configuration afterwards...

@eduperez I had looked at the contents of /lib, thinking that maybe it was a file permission/ownership problem. But I compared it to another (different) OpenWrt device and the listings were identical for libgcc_s.so.1 and libc.so (as ldd shows that libgcc_s depends only on libc).

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.