Hardware Is this 128gb sd card good for 3ds?

[Tackskull]

I found on amazon a good offer for this SD card https://www.amazon.it/Samsung-MB-MC...ie=UTF8&qid=1546553623&sr=8-1&keywords=sd+128

With my previous sd cards (I was using 2 Kingston sd card of 64gb each) and I had a lot of problem with corrupted games and save data, I want a good SD card, that once I put a lot of games inside I can play for ever without problems. If this sd card is not goo, can you tell me which one is good?

Thanks

 

[Darukeru]

Yes Samsung microsd cards are good. I have a Silicon Power 128GB, this brand isn't as recognized as Kingston or Samsung but I haven't had any problem with it in this two last years.

 

[TurdPooCharger]

30€ converts to US $34. That price isn't so good because the cheapest going rates are $20 for a 128 GB and ~$50 for a 256 GB over this side of the Atlantic Ocean. Someone more familiar with European market will have to advise you if that's a good price.

That card model and brand is fine. However, you should Full Write + Verify Test your new card with H2testw before putting stuff on it and using it because of counterfeits.

 

[Tackskull]

30€ converts to US $34. That price isn't so good because the cheapest going rates are $20 for a 128 GB and ~$50 for a 256 GB over this side of the Atlantic Ocean. Someone more familiar with European market will have to advise you if that's a good price.

That card model and brand is fine. However, you should Full Write + Verify Test your new card with H2testw before putting stuff on it and using it because of counterfeits.

I am european so no problem with the price. Yes I know that program thanks.
Do you know if there is a way to make a kingston sd card working well during the time or is that just a bad card?

 

[TurdPooCharger]

I am european so no problem with the price. Yes I know that program thanks.
Do you know if there is a way to make a kingston sd card working well during the time or is that just a bad card?

Did you test the Kingston with H2testw? Kingston is a real brand but is highly targeted by counterfeiters. A flash memory that has failed in H2testw cannot be fixed nor entrusted with your data. You wait until the new card arrives.

 

[Tackskull]

Did you test the Kingston with H2testw? Kingston is a real brand but is highly targeted by counterfeiters. A flash memory that has failed in H2testw cannot be fixed nor entrusted with your data. You wait until the new card arrives.

I did it some times ago but after a bit the sd gave me problem again, yes I'll just wait for this sd and that's it. Thanks you guys

 

[TheToaster]

Should I use 64KB clusters for a 128 GB card? Doesn't it take up more space for files, and if so, how much space will I be sacrificing if I use 64 KB?

 

[Hayato213]

Should I use 64KB clusters for a 128 GB card? Doesn't it take up more space for files, and if so, how much space will I be sacrificing if I use 64 KB?

32kb cluster is enough

 

[TheToaster]

32kb cluster is enough

Yes, I know it's enough, but what are the benefits/drawbacks to using 64KB versus 32KB in a 128 GB card?

 

[Hayato213]

Yes, I know it's enough, but what are the benefits/drawbacks to using 64KB versus 32KB in a 128 GB card?

Not really same effect, 3ds games are under 4GB so using 64kb cluster wouldn't benefit much as compare to PS4 games that are like 40-50GB, using the right cluster would show you the correct size of available storage when you plug it into a computer.

 

[TurdPooCharger]

Yes, I know it's enough, but what are the benefits/drawbacks to using 64KB versus 32KB in a 128 GB card?

Testing 64 KB Allocation Size

If you want to know if your 128 GB card will work with 64 KB cluster size, install several GBA VC games and check for graphical glitch. Also check if full 10 themes shuffle works.

I have long suspected the reason why certain 128 GB cards do not work with the larger cluster size is because some are short in usable capacity at the make or break it limit (ie, slightly less than 118-119 GB).

Edit - You definitely should full Write + Verify test it in H2tesw before using it.

 

[TheToaster]

Testing 64 KB Allocation Size

If you want to know if your 128 GB card will work with 64 KB cluster size, install several GBA VC games and check for graphical glitch. Also check if full 10 themes shuffle works.

I have long suspected the reason why certain 128 GB cards do not work with the larger cluster size is because some are short in usable capacity at the make or break it limit (ie, slightly less than 118-119 GB).

Edit - You definitely should full Write + Verify test it in H2tesw before using it.

Thank you. What if I use a higher class (UHS class 3 maybe, or V30) microSD card and then format to 32KB? Will that be as fast as a regular Class 10 128 GB microSD on 64KB?

 

[lone_wolf323]

Thank you. What if I use a higher class (UHS class 3 maybe, or V30) microSD card and then format to 32KB? Will that be as fast as a regular Class 10 128 GB microSD on 64KB?

Nope, that doesnt affect it. It runs only aswell as what the 3ds console hardware is capable of. not the full extent of the card

 

[ghjfdtg]

