Homebrew Official [Release] EmuNAND9 - Open Source EmuNAND Formatter & Manager

[sp3off]

Hello everyone. First, thank you @dok3 for your emunand tool. I have a question: since i have a 32gb SD card, i want to switch to 64k clusters but i know i can't without touching to my files. So, i want to know how we can save our data in our emunand, then format then reinject. Have you got a n idea ? Thank you in advance.

 

[hofotureas]

i wonder too, how to switch to 64k cluster.
does this work with no emunand:

backup to sysNAND.bin
copy sd content to external backup solution
format with noemunand settings
copy sd content back
restore sysNAND.bin

i wonder because im used to make backups as a whole image, including partion tables and all that jazz. restoring would mean to restore non 64k clusters. but since emunand9 does not make full bit wise backup, it should only restore "files", right?

 

[Serphirot]

i wonder too, how to switch to 64k cluster.
does this work with no emunand:

backup to sysNAND.bin
copy sd content to external backup solution
format with noemunand settings
copy sd content back
restore sysNAND.bin

i wonder because im used to make backups as a whole image, including partion tables and all that jazz. restoring would mean to restore non 64k clusters. but since emunand9 does not make full bit wise backup, it should only restore "files", right?

As far as I know you can only format the emunand with it to have 64k cluster size. And if you don´t use emunand you don´t have to wory about it because having no emunand is faster than loading the emunand from the sd card anyways.

 

[hofotureas]

thanks for the reply!
i used "the guide" https://github.com/Plailect/Guide/wiki to setup my new 3ds.

u are right. since i have sysnand, system is loaded from internal.

but that made me wonder.

my sd card is formatted in 32k. just to format it with normal formating tools to 64k should still increase loading time of installed games, right?

 

[Serphirot]

thanks for the reply!
i used "the guide" https://github.com/Plailect/Guide/wiki to setup my new 3ds.

u are right. since i have sysnand, system is loaded from internal.

but that made me wonder.

my sd card is formatted in 32k. just to format it with normal formating tools to 64k should still increase loading time of installed games, right?

Yes it should it still has to be formated in a format that the 3ds can read so dont use ext4 or f2fs. These can´t be loaded by a 3ds as far as i know.

 

[Darktalon]

i wonder too, how to switch to 64k cluster.
does this work with no emunand:

backup to sysNAND.bin
copy sd content to external backup solution
format with noemunand settings
copy sd content back
restore sysNAND.bin

i wonder because im used to make backups as a whole image, including partion tables and all that jazz. restoring would mean to restore non 64k clusters. but since emunand9 does not make full bit wise backup, it should only restore "files", right?

I did it myself last night. You don't even have to restore your sysNAND because thats on your internal 3DS memory not the SD Card. So just backup the sd contents. Format with noemunand settings. Copy SD Content back. Profit.

 

[Selim873]

EDIT: Nevermind, I'm dumb. lol

 

[Conn0r]

@d0k3 Would large SD cards + 64k clusters decrease boot time of A9LH?

 

[fr3quency]

@d0k3 Would large SD cards + 64k clusters decrease boot time of A9LH?

Large cards increase boot time. 64GB is fine but 128GB increases the boot time (no matter the cluster size) from what I have seen from other users. 64kb cluster size is the way to go, hands down. Just buy a 64GB SDcard and you will be good to go! I boot Luma3DS in 8-9s exactly(64GB microSD + 64KB cluster size)

Sent from my Nexus 5

 

[C02]

Quick question. I am getting a new sd card 64gb and can use this to format my sd card then transfer the files on my pc?

 

[d0k3]

Quick question. I am getting a new sd card 64gb and can use this to format my sd card then transfer the files on my cpu?

Yup, you can. Even if you don't want to use EmuNAND. And you meant from your PC, right?

 

[neighborhoodqt]

Hi, I'm following this guide and am currently on part 2, step 22.
When I try to backup sysNAND to file, I get the following message:
"Creating sysNAND.bin...
Could not create sysNAND.bin!
Backup SysNAND to file: failed!
Press B to return, START to reboot."
Not sure where I went wrong or how to fix this. Any advice would be appreciated

 

[d0k3]

Hi, I'm following this guide and am currently on part 2, step 22.
When I try to backup sysNAND to file, I get the following message:
"Creating sysNAND.bin...
Could not create sysNAND.bin!
Backup SysNAND to file: failed!
Press B to return, START to reboot."
Not sure where I went wrong or how to fix this. Any advice would be appreciated

