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

eMMC partition mount failure at startup #172

Open
SirDawson opened this issue Nov 3, 2024 · 19 comments
Open

eMMC partition mount failure at startup #172

SirDawson opened this issue Nov 3, 2024 · 19 comments
Labels
bug Something isn't working good first issue Good for newcomers question Further information is requested

Comments

@SirDawson
Copy link

An error occurs upon opening nxdumptool in either applet mode or title takeover. Here is what it says:
"An error occurred while initializing resources."
"bisStorageMountPartition: Failed to mount SAFE partition via FatFs! (13)."

  1. Access the hbmenu through either title takeover or applet mode.
  2. Open nxdumptool.
  3. See error.
  • Horizon OS (Switch FW) version: 19.0.1
  • CFW: Atmosphère
  • CFW version: 1.8.0
  • Atmosphère launch method (if applicable): Hekate
  • nxdumptool version: 2.0.0
  • Homebrew launch method: both title override and applet
  • Source storage used with the application (if applicable): N/A
  • SD card specs: Lexar 512 GB, FAT32 partition

Screenshots
2024110302114500-E5B04B40CFD924420DF6142200E473B4

Logfile
nxdt_rw_poc.log

@SirDawson SirDawson added the bug Something isn't working label Nov 3, 2024
@DarkMatterCore
Copy link
Owner

Hi there. Thanks for reporting this issue.

This is related to the new eMMC FAT partition browser that I recently implemented into nxdumptool-rewrite.

FatFs documentation states the following information about error code 13:

FR_NO_FILESYSTEM
Valid FAT volume could not be found in the drive. One of the following possibilities is suspected.
The FAT volume on the drive is collapsed.
Wrong lower layer implementation.
Wrong VolToPart[] settings. (FF_MULTI_PARTITION = 1)

I'm positive it couldn't possibly be a fault within my DiskIO implementation (which is just a call to fsFsStorageRead with some extra code to handle sector -> offset conversion), and FF_MULTI_PARTITION is intentionally disabled in the codebase... so I'd say your sysMMC's SAFE partition doesn't seem to hold a valid FAT partition for some reason. I don't think it's specifically a compatibility issue with HOS 19.0.0+.

If possible, please get in touch with me via Discord (my DMs are always open) or e-mail, whichever you prefer. I'd like to take a better look at this.

@DarkMatterCore DarkMatterCore added good first issue Good for newcomers question Further information is requested labels Nov 3, 2024
@SonicAtari
Copy link

Hi was this issue ever worked out I'm currently having the same issue.

@Whovian9369
Copy link
Collaborator

I am unable reproduce this using the current available build (commit ca61151) on my personal Erista console using Title Takeover.

@DarkMatterCore
Copy link
Owner

@SonicAtari The user who reported this issue hasn't gotten in touch with me, so I haven't been able to debug it any further. I'm still interested in knowing why it fails, though.

@SavXL
Copy link

SavXL commented Nov 4, 2024

Hi there. Thanks for reporting this issue.

This is related to the new eMMC FAT partition browser that I recently implemented into nxdumptool-rewrite.

FatFs documentation states the following information about error code 13:

FR_NO_FILESYSTEM
Valid FAT volume could not be found in the drive. One of the following possibilities is suspected.
The FAT volume on the drive is collapsed.
Wrong lower layer implementation.
Wrong VolToPart[] settings. (FF_MULTI_PARTITION = 1)

I'm positive it couldn't possibly be a fault within my DiskIO implementation (which is just a call to fsFsStorageRead with some extra code to handle sector -> offset conversion), and FF_MULTI_PARTITION is intentionally disabled in the codebase... so I'd say your sysMMC's SAFE partition doesn't seem to hold a valid FAT partition for some reason. I don't think it's specifically a compatibility issue with HOS 19.0.0+.

If possible, please get in touch with me via Discord (my DMs are always open) or e-mail, whichever you prefer. I'd like to take a better look at this.

Apologies. I made this bug report from my college account. This is the account I actually wanted to make the report from. I was unfortunately very busy yesterday, but I've sent you a friend request on Discord and will get with you later today.

