Hardware SD Card is corrupted every 4-5 months

  • Thread starter Thread starter erc207
  • Start date Start date
  • Views Views 882
  • Replies Replies 7

erc207

Member
Newcomer
Joined
Dec 13, 2018
Messages
10
Reaction score
1
Trophies
0
Age
46
XP
190
Country
United States
I have three 512 GB Samsung EVO micro SD cards, all genuine. One bought on Amazon, and two from Best Buy.

I've never used the ExFAT file system on them, only FAT32.

All three of the cards have suffered from data corruption within 4-5 months of starting to use them. It's happened multiple times to a couple of them. I've run various scans of the cards, and they don't turn up any hardware defects or issues. I'll recover my save games, start fresh, get everything set up again, and it'll run fine for another few months.

Is data corruption just an expected side effect? I know SDCards aren't really well suited for running an OS and software. I'm kind of hoping it's just a flaky reader because that's an easy fix, but most of the posts I've seen about them say they just suddenly stopped reading cards altogether which hasn't been my experience.
 
I have three 512 GB Samsung EVO micro SD cards, all genuine. One bought on Amazon, and two from Best Buy.

I've never used the ExFAT file system on them, only FAT32.

All three of the cards have suffered from data corruption within 4-5 months of starting to use them. It's happened multiple times to a couple of them. I've run various scans of the cards, and they don't turn up any hardware defects or issues. I'll recover my save games, start fresh, get everything set up again, and it'll run fine for another few months.

Is data corruption just an expected side effect? I know SDCards aren't really well suited for running an OS and software. I'm kind of hoping it's just a flaky reader because that's an easy fix, but most of the posts I've seen about them say they just suddenly stopped reading cards altogether which hasn't been my experience.
It should not be happening regularly, that indicates some kind of deeper issue. Have you had a lot of crashes on the Switch? Crashes/power loss can lead to corruption but normally it wouldn't corrupt the entire file system, you can get unlucky though.
 
Have you ever h2testw the cards ?
Yes, no issues.

It should not be happening regularly, that indicates some kind of deeper issue. Have you had a lot of crashes on the Switch? Crashes/power loss can lead to corruption but normally it wouldn't corrupt the entire file system, you can get unlucky though.
No crashes at all, until I do get one, and then I've got a corrupted emunand.

I'm thinking about replacing the SD Card reader in the switch, but I'm kind of doubting that's the problem.
 
Yes, no issues.


No crashes at all, until I do get one, and then I've got a corrupted emunand.

I'm thinking about replacing the SD Card reader in the switch, but I'm kind of doubting that's the problem.

I will recommend going with Sandisk if Samsung is giving you problem, I have no issue with Sandisk cards. Consider you got three of the same cards, problem is probably the specific model of card.
 
  • Like
Reactions: _iggyman_
I have had the same issue 3 times. Also Samsung SD cards - 256 GB. I have 2 of them and it happened on both. When it happens I can't boot EmuMMC. The error is different, sometimes I get an error number, sometimes I just get a black screen after the ATM/Nintendo logo.
It is only my raw EmuMMC that is affected. The Fat32 partition is fine each time. Last time it happened I decided to try with a filebased EmuMMC. Since then I haven't seen the issue. Whether that solved it or it just didn't happen yet I don't know.
 
I have had the same issue 3 times. Also Samsung SD cards - 256 GB. I have 2 of them and it happened on both. When it happens I can't boot EmuMMC. The error is different, sometimes I get an error number, sometimes I just get a black screen after the ATM/Nintendo logo.
It is only my raw EmuMMC that is affected. The Fat32 partition is fine each time. Last time it happened I decided to try with a filebased EmuMMC. Since then I haven't seen the issue. Whether that solved it or it just didn't happen yet I don't know.

I have always used raw emummc as well, but for whatever reason I also chose a file-based emummc this time around. I'm not sure if there are any pros/cons of one vs the other, but I suppose time will tell if this works out.

I will also pick up a Sandisk card, and maybe a new card reader module which is cheap and easy to replace.

Of course, at the end, I'll have changed so many things I won't know what the problem was to begin with.
 
The reason the card corrupts is most likely the crash, fat32 is very susceptible to file system corruption if any write is suddenly interrupted for any reason. That area is also one of the biggest upgrades that exFAT has over fat32, as they've added a whole bunch of guardrails for that specific scenario.

I would suggest making sure everything is updated on your end so you have all bugfixes that are available, I wouldn't bother changing the card module unless it also starts happening on the SanDisk card, too.
Also, there are minor timing differences between Samsung and SanDisk cards, and Nintendo has partnered with SanDisk so chances are compatibility is a bit higher with SanDisk than with Samsung. That can get exacerbated when you have hacked software running as that may not fully respect standard timing requirements.
 
  • Like
Reactions: erc207

Site & Scene News

Popular threads in this forum