Homebrew Discussion Precautions of using Exfat and my experience

Did you encounter a Similar issue


  • Total voters
    33
  • Poll closed .

LegndaryThemeCreator

Active Member
OP
Newcomer
Joined
Dec 11, 2016
Messages
30
Trophies
0
Age
24
XP
122
Country
My Switch Setup before incident
SD Card is a Sandisk 200GB SDXC
Using Hekate 4.2 Bootloader, Atmosphere 0.7.5 Komos 3.0.0
(PS i am a Noob With The Switch Homebrew Scene)

I was using Homebrew like normal and I was going through all the apps that were included with SD-files or Kosmos as it is now, and opened the Kosmos updater, not thinking about the implications of its warning when it opened, i proceeded with running it, little did i know it would update the files before you could exit the program, and so it updated to 3.0.1

No big deal or so i thought.

So i went and turned off my switch to take my SD card out and put it into my PC until i couldn't access my SD card in file explorer. So i put in back into my switch and booted CFW like normal, everything was fine, I could open Homebrew launcher and load apps, but to make sure i could access my files i opened a ftp server app and connected it over WiFi through my PC, Just to be safe i copied all my files across so i wouldn't have to download everything again especially all the Nintendo apps i installed.

So why am i telling you this? You ask, Well...

After 6 hours of transferring my files across, around 32GB, (Aussie Internet if you're wondering why it took so long) i put my SD card back into my switch and booted OFW (Original Firmware AKA Horizon) and decided to format my Sd card using the setting on the switch incase something was wrong after using Homebrew, formatted it and so far it worked. I powered down my switch and took my SD card out and put in back into my PC, but the problem persisted, worried i had messed up my SD Card i decided to do some google searching. No help on Nintendo.com btw, Searched Gbatemp for similar issues/threads but no luck. so i decided to shift my attention to find fixes for SD Card Corruptions and solutions from different forums and sites. After using CMD solutions and Disk-part commands i ended up with a SD card that had no format system of any kind which eventually lead me to "Test-disk" application. After some guides of using the program and many failed attempts i learned the Entire Partition Table, Boot loader/Sector as well as backup Partition's were completely blank, and so i ended up with a blank unusable SD Card (Using the Applications and CMD took over 4 Hours to figure out and learn from guides on the web) after awhile i gave up trying to fix it. I took my SD card out of my PC and decided to use another one (8GB) and it loaded when file explorer opened

Which Gave me the idea!!!

if the 8GB loaded, it wasn't Windows with the issue, but rather the 200GB SD Card, regaining hope of fixing it i took the 8GB out and put the 200GB back into my PC and then...i got a new dialogue box to format my SD Card and so i did and...whola it worked again excited with relief i wanted to share this experience and to notify anybody of a similar experience in the future on how to fix this circumstance.

What i Learned today.
1. Check and read all info of the Homebrew app You're using and the precautions they can have, not acknowledging the precautions can cause serious consequences.
2. Don't do what i did, it took me 10 hours to get through this...
and 3. there is always a solution

I just also want to say that the Homebrew developer's if they are reading this, i do have respect for the time and energyYou people give towards this community and to make Homebrew as simple as possible and i don't blame anyone but me for my carelessness.

Also whether this is a bug or not i just want to make it clear that this circumstance could be a "one-of" scenario.
 

dankasfuk

New Member
Newbie
Joined
Sep 13, 2009
Messages
2
Trophies
0
XP
42
Country
United States
The sun hasn't died and destroyed our entire solar system... *yet ;D

I don't understand why this continues to be a topic of discussion. Using exfat with any type of homebrew or CFW absolutely WILL cause filesystem corruption, it's just a matter of time. If you are willing to accept the risk that at some point, your SD card will need to be reformatted and all data lost, then by all means keep using exfat. Otherwise, just back it up now and convert it to FAT32. At this point there is no reason not to since all the tools exists to get around the filesize limitations.
 
  • Like
Reactions: bad361

bad361

Well-Known Member
Member
Joined
Jun 18, 2018
Messages
1,168
Trophies
0
Location
Moscow
XP
2,447
Country
Russia
Strangely enough, couple of days ago i had a strange accident with my 64gb exfat sd too. Been using exfat without any major problems since i got swithch, even tho every second person here tells to use fat32 for good. Well, as for the accident, i was on latest reinx on 6.0 with lots of nsp's, homebrews and retroarch roms on my sd.. I was testing the new half life port version and got several hard crashes (known issue) and as always i just did a reset, went back on reinx, everything seemed fine, all the nsp's on home screen were there and i left the switch as it was. After a while i tried to launch a game to play but it failed with an error and told me to check its contents. I entered the data management on my switch and to my surprise all of my nsp's that were installed on the sd were 0 mb. Then i checked sd on my pc and realized that the whole Nintendo folder was completely empty along with some other random folders on my sd. My sd card was full as before, but there were no files on it. Fortunately enough reinx folder wasn't affected and i still could lauch cfw and most of the homebrews, but all of my nsps and some RA folders were gone. Only after that accident i ultimately decided to go for fat32 since now you can simply install large nsp's via tinfoil usb/network methods. So, yeah.. Lesson learned the hard way i guess.
 

blawar

Developer
Developer
Joined
Nov 21, 2016
Messages
1,708
Trophies
1
Age
40
XP
4,311
Country
United States
shouldn't nintendo's official forum be full of "help! my exfat card corrupted" threads then?

It would, if people could run nintendo certified homebrew :) Nintendo very rarely writes to the SD card, and they dont have users pressing the home button force closing their app's causing corruption.
 

naddel81

Well-Known Member
Member
Joined
Dec 14, 2009
Messages
2,549
Trophies
1
XP
3,787
Country
United States
It would, if people could run nintendo certified homebrew :) Nintendo very rarely writes to the SD card, and they dont have users pressing the home button force closing their app's causing corruption.

so how to be save when using checkpoint etc.? not using the home button?!
 

Dichotomy754

Well-Known Member
Member
Joined
Nov 11, 2018
Messages
154
Trophies
0
Age
33
XP
671
Country
United States
Yeah, I've had a fair bit of issues running exfat. It's forced me to keep backups though, so I think I'll keep it. It's not like I'm at risk of loosing my games or saves, just loosing time.
 

Sonansune

Well-Known Member
Member
Joined
Jul 2, 2015
Messages
3,734
Trophies
1
XP
2,142
Country
Canada
exfat file system corruption eats up spaces.
I experienced it days ago. switched to fat32.

exfat with 2gb available into fat32 with 15gb available. who knows where the heck those 13gb goes on exfat...
 

crimpshrine

Well-Known Member
Member
Joined
Jun 18, 2014
Messages
594
Trophies
0
XP
1,169
Country
United States
It would, if people could run nintendo certified homebrew :) Nintendo very rarely writes to the SD card, and they dont have users pressing the home button force closing their app's causing corruption.

So does this mean that if you don't use any homebrew and your only using XCI's or installed NSP's on exfat, that your not likely going to see an issue? I am confused, is there a risk in hitting the home button when running an XCI or installed NSP? Or in this case, the issue would be hitting the home button when either was saving (a save game) I really like the added benefit of access speed with exfat and don't use homebrew apps outside of CFW via SXOS or others.
 

blawar

Developer
Developer
Joined
Nov 21, 2016
Messages
1,708
Trophies
1
Age
40
XP
4,311
Country
United States
So does this mean that if you don't use any homebrew and your only using XCI's or installed NSP's on exfat, that your not likely going to see an issue? I am confused, is there a risk in hitting the home button when running an XCI or installed NSP? Or in this case, the issue would be hitting the home button when either was saving (a save game) I really like the added benefit of access speed with exfat and don't use homebrew apps outside of CFW via SXOS or others.

You are correct, there is no/minimal risk of corruption if you run zero homebrew. XCI's and NSP's do not write to the SD card, they write to the NAND which is fat32. Using home button is fine with XCI's and NSP's.
 

maxx488

Well-Known Member
Member
Joined
Jun 15, 2018
Messages
219
Trophies
0
Age
27
XP
897
Country
Argentina
You know when windows says It cant read it and needs to be formatted all you have to do is run a chkdsk and it'll work again right??...
 

blawar

Developer
Developer
Joined
Nov 21, 2016
Messages
1,708
Trophies
1
Age
40
XP
4,311
Country
United States
You know when windows says It cant read it and needs to be formatted all you have to do is run a chkdsk and it'll work again right??...

Window's solution is to just delete corrupted files and return the SD to a "normal" state, however there was still data loss. This has the effect of basically uninstalling some games, removing CFW / boot.dat, etc. Then you have to try to figure out what got removed. Its faster to just convert to fat32 and just not worry about it.
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Xdqwerty @ Xdqwerty: @BakerMan, I have a piano keyboard but I never use it