Jump to content

Recommended Posts

I don't know why but my backup scripts started to faill and the most recent produced this log. Am I correct in thinking this is a fatal error. Do the 'bad media set header' reports indicate drive failure or just disk corruption? Scrap and start again? Can I recover aythting? DiskWarrior unable to repair - runs out of memory - waiting for version 5 which is supposed to deal better with ™ and Retrospect-type backp files.

 

Any advice?

 

Thanks

 

Normal backup using WGS2015 at 26/06/2015 18:29:43

Adding to 7.3 TB of backup set data, starting at file index 15,111

!Bad Media Set header found (0xx at 9004347e)

!Bad Media Set header found (0xx at a8800d78)

!Generated MD5 digest for file "" does not match stored MD5 digest.

!Bad Media Set header found (0xx at beae827f)

!Generated MD5 digest for file "" does not match stored MD5 digest.

!Bad Media Set header found (0xx at 34003300)

!Bad Media Set header found (0xx at 57a0005)

!Bad Media Set header found (0xx at 7a00b002)

!Bad Media Set header found (0xx at ffffffff)

!Generated MD5 digest for file "/Volumes/Macintosh HD/IDA (2013).m4v" does not match stored MD5 digest.

!Bad Media Set header found (0xx at 39802e3)

!Bad Media Set header found (0xx at 48a004ac)

!Bad Media Set header found (0xx at e9384330)

!Bad Media Set header found (0xx at 33c4026)

!Bad Media Set header found (0xx at 30011b80)

!Bad Media Set header found (0xx at c4012680)

!Bad Media Set header found (0xx at dd02a6a0)

!Bad Media Set header found (0xx at 1000000)

!Bad Media Set header found (0xx at 208c0df)

!Bad Media Set header found (0xx at b09b6902)

!Bad Media Set header found (0xx at 802cb8c0)

!Bad Media Set header found (0xx at 52004700)

!Bad Media Set header found (0xx at b400d0c0)

!Bad Media Set header found (0xx at 192004a0)

!Bad Media Set header found (0xx at 3a8412b)

!Bad Media Set header found (0xx at 82830114)

!Bad Media Set header found (0xx at c28bb803)

!Bad Media Set header found (0xx at 4012600e)

!Bad Media Set header found (0xx at fce133f8)

!Bad Media Set header found (0xx at 3dc0169)

!Bad Media Set header found (0xx at 4012600e)

!Bad Media Set header found (0xx at 4b001e20)

!Bad Media Set header found (0xx at 41d600c)

!Bad Media Set header found (0xx at bc0164c0)

!Bad Media Set header found (0xx at 1000000)

!Bad Media Set header found (0xx at ec80181)

TFile::Read: read failed, /Volumes/4TB external/Retrospect/27Jan15/4-27Jan15/AC015111.rdb, oserr 16, error -1,020

!Trouble reading: "4-27Jan15" (330753), error -204 (device busy)

To Backup Set 27Jan15...

Can't access volume iTunes on Astra’s Computer, error -535 (backup client: network unavailable)

 

Can't access volume Macintosh HD on Astra’s Computer, error -535 (backup client: network unavailable)

- 26/06/2015 18:29:43: Copying Macintosh HD

Using Instant Scan

26/06/2015 18:32:30: Found: 1689018 files, 403542 folders, 933.3 GB

26/06/2015 18:38:00: Finished matching

26/06/2015 18:41:28: Copying: 97790 files (98.8 GB) and 51 hard links

Adding to 7.3 TB of backup set data, starting at file index 15,111

!Bad Media Set header found (0xx at 9004347e)

!Bad Media Set header found (0xx at a8800d78)

!Generated MD5 digest for file "/Volumes/Macintosh HD/FOXCATCHER.m4v" does not match stored MD5 digest.

!Bad Media Set header found (0xx at 50022630)

!Bad Media Set header found (0xx at 839adf70)

!Bad Media Set header found (0xx at 2e736864)

!Media Set format inconsistency (4 at 336057384)

!Bad Media Set header found (0xx at 3532c682)

!Generated MD5 digest for file "" does not match stored MD5 digest.

!Bad Media Set header found (0xx at 4b7c4682)

!Bad Media Set header found (0xx at 400204a0)

!Bad Media Set header found (0xx at a07da380)

!Bad Media Set header found (0xx at a2803be)

!Bad Media Set header found (0xx at dd63e1a4)

!Bad Media Set header found (0xx at d0091540)

!Generated MD5 digest for file "/Volumes/Macintosh HD/IDA (2013).m4v" does not match stored MD5 digest.

!Bad Media Set header found (0xx at 52787672)

!Bad Media Set header found (0xx at 641b3758)

!Bad Media Set header found (0xx at 23e8038)

!Bad Media Set header found (0xx at c00bf001)

!Bad Media Set header found (0xx at 9001d040)

!Bad Media Set header found (0xx at 6ee60301)

!Bad Media Set header found (0xx at 40282400)

!Bad Media Set header found (0xx at b00a8750)

!Bad Media Set header found (0xx at b09b6902)

!Bad Media Set header found (0xx at 802cb8c0)

!Bad Media Set header found (0xx at 52787672)

!Bad Media Set header found (0xx at 4803414d)

!Bad Media Set header found (0xx at ad7a687b)

!Bad Media Set header found (0xx at 2e736864)

!Media Set format inconsistency (4 at 336075476)

!Bad Media Set header found (0xx at 56906171)

!Bad Media Set header found (0xx at 2e736864)

!Media Set format inconsistency (4 at 336075800)

!Bad Media Set header found (0xx at f2008c8)

!Bad Media Set header found (0xx at 2708a047)

!Bad Media Set header found (0xx at 8e457cc1)

!Bad Media Set header found (0xx at 6d400750)

!Bad Media Set header found (0xx at d00fbcc0)

!Bad Media Set header found (0xx at 4015c008)

!Bad Media Set header found (0xx at 98034f90)

!Bad Media Set header found (0xx at 80022380)

!Bad Media Set header found (0xx at c01ec000)

!Bad Media Set header found (0xx at 59500648)

TFile::Read: read failed, /Volumes/4TB external/Retrospect/27Jan15/4-27Jan15/AC015111.rdb, oserr 16, error -1,020

!Trouble reading: "4-27Jan15" (330753), error -204 (device busy)

!Catalog File out of sync with Media Set "27Jan15".

26/06/2015 18:45:29: Execution incomplete

Remaining: 97,790 files, 98.8 GB

Completed: 0 files, 0 B

  • Like 2

Share this post


Link to post
Share on other sites

Does the error messages give any clue about which .rdb files that are the problem?

If so, move them to the desktop (for instance) and run recatalog again. The source files in the problematic .rdb files will be backed up again during the next backup.

Share this post


Link to post
Share on other sites

Actually looking through the log, the issue seems to be with the following file AC015111.rdb.  Try moving this file to the desktop like Lennart said and see if that fixes your issue.

Share this post


Link to post
Share on other sites

Thanks for your replies. I think the problem is that the disk is damaged - but I can’t get rid of it from the catalog or the Media Set.

 

I have disconnected the disk, repaired the set, listing only three drives as members, but the repair/rebuild operation keeps asking for the fourth disk.

 

I have tried to remove it from the Media set window but the minus button is greyed out.

 

I’m assuming that if I get rid of this disk from Retrospect’s ‘memory’ then I can run the backup again and use another disk for the missing files. Yes?

 

How about if I copied the existing backup to a new set of disks under a different Media Set name - would Retrospect still ask for the missing disk before completing the operation?

 

Thanks

Share this post


Link to post
Share on other sites

Thanks - that's what I thought but although it was marked as lost the rebuild always asked for it.

 

Anyway, a Copy script has created a new Media Set without requesting the fourth drive (disconnected) and I am just waiting for it to stop verifying. It is only about half the size of the original set so I don't know what has been purged.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×