search

Atmosphere-NX / Atmosphere

Atmosphère is a work-in-progress customized firmware for the Nintendo Switch.
GNU General Public License v2.0
14.42k stars 1.22k forks source link

Fatal error #1124

Closed Klepuna420 closed 4 years ago

Klepuna420 commented 4 years ago

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?

Additional context?

no

SciresM commented 4 years ago

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

Klepuna420 commented 4 years ago

report_0000000008cf90de.zip This should be the report. Sorry

kenman345 commented 4 years ago

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 commented 4 years ago

I have formatted sd card to fat32 and then problem solve

kenman345 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 notifications@github.com 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 https://github.com/Atmosphere-NX/Atmosphere/issues/1124#issuecomment-674351392, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACTYZV26BNFWSKKHQ4L6WEDSAYLH5ANCNFSM4P5EKPCA .

kenman345 commented 4 years ago

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 notifications@github.com 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 https://github.com/Atmosphere-NX/Atmosphere/issues/1124#issuecomment-674351392, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACTYZV26BNFWSKKHQ4L6WEDSAYLH5ANCNFSM4P5EKPCA .

Klepuna420 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

ther0n commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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.

sdiniz-truelogic commented 4 years ago

@SciresM, thanks for clarifying. I’ll reproduce the error again and create a new issue with the fatal error reports. Will update here once I have the issue created.

spencerdiniz commented 4 years ago

Can someone point me to documentation on how to retrieve the fatal error reports? I was able to reproduce the fatal error, but I don't see any reports in the SD card (looked for *.bin files). Are the reports saved to Switch internal memory?

SciresM commented 4 years ago

they're saved to sd:/atmosphere/fatal_errors -- the screen that displays on fatal error gives you the file path.

spencerdiniz commented 4 years ago

@SciresM, thanks again. My SD doesn't contain that directory. And the fatal error screen doesn't display a path. Instead, it prints out "Failed to save report to the SD card!".

SciresM commented 4 years ago

Does the atmosphere dir itself have the archive bit set? If not, try creating a "fatal_errors" dir and make sure it doesn't have the archive bit set. This sounds like SD fuckery to me.

spencerdiniz commented 4 years ago

Does the atmosphere dir itself have the archive bit set? If not, try creating a "fatal_errors" dir and make sure it doesn't have the archive bit set. This sounds like SD fuckery to me.

@SciresM, first of all, thanks for your attention and time. There's definitely some fuckery...

I created the "fatal_errors" directory manually, reproduced the error and crash report was successfully saved. But, when I tried to read the SD card in Windows to retrieve the report, I got a message that the SD was not formatted, and was not able to retrieve the report.

So, I started the whole thing again (determined to get the report). I formatted the SD to exFAT, but this time, I manually created the "fatal_errors" directory from the get-go (since I knew I would need it). However, when I tried to reproduce the error, everything worked and Atmosphere booted.

So I tried a 3rd time (with the original steps). Formatted, copied Atmosphere to SD and injected fusee-primary.bin... and... No fatal error!

I can no longer reproduce the fatal error. I going to try again... and update here if I can manage to reproduce again.

Best regards, Spencer

Klepuna420 commented 4 years ago

I downgraded now to 13.0.0 and it works. Its something with the new atmosphere version I think. I think I'm just waiting for a new atmosphere version. I also tried to "Fix Archive Bit" But still got this crash. Is there anything else that I should try?

LunaerD commented 4 years ago

Is there any new info about this fatal error ? i just updated Hekate and atmosphere to the latest release but i'm experiencing the exact same crash.

spencerdiniz commented 4 years ago

I was not longer able to reproduce this error with a difference SD card. My previous SD card seemed to be broken.

On 28 Aug 2020, at 11:22, LunaerD notifications@github.com wrote:

Is there any new info about this fatal error ? i just updated Hekate and atmosphere to the latest release but i'm experiencing the exact same crash.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Atmosphere-NX/Atmosphere/issues/1124#issuecomment-682607664, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTKGGTQVFAPHE5ATXNMM3LSC64SFANCNFSM4P5EKPCA.

Klepuna420 commented 4 years ago

Hello,

I tried to install the new 14.2 version but still got the same error. Still have to use atmosphere 13.0... Here is the report if it can help in any way:

report_000000000911b1ee.zip

iMaxed0ut commented 4 years ago

Same issue when updating to 0.14.4 and Hekate 5.3.3. Panic error causing a crash in the boot process.

These are the bin reports from the times its crashed. Bin Reports.zip

it was on folder 0100000000000042. I found that deleting the directory it was referencing allowed me to successfully boot into CFW.

KamiSquadX commented 2 years ago

has this issue been resolved yet??

ghost commented 2 years ago

has this issue been resolved yet??

@nwhiteman42 Please don't try to provide support for issues you don't understand.

@Leonelvader This is actually the same issue as #1124, #1145, #1173 and was fixed recently. The next Atmosphere release won't trigger the problem.

Zip containing fixed erpt-sysmodule (extract to your SD card, replacing the 0.14.4 release one) here.

KamiSquadX commented 2 years ago

thanks for the swift reply. so i downloaded the atmosphere-0.14.4-erpt-fix so this drag and drop should fix it? trying it now

ghost commented 2 years ago

thanks for the swift reply. so i downloaded the atmosphere-0.14.4-erpt-fix so this drag and drop should fix it? trying it now

Considering how said issue has been closed, I think using the latest Atmosphere will completely fix this for you. I quoted Scires to say "yes, it's been fixed." Apparently if the issue still persists, it could be your SD or reader being messed up, according to some comment I found.

Also, this is an old issue--please don't comment on those! If you want support go to the ReSwitched Discord, if you've found a bug, please open up a new report~

KamiSquadX commented 2 years ago

I got this error from using the latest atmosphere. never had this happen before. it happened after repeatedly trying to load retroarch etc, atmosphere crashes, restart using payload injector dongle, repeat all this like 3 times, until trying to launch cfw gives the black screen fatal error message. Where is the discord link cause i still need help with this. report_0000000001566de7.zip

ghost commented 2 years ago

I got this error from using the latest atmosphere. never had this happen before. it happened after repeatedly trying to load retroarch etc, atmosphere crashes, restart using payload injector dongle, repeat all this like 3 times, until trying to launch cfw gives the black screen fatal error message. Where is the discord link cause i still need help with this. report_0000000001566de7.zip

https://discord.gg/ZdqEhed good luck!!