Looks like a problem with your SD card. You can try using either Decrypt9 or OTPHelper to backup the SysNAND. If that works, let me know it did. If not, you need to format your SD card, I guess.

 

[neighborhoodqt]

Looks like a problem with your SD card. You can try using either Decrypt9 or OTPHelper to backup the SysNAND. If that works, let me know it did. If not, you need to format your SD card, I guess.

Alright, OTPHelper successfully made the backup. Thanks for the help!
Out of curiosity though, what about my SD card do you think could have caused the problem? I'm really trying not to make any mistakes here

 

[nl255]

Are there any plans to support dual emunands since most CFW has added support for them?

 

[d0k3]

Are there any plans to support dual emunands since most CFW has added support for them?

I have been thinking about enabling to format the SD card for multiple EmuNANDs, you would still have to use other tools to setup any EmuNAND beyound the first.

The full story for this is that I am unhappy with how multiple EmuNANDs are handled by CFWs now. CFWs use fixed offsets for multi EmuNANDs, which is a giant waste of space. An example: for N3DS, the first EmuNAND would be at the start of the SD card, the second @2GB, the third at @4GB, the fourth at 6GB and so on. So, four EmuNANDs chip away a total of 8GB of your EmuNAND space. However, if it is done in the best way possible, four EmuNANDs only use 5GB of your SD space. The right (and also: much more flexible) way of doing multiple EmuNANDs would be to use entries in the MBR (look that up if you don't know what it is) to do proper partitions for EmuNANDs and have CFWs use these entries to determine the position of the EmuNAND.

So, tl;dr? Not now, maybe later. If there is enough demand I'll allow you to format the SD card for multiple ones, though.

 

[nl255]

I have been thinking about enabling to format the SD card for multiple EmuNANDs, you would still have to use other tools to setup any EmuNAND beyound the first.

The full story for this is that I am unhappy with how multiple EmuNANDs are handled by CFWs now. CFWs use fixed offsets for multi EmuNANDs, which is a giant waste of space. An example: for N3DS, the first EmuNAND would be at the start of the SD card, the second @2GB, the third at @4GB, the fourth at 6GB and so on. So, four EmuNANDs chip away a total of 8GB of your EmuNAND space. However, if it is done in the best way possible, four EmuNANDs only use 5GB of your SD space. The right (and also: much more flexible) way of doing multiple EmuNANDs would be to use entries in the MBR (look that up if you don't know what it is) to do proper partitions for EmuNANDs and have CFWs use these entries to determine the position of the EmuNAND.

So, tl;dr? Not now, maybe later. If there is enough demand I'll allow you to format the SD card for multiple ones, though.

How about backing up and restoring the second (or third or fourth) emunand? That is the main thing I would be interested in.

 

[d0k3]

How about backing up and restoring the second (or third or fourth) emunand? That is the main thing I would be interested in.

Well, you need to use external tools with that. Backing up / restoring does not fit well in the current codebase (aka means a lot of work), and as I said, I don't want to promote the current way of doing things further.

 

[temp1312]

Everything benefits from 64k clusters, this is for the data on the SD card, not for the actual EmuNAND (yup, you also profit if you don't have an EmuNAND). And there are no compatibility issues.

Thank you for your amazing work.
So the 64k thing just effects the fat32 partition of the SD card and has nothing to do with emunand partition because it is not fat32 formatted. Here my questions are:
1. Is it different from formatting the SD fat32 partition with 64k parameter using Windows 10?
2. Will "complete redand setup" format the fat32 partition with 64k, or I have to use the "SD format options"?

Thank you.

Sent from my Nexus 7 using Tapatalk

 

[d0k3]

Thank you for your amazing work.
So the 64k thing just effects the fat32 partition of the SD card and has nothing to do with emunand partition because it is not fat32 formatted. Here my questions are:
1. Is it different from formatting the SD fat32 partition with 64k parameter using Windows 10?
2. Will "complete redand setup" format the fat32 partition with 64k, or I have to use the "SD format options"?

Thank you.

Sent from my Nexus 7 using Tapatalk

1. Yes, Windows does not format SD cards according to official recommendations. Not doing this may hinder performance. In fact, EmuNAND9 is the only tool I know that uses 64k clusters and does a proper SD format.
2. Yes, but your SD card needs to be >= 16GB (64k clusters don't make sense for lower sizes).