The problem is the FAT driver code. It was not meant/tested with >32 GB. Slowdowns will occur because it has more work to do. Similar to how GodMode9 will take ages to start sometimes. The GBA VC glitches are an unintended result of this slow access time.

I would try shrinking the partition on a 128+ GB card and see if it still causes problems with different cluster sizes just for science.

 

[TheToaster]

Nope, that doesnt affect it. It runs only aswell as what the 3ds console hardware is capable of. not the full extent of the card

Testing 64 KB Allocation Size

If you want to know if your 128 GB card will work with 64 KB cluster size, install several GBA VC games and check for graphical glitch. Also check if full 10 themes shuffle works.

I have long suspected the reason why certain 128 GB cards do not work with the larger cluster size is because some are short in usable capacity at the make or break it limit (ie, slightly less than 118-119 GB).

Edit - You definitely should full Write + Verify test it in H2tesw before using it.

Thank you. I have decided to use 32KB for now and switch over to 64KB if it's too slow. I do have a few questions though.

1.) If I were to switch over to 64KB, does that mean I have to copy/paste my entire SD card to my desktop, reformat with 64KB, then copy/paste back again? Or is there a way I can do it without formatting again?

2.) Are there any other optimizations or anything I can do to the SD card so that i can get the most loading/boot speed out of it?

 

[TurdPooCharger]

1.) If I were to switch over to 64KB, does that mean I have to copy/paste my entire SD card to my desktop, reformat with 64KB, then copy/paste back again? Or is there a way I can do it without formatting again?

You have to copy & paste stuff onto a computer and reformat it into FAT32 + 64 KB cluster size if you plan to change the cluster size later.

Whatever you do, DO NOT USE the pro version of MiniTool Partition Wizard's cluster size changer or anything like it.
From my own previous testings, changing the cluster size without a proper reformat can cause persistent boot issues, in-game lag, and slow loading.
This is made worse as quick and full reformats by themselves do not fix the misbehaviors.

The only way I was able to consistently fix an affected card is by triple reformatting with each one of these: SD Memory Card Formatter, guiformat, and MiniTool Partition Wizard's (free edition) using the latter delete partitions, rebuild MBR, and reformat.

2.) Are there any other optimizations or anything I can do to the SD card so that i can get the most loading/boot speed out of it?

No. If you have a card that meets or exceeds Class 10 speed, have it check with H2testw to be free of hardware problems, formatted in FAT32 and with an appropriate + compatible cluster size (recommended: 32 KB / optional : 64 KB if card is at minimum 128 GB AND determined to be glitch/bug free in GBA VC & full theme shuffles), that's about as good as you can do for your setup.

Oh btw, to answer your previous question, the 3DS systems cannot take advantage of UHS-II and UHS-III cards because their SD slot readers weren't designed with the extra pins in mind. They are essentially bottle necked, like how a USB 3.0 flashdrive with backwards compatible will underclock read & write speeds for older Windows 7 era computers with USB 2.0 ports.

 

[TheToaster]

You have to copy & paste stuff onto a computer and reformat it into FAT32 + 64 KB cluster size if you plan to change the cluster size later.

Whatever you do, DO NOT USE the pro version of MiniTool Partition Wizard's cluster size changer or anything like it.
From my own previous testings, changing the cluster size without a proper reformat can cause persistent boot issues, in-game lag, and slow loading.
This is made worse as quick and full reformats by themselves do not fix the misbehaviors.

The only way I was able to consistently fix an affected card is by triple reformatting with each one of these: SD Memory Card Formatter, guiformat, and MiniTool Partition Wizard's (free edition) using the latter delete partitions, rebuild MBR, and reformat.


No. If you have a card that meets or exceeds Class 10 speed, have it check with H2testw to be free of hardware problems, formatted in FAT32 and with an appropriate + compatible cluster size (recommended: 32 KB / optional : 64 KB if card is at minimum 128 GB AND determined to be glitch/bug free in GBA VC & full theme shuffles), that's about as good as you can do for your setup.

Oh btw, to answer your previous question, the 3DS systems cannot take advantage of UHS-II and UHS-III cards because their SD slot readers weren't designed with the extra pins in mind. They are essentially bottle necked, like how a USB 3.0 flashdrive with backwards compatible will underclock read & write speeds for older Windows 7 era computers with USB 2.0 ports.

