"cannot open shared object file: Input/output error" - for everything

ramonsnir · 2015-07-25 15:45:27

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).

ewaller · 2015-07-25 16:02:30

My first inclination would be that you are going to need to repair this from inside a chroot hosted by your install media.
Are you doing all of this remotely via ssh? If you reboot, it might not come back up, but have you tried that?

ramonsnir · 2015-07-25 16:18:17

I have not tried to reboot, and I too suspect that it will not come back up.

My current working theory is an SSD failure as I can't find any stale file handles in the secondary drive, and I've scheduled transportation for tomorrow...

Once I do get there and use an alternative boot device, what should I try? Regular fsck?

ewaller · 2015-07-25 16:19:59

That might not be a bad choice. My first inclination had been to get a look at the journal.

ramonsnir · 2015-07-25 16:24:07

Well, that too will require booting from a different device - journalctl was not spared from the havoc.

Thanks!

R00KIE · 2015-07-25 20:13:15

I would try to look at the output of dmesg, if it works that is, as it might provide some clues to what happened.

If it is an ssd and you have important data there that you haven't backed up, prepare for the worst as SSDs can just stop working after a reboot, see [1] to see what I mean.

[1] http://techreport.com/review/26523/the- … a-petabyte

ramonsnir · 2015-07-26 04:15:05

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!

R00KIE · 2015-07-26 09:56:41

That's good, but it doesn't mean you will be as lucky next time, be sure to do regular updates. Also keep and eye on smart parameters, I suppose SSDs will give enough advance warning before dying.

I haven't searched specifically for these kinds of problems but I suppose they will not be widely known or documented, out of curiosity which brand and model of ssd did this?

ramonsnir · 2015-07-26 10:05:11

I install updates every day (and backup, the important data). I'm pretty sure the smart parameters thing isn't supported in my SSD model (I remember checking that when I installed it).

ewaller · 2015-07-26 14:50:13

I am wondering if something had been pulled in to memory and was resident, and then it got upgraded on disk. The version in memory did not get up dated and was incompatible with other stuff that did get upgraded. I'm thinking your I/O problems were a figment of this strange state that went away when you rebooted and everything loaded fresh.

ramonsnir · 2015-07-26 14:53:26

For the record, the SSD is using btrfs. Perhaps it's some strange bug with it.

Arch Linux

#1 2015-07-25 15:45:27

"cannot open shared object file: Input/output error" - for everything

#2 2015-07-25 16:02:30

Re: "cannot open shared object file: Input/output error" - for everything

#3 2015-07-25 16:18:17

Re: "cannot open shared object file: Input/output error" - for everything

#4 2015-07-25 16:19:59

Re: "cannot open shared object file: Input/output error" - for everything

#5 2015-07-25 16:24:07

Re: "cannot open shared object file: Input/output error" - for everything

#6 2015-07-25 20:13:15

Re: "cannot open shared object file: Input/output error" - for everything

#7 2015-07-26 04:15:05

Re: "cannot open shared object file: Input/output error" - for everything

#8 2015-07-26 09:56:41

Re: "cannot open shared object file: Input/output error" - for everything

#9 2015-07-26 10:05:11

Re: "cannot open shared object file: Input/output error" - for everything

#10 2015-07-26 14:50:13

Re: "cannot open shared object file: Input/output error" - for everything

#11 2015-07-26 14:53:26

Re: "cannot open shared object file: Input/output error" - for everything

Board footer