Fatal error

[Klepuna420]

#813 # What's the issue you encountered?
Fatal error.

How can the issue be reproduced?

-Injekt Payload (hekate_ctcaer_5.3.2)
-Launch CFW (emuMMC)

Crash Report

report_0000000008cf90de
Title ID 010000000000002b

System Firmware Version

10.1.0

Environment?

• What bootloader (fusèe, hekate, etc) was Atmosphère launched by:
  I use hakate

• Official release or unofficial build:
  Official release version hekate_ctcaer_5.3.2_Nyx_0.9.3

• Do you have additional kips or sysmodules you're loading:
  no

• Homebrew software installed:
  no

Additional context?

no

[SciresM]

You did not upload the crash report. Help cannot be provided until you upload it.

[Klepuna420]

report_0000000008cf90de.zip
This should be the report. Sorry

[kenman345]

im also having this issue. same error code. let me know if i can help provide information that helps figure this out as well

[carcaschoi]

I have formatted sd card to fat32 and then problem solve

[kenman345]

I have tried that without success
I've tried it multiple times, from scratch following different guides each time that all basically had me do the same things just some used sdsetup for setting my sd card up and others had me download the individual things they wanted me to use. I would really love for this to be figured out.
report_08dfb229.zip

[Klepuna420]

I also tried to format to fat32 but same error. I tried many different tutorials but always the same. My switch was hacked before this error. I formated my sd card and saved all the things on my desktop. Put them back on my sd card and this happened.

[monaa9]

Ive been having the same issue. Formatted my sd card to fat32 and even tried the same thing with a different one but the problem persists.

[kenman345]

So I still have this issue with my 512gb microSD card but I found a 64gb microSD I had spare and set it up identically. Besides being unable to put the Nintendo folder on it, i followed the exact same steps and it worked on the first try and every time since then. But if I try my 512gb card it simply gives me this error. I wonder if it has something to do with that.

…

On Sat, Aug 15, 2020 at 1:19 AM monaa9 ***@***.***> wrote: Ive been having the same issue. Formatted my sd card to fat32 and even tried the same thing with a different one but the problem persists. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1124 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACTYZV26BNFWSKKHQ4L6WEDSAYLH5ANCNFSM4P5EKPCA> .

[kenman345]

When I get a chance I shall take a look and see if the extra pin is used for the 512 that SDXC defines but is not usually on or needed for 64gb cards. On Sat, Aug 15, 2020 at 3:18 PM Kenneth Salomon <kensalomon@gmail.com> wrote:

…

So I still have this issue with my 512gb microSD card but I found a 64gb microSD I had spare and set it up identically. Besides being unable to put the Nintendo folder on it, i followed the exact same steps and it worked on the first try and every time since then. But if I try my 512gb card it simply gives me this error. I wonder if it has something to do with that. On Sat, Aug 15, 2020 at 1:19 AM monaa9 ***@***.***> wrote: > > > Ive been having the same issue. Formatted my sd card to fat32 and even > tried the same thing with a different one but the problem persists. > > > > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#1124 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACTYZV26BNFWSKKHQ4L6WEDSAYLH5ANCNFSM4P5EKPCA> > . > > >

[Klepuna420]

Im using a 64 gb sd card and getting this error. I don't know if my sd card is the problem or any file is missing or something like this. Is there any tutorial which I should follow to be 100% sure that the problem is not me, doing anything wrong?

[spencerdiniz]

I'm having the same issue. I tried 3 different SD cards (64GB and 128GB), with different formats (exFAT and FAT32).
This is happening on versions 0.14.0 and 0.14.1.

Eventually, I went back to 0.13.0, which is working fine.
I'll wait for another 0.14.x release before trying again.

For now, I'm running 0.13.0 on a 64GB exFAT micro SD without any issues.

[kenman345]

hm...I'll try a downgrade of Atmosphere then too on my larger card since that would be more convenient

[ther0n]

My SD card is formatted as exFAT and I was having a similar issue.

I fixed the issue by running Hekate then choosing the Tools tab. At the bottom tap on "Arch bit - RCM - Touch -Partitions", then click "Fix Archive Bit"

After doing that I was able to boot up successfully.

[spencerdiniz]

My SD card is formatted as exFAT and I was having a similar issue.

I fixed the issue by running Hekate then choosing the Tools tab. At the bottom tap on "Arch bit - RCM - Touch -Partitions", then click "Fix Archive Bit"

After doing that I was able to boot up successfully.

I tried "Fix Archive Bit", but it didn't work for.
Only downgrading to 0.13.0 worked.

[SciresM]

fwiw @ "same issue" people, I really doubt it.

All errors in atmosphere show up to the user as "fatal error occurred", the particulars only really matter to me and are saved in the report binaries.

The issue the OP of this issue has is that his erpt save is somehow causing the save:/ mountpoint to be invalid when reading an attachment -- this is bizarre and I have literally no idea what would cause it, having triple checked the code since I received his reports. There's an obvious fix -- "delete the erpt save", which I would expect would work, but I haven't suggested it yet because I want to understand why their save causes the problem.

Everyone else almost certainly has different issues that you think are the same because of how the error display mechanism works but are really different. @spencerdiniz should create a new issue/upload his fatal error reports.