On Sat, Apr 17, 2021 at 08:33:59PM +0100, Antonio Carlini via cctalk wrote: > On 17/04/2021 19:35, Al Kossow via cctalk wrote: > > On 4/17/21 11:30 AM, Antonio Carlini via cctalk wrote: > > > > > So far I've just tried using dd to recover the data but perhaps I > > > should try to find something that won't give up when the OS reports > > > an unreadable sector. Anyone have any suggestions? > > > > > > ddrescue > > > > I guess I should've remembered that one, thanks! > > > So has this just lost ~3KiB? "pct rescued" suggests that it did quite well. > Does "bad areas" mean one bad sector (2048 bytes)? > > > $ ddrescue -r5 -v /dev/sr1 JUL89DIST.iso JUL89DIST.map > GNU ddrescue 1.23 > About to copy 623247 kBytes from '/dev/sr1' to 'JUL89DIST.iso' > Starting positions: infile = 0 B, outfile = 0 B > Copy block size: 128 sectors Initial skip size: 128 sectors > Sector size: 512 Bytes > > Press Ctrl-C to interrupt > ipos: 623246 kB, non-trimmed: 0 B, current rate: 0 B/s > opos: 623246 kB, non-scraped: 0 B, average rate: 1303 kB/s > non-tried: 0 B, bad-sector: 4096 B, error rate: 73 B/s > rescued: 623243 kB, bad areas: 1, run time: 7m 58s > pct rescued: 99.99%, read errors: 49, remaining time: n/a > time since last successful read: 5m 11s > Finished > > This is what ls sees (I renamed the ISO to match what it actually is): > > > -rw-rw-r-- 1 antonioc antonioc 623243264 Apr 17 20:14 > CDROM-AG-MN36E-RE-1989-07-VMS-CONDIST.iso > > (That happens to be exactly the same result as dd).
That looks pretty good already! Can you try with "-b 2048 -d" for direct disc access and maybe once more with "-R" for reverse? Cheers, Malte -- Malte Dehling <mdehling at gmail.com>
