Hi Philippe

Looks like i misread your joblog.  I missed that its forwarding the volume to 0:256 (i.e. it skips the first 256 bytes [0, 255]). That means that the first 256 bytes (the volume label) are read correctly (as you verified). Could you instead post the bytes [256, 280] (or to make off-by-ones more unlikely, the first 300 bytes) ?
Sorry for the inconvenience!

Kind Regards
Sebastian Sura

Am 18.06.24 um 11:14 schrieb 'Philippe' via bareos-users:
Hi Sebastian,

thanks for your answer!

Here's what I get from the disk:

$ dd if=AI-Incremental-0525 bs=24 count=1 status=none | xxd
00000000: c75d 2e97 0000 00ff 0000 0000 4242 3032 .]..........BB02
00000010: 0000 0030 6640 9701                      ...0f@..

comparing this with another file it doesn't look that bad for me:

$ dd if=AI-Incremental-0526 bs=24 count=1 status=none | xxd
00000000: d5fa 7af2 0000 00ff 0000 0000 4242 3032 ..z.........BB02
00000010: 0000 0030 6659 a382                      ...0fY..

fwiw: the data resides on a zfs (scrubbed, verified) and the sd machine powers up before the backups start and shuts down when completed.


Kind regards,

Philippe


On 18.06.24 09:25, Sebastian Sura wrote:
Hi Philippe

It looks like the first block header of your volume somehow got corrupted. Could you try to read the first 24 bytes of that volume and send them here  ? The block header is supposed to look like this: https://docs.bareos.org/DeveloperGuide/mediaformat.html#block-header While its probably not possible repair the block header ourselves, we might be able to identify which byte was not written
and try to put it into a state where bareos will accept it.

Kind Regards
Sebastian Sura

Am 17.06.24 um 16:48 schrieb 'Philippe' via bareos-users:
(re-sending to list)

Hi Andreas,


thanks for clarifying this. So, probably at least after Bareos throwing the "does not exists" error the file shows up with a size of 61GiB.

Taking a closer look this report seem to have two errors, one "non-fatal" error saying

Volume data error at 0:256! Wanted ID: "BB02", got "B02". Buffer discarded.

and the "fatal" error related to the non-existing file at some point of time.

I don't know what's broken here but since the errors are refering to different files every day regarding the fatal error but not the "non-fatal" error, I believe the AI-Incremental-0525 file (which exists for a month now and is 530M of size) might be corrupted.

12-Jun 12:52 storage JobId 42456: Forward spacing Volume "AI-Incremental-0525" to file:block 0:256. 12-Jun 12:52 storage JobId 42456: Error: stored/block.cc:291 Volume data error at 0:256! Wanted ID: "BB02", got "B02". Buffer discarded. 12-Jun 12:52 storage JobId 42456: Fatal error: stored/mac.cc:696 Fatal append error on device "File-Consolidated-storage" (/backup/bareos-consolidated-tape): ERR=stored/dev.cc:597 Could not open: /backup/bareos-consolidated-tape/AI-Consolidated-0577, ERR=No such file or directory

13-Jun 12:54 storage JobId 42515: Forward spacing Volume "AI-Incremental-0525" to file:block 0:256. 13-Jun 12:54 storage JobId 42515: Error: stored/block.cc:291 Volume data error at 0:256! Wanted ID: "BB02", got "B02". Buffer discarded. 13-Jun 12:54 storage JobId 42515: Fatal error: stored/mac.cc:696 Fatal append error on device "File-Consolidated-storage" (/backup/bareos-consolidated-tape): ERR=stored/dev.cc:597 Could not open: /backup/bareos-consolidated-tape/AI-Consolidated-0578, ERR=No such file or directory

14-Jun 12:54 storage JobId 42574: Forward spacing Volume "AI-Incremental-0525" to file:block 0:256. 14-Jun 12:54 storage JobId 42574: Error: stored/block.cc:291 Volume data error at 0:256! Wanted ID: "BB02", got "B02". Buffer discarded. 14-Jun 12:54 storage JobId 42574: Fatal error: stored/mac.cc:696 Fatal append error on device "File-Consolidated-storage" (/backup/bareos-consolidated-tape): ERR=stored/dev.cc:597 Could not open: /backup/bareos-consolidated-tape/AI-Consolidated-0579, ERR=No such file or directory

15-Jun 13:03 storage JobId 42633: Forward spacing Volume "AI-Incremental-0525" to file:block 0:256. 15-Jun 13:03 storage JobId 42633: Error: stored/block.cc:291 Volume data error at 0:256! Wanted ID: "BB02", got "B02". Buffer discarded. 15-Jun 13:03 storage JobId 42633: Fatal error: stored/mac.cc:696 Fatal append error on device "File-Consolidated-storage" (/backup/bareos-consolidated-tape): ERR=stored/dev.cc:597 Could not open: /backup/bareos-consolidated-tape/AI-Consolidated-0581, ERR=No such file or directory

16-Jun 12:51 storage JobId 42692: Forward spacing Volume "AI-Incremental-0525" to file:block 0:256. 16-Jun 12:51 storage JobId 42692: Error: stored/block.cc:291 Volume data error at 0:256! Wanted ID: "BB02", got "B02". Buffer discarded. 16-Jun 12:51 storage JobId 42692: Fatal error: stored/mac.cc:696 Fatal append error on device "File-Consolidated-storage" (/backup/bareos-consolidated-tape): ERR=stored/dev.cc:597 Could not open: /backup/bareos-consolidated-tape/AI-Consolidated-0583, ERR=No such file or directory

17-Jun 12:53 storage JobId 42751: Forward spacing Volume "AI-Incremental-0525" to file:block 0:256. 17-Jun 12:53 storage JobId 42751: Error: stored/block.cc:291 Volume data error at 0:256! Wanted ID: "BB02", got "B02". Buffer discarded. 17-Jun 12:53 storage JobId 42751: Fatal error: stored/mac.cc:696 Fatal append error on device "File-Consolidated-storage" (/backup/bareos-consolidated-tape): ERR=stored/dev.cc:597 Could not open: /backup/bareos-consolidated-tape/AI-Consolidated-0585, ERR=No such file or directory

So, are some of my backups lost? What can I do here - remove the nextcloud-jobs and all previous backups and start from scratch?

Kind regards,

Philippe


--
 Sebastian Sura                  [email protected]
 Bareos GmbH & Co. KG            Phone: +49 221 630693-0
 https://www.bareos.com
 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
 Komplementär: Bareos Verwaltungs-GmbH
 Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz

--
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/404fd4b4-961d-4fd5-a161-1d4079cc9d4d%40bareos.com.

Reply via email to