Created attachment 962 [details]
I tried to install ipfire (core 161) using the iso created via ipfire's backup menu. For unknown reasons, after the installation succeeded, the backup was found but could not be restored.
Only error message I got was "An error occured when the backup file was restored" which of course doesn't help at all in finding the problem.
This should really be more informative:
- What error happened exactly?
- Where can I find more information about this?
- Is there a log file?
(In reply to Larsen from comment #0)
> This should really be more informative:
> - What error happened exactly?
> - Where can I find more information about this?
> - Is there a log file?
You can press Alt-F2 to get to the error console and see more about what went wrong.
Could you please test this patch for me, because I believe that it fixes the problem:
Thanks for the quick fix. Testing the patch on our production machine, it now created a gzipped IPF instead of a tar one. I was then able to successfully install/restore in VirtualBox.
As for the actual topic of this ticket: Would be quite useful if the error message was expanded to include "Press Alt+F2 for possibly more details".
Just installed Core 162. The fix is not yet implemented as it seems.
The commit for the fix is in the Core Update 163 build.
Although the underlying problem has been fixed, the error message still should be redacted to present the user more information than just "an error has occured", meaning "good luck trying to figure out what exactly".
(In reply to Larsen from comment #6)
> Although the underlying problem has been fixed, the error message still
> should be redacted to present the user more information than just "an error
> has occured", meaning "good luck trying to figure out what exactly".
I agree with this, but there is no way to do this. The installer calls tar to extract the backup tarball and we do not know what went wrong when it does since tar only returns an error code to us.
The installer software isn't flexible enough that we could read a log file or something similar and display it to the user. If it would offer that flexibility, I wouldn't be too sure whether that is helping everyone.
So for as long as this does not show up again, there should be no need to invest too much time into this.
I guess tar's error code could be added to the current output to at least have some more info, couldn't it?
It will only be one for “an error has occurred” or zero for “no error has occurred”. There is no further information to be drawn from this.
I see. Thought the error code would be in a broader range than that.