Doesn't boot as of rpcs3-v0.0.5-7624-cfe07098_win64. Get 'sys_fs_stat' failed with 0x8001003a : CELL_ENOTMOUNTED, “/dev_bdvd”
Tested in:
i7 6700k
gtx1060 6gb
16gb ddr3
PPU LLVM.log.gz
PPU Interpreter fast.log.gz
PPU Interpreter precise.log.gz
leskal
All 21 comments
Github is not for support questions, use discord or forums instead.
You have broken config. Please close this issue and ask in an appropriate channel if you still can't fix it.
13xforever
on 2 Jan 2019
Github is not for support questions, use discord or forums instead.
You have broken config. Please close this issue and ask in an appropriate channel if you still can't fix it.
I have test clean install of rpcs3 and the problem exists. So it's not config prob
leskal
on 2 Jan 2019
@leskal That's not what he meant. If by "as of rpcs3-v0.0.5-7624-cfe07098_win64" you meant that the game with the same configuration set was working on the previous build but is now broken with that, this report is completely fine.
But if not, and you just tried said build and the game didn't work, this doesn't belong here, as it's not a regression. For support, the project's Discord server is to be used, not this issue tracker.
dio-gh
on 2 Jan 2019
@leskal That's not what he meant. If by "as of rpcs3-v0.0.5-7624-cfe07098_win64" you meant that the game with the same configuration set was working on the previous build but is now broken with that, this report is completely fine.
But if not, and you just tried said build and the game didn't work, this doesn't belong here, as it's not a regression. For support, the project's Discord server is to be used, not this issue tracker.
I have test with the two previous builds and was the same prob. I just mension the build number i take the logs
leskal
on 2 Jan 2019
I see that you have also commented in the appropriate topic in the forums, thank you for that.
Nevertheless, this report is still incomplete currently, as it misses which build actually broke it (if it is truly broken). If you could determine that and add it to the original post, the issue could remain open and devs could attempt fixing it much easier.
The easiest way to do this is by bisecting builds. Pick a build from long before and test if it works with that. If not, go for an even older one. When you found one that the game does work with, you then test it with the build in the middle between the last non-working and the working build you just found. Rinse & repeat, till you find the build that broke it. With this, you can minimize the time looking for the build that regressed it.
Before you attempt this, I'd definitely recommend testing the validity of your dump with an IRD checker via a tool you can find here. If you are not sure what that means, or you are unsure whether this is truly a regression, ask for help at the project's Discord in #help.
dio-gh
on 2 Jan 2019
I see that you have also commented in the appropriate topic in the forums, thank you for that.
Nevertheless, this report is still incomplete currently, as it misses which build actually broke it (if it is truly broken). If you could determine that and add it to the original post, the issue could remain open and devs could attempt fixing it much easier.
The easiest way to do this is by bisecting builds. Pick a build from long before and test if it works with that. If not, go for an even older one. When you found one that the game does work with, you then test it with the build in the middle between the last non-working and the working build you just found. Rinse & repeat, till you find the build that broke it. With this, you can minimize the time looking for the build that regressed it.
Before you attempt this, I'd definitely recommend testing the validity of your dump with an IRD checker via a tool you can find here. If you are not sure what that means, or you are unsure whether this is truly a regression, ask for help at the project's Discord in #help.
I will try to find the last build that works with this game and i will report here
leskal
on 2 Jan 2019
Thanks!
dio-gh
on 2 Jan 2019
Thanks!
Last working build with this game is 0.0.5-7549:
With 0.0.5-7550:
leskal
on 2 Jan 2019
Awesome, thank you for your report! Apparently, PR #5370 was the one that broke it.
dio-gh
on 2 Jan 2019
This game boots for me. Check your files with PS3-ISO-Rebuilder.
NicknineTheEagle
on 2 Jan 2019
This game boots for me. Check your files with PS3-ISO-Rebuilder.
I 'll check it and report back!
leskal
on 2 Jan 2019
Post a screenshot of the results when you're done.
NicknineTheEagle
on 2 Jan 2019
Post a screenshot of the results when you're done.
Ok, if helps, I will also provide folder tree
leskal
on 2 Jan 2019
Post a screenshot of the results when you're done.
Ok, if helps, I will also provide folder tree
leskal
on 3 Jan 2019
As you can see, your copy of the game is corrupted, which is why the code breaks, probably. I'm sure the code could handle this a bit more gracefully though.
dio-gh
on 3 Jan 2019
His dump has additional PS3_DISC.SFB inside PS3_GAME dir for whatever reason which screws up the checks. PIC0.PNG is modified and PS3UPDATE.PUP are missing. Kind of looks like a pirated copy.
NicknineTheEagle
on 3 Jan 2019
Remove /ps3_game/ps3_disc.sfb.
Dump is corrupted, yes. Please do not jump to conclusions tho.
13xforever
on 3 Jan 2019
@NicknineTheEagle I peeked through the changes of the PR quickly, why does that screw up the checks? It's just that the PIC0.png is corrupted. I'm fairly sure if he fixed that, the game would work.
dio-gh
on 3 Jan 2019
Removing this: /ps3_game/ps3_disc.sfb fixes the boot. But how a modified picture and a missing ps3 firmware prevents from booting the game?
leskal
on 3 Jan 2019
It's the extra ps3_disc.sfb, the code looks for this file to determine if the app is a disc game, this file being in the wrong location screws things up.
NicknineTheEagle
on 3 Jan 2019
I peeked harder and it makes sense now :)
Closable.
dio-gh
on 3 Jan 2019
Related issues
AniLeo
·
3Comments
elad335
·
3Comments
AniLeo
·
3Comments
Xcedf
·
3Comments
XeClutch
·
3Comments
Most helpful comment
Last working build with this game is 0.0.5-7549:
With 0.0.5-7550:
