| 1 |
2009/11/18 Maxim Wexler <maxim.wexler@×××××.com>: |
| 2 |
> Hi group, |
| 3 |
> |
| 4 |
> I ran emerge -avuDN world and came up with blocked packages which I |
| 5 |
> eliminated by un-merging device-mapper and e2fsprogs-libs. When I |
| 6 |
> rebooted was greeted by a maintenance console and the message |
| 7 |
> "libblkid.so.1 cannot open shared object file". A little googling |
| 8 |
> later I realized that e2fsprogs-libs should not have been removed. No |
| 9 |
> problem, I'll chroot and fix it. |
| 10 |
> |
| 11 |
> After the chroot I was able to mount /dev/sda1 on /mnt/gentoo but |
| 12 |
> couldn't mount /dev/sdb2 |
| 13 |
> on /var where portage is kept on this system. The error was identical |
| 14 |
> to the original one when the pc was first rebooted: |
| 15 |
> |
| 16 |
> "mount: error while loading shared libraries: libblkid.so.1..." |
| 17 |
> |
| 18 |
> I tried to run e2fsck on /dev/sda2 but got this error msg: |
| 19 |
> |
| 20 |
> "e2fsck: error while loading shared libraries: libcom_err.so.2: cannot |
| 21 |
> open shared object file..." |
| 22 |
> |
| 23 |
> Any one see a way past this impasse? I'm using ext2 with the journal option. |
| 24 |
|
| 25 |
I had to downgrade e2fsprogs last night to test some apparent |
| 26 |
incompatibility with the new HAL version (which won't compile on older |
| 27 |
util-linux, and this depends on e2fsprogs). |
| 28 |
|
| 29 |
I believe the advice already posted would be a good start and should |
| 30 |
fix your system. |
| 31 |
|
| 32 |
For the future, I suggest a useful thing to avoid annoyance and |
| 33 |
hassles like this in portage: |
| 34 |
|
| 35 |
One thing I suggest here is if you can spare some harddisk space, |
| 36 |
universally enable the portage feature buildpkg in make.conf. This |
| 37 |
will keep a .tgz of all binary packages as they were compiled before |
| 38 |
they were installed by portage. I've had the feature enabled for a |
| 39 |
few months, in which time a very large portion of my system has been |
| 40 |
re-compiled. Right now, /usr/portage/packages takes up about 600 MB |
| 41 |
of my disk space. |
| 42 |
|
| 43 |
When I was downgrading e2fsprogs (more difficult and risky than |
| 44 |
upgrade), I was able to emerge -k on e2fsprogs and libs (I had to |
| 45 |
disable collision-protect and protect-owned, which is only recommended |
| 46 |
for special cases when you are aware of what you're doing) and resume |
| 47 |
the system. |
| 48 |
|
| 49 |
For upgrading these kinds of files, what you need to do is a |
| 50 |
--fetchonly first on any blocked packages. |
| 51 |
|
| 52 |
If your problems persist and you just cannot get the system back in |
| 53 |
shape using a live CD, I suggest emailing the list your architecture |
| 54 |
and system details (ideally, just attach make.conf), and someone with |
| 55 |
similar hardware and USE flags might be nice enough to run a buildpkg |
| 56 |
for you and post the binaries somewhere. I'd post mine right now, but |
| 57 |
I'd rather wait to hear back your results and hardware specs. |
| 58 |
|
| 59 |
~daid |
Archives