13xforever / ps3-disc-dumper

A handy utility to make decrypted PS3 disc dumps
MIT License
439 stars 29 forks source link

When in the decryption and copying files section the process can hang indefinitely #6

Closed fac7orx closed 4 years ago

fac7orx commented 4 years ago

When decrypting a game such a killzone 3 the "decrypting and copying files..." process hangs at around 10.88GB transferred, and cannot recover. The transfer then continues to bounce around this number and never go beyond it.

Using a compatible drive on the list: WH14NS40

https://rpcs3.net/quickstart

13xforever commented 4 years ago

Attach log. But usually this means your disc is scratched, so it has to retry bad sectors multiple times, which is super slow.

fac7orx commented 4 years ago

Hi you can get the log file here:

https://www.mediafire.com/file/7t5rt9gzbn897vn/2019-09-06.log/file

There may be remnants of me attempting another run. I did do another run and so far it is on 12.13GB. So it got passed the 10.88GB area this time around for some reason. However, I am fearful it may hang at some other spot. Will report back if it does.

On Fri, Sep 6, 2019 at 6:28 PM Ilya notifications@github.com wrote:

Attach log. But usually this means your disc is scratched, so it has to retry bad sectors multiple times, which is super slow.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/13xforever/ps3-disc-dumper/issues/6?email_source=notifications&email_token=ANDU6G7NF32SYKKWJUFOO33QILKQTA5CNFSM4IUNUWU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6EG4NA#issuecomment-529034804, or mute the thread https://github.com/notifications/unsubscribe-auth/ANDU6GYWTMA3LNVG5USBESLQILKQTANCNFSM4IUNUWUQ .

fac7orx commented 4 years ago

Hi,

It seems to have hanged again at 24.38GB this time. Here is the new log file:

http://www.mediafire.com/file/5i4w6pysgyvwawp/2019-09-06%25282%2529.log/file

Update:

Tried for a 3rd time. So far 2x in a row it hung on 24.38GB. I am going to try another gmae. This one was used. The other one I purchased is brand new.

13xforever commented 4 years ago

why mediafire lol, just zip it and attach here directly. you're trying to dump a damaged 2-layer disc, of course it will have problem on the first layer, and then on the second at the same spot

fac7orx commented 4 years ago

Killzone only log: 2019-09-06(2).log

Log with a bunch of messing around trying mgs and killzone: log zipped.zip

The other log was too big to host. It encompassed a lot of crashes. However, I compressed it as suggested and was able to post it here directly.

I would agree with you with the disc is used and perhaps has some scratches. If possible please check logs to make sure, but I will take your advice and get a disc cleaner for the other game. Hopefully, I don't have to repurchase. I did experience the hang on the mgs legacy collection. It may be in that 45mb log. However, I got mgs to successfully transfer at this time after retrying it. Killzone 3 disc is still causing me some issues. Thank you for the help so far.

Would it be possible to maybe add a warning if it gets stuck in this hanging state where it is constantly retrying? Maybe like "Check disc for scratches? after it tries a few times and then either a continue or cancel button? This could help the user troubleshoot instead of messaging right away?

I managed to extract some other games ok at this time after messing around a bit.

Did not work:

Killzone 3: Perhaps is scratched too much

Worked:

Uncharted 1 Uncharted 2 Metal gear solid legacy collection

Thank you again and the tool is pretty good I appreciate the time you have taken to make it :).

Update:

I managed to get the Killzone 3 disc dumped successfully. Here is the log. I am not sure what exactly I did differently: 2019-09-07.log

So, I got all my games transferred ok. However, There are logs above for reference that had failures/ hanged, if anything stands out to you or may be the disc was just scratched. Thank you again.

13xforever commented 4 years ago

you did nothing differently, it's just OS/drive cached the problematic sectors, so it took less time to go over them