Getting generic backup failed error message

The place to discuss Mac OS X version of MakeMKV
Post Reply
Message
Author
codefast
Posts: 9
Joined: Wed Sep 11, 2013 5:03 pm

Getting generic backup failed error message

#1 Post by codefast » Thu Oct 29, 2015 4:47 pm

Hi,

I have an external blu-ray player that I've used a lot to backup my BluRay discs. Recently, I've started getting errors when trying to rip any disc, even ones that have been successfully ripped before.

This is the error code I'm getting:
003332:0000 Saved BD+ dump file as /Users/username/.MakeMKV/dump_Dr_No_5053CB7AB22D4EE6.tgz
003328:0000 BD+ code processed, got 1 FUT(s) for 1 clip(s)
005085:0000 Loaded content hash table, will verify integrity of M2TS files.
001003:0020 DEBUG: Code 2 at *8}QvFmV@(0m^'m2 ]39dAL:29393447
001003:0020 DEBUG: Code 0 at xi*]rgmXa`EFp##6y\l:29396621
001003:0020 DEBUG: Code 0 at 9(x(.-2A?|Cs;F[whtg7:121265108
Can someone explain what these codes mean? The drive is plugged directly into a computer, has an external power source, and seems to be working fine otherwise.

Thanks

codefast
Posts: 9
Joined: Wed Sep 11, 2013 5:03 pm

Re: Getting generic backup failed error message

#2 Post by codefast » Tue Nov 03, 2015 5:24 pm

I just tried a different Blu-Ray drive and got the same error codes. :(

Anyone have any suggestions here? I don't want to have to use the original disks to watch these movies. Much happier when I can stream them off of my NAS.

Code: Select all

DEBUG: Code 0 at %[\j3SR=c9%4X}~F:121262624

Code: Select all

BD+ code processed, got 1 FUT(s) for 1 clip(s)
Loaded content hash table, will verify integrity of M2TS files.
DEBUG: Code 2 at *8}QvFmV@(0m^'m2 ]39dAL:29393447
DEBUG: Code 0 at xi*]rgmXa`EFp##6y\l:29396621
DEBUG: Code 0 at 9(x(.-2A?|Cs;F[whtg7:121265108
Backup failed

codefast
Posts: 9
Joined: Wed Sep 11, 2013 5:03 pm

Re: Getting generic backup failed error message

#3 Post by codefast » Tue Nov 03, 2015 5:53 pm

Wow, I'm an idiot. This mac was a replacement for another mac with a different drive setup. Turns out the output path didn't exist on the new drive because it symlinked to a nonexistent external drive. :oops:

Sorry for the noise...

Woodstock
Posts: 10323
Joined: Sun Jul 24, 2011 11:21 pm

Re: Getting generic backup failed error message

#4 Post by Woodstock » Tue Nov 03, 2015 9:44 pm

Sending data to non-existent places? No, I've NEVER (cough, cough) done THAT! :)

Note: Media servers do not necessarily reboot after a power failure, so you can find yourself 12TB low on disk space at times.... :roll:

Post Reply