When you say test if its glitch/bug free in GBA VC games or do 10 theme shuffles (I assume that's a thing in CHMM2, I guess. I dont really use custom themes that often), do I do that AFTER I have formatted the 128GB card to 64KB? Or is it something that will happen to it even on 32KB?

 

[TurdPooCharger]

When you say test if its glitch/bug free in GBA VC games or do 10 theme shuffles (I assume that's a thing in CHMM2, I guess. I dont really use custom themes that often), do I do that AFTER I have formatted the 128GB card to 64KB? Or is it something that will happen to it even on 32KB?

CHMM2, Themely, and Anemone3DS ← defacto homebrew theme manager.

What you do with the 128 GB card in question once you get it:

1. Reformat in FAT32 + 64 KB cluster size.
2. Full Write + Verify Test the empty card with H2testw; to protect yourself from receiving a counterfeit.
3. Delete the *.h2w test files if it passes without issue.
4. Build a temporary or bare-bone test custom firmware setup. Don't use your main setup yet until after testing is concluded. You can use this kit here.
   • You hold off copying your main setup to save time getting your results.
5. Install several GBA VC and launch them. See if you get this image glitch like this.
6. Shuffle 10 themes with homebrew theme manager of choice: check with ON/OFF power sessions.
   • You may need to debug by deleting the theme extdata and trying again. See Section VI from this post.

If either GBA VC or themes do not react well with 64 KB cluster size, you reformat and drop it down to 32 KB.

 

[TurdPooCharger]

The problem is the FAT driver code. It was not meant/tested with >32 GB. Slowdowns will occur because it has more work to do. Similar to how GodMode9 will take ages to start sometimes. The GBA VC glitches are an unintended result of this slow access time.

I would try shrinking the partition on a 128+ GB card and see if it still causes problems with different cluster sizes just for science.

I tried your idea of partitioning my 128 GB card. It was resized to 60 59 GB, which is what a typical 64 GB card is. You can see the GBA VC graphical bug is present when used with 64 KB cluster size. I'll increase the partition and report back what that stability limit might be.

​

Edit - Findings and Observations
Sorry guys, but the results I'm getting are inconclusive or not repeatable. Without good control variables, these are what I could come up with.

I could not find an exact hard number. Increasing the partition by 1 GB, 0.2 GB, and 0.1 GB increments starting from 59 GB, I could not consistently reproduce the bug after the 63 GB mark. However, this is not to say a card with a partition bigger than 63 GB will not be affected. I later dropped back to 59 GB partition and had lower than expected occurrences of the bug.

If I use MiniTool Partition Wizard to delete the partitions, rebuild MBR, make a new partition at a size known to glitch (ie, at 59 GB), reformat in FAT32 + 64 KB cluster, and reinstall a new copy of Metroid Fusion with FBI, the bug tends to happen but not always.

If I install Metroid Fusion, experience the graphical glitch like the above, copy everything from the card, and paste it back overwriting the original files, the bug tends to go away. At some point, the bug stops appearing.

There seems to be weak correlation with the bug likely to happen if there's a longer than usual loading times after launching the game.

Perhaps installing Metroid Fusion over and over again temporarily fixes the bug. I tried adding The Legend of Zelda - The Minish Cap into the mix but with no luck of it showing again.

 

[ghjfdtg]

Yeah, it doesn't like 64 KB clusters. What about 32 KB with shrinked partition on bigger cards like 256 GB? If this still has issues i take that back (huge partitions are still slow but this glitch probably has other reasons in that case). Next guess is power consumption. Huge capacity cards often have beefier controllers in them + the NAND flash may take more aswell.

 

[TurdPooCharger]

Yeah, it doesn't like 64 KB clusters. What about 32 KB with shrinked partition on bigger cards like 256 GB? If this still has issues i take that back (huge partitions are still slow but this glitch probably has other reasons in that case). Next guess is power consumption. Huge capacity cards often have beefier controllers in them + the NAND flash may take more aswell.

I don't know if you caught my above edited post.

Anyway, I triple reformatted my PNY 128 GB micro SDXC with Memory Card Formatter, guiformat, and MiniTool Partition Wizard. My n3DSXL battery was also removed and reinserted. The card was reformatted with a 3.73 GB partition in FAT32 + 32 KB cluster size.

Metroid and Zelda GBA VC were freshly reinstalled with FBI. While I couldn't reproduce the bug with this setup, I notice loading times from launch decreased from 18 s (59 GB partition, FAT32 + 64 KB cluster size) to around 11 s (3.73 GB partition, FAT32 + 32 KB).

 

[ghjfdtg]

So basically what i thought. High loading time (caused by big partitions) --> GBA VC glitches. It really seems to be an unintended side result. Officially only up to 32 GB is supported. I guess they never tried higher than that.

 

[TurdPooCharger]

So basically what i thought. High loading time (caused by big partitions) --> GBA VC glitches. It really seems to be an unintended side result. Officially only up to 32 GB is supported. I guess they never tried higher than that.

Except that doesn't necessarily seem to be case for all large partitions. If you reformat an entire 128 GB card (in my case, usable capacity is 120.25 GB) in FAT32 + 2 KB cluster size (yes, that number is two), GBA VC games can take up to 5 minutes to load without the glitch appearing.

I once repeated the FAT32 + 2KB cluster size experiment on my 256 GB card using a micro-standard cable adapter and that took an even way longer time to load. I can't recall what its time was clocked at, but it was definitely more than 15 minutes and less than 30.