Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange things going on with RipGuard #135

Open
Feathered-Serpent opened this issue Jun 10, 2022 · 0 comments
Open

Strange things going on with RipGuard #135

Feathered-Serpent opened this issue Jun 10, 2022 · 0 comments

Comments

@Feathered-Serpent
Copy link

Version
32 bit, AnsiBuild, 20220606T232558

Describe the bug
As expected with RipGuard, there are a "few" areas, where the bad sectors are placed. New for me is, that there could be so many, like here:

Error sectors range: LBA 457554 to 457583 = 30 -> Filled with 0x00
Error sectors range: LBA 458946 to 459244 = 299 -> Filled with 0x00
Error sectors range: LBA 469147 to 469769 = 623 -> Filled with 0x00
Error sectors range: LBA 471642 to 472535 = 894 -> Filled with 0x00
Error sectors range: LBA 474714 to 475403 = 690 -> Filled with 0x00
Error sectors range: LBA 475404 to 475499 = 96 -> Filled with 0x00
Error sectors range: LBA 477959 to 478137 = 179 -> Filled with 0x00
Error sectors range: LBA 481673 to 481868 = 196 -> Filled with 0x00
Error sectors range: LBA 481869 to 482366 = 498 -> Filled with 0x00
Error sectors range: LBA 486038 to 486413 = 376 -> Filled with 0x00
Error sectors range: LBA 489688 to 490387 = 700 -> Filled with 0x00
Error sectors range: LBA 492841 to 493437 = 597 -> Filled with 0x00
Error sectors range: LBA 498960 to 499346 = 387 -> Filled with 0x00
Error sectors range: LBA 502913 to 502970 = 58 -> Filled with 0x00
Error sectors range: LBA 506002 to 507596 = 1595 -> Filled with 0x00
Error sectors range: LBA 511248 to 511438 = 191 -> Filled with 0x00
Error sectors range: LBA 511439 to 512229 = 791 -> Filled with 0x00
Error sectors range: LBA 512230 to 512614 = 385 -> Filled with 0x00
Error sectors range: LBA 515157 to 515637 = 481 -> Filled with 0x00
Error sectors range: LBA 515638 to 515937 = 300 -> Filled with 0x00
Error sectors range: LBA 519808 to 520903 = 1096 -> Filled with 0x00
Error sectors range: LBA 521387 to 521484 = 98 -> Filled with 0x00
Error sectors range: LBA 521485 to 522579 = 1095 -> Filled with 0x00
Error sectors range: LBA 523613 to 523712 = 100 -> Filled with 0x00
Error sectors range: LBA 524858 to 525052 = 195 -> Filled with 0x00
Error sectors range: LBA 525080 to 525577 = 498 -> Filled with 0x00
Error sectors range: LBA 525713 to 526275 = 563 -> Filled with 0x00
Error sectors range: LBA 528369 to 528554 = 186 -> Filled with 0x00
Error sectors range: LBA 534994 to 535287 = 294 -> Filled with 0x00
Error sectors range: LBA 537604 to 538603 = 1000 -> Filled with 0x00
Error sectors range: LBA 538604 to 539075 = 472 -> Filled with 0x00
Error sectors range: LBA 539076 to 539259 = 184 -> Filled with 0x00
Error sectors range: LBA 539260 to 539834 = 575 -> Filled with 0x00
Error sectors range: LBA 539891 to 540174 = 284 -> Filled with 0x00
Error sectors range: LBA 541557 to 541852 = 296 -> Filled with 0x00
Error sectors range: LBA 546059 to 546151 = 93 -> Filled with 0x00

and in the end the most strange thing:

Error sectors range: LBA 554395 to 458975 = -95419 -> Filled with 0x00

It went over all areas again with "Read back a sector" without telling about the former errors. Unfortunately the ISO is not usable in the end, as in MakeMKV can only 'see' three titles on the whole disc, where on the original disc it shows 33 titles (and obviously also ignores the errorneous sectors, at least upon title scanning).

How could it not find the error e.g. at 546151 when it travelled back from 554395?

Disc title
Scrubs (German edition aka "Scrubs - Die Anfänger", Season 7, Disc 2)

Log file
DIC Logs.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant