Hardware Okay can we actually talk about corruption?

[Deleted User]

I have two Samsung Evo Select cards, 256 GB exfat for games (and checkpoint) the other one
128 GB fat32 for homebrew. Never had issues so far. Mainly using sxos.

Then again i´m mostly transferring files the hard way - turn off the switch, get sd card out...

I will stick to fat32 in the future, using split files has no
disadvantages and sxos usb support can use exfat drives.

 

[The Real Jdbye]

If you are having this problem as well please check out the poll and select the options that apply to your case. We can all attempt to isolate commonalities.

Threads involving title corruption are frequently dismissed as "your SD card is dead buy a new one." I use five different SD cards. At least two of them had never been used before, were tested as working, formatted to FAT32, and the problem immediately presented itself. Back-ups were placed using nut server and USB. I have also tried installing via network. It seems to be completely random.

Most of the time I will find that out of a dozen, two or three didn't install correctly. Most recently I did a large batch of about twenty, and nearly all of them were corrupt. It happens with every SD card I own.

Are there logs or something so we could possibly take a look at what exactly is happening?
Is that not something the Switch is capable of, or just something nobody has implemented yet?
If not, is it at least possible to generate some error code representing where the failure took place?

For those of you who have never had this issue, how many SD cards have you used? Were any of them exfat? What CFW are you using, and what method did you use to install it?

If you are trying to install XCI converts, or custom scene DLC unlockers, they will fail to install as corrupted, unless you enable installing of unsigned code in the settings (not recommended though as it makes you vulnerable to malicious NSPs)

You can check your games with NX Game Info on PC. It should say which NSPs are converts, and which ones pass signature checks. Converts will always fail signature checks but other NSPs should not, however a lot of scene release DLC will fail signature checks anyway because they are custom made DLC unlockers and not actually dumped from eShop.

It probably has nothing to do with corruption.

 

[0x3000027E]

What I am not understanding is if Nin's drivers are so faulty, why they don't they fix them?

I am also looking for a more reasonable set of statistics that contains a summary of Switch users who have not hacked their Switch, have not run homebrew, etc. to see how those numbers compare to users who have hacked the switch. Fact of the matter is that if you are running homebrew, you are not using the system as was intended/designed, so unusual behavior can be expected from time to time.

Using 2 exFat cards, daily, for 16 months now w/ CFW without corruption, btw, (not that it matters).

 

[The Real Jdbye]

What I am not understanding is if Nin's drivers are so faulty, why they don't they fix them?

I am also looking for a more reasonable set of statistics that contains a summary of Switch users who have not hacked their Switch, have not run homebrew, etc. to see how those numbers compare to users who have hacked the switch. Fact of the matter is that if you are running homebrew, you are not using the system as was intended/designed, so unusual behavior can be expected from time to time.

Using 2 exFat cards, daily, for 16 months now w/ CFW without corruption, btw, (not that it matters).

It's not limited to hacked consoles, it will happen from a crash, no matter what causes the crash. It just so happens that crashes are more frequent in homebrew.

When Pokemon Sword/Shield came out, there was a bug that would crash the system, and if it happened during autosaving, it would corrupt your entire card if on exFAT. If on FAT32, at most it would corrupt your save data for the game. Regardless of whether the console is hacked or not.
Unsure if that bug has been fixed by now. But anyway, SciresM did some research into it and did a writeup:

https://mobile.twitter.com/sciresm/status/1195341413484883969

It's just not a frequent occurrence for full system crashes to occur, so Nintendo probably aren't too worried about it.

 

[JFizDaWiz]

I had this issue with corrupted titles on a FAT32 after switching from Kosmos to vanilla Atmos, then i gave up and re-created emuMMC and it was working.

 

[ZachyCatGames]

What I am not understanding is if Nin's drivers are so faulty, why they don't they fix them?

It would require a decent amount of effort and they have zero reasons to do so.

 

[Treskatae]

If you are trying to install XCI converts, or custom scene DLC unlockers, they will fail to install as corrupted, unless you enable installing of unsigned code in the settings (not recommended though as it makes you vulnerable to malicious NSPs)

You can check your games with NX Game Info on PC. It should say which NSPs are converts, and which ones pass signature checks. Converts will always fail signature checks but other NSPs should not, however a lot of scene release DLC will fail signature checks anyway because they are custom made DLC unlockers and not actually dumped from eShop.

It probably has nothing to do with corruption.

That would make sense. I had not checked to see if they were converts. I've just completely reformatted another SD this weekend and set it up from scratch. Installing with Awoo from SD I ran into an "Invalid NCA magic" error, which I believe is unique to XCI files and so would seem to very much support your suggestion. I'll run a check using that software to double check, but this seems the most likely cause.

 

[The Real Jdbye]

That would make sense. I had not checked to see if they were converts. I've just completely reformatted another SD this weekend and set it up from scratch. Installing with Awoo from SD I ran into an "Invalid NCA magic" error, which I believe is unique to XCI files and so would seem to very much support your suggestion. I'll run a check using that software to double check, but this seems the most likely cause.

In addition to checking every game I download with NX Game Info, I also run them through nspverify which checks every byte of data, as corruption and bad dumps can happen. Just gives me some peace of mind knowing any weird issues won't be caused by a corrupted or bad dump.

 

[Treskatae]

Alright I'm editing the OP confirming this to be the issue in my case.