Results 1 to 3 of 3

Thread: appassure, maintenance mode, fsck.ext3

  1. #1

    Default appassure, maintenance mode, fsck.ext3

    One of our guys installed the Appassure Client for SLES on Opensuse 11.3 - i586. Unfortunately, that broke something.

    Fsck.ext3 throws this error on boot:
    fsck.ext3: error while loading share libraries: libext2fs.so.2: cannot open shared object file: No
    such file or directory

    Fsck fails, so the system loads into maintenance mode with a read only file system.

    I ran fsck on the drive, and it succeeds every time. The box is running in ESXI with a drive array, and I don't think we have a bad drive. This started with Appassure, and that is probably the problem. And no, there is no snapshot from before the install, sadly. I have one now that I am trying multiple fixes.

    The instructions for removing the appassure agent have been run. The installation script may be run with "-u" to uninstall. It fails to download '/repodata/repomd.xml' several times, then takes the rpm packages out. At this point, it has been run, and running it again it says 'Nothing to do'.

    Another Appassure deployment guide includes instructions for removing the Appassure components with rpm and zypper. This has worked in the past when someone decides to try to use appassure to backup this box and causes this issue, but it is not working this time. This set of commands succeed--all the rpm removals are successful. However, the "zypper remove dkms" throws some more repodata errors, and then says "Nothing to do."

    There are still some errors when it boots pertaining to appassure, even in maintenance mode, namely the alias for Appassure VSS entry in /etc/sysconfig/kernel. I've commented it out, but it occurs after the fsck check and changed nothing. It does make me think Appassure did not uninstall correctly. Also, the ldd /sbin/fsck.ext3 shows that libext2fs.so.2 is in /opt/appassure/lib/libext2fs.so.2, which it is, but that is not the original library location. There is an extra entry in lib.so.conf, and if the opt/appassure is removed, the ldd result goes back to /lib/libext2fs.so.2, but the problem does not go away.

    Is this an Fsck.ext3 issue? The object not found problem would seem to indicate that, but the /lib/libext2fs.so.2 is present, and linked to /lib/libext2fs.so.2.4.

    I've reinstalled the rpm for util-linux. No change. I've tried to reinstall appassure, but the script won't complete without downloads or the original iso (which I don't have and can't find for opensuse 11.3 1-82 i586). I tried to upgrade to 11.3 final, but it failed on the grub configuration, and then would not boot. I rolled back to a snapshot before the 11.3 upgrade, so I am back at square one.

    Is this really a grub problem somehow?

  2. #2
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    30,484

    Default Re: appassure, maintenance mode, fsck.ext3

    The problem in getting help hre might be that:
    • opeenSUSE 11.3 is way out of support and thus not many users here have it available for any tests;
    • this is not the SLES forum and people here normaly have few to no SLES/SLED knowledge.


    My personal conclusion would be that putting a typical SLES (for any version, you mentioned none) application on openSUSE is only something that should be done by somebody who knows th ins and outs of the application and of both distributions.
    Henk van Velden

  3. #3
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: appassure, maintenance mode, fsck.ext3

    On 2014-03-28 17:56, Jeff S wrote:
    >
    > One of our guys installed the Appassure Client for SLES on Opensuse 11.3
    > - i586. Unfortunately, that broke something.


    I don't know anything about that Appassure. However, in general, you can
    not put something designed for SLES in openSUSE.

    On the other hand, openSUSE 11.3 is obsolete, out of maintenance. Any
    reason you are using it?

    > Fsck.ext3 throws this error on boot:
    > fsck.ext3: error
    > while loading share libraries: libext2fs.so.2: cannot open shared object
    > file: No
    >
    > such file or directory


    So you probably replaced some system components/libraries in your
    system. Or the library resides on a mount that is not yet available.

    I can not make more conjectures, because I have no idea what that
    Appassure changes.


    If you want to recover your openSUSE 11.3, I suggest you install it
    again from scratch. You can pick up data and configuration from the
    other machine, with care.

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" at Telcontar)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •