Hello Sergio, Yes, it has all signs of being a hardware error. A critical target error with a sector address that is reasonable for Bacula's byte address sounds to me like the OS had a write error so the disk could not be read correctly by Bacula. The time of the kernel error is after the Bacula read, so perhaps sometime after the disk was written by Bacula it started going bad. About the only thing you can do now is run the the restore (either with bextract or on the bacula-sd execution line) with -p, so that Bacula will try to ignore errors. You might be able to restore something. Best regards, Kern On 07/06/2017 04:57 PM, Sergio Belkin
wrote:
|
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users