Need some help troubleshooting here folks. I can dump emunand on the card both as partition and files, but when I load up the emunand the switch crashes right after the home screen loads up. The details are as follows:
- Switch OFW is 2.2 (nand backed up already)
- updated OFW offline via Choi to 2.2 to support exFat
- SX OS 2.5
- sd card reads fine under data management formatted as both exFat and fat32
- have successfully created emunand on sys previously
- have booted into emunand on sd (files) with a 64gb micro formatted as fat32
- CANNOT boot emunand (crashing as previously stated) with 200gb sd as files or partition. The sd DOES read under data management when booted into OFW before and after emunands are created on sd card. Card has been formatted as fat32 and exFat during troubleshooting with zero success regarding emunand.
Ive been racking my brain as to the issue. I tried formatting the card to fat32, create the emu partition, and loading and still get crashes. Tried formatting fat32, creating emu part, then formatting the remaining space as exFat, and still get the crashing.
At first I thought it was a format issue...maybe emunand doesnt play nice when formatted under exFat since the 64gb card seemed to be okay with emu files (I didnt try emu partition with the card), but dont believe this is the issue. I then thought I could have a bad card, but if that was the case, wouldnt I get some read errors when checking for it under OFW data management?
I suppose I could just create the emunand the old fashioned way and split the system memory, but I prefer to keep in on the sd card in case of any major damage during read/writes (cheaper to replace the card than the switch). Perhaps im over thinking it? Do you think emunand on system memory is just as safe for the health of the system hardware? I plan to keep the switch offline as much as possible fyi.
update: attempted to create emunand on system again and get crashing :\ I'm going to start fresh and restore original nand via hekate...perhaps theres something leftover from the first emunand created on the system memory that is causing the issue.
- Switch OFW is 2.2 (nand backed up already)
- updated OFW offline via Choi to 2.2 to support exFat
- SX OS 2.5
- sd card reads fine under data management formatted as both exFat and fat32
- have successfully created emunand on sys previously
- have booted into emunand on sd (files) with a 64gb micro formatted as fat32
- CANNOT boot emunand (crashing as previously stated) with 200gb sd as files or partition. The sd DOES read under data management when booted into OFW before and after emunands are created on sd card. Card has been formatted as fat32 and exFat during troubleshooting with zero success regarding emunand.
Ive been racking my brain as to the issue. I tried formatting the card to fat32, create the emu partition, and loading and still get crashes. Tried formatting fat32, creating emu part, then formatting the remaining space as exFat, and still get the crashing.
At first I thought it was a format issue...maybe emunand doesnt play nice when formatted under exFat since the 64gb card seemed to be okay with emu files (I didnt try emu partition with the card), but dont believe this is the issue. I then thought I could have a bad card, but if that was the case, wouldnt I get some read errors when checking for it under OFW data management?
I suppose I could just create the emunand the old fashioned way and split the system memory, but I prefer to keep in on the sd card in case of any major damage during read/writes (cheaper to replace the card than the switch). Perhaps im over thinking it? Do you think emunand on system memory is just as safe for the health of the system hardware? I plan to keep the switch offline as much as possible fyi.
update: attempted to create emunand on system again and get crashing :\ I'm going to start fresh and restore original nand via hekate...perhaps theres something leftover from the first emunand created on the system memory that is causing the issue.
Last edited:
