CaMiX
Member
- Joined
- Jul 18, 2010
- Messages
- 22
- Likes
- 4
AnyDVD is good for bad sector based protections and other protection stuff etc., but I'm not sure about normal unreadable sectors,
based on bad fabrication or scratches causing this.
Still AnyDVD is needed later after the ddrescue process to decrypt the image, for playing or by reripping
The problem is, those programs can't resume if interrupted, if you want to procede the copy/rescue process in another optical drive, which might be able to read out further problematic blocks, which the other drive couldn't.
Also you've to click through error messages about bad sector readings all the time etc.
takes more time etc.
So normal ripping programs are not specialized for Blu-rays and DVDs and CDs on normal unreadable sectors, (not based on a copy protection).
Though "ddrescue" (gddrescue) is bad for Blu-ray discs which ask for bus encryption (only in a capable drive),
and ddrescue is not recommended to be used on bad sectors discs (based on a bad sector copy protection)
But the AnyDVD status window in his logfile does show, "bad sector protection not found".
Also hisc Star Wars discs do not ask for bus encryption so it doesn't matter with his discs that his LG BH16NS40 supports it, the mods/dev explained to me.
So ddrescue could be a first option in this case.
https://en.wikipedia.org/wiki/Ddrescue
ddrescue is included in Knoppix Live Linux System (DVD)
In Debian and Ubuntu the package is called "gddrescue", the cosole program name though is called "ddrescue", not to confuse with "dd_rescue" which is another program.
What he could try to do first is:
Booting Knoppix from DVD or USB flash drive. Then mount his NTFS partition. Run ddrescue from his desired location on his NTSC volume.
Open console/bash/shell/terminal -window
1st step with ddrescue: ddrescue will first rescue only the easily recoverable (relatively quickly readable) data:
ddrescue --idirect --sector-size=2048 -n -v -v /dev/srX ddrescue_Star_Wars_Attack_Of_The_Clones.iso mapfile_ddrescue_Star_Wars_Attack_Of_The_Clones.log
--idirect: Direct access from the input device (source), not using internal RAM/kernel buffers
but this option can also be left out, not so important, but doesn't harm.
All my drives (LG BH16NS40, Pioneer BDR-205, LiteON iHOS-104) seem to provide raw access.
--sector-size=2048: for the Block size, on DVD and Blu-ray UDF block/sector size is 2048 Bytes
-n: skip the scraping phase: not easily and not quickly reable sectors are "ignored" and jumped across until next readable sectors reached. Avoids spending a lot of time trying to rescue the most difficult parts of the file/(or disc).
-v: verbose: printing more precise info how it's progressing. WHen more specified it's more detailed.
/dev/srX : Blu-ray source drive
ddrescue_Star_Wars_Attack_Of_The_Clones.iso : image_file_to save rescued data to
mapfile_ddrescue_Star_Wars_Attack_Of_The_Clones.log : name for map file ,(only) all failed blocks are marked and listed. Needed for proceeding from last point.
So the mapfile name is important, so that ddrescue can resume further, you don't need to restart the process from the beginning, especially useful if it takes several hours
You can "abort" the process with STRG+C (CTRL+C) at any time and procede when the mapping logfile is specified.
You can take any map file name and image file name, but should not rename them for further rescue attempts!!
2nd step, leaving out "-n" option, for trimming and scraping retrying the failed bad blocks.
ddrescue --idirect --sector-size=2048 -v -v --retry-passes=2 /dev/srX ddrescue_Star_Wars_Attack_Of_The_Clones.iso mapfile_ddrescue_Star_Wars_Attack_Of_The_Clones.log
The failed blocks are filled with zeros in the ddrescue iso-image file and listed in the log file. If more sectors gets rescued, their entries are deleted within the map logfile, so it does not need to retry those, because already recovered.
The LG BH16NS40 lists the correct sector count on Blu-ray discs, though my LiteON iHOS104 doesn't!
Here the "--complete-only" option is helpful.
If you had such drive, the iso could get corrupt if you left out the option "--complete-only"
I had to rerun ddrescue deleting the old iso because I forgot, that my Liteon iHOS104 reports higher sector count than actaully is. The iso was 2 Gigabytes bigger suddenly when changing the disc into the Liteon to procede further to recover more sectors.
Additionally with --complete-only option the iso with the same size is in my Pioneer
and BH16NS40.
It's always useful to have one or two backups of the different ddrescue steps.
ddrescue --idirect --sector-size=2048 -v -v --complete-only --retry-passes=2 /dev/srX ddrescue_Star_Wars_Attack_Of_The_Clones.iso mapfile_ddrescue_Star_Wars_Attack_Of_The_Clones.log
https://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html
3rd step rerun the process: with two addional parameters: --retrim --try-again
ddrescue --idirect --sector-size=2048 -v -v --complete-only --retrim --try-again --retry-passes=2 /dev/srX ddrescue_Star_Wars_Attack_Of_The_Clones.iso mapfile_ddrescue_Star_Wars_Attack_Of_The_Clones.log
Addiobaly if you have a spare disc, even if dfective, but mayba at other sectors, or the bad sectors are problematic but more easily to recover, you can rerun with:
ddrescue --idirect --sector-size=2048 -v -v --complete-only --retrim --try-again --retry-passes=2 /dev/srX ddrescue_Star_Wars_Attack_Of_The_Clones.iso mapfile_ddrescue_Star_Wars_Attack_Of_The_Clones.log
in another optical drive, didn't he buy a spare drive? Same model? And maybe he has a friend with snother Blu-ray drive model, he can borrow, where he can resume further the process!
And maybe he has spare discs with identical data, it's a further chance to recover rest failing blocks.
After 100 percent is recovered he can mount the ddrescue iso in Virtual Clone Drive and decrypt it normally with AnyDVD.
It's also working with not fully rescued images, but some of the data then is wrong (those filled with zeros from the missing failed blocks)
Handbrake transcoder might make problems perhaps if not fully recovered, (but maybe I'm wrong)
How do you know what the sector count is for each drive? Separate command?