WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Problem with restore fsarchiver  (Read 3481 times)

Offline wandows

  • Newbie
  • *
  • Posts: 3
Problem with restore fsarchiver
« on: December 15, 2010, 08:46:59 PM »
This is my first post, sorry if I posted in the wrong place.

Fsarchiver always used to backup and restore using "System rescue cd ". There is little known and Tinycore've been doing some testing to unzip the files. "fsa", but gave the following error message:

"the data block (Which is shared by multiple files) is corrupt"

could someone give me a light on this error.

Since already many thanks.

Offline gutmensch

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 605
  • I can make it disappear, have no fear!
    • remembrance blog
Re: Problem with restore fsarchiver
« Reply #1 on: December 16, 2010, 07:31:17 AM »
please run
Code: [Select]
$ tce-update
first in a terminal to get a newer version. I updated fsarchiver, there was also a problem with a link to the lzma lib.

if the problem persists please use the debug options (-d -v) of fsarchiver and attach them to your post. I made a quick test with savefs and restorefs and it worked for me.
If I seem unduly clear to you, you must have misunderstood what I said. (Alan Greenspan)

Offline wandows

  • Newbie
  • *
  • Posts: 3
Re: Problem with restore fsarchiver
« Reply #2 on: December 16, 2010, 08:55:07 PM »
please run
Code: [Select]
$ tce-update
first in a terminal to get a newer version. I updated fsarchiver, there was also a problem with a link to the lzma lib.

if the problem persists please use the debug options (-d -v) of fsarchiver and attach them to your post. I made a quick test with savefs and restorefs and it worked for me.

I did what you recommended and then running the tce-update was enough to solve the problem.

Savefs was created with a new backup. fsa

Restfs was restored with the file created and restored an old file created with "System Rescue CD".

Regarding the creation of symbolic link Liblzma.so.0 I had solved by searching here in the forum.
I added the following lines in /opt/bootlocal.sh link to be created shortly after boot.
Correct me if I did the correct procedure.

ln -s /usr/local/lib/liblzma.so /usr/local/lib/liblzma.so.0
ldconfig


Thank gutmensch, since I'm very grateful.

Offline gutmensch

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 605
  • I can make it disappear, have no fear!
    • remembrance blog
Re: Problem with restore fsarchiver
« Reply #3 on: December 17, 2010, 09:15:19 AM »
Regarding the creation of symbolic link Liblzma.so.0 I had solved by searching here in the forum.
I added the following lines in /opt/bootlocal.sh link to be created shortly after boot.
Correct me if I did the correct procedure.

ln -s /usr/local/lib/liblzma.so /usr/local/lib/liblzma.so.0
ldconfig


That was indeed absolutely correct but now it shouldn't be necessary anymore because fsarchiver now links to liblzma.so.5 and not liblzma.so.0 anymore. :)

Glad that I could be of help, you're welcome!
If I seem unduly clear to you, you must have misunderstood what I said. (Alan Greenspan)

Offline wandows

  • Newbie
  • *
  • Posts: 3
Re: Problem with restore fsarchiver
« Reply #4 on: December 17, 2010, 11:01:42 AM »
Regarding the creation of symbolic link Liblzma.so.0 I had solved by searching here in the forum.
I added the following lines in /opt/bootlocal.sh link to be created shortly after boot.
Correct me if I did the correct procedure.

ln -s /usr/local/lib/liblzma.so /usr/local/lib/liblzma.so.0
ldconfig


That was indeed absolutely correct but now it shouldn't be necessary anymore because fsarchiver now links to liblzma.so.5 and not liblzma.so.0 anymore. :)

Glad that I could be of help, you're welcome!


I removed the lines that were added to the / opt / bootlocal.sh and functioned normally.

 Good thing that this little bug has been fixed.

 Thank you for the great reception and attention.  ;D