Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

pacman: error while loading shared libraries: libarchive.so.13: cannot open shared object file: Input/output error

Almost every command responds with something like this, each with a different shared object. At least the coreutils are functioning...

It just happened at a single moment, I suspect due to a bad package installation (I had an AUR update running in a separate SSH session that since disconnected).

I can't even access the pacman log, because... well...

When ls'ing /usr/share I get (trimmed response):

ls: cannot access libndr.so.0.0.3: Input/output error
ls: cannot access libsamdb.so: Input/output error
ls: cannot access libsamba-credentials.so.0: Input/output error
ls: cannot access libdcerpc.so: Input/output error
ls: cannot access libdcerpc-samr.so.0: Input/output error
ls: cannot access libSoundTouch.so.0: Input/output error
ls: cannot access libSoundTouch.so.0.0.0: Input/output error
ls: cannot access libjavascriptcoregtk-4.0.so.18.1.11: Input/output error
ls: cannot access libclangLex.a: Input/output error
ls: cannot access libclangParse.a: Input/output error
ls: cannot access libclangAnalysis.a: Stale file handle
ls: cannot access libclangFrontendTool.a: Stale file handle
ls: cannot access libclangBasic.a: Input/output error
ls: cannot access libclangSema.a: Stale file handle
ls: cannot access libclangAST.a: Stale file handle
ls: cannot access libclangDriver.a: Stale file handle

Any idea how to start dealing with this? I should note that I don't have physical access to the machine (at probably won't have for a couple more days).

share|improve this question
    
What does dmesg tell you? –  Tero Kilkanen Jul 25 at 16:48
    
@TeroKilkanen /usr/bin/dmesg: Input/output error –  Ramon Snir Jul 25 at 17:02
    
Try cat /proc/kmsg in one session and accessing the filesystem in another session. This should show the kernel error messages if dmesg command fails like that. –  Tero Kilkanen Jul 26 at 2:03
    
@TeroKilkanen Both sudo and su are inaccessible :'-( I'm going to get physical access to the computer today, hopefully fsck will get some results. –  Ramon Snir Jul 26 at 3:00

1 Answer 1

up vote 0 down vote accepted

There must be something basic about SSDs that I don't understand, but I'll post this as hope to all future Googlers:

I backed-up everything I could (directory listings, mostly - and some files that were still accessible), then rebooted ('cause hunch). EVERYTHING CAME BACK TO NORMAL. I don't know how a reboot can resolve disk issues, but apparently - it can.

Cross your fingers and have hope, future readers!

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.