@SonicAtari
Copy link

I also sent a request I'm under awasomeman

@Ry3yr
Copy link

Ry3yr commented Nov 9, 2024

2024111000140800-DB1426D1DFD034027CECDE9C2DD914B8
I get a "keys not compatible error" as of 19.

I redumped title n prod keys but it persists.
Shame, I wanted to extract some game models.
Maybe I need to find my V1 Switch 😺

@DarkMatterCore
Copy link
Owner

I get a "keys not compatible error" as of 19.

I redumped title n prod keys but it persists. Shame, I wanted to extract some game models. Maybe I need to find my V1 Switch 😺

Unrelated issue. Find a newer Lockpick_RCM build and use it to redump your keys.

@Ry3yr
Copy link

Ry3yr commented Nov 9, 2024

I see.
Never thought I'd have to update that too.
(Wonder why that would change)

Thx !

Edit:
I re-dumped (with the newest nxdumper rewrite.nro)
prod.keys
titles.keys
partialaes.keys

and redownloaded the latest nxdumptool.
The error persitsts.

I even ran the partialaes.keys through the PartialAesKeyCrack.zip (successfully),
but don't really see how that will solve the mariko_kek issue (bundle them as file ?

I'm confused.

Repository owner deleted a comment from lividhen Nov 11, 2024
@Whovian9369
Copy link
Collaborator

We cannot tell people where or how to find newer versions of Lockpick_RCM.

@lividhen
Copy link

Whoopsie! My bad!

@krubihon
Copy link

I encountered the same issues as OP

launched through title override

512 Samsung SD Card

@DarkMatterCore
Copy link
Owner

@krubihon Please provide more details about your setup. Did you use any specific tools to modify your eMMC partitions in any way or capacity?

@krubihon
Copy link

Nothing I know of, It uses the latest update and atmosphere as well as sig patches. Basically the same as OP

@DarkMatterCore DarkMatterCore changed the title Seemingly Incompatible with 19.0.1 eMMC partition mount failure at startup Dec 11, 2024
@impeeza
Copy link

impeeza commented Dec 19, 2024

If worth for something, I am Using FW 19.0.1 Atmosphère 1.8.0 and the release from https://github.com/DarkMatterCore/nxdumptool/releases/tag/rewrite-prerelease running the program on full title Homebrew loader mode I get:
image
I am attaching my log file
nxdt_rw_poc.zip

Amusingly running rewrite-prerelease on Homebrew Loader ON Applet mode, a text version is displayed and you can dump NSP without problem:

image

image

Also, on my setup, the version 1.1.5 starts ok, and you can select the cartridge or the installed titles but when you are about to dump a title the error retrieveProcessMemory: unable to retrieve debug handle for process with Title ID 0100000000000000! is shown:
image

@DarkMatterCore
Copy link
Owner

@impeeza you're describing a different problem altogether. Are you using a custom forwarder / Atmosphère build / HBMenu build?

v1.1.5 is deprecated and no longer kept up to date.

@impeeza
Copy link

impeeza commented Dec 19, 2024

yes I know about 1.1.5 I mentioned just for adding context.

I am using traditional Title override (Pressing R while loading a game) and for applet mode using the album applet.

By the way I am using NoGC setting on Hekate, that can be a factor.

@DarkMatterCore
Copy link
Owner

@impeeza just asking, because custom forwarders and/or loaders are known to trigger this kind of problems.

Having NoGC enabled should not be an issue, since that's not related to the svc debug calls that are failing in this case (according to your logfile).

Other than that, I have no idea what could be happening. It sounds like a loader issue.

@impeeza
Copy link

impeeza commented Dec 19, 2024

I just upgraded manually my hbmenu.nro and now the full title override mode works fine, you were right the problem was the Hombrew Menu and Homebrew Loader. I don't know why do not got upgraded when I upgraded Atmosphère.

image

image

Thanks mate. sorry for spamming the issue thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers question Further information is requested
Projects
None yet
Development

No branches or pull requests

9 participants