public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] glibc can't find /lib/libdl.so.2
Date: Sun, 19 Mar 2023 11:27:06 +0000	[thread overview]
Message-ID: <2138515.irdbgypaU6@lenovo.localdomain> (raw)
In-Reply-To: <cc36c1000d9a6e0c4b5d5caac25ae90b61fa48e3.camel@connell.tech>

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

On Sunday, 19 March 2023 02:46:18 GMT Matt Connell wrote:
> On Sat, 2023-03-18 at 18:36 +0000, Michael wrote:
> > The kernel has IA32_EMULATION compiled in:
> > 
> >  # grep IA32_EMULATION /usr/src/linux/.config
> > CONFIG_IA32_EMULATION=y
> 
> Small nit-pick: Is it enabled in the kernel that is actually running?  
> 
> zgrep CONFIG_IA32_EMULATION /proc/config.gz

I don't have IKCONFIG in the kernel, but I did check in the first instance 
which kernel I had booted with.


> > and /lib/libdl.so.2 appears to be present and correct
> 
> Is the file (or the filesystem, or the disk) possibly corrupted?  The
> "cannot real file data: Input/output error" is troubling.  I would try
> fsck'ing the file system from a live USB if possible.

Yes!  This was the problem.  I have a corrupted partition and all sort of 
files can't be accessed.  :-(

Now to see how old the backup I have is and take it from there.  Thanks for 
pointing me in the right direction.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-03-19 11:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-18 18:36 [gentoo-user] glibc can't find /lib/libdl.so.2 Michael
2023-03-18 19:37 ` Peter Böhm
2023-03-18 21:11   ` Michael
2023-03-19  2:46 ` Matt Connell
2023-03-19 11:27   ` Michael [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2138515.irdbgypaU6@lenovo.localdomain \
    --to=confabulate@kintzios.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox