Corrupted 'luma' folder in CTRNAND?

[barn4721]

Hi all, I was looking at my CTRNAND files when I noticed that the luma folder was full of corrupted items, I remember installing Luma3DS to NAND a few years ago, but I wasn't expecting it to corrupt. Booting my 2DS without the SD card works just fine, but I'd still like to know how to get rid of the mess. Note that I don't really have a backup from before I had Luma3DS installed to NAND.

 

[SylverReZ]

Delete the "luma" folder from your CTRNAND using GM9. It will not damage anything as when you boot Luma3DS for the first time, the 'boot.firm' file is transferred to the NAND for booting the system without an SD card (this includes the configuration after you've set it all up).

 

[barn4721]

Deleting the luma folder via GM9 gives me the error "Failed deleting: luma (<A> to continue)", same thing happens when trying to delete any file/folder inside of it

 

[SylverReZ]

Deleting the luma folder via GM9 gives me the error "Failed deleting: luma (<A> to continue)", same thing happens when trying to delete any file/folder inside of it

SD card is most likely corrupted. Double check it with h2testw, then re-format to FAT32 32kb cluster.

 

[barn4721]

I formatted the SD with 32KB clusters and I still get the same error (although I'm not sure why this matters, the luma folder I'm speaking of is in CTRNAND, totally seperate from the SD), I also decided to try out TinyFormat and CTRTransfer (ctrtransfer images provided by 3ds.hacks.guide - region changing article), both did not work, the luma folder is still sitting there.

 

[SylverReZ]

I formatted the SD with 32KB clusters and I still get the same error

But did you read the last part that I said?

Double check it with h2testw

I mentioned to you that you should use h2testw, it can check for any corrupted sectors or other forms of damage. You can get tons of them if the SD card that you have is fake. Quick formatting will not fix anything.

 

[barn4721]

Ah sorry. Although I had to check with F3 instead of h2testw since the latter is Windows only, but everything seems fine either way:
Data OK: 29.71 GB (62309312 sectors) Data LOST: 0.00 Byte (0 sectors) Corrupted: 0.00 Byte (0 sectors) Slightly changed: 0.00 Byte (0 sectors) Overwritten: 0.00 Byte (0 sectors) Average Reading speed: 10.33 MB/s

 

[anotherthing]

I'm just shooting turkeys here, but could it be that the Luma files on your CTRNAND look like that because they're encrypted? And the reason you can't delete them is because your CTRNAND is write locked by default?

In other words, are you sure there's actually a problem there?

 

[Aletron9000]

Have you tried backing up your NAND and mounting CTRNAND using ninfs? Maybe you can delete the files from there. If not, maybe it'll at least give you a better explanation as to why you can't delete the folder.

 

[barn4721]

I'm just shooting turkeys here, but could it be that the Luma files on your CTRNAND look like that because they're encrypted? And the reason you can't delete them is because your CTRNAND is write locked by default?

In other words, are you sure there's actually a problem there?

I have Luma3DS installed on another 3DS' CTRNAND and it doesn't have these corrupted files, I can also delete the folder just fine.

Post automatically merged: Nov 26, 2024

Have you tried backing up your NAND and mounting CTRNAND using ninfs? Maybe you can delete the files from there. If not, maybe it'll at least give you a better explanation as to why you can't delete the folder.

I was able to mount ctrnand_full.img, trying to delete the luma folder causes the mount to immediately go read-only, although I think that can be disabled with a flag, but I'm not really sure on what to do from here.

Post automatically merged: Nov 26, 2024

Possibly dumb idea: Maybe I could recreate ctrnand_full.img by copying the folders except the luma one to a empty raw image file , and then swap the original one in the backup with the recreated image? I don't really know the limits of this.

 

[Kirbydogs]

I have Luma3DS installed on another 3DS' CTRNAND and it doesn't have these corrupted files, I can also delete the folder just fine.

Post automatically merged: Nov 26, 2024

I was able to mount ctrnand_full.img, trying to delete the luma folder causes the mount to immediately go read-only, although I think that can be disabled with a flag, but I'm not really sure on what to do from here.

Post automatically merged: Nov 26, 2024

Possibly dumb idea: Maybe I could recreate ctrnand_full.img by copying the folders except the luma one to a empty raw image file , and then swap the original one in the backup with the recreated image? I don't really know the limits of this.

Is this an Old 2DS? Might be SD card write protection, not sure though.