I have a Wii U console that is from 2013. Came in with a bad eMMC. I installed ISFShax, did a backup of SLC and SLCCMPT. Turned the console off and installed a NAND-AID. Reassembled the console and began the rebuild of the MLC. The process started with a blue blinking light and continued that way for roughly 15 hours. I was busy and didn't get back to it but I was expecting the light to be a static blue indicating it was done as the usual rebuild time for the MLC in my experience is roughly 20 minutes or less. When I found that it was still blinking I decided to interrupt the process and have a look at the log. The log indicated that 8 out of 52 titles had been successfully written to the MLC. 

Update: I BELIEVE THE LOG I VIEWED WAS FROM ANOTHER CONSOLE. SO THIS CAN BE IGNORED

Now initially I was like okay, something is seriously wrong. The Wii U console has an internal transfer rate of approximately 25MB per second, limited by the bus it uses. This means the total time required to write roughly 1.1GB of data should be around 10 minutes if nothing else got in the way. We know that isn't true because of how the Wii U rebuilds the MLC so sometimes it takes 20-30 minutes for these to complete. This transfer rate can be effected depending on the SD Cards you use during the rebuild process (meaning what is installed in the NAND-AID and what is used in the front of the Wii U consoles that holds the rebuilding tools/52 titles).

So I disassembled the console, inspected the NAND-AID and double checked everything. There is nothing I can find that is wrong with the installation of it. After triple checking all connections I decided to swap out the SD Cards just to be sure neither of them were defective. Unfortunately no improvement came from doing that. Just to be sure I verified the SD Cards in a computer and they pass read/write tests with flying colors. So where do we go from here?

Well my initial thoughts were that perhaps the console has a problem with the SLC, CPU or RAM. The problem with this theory is that it doesn't seem to display any symptoms that I would expect from problems with these components and usually speaking you won't make it this far into the repair.

After many hours thinking about what the heck could be wrong, I suddenly remembered that the SD Card Slot will operate in 1-bit transfer mode if its missing the data3 connection. I thought this has to be it, there is something wrong with the SD Card Slot!! So my curious mind began wondering, if that is the problem and the console is working in only 1-bit transfer mode can you rebuild an MLC like this???

Well we are going to find out. I am going ahead with a test, if it took 15 hours to complete 8 titles, assuming all things linear (yeah its a big assumption, but might as well test the theory out) that means the console should complete the rebuild process in about 4 days. So I set it up to rebuild on 9/26/2024 and walked away with a plan to check its status on 9/30/24 @ 1PM. My reason for doing this test is just that I want to see if it will actually complete rebuilding the MLC. Additionally whatever the outcome is I plan on replacing the SD Card Slot to see if that fixes the problem.

So look for an update on 9/30/2024 after 1PM. 

Edit: We can ignore my theory about the MLC being rebuilt while the SD Card is operating in 1 bit transfer mode because I am not sure if that is what is happening.

I was thinking about this 1bit transfer mode and I am unable to locate the documentation about it online. Lets assume what I remember is correct and it only transfers at 1bit per second. If that is the case, than it would mean to transfer 1GB of data it should take around 92 days to complete. Meaning the 4 days I am giving this to finish won't be anywhere close to what it would actually need.....

I think I will just let it go since I don't know for a fact if its operating in 1bit transfer mode; after all it was just a theory I had after racking my brain out trying to figure out why the transfer rate was so slow. My problem is I have too much information about too many things in my head and its sometimes difficult for me to find the reference material online to verify the information. This is half the reason I created this website so that I could stay organized and hopefully find the information I am looking for when I need to reference it. 

Anyhow, tomorrow is another day. I will be back on Monday 9/30/2024 to investigate this further.

Okay, so I went ahead and interrupted (using this term loosely because I actually think it wasn't rebuilding the MLC at all) the rebuild of the MLC. There is no information in the logs that I can find to discloses what the problem might be. Additionally I went back and tried to duplicate the MLC log showing progress, and I cannot get anything. I don't think the log file is written until the end of the MLC rebuild process, so getting a partial log file doesn't make sense. I think I may have left an old log file on the memory card from a previous Wii U.

The only symptom that I can find that is repeatable is the MLC will erase properly, the scfm.img will delete properly and if I try to rebuild the MLC the front power LED light will blink blue and never go solid. So its an interesting dilemma where we get the correct sign that rebuilding is working, but the process never completes and for some strange reason we do not get an indication of an error, like the LED changing to red for example. The obvious indication of an error is that this Wii U went for 4 days and still had a blinking blue LED. 

What I am going to do is replace the SD Card Slot and see if that helps. Its the only thing I can think of that would cause this problem. I have already replaced the SD card with another one and tested/verified that both are actually working so I am confident it is not an SD Card issue.

I stand corrected. It would appear the mlc.log is written during the rebuild process. The wafel_setup_mlc.ipx was updated since the last time I used it. So I don't know if anything has been changed. What strikes me as odd is I am used to seeing the log start with a bunch of directories being created, which looks like this:
MakeQuota;/vol/storage_mlc01/sys;-00000000
MakeDir;/vol/storage_mlc01/usr;-00000000
MakeDir;/vol/storage_mlc01/usr/boss;-00000000
MakeDir;/vol/storage_mlc01/usr/save;-00000000
MakeDir;/vol/storage_mlc01/usr/save/00050010;-00000000
MakeDir;/vol/storage_mlc01/usr/packages;-00000000
MakeDir;/vol/storage_mlc01/usr/tmp;-00000000
Flush;MLC;-00000000
OpenDir;/vol/sdcard/wafel_install;-00000000
OpenMCP;/vol/sdcard/wafel_install;-00000000
InstallInfo;0005001b10051000;-00000000
Install;0005001b10051000;-00000000
The log created from this Wii U looks like this:
OpenDir /vol/sdcard/wafel_install: 0
OpenMCP /vol/sdcard/wafel_install: 0
InstallInfo 0005001010040100: 00000000
Install 0005001010040100: 00000000
InstallInfo 0005001010041100: 00000000
Install 0005001010041100: 00000000
InstallInfo 0005001010043100: 00000000
Install 0005001010043100: 00000000
InstallInfo 0005001010044100: 00000000
Install 0005001010044100: 00000000
InstallInfo 0005001010045100: 00000000
Install 0005001010045100: 00000000
InstallInfo 0005001010047100: 00000000

It doesn't show the directories being created at all. Without those directories the MLC cannot be rebuilt. Additionally the Open directory is different:

"OpenDir /vol/sdcard/wafel_install: 0"  Vs
"OpenDir;/vol/sdcard/wafel_install;-00000000"

I don't know if the way the log is written was changed or if this indicates something else.

Lets move forward. I am going to replace the SD Card slot and see if it changes anything. I am currently operating on the assumption that data is being written JUST VERY SLOWLY to the NAND-AID. Also I am going to assume the log doesn't indicate a problem and the slight differences don't mean anything for right now. I cannot find any documentation on how to interpret the log file.  I attempted to look at the source code for wafel_setup_mlc.ipx to see how the log file is being written, but it doesn't appear to be in the source code or I have simply overlooked it. Programming/Coding really isn't my thing though so its possible I just missed it.

I have replaced the SD Card Slot. Lets try this again and see if we can get this Wii U working. I did look at the other SD Card Slot and there doesn't appear to be anything wrong with it at least externally, but I did notice that when pushing and SD Card into it there was some resistance, so lets hope the SD Card slot was defective.

No difference. Walked away for a couple hours because I had some other things to do here is the new log after 3 hours.
OpenDir /vol/sdcard/wafel_install: 0
OpenMCP /vol/sdcard/wafel_install: 0
InstallInfo 0005001b10057000: 00000000
Install 0005001b10057000: 00000000
InstallInfo 0005001b10058000: 00000000
Install 0005001b10058000: 00000000
InstallInfo 0005001b10059100: 00000000
Install 0005001b10059100: 00000000
InstallInfo 0005001b10063000: 00000000
Install 0005001b10063000: 00000000
InstallInfo 0005001b10065000: 00000000
Install 0005001b10065000: 00000000
InstallInfo 0005001b10067100: 00000000
Install 0005001b10067100: 00000000
InstallInfo 0005001b10068000: 00000000
Install 0005001b10068000: 00000000
InstallInfo 0005001b10069100: 00000000
Install 0005001b10069100: 00000000
InstallInfo 000500101004a100: 00000000
Install 000500101004a100: 00000000
InstallInfo 000500101004b100: 00000000
Looks like it made it a bit further, but not sure that really matters. The chance of it completing seems unlikely as even after running it for 4 days previously the log didn't show any more progress. I am going to re-trace my steps here just to be sure I haven't missed anything....

Left the console running for 6 days as I forgot about it. The outcome has a slight improvement which piques my curiosity of why this is rebuilding the MLC so slow on a NAND-AID installation with no detectable problems.

It made it quite a bit further this time, wafel_setup_mlc.log below 

OpenDir /vol/sdcard/wafel_install: 0
OpenMCP /vol/sdcard/wafel_install: 0
InstallInfo 000500301001910a: 00000000
Install 000500301001910a: fffbf3b5
InstallInfo 000500301001810a: 00000000
Install 000500301001810a: fffbf3b5
InstallInfo 000500301001710a: 00000000
Install 000500301001710a: fffbf3b5
InstallInfo 000500301001610a: 00000000
Install 000500301001610a: fffbf3b5
InstallInfo 000500301001510a: 00000000
Install 000500301001510a: fffbf3b5
InstallInfo 000500301001410a: 00000000
Install 000500301001410a: fffbf3b5
InstallInfo 000500301001310a: 00000000
Install 000500301001310a: fffbf3b5
InstallInfo 000500301001210a: 00000000
Install 000500301001210a: fffbf3b5
InstallInfo 000500301001110a: 00000000
Install 000500301001110a: fffbf3b5
InstallInfo 000500301001010a: 00000000
Install 000500301001010a: fffbf3b5
InstallInfo 00050030100111ff: 00000000
Install 00050030100111ff: fffbf3b5
InstallInfo 000500301006d10a: 00000000
Install 000500301006d10a: fffbf3b5
InstallInfo 000500301001a10a: 00000000
Install 000500301001a10a: fffbf3b5
InstallInfo 000500101005a100: 00000000
Install 000500101005a100: fffbf3b5
InstallInfo 000500101004e100: 00000000
Install 000500101004e100: fffbf3b5
InstallInfo 000500101004d100: 00000000
Install 000500101004d100: fffbf3b5
InstallInfo 000500101004c100: 00000000
Install 000500101004c100: fffbf3b5
InstallInfo 000500101004b100: 00000000
Install 000500101004b100: fffbf3b5
InstallInfo 000500101004a100: 00000000
Install 000500101004a100: fffbf3b5
InstallInfo 0005001b10069100: 00000000
Install 0005001b10069100: fffbf3b5
InstallInfo 0005001b10068000: 00000000
Install 0005001b10068000: fffbf3b5
InstallInfo 0005001b10067100: 00000000

At this point I have tripled checked everything I can check. I have no idea what the cause of this problem is and I don't know what other troubleshooting I can do. I thought about installing defuse, but I recall that is only necessary if ISFShax cannot be installed. For this particular console its installed and functioning.

Dump the system crash logs, maybe they have something helpful

Crash logs are attached. I forgot how to calculate which log is the most recent from the meta.bin file.

Oh looks like hexadecimal, so coverted 005F to decimal would be 95, so log 95. Let me know if this is correct.

Well log 95 shows some interesting stuff. Can be viewed below:
----------- Starting System Log -----------
00:00:00:311: MMC(0): initializing Controller 0, Slot 0 base 0x0D070000
00:00:00:312: MMC(3): initializing Controller 2, Slot 0 base 0x0D100000
00:00:00:312: MMC(4): initializing Controller 3, Slot 0 base 0x0D110000
00:00:00:427: USB Trace: Activating root hubs @ uptime 0.424 s with options 0x40000.
00:00:00:449: UHS0 Trace: DevFsm(EHCI-0/L0/P0): Creating device, speed=HIGH.
00:00:00:455: UHS0 Trace: DevFsm(OHCI-0:0/L0/P0): Creating device, speed=FULL.
00:00:00:457: USB Info: UhsServerAddHc 0 OK.
00:00:00:476: UHS0 Trace: DevFsm(EHCI-1/L0/P0): Creating device, speed=HIGH.
00:00:00:482: UHS0 Trace: DevFsm(OHCI-1:0/L0/P0): Creating device, speed=FULL.
00:00:00:484: USB Info: UhsServerAddHc 1 OK.
00:00:00:497: TEST Info: crossProcessHeap OK.
00:00:00:501: UHS0 Trace: Powering on root hub group 0.
00:00:00:507: AUXIL Info: crossProcessHeap OK.
00:00:00:517: UHS0 Trace: Powering on root hub group 1.
00:00:00:519: AHCI_MGR Trace: Turning on drive power.
00:00:00:519: AHCI_MGR Trace: Turning on drive power.
00:00:00:524: AHCI_MGR Trace: Initializing phy.
00:00:00:524: AHCI_MGR Trace: Initializing phy.
00:00:00:524: AHCI_DRV Trace: Initiating cold open.
00:00:00:524: AHCI_DRV Trace: Initiating cold open.
00:00:00:524: AHCI_DRV Trace: Resetting HBA.
00:00:00:525: AHCI_DRV Trace: Resetting HBA.
00:00:00:528: AUXIL Info: Net OK.
00:00:00:575: AHCI_DRV Trace: HBA Reset OK.
00:00:00:575: AHCI_DRV Trace: HBA Reset OK.
00:00:00:575: AHCI_DRV Trace: link ready, speed is GEN 1.
00:00:00:576: AHCI_DRV Trace: link ready, speed is GEN 1.
00:00:00:727: ISFS: FAT INFO (ch WUP): slot 49 / seq 968398 (Each FAT slot has been updated 15131 times in avr)
00:00:00:727: ISFS: fs_fat.c(545)FAT INFO (ch WUP): slot 49 / seq 968398 (Each FAT slot has been updated 15131 times in avr)
00:00:00:727: FSA: [uptime 0.727 s]: Attached volume to slc01 (isfs): Capacity 511 MB, 262016 logical blocks of size 2048 B.
00:00:00:850: ISFS: FAT INFO (ch RVL Compat): slot 7 / seq 195801 (Each FAT slot has been updated 12237 times in avr)
00:00:00:851: ISFS: fs_fat.c(545)FAT INFO (ch RVL Compat): slot 7 / seq 195801 (Each FAT slot has been updated 12237 times in avr)
00:00:00:852: FSA: [uptime 0.852 s]: Attached volume to slccmpt01 (isfs): Capacity 511 MB, 261632 logical blocks of size 2048 B.
00:00:00:862: SCFM:Start init. BUILD_TIME:[16:02:03]
00:00:00:867: SCFM:FSAInit
00:00:00:867: SCFM:AddClient
00:00:00:869: SCFM:scfmMountSlc
00:00:00:869: SCFM:scfmLoad
00:00:00:869: SCFM:Done init.
00:00:00:871: PCFS: Disabled because we are in PROD mode.
00:00:00:872: MCP: booting from NAND
00:00:00:872: MCP: Boot PM flags - PON_COLDBOOT PON_POWER_BTN PON_SMC
00:00:00:890: MCP: Cafe OS SDK Version 2.13.01 Build 69088 Branch sdk_2_13
00:00:00:891: MCP: Booting on Espresso (0x0000700100000201), Latte (0x25100028), RTC (0x01)
00:00:00:891: MCP: Platform - boardType(CF), boardRevision(11), devicePresence(0x00000000), sataDevice(3), consoleType(1)
00:00:00:898: FSA: [uptime 0.898 s]: Attached volume to sdcard01 (fat): Capacity 61056 MB, 125042688 logical blocks of size 512 B.
00:00:00:900: ISFS: FAT block entries check start
00:00:00:900: ISFS: fs_ops.c(2215)FAT block entries check start
00:00:00:903: ISFS: FAT block entries check finished.
00:00:00:904: ISFS: fs_ops.c(2292)FAT block entries check finished.
00:00:00:912: SCFM: Create new slc cache image.
00:00:00:913: SCFM: Preparing for mlc format in MCP sequence
00:00:01:142: AHCI_DRV Trace: device ready.
00:00:01:142: AHCI_DRV Trace: device ready.
00:00:01:142: AHCI_DRV Trace: port operational.
00:00:01:142: AHCI_DRV Trace: port operational.
00:00:01:147: ODM: ODM: Successfully configured preload cache
00:00:01:147: ODM odm_fsm.c(856): ODM: Successfully configured preload cache
00:00:01:384: FSA: [uptime 1.384 s]: Attached volume to mlc01 (raw): Capacity 29760 MB, 60948480 logical blocks of size 512 B.
00:00:01:386: FSA: [uptime 1.386 s]: Attached volume to ramdisk01 (raw): Capacity 125 MB, 129022 logical blocks of size 1024 B.
00:00:01:387: MCP: Formatting Device ramdisk to wfs
00:00:01:530: FSA: [uptime 1.530 s]: Attached volume to ramdisk01 (wfs): Capacity 125 MB, 129022 logical blocks of size 1024 B.
00:00:01:531: MCP: Format Complete
00:00:01:539: MCP: Formatting Device mlc to wfs
00:00:03:287: FSA: [uptime 3.287 s]: Attached volume to mlc01 (wfs): Capacity 29760 MB, 60948480 logical blocks of size 512 B.
00:00:03:288: MCP: Format Complete
00:00:05:243: ISFS: FAT block entries check start
00:00:05:243: ISFS: fs_ops.c(2215)FAT block entries check start
00:00:05:246: ISFS: FAT block entries check finished.
00:00:05:247: ISFS: fs_ops.c(2292)FAT block entries check finished.
00:00:05:349: [ES] checkOwnedTitleUpdateFlags: no delete in progress
00:00:05:349: [ES] checkOwnedTitleUpdateFlags: no import in progress
00:00:05:360: MCP: File loading from ramdisk cache is enabled
00:00:05:361: MCP: Master title 0005001010040100 os 000500101000400a from mlc01 flags 0004
00:00:05:372: MCP: no valid title list found, rebuilding...
00:00:05:377: MCP: os version 10 NDEBUG (0x000500101000400a)
00:00:05:378: MCP: FSA volume on device /dev/mlc01 (wfs) attached @ uptime 5.378 s.
00:00:05:380: MCP: FSA volume on device /dev/ramdisk01 (wfs) attached @ uptime 5.380 s.
00:00:05:380: MCP: Titles scanned (dev_state 0006) on device /dev/ramdisk01 (wfs) @ uptime 5.380 s.
00:00:05:380: MCP: FSA volume on device /dev/sdcard01 (fat) attached @ uptime 5.380 s.
00:00:05:381: MCP: Titles scanned (dev_state 0006) on device /dev/sdcard01 (fat) @ uptime 5.381 s.
00:00:05:381: MCP: FSA volume on device /dev/slc01 (isfs) attached @ uptime 5.381 s.
00:00:05:381: MCP: FSA volume on device /dev/slccmpt01 (isfs) attached @ uptime 5.381 s.
00:00:05:381: MCP: Titles scanned (dev_state 0006) on device /dev/slccmpt01 (isfs) @ uptime 5.381 s.
00:00:05:385: MCP: Titles scanned (dev_state 0004) on device /dev/mlc01 (wfs) @ uptime 5.385 s.
00:00:05:389: MCP: Titles scanned (dev_state 000c) on device /dev/mlc01 (wfs) @ uptime 5.389 s.
00:00:05:391: MCP: Titles scanned (dev_state 0006) on device /dev/mlc01 (wfs) @ uptime 5.391 s.
00:00:05:429: MCP: Titles scanned (dev_state 000e) on device /dev/slc01 (isfs) @ uptime 5.429 s.
00:00:05:448: MCP: ECO mode is disabled
00:00:05:448: [+-* DK is ready for console input *-+]
00:00:05:448: MCP: syslog mask is set to 0xffffffff
00:00:05:450: W2C: Does not need W2C-reflection
00:00:05:784: UHS1 Trace: DevFsm(EHCI-2/L0/P0): Creating device, speed=HIGH.
00:00:05:787: UHS1 Trace: DevFsm(OHCI-2:0/L0/P0): Creating device, speed=FULL.
00:00:05:787: CCR_MAIN: activating root hub.
00:00:05:892: FS_MAIN: UMS Server Created.
00:00:05:940: BT: BTA/BTE/STACK now operational
00:00:06:092: UHS1 Trace: DevFsm(EHCI-2/L1/P1): Creating device, speed=HIGH.
00:00:06:094: UHS1 Trace: DevFsm: There are now a total of 1 connected devices.
00:00:06:133: UHS1 Trace: CltIfFsm(V057e|P0341|IF0): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.130 s.
00:00:06:136: UHS1 Trace: CltIfFsm(V057e|P0341|IF1): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.133 s.
00:00:06:138: UHS1 Trace: CltIfFsm(V057e|P0341|IF2): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.136 s.
00:00:06:141: UHS1 Trace: CltIfFsm(V057e|P0341|IF3): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.139 s.
00:00:06:144: UHS1 Trace: CltIfFsm(V057e|P0341|IF4): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.141 s.
00:00:06:147: UHS1 Trace: CltIfFsm(V057e|P0341|IF5): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.144 s.
00:00:06:150: UHS1 Trace: CltIfFsm(V057e|P0341|IF6): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.147 s.
00:00:06:153: UHS1 Trace: CltIfFsm(V057e|P0341|IF7): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.150 s.
00:00:06:156: UHS1 Trace: CltIfFsm(V057e|P0341|IF8): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.153 s.
00:00:06:159: UHS1 Trace: CltIfFsm(V057e|P0341|IF9): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.156 s.
00:00:06:162: UHS1 Trace: CltIfFsm(V057e|P0341|IF10): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.159 s.
00:00:06:164: UHS1 Trace: CltIfFsm(V057e|P0341|IF11): Device EHCI-2/L1/P1/A01 entering probing state @ uptime 6.162 s.
00:00:06:167: UHS1 Trace: CltIfFsm(V057e|P0341|IF0): Acquired by client in pid 6.
00:00:06:168: UHS1 Trace: CltIfFsm(V057e|P0341|IF0): Enable endpoints 0x00080000.
00:00:06:209: __ccr_hid_attach_add_interface: idx 0 ep 3
00:00:06:211: UHS1 Trace: CltIfFsm(V057e|P0341|IF1): Acquired by client in pid 6.
00:00:06:213: UHS1 Trace: CltIfFsm(V057e|P0341|IF1): Enable endpoints 0x00100000.
00:00:06:254: __ccr_hid_attach_add_interface: idx 1 ep 4
00:00:06:256: UHS1 Trace: CltIfFsm(V057e|P0341|IF2): Acquired by client in pid 6.
00:00:06:258: UHS1 Trace: CltIfFsm(V057e|P0341|IF3): Acquired by client in pid 6.
00:00:06:261: UHS1 Trace: CltIfFsm(V057e|P0341|IF3): Activating bAlternateSetting 0.
00:00:06:265: UHS1 Trace: CltIfFsm(V057e|P0341|IF4): Acquired by client in pid 6.
00:00:06:267: UHS1 Trace: CltIfFsm(V057e|P0341|IF5): Acquired by client in pid 6.
00:00:06:269: UHS1 Trace: CltIfFsm(V057e|P0341|IF5): Activating bAlternateSetting 0.
00:00:06:273: UHS1 Trace: CltIfFsm(V057e|P0341|IF7): Acquired by client in pid 6.
00:00:06:275: UHS1 Trace: CltIfFsm(V057e|P0341|IF7): Enable endpoints 0x08001000.
00:00:06:277: UHS1 Trace: CltIfFsm(V057e|P0341|IF8): Acquired by client in pid 6.
00:00:06:279: UHS1 Trace: CltIfFsm(V057e|P0341|IF9): Acquired by client in pid 6.
00:00:06:281: UHS1 Trace: CltIfFsm(V057e|P0341|IF9): Activating bAlternateSetting 0.
00:00:06:286: UHS1 Trace: CltIfFsm(V057e|P0341|IF10): Acquired by client in pid 6.
00:00:06:288: UHS1 Trace: CltIfFsm(V057e|P0341|IF11): Acquired by client in pid 6.
00:00:06:290: UHS1 Trace: CltIfFsm(V057e|P0341|IF11): Activating bAlternateSetting 0.
00:00:06:292: DRH chip revision 00000040
00:00:06:292: DRH firmware version 190c0117
00:00:06:292: DRH cdc version 00080000
00:00:06:292: DRH wifi module id a8e502d0
00:00:06:293: DRH SPL id 00001c58
00:00:06:449: AUXIL Info: resumed.
00:00:06:519: MCP: boot1 version 2.11.09
00;00;05;765: COSREPORT: Set level:1 from syslog level
00;00;05;765:
----------------------------------------------- BPERF: (0/5765860) PPC Init.
00;00;05;765: Cafe OS SDK Version 2.13.01 Build 69088 Branch sdk_2_13
00;00;05;765: PPC NDEBUG Kernel Build date - Feb  4 2021 16:37:45
00;00;05;765: BUILT AS OS_VERSION_MAJOR 000500101000800A MINOR 0x3DE8
00;00;05;765: core=1 COLD BOOT
00;00;05;765: SOFT INTERRUPT MODE
00;00;05;765: -----------------------------------------------

00;00;05;773: KiCblRegisterBlocks() completed with status 0:-4.
00;00;05;773: PROD Mode - don't even try to load kdebug.elf
00;00;05;774: title id: 5001010040100, app type 90000001
00;00;05;774:
00;00;05;774: ---------------------------------------
00;00;05;774: OS VERSION ID     0x000500101000400A
00;00;05;774: MASTER TITLE ON   FLASH
00;00;05;774: ---------------------------------------
00;00;05;774:
00:00:06:558: MCP: loaded and parsed 'preload.txt' at '/vol/system/title/00050010/1000400a/code'
00:00:06:575: MCP: Wake 0 signal
00;00;06;466: DIAG:+KiRPLLoaderSetup
00;00;06;467: DIAG:-KiRPLLoaderSetup: before no-return call to KiLoadContext (0xEFE09400) (0x01003FFC)
00:00:06:622: DRH using runtime generated WLAN data
00:00:06:622: Setting DRH to Normal mode
00:00:06:623: setting DRH system time to 00:01:20
00:00:06:624: sending DRC WOWL wake
00:00:06:780: NET: Applied interface MTU (wl0:1400 eth0:1400).
00:00:06:792: USBETH Trace: Created interface 100.
00:00:06:866: WUD_BCMFWCheck ==> chipname 20702A1 build 517 from SERIAL FLASH
00:00:06:868: BT: BTRM now Active (WUD Operational)
00;00;07;217: DIAG:+KiProcess_FinishInitAndPreload
00;00;07;217: KiCblRegisterBlocks() completed with status 0:-4.
00;00;07;234: Kernel is loading shared data...
00:00:08:538: ccr_admin_wowl_wake_drc() returned 0
00:00:10:958: Cleaning /vol/storage_mlc01/sys/import/crash
Process 1, Error 0xCAFEBADD
*** LoadShared times out loading shared data.


--Core1-UPID1--- Exception Context 0xFFE442D8 ------RAMPID 1------

CR    = 0x00000000
CTR   = 0x00000000
LR    = 0x00000000
SRR0  = 0x00000000
SRR1  = 0x00000000
r0   = 0x00000000 (             0)  r16  = 0x00000000 (             0)
r1   = 0x00000000 (             0)  r17  = 0x00000000 (             0)
r2   = 0x00000000 (             0)  r18  = 0x00000000 (             0)
r3   = 0x00000000 (             0)  r19  = 0x00000000 (             0)
r4   = 0x00000000 (             0)  r20  = 0x00000000 (             0)
r5   = 0x00000000 (             0)  r21  = 0x00000000 (             0)
r6   = 0x00000000 (             0)  r22  = 0x00000000 (             0)
r7   = 0x00000000 (             0)  r23  = 0x00000000 (             0)
r8   = 0x00000000 (             0)  r24  = 0x00000000 (             0)
r9   = 0x00000000 (             0)  r25  = 0x00000000 (             0)
r10  = 0x00000000 (             0)  r26  = 0x00000000 (             0)
r11  = 0x00000000 (             0)  r27  = 0x00000000 (             0)
r12  = 0x00000000 (             0)  r28  = 0x00000000 (             0)
r13  = 0x00000000 (             0)  r29  = 0x00000000 (             0)
r14  = 0x00000000 (             0)  r30  = 0x00000000 (             0)
r15  = 0x00000000 (             0)  r31  = 0x00000000 (             0)

OSContext is unused (NULL)



Kernel Stack Trace 0xFFE43E68 ----

CoreId: 1     Stack: 0xFFE43E68
Address:      Back Chain    LR Save
0xFFE43E68:   0xFFE43EA0    0xFFF0F07C +0x0
0xFFE43EA0:   0xFFE43EE8    0xFFF14F6C +0x0
0xFFE43EE8:   0xFFE43EF0    0xFFF15198 +0x0
0xFFE43EF0:   0xFFE43F00    0xFFF129A0 +0x0
0xFFE43F00:   0x00000000    0xFFF01FCC +0x0
00;00;17;266: KiCblRegisterBlocks() completed with status 0:-4.
00:00:17:405: COS encountered unrecoverable error...

Pending Resource Request for COS processes...
        Title Id       Process Id -> RM Path            
00:00:22:475: MCP: life time number of fatal errors - 92
00:00:22:475: MCP: storing current logs as '/vol/system/logs/93.log'
00:00:22:737: ACT: Account not found. Created.
00:00:22:738: ACT: Current account is #1.
00:00:23:381: MCP: Finished storing current logs as '/vol/system/logs/93.dsc'
00:00:23:381: COS encountered unrecoverable error...

Pending Resource Request for COS processes...
        Title Id       Process Id -> RM Path            
00:00:28:381: MCP: life time number of fatal errors - 93
00:00:28:381: MCP: storing current logs as '/vol/system/logs/94.log'
00:00:29:046: MCP: Finished storing current logs as '/vol/system/logs/94.dsc'
00:00:29:046: COS encountered unrecoverable error...

Pending Resource Request for COS processes...
        Title Id       Process Id -> RM Path            
00:00:34:046: MCP: life time number of fatal errors - 94
]
I don't know what most of this means, but I can see that the console is detecting the mlc01 and it appears its able to format it properly. Indicated by this in the log:
00:00:01:384: FSA: [uptime 1.384 s]: Attached volume to mlc01 (raw): Capacity 29760 MB, 60948480 logical blocks of size 512 B.
00:00:01:386: FSA: [uptime 1.386 s]: Attached volume to ramdisk01 (raw): Capacity 125 MB, 129022 logical blocks of size 1024 B.
00:00:01:387: MCP: Formatting Device ramdisk to wfs
00:00:01:530: FSA: [uptime 1.530 s]: Attached volume to ramdisk01 (wfs): Capacity 125 MB, 129022 logical blocks of size 1024 B.
00:00:01:531: MCP: Format Complete
00:00:01:539: MCP: Formatting Device mlc to wfs
00:00:03:287: FSA: [uptime 3.287 s]: Attached volume to mlc01 (wfs): Capacity 29760 MB, 60948480 logical blocks of size 512 B.
00:00:03:288: MCP: Format Complete
ramdisk01, not entirely sure what that is, perhaps its part of the SLC? 

It also detects the 64GB sd card plugged into the front of the console. Which is what I believe this is indicating
00:00:00:891: MCP: Platform - boardType(CF), boardRevision(11), devicePresence(0x00000000), sataDevice(3), consoleType(1)
00:00:00:898: FSA: [uptime 0.898 s]: Attached volume to sdcard01 (fat): Capacity 61056 MB, 125042688 logical blocks of size 512 B.
Additionally I believe the console is detecting the NAND-AID and SD Card as capable of full speed and that can be seen in the log here:
00:00:05:784: UHS1 Trace: DevFsm(EHCI-2/L0/P0): Creating device, speed=HIGH.
00:00:05:787: UHS1 Trace: DevFsm(OHCI-2:0/L0/P0): Creating device, speed=FULL.
If this is accurate, than my initial theory about it writing in 1 bit mode would be incorrect. I had already assumed this was incorrect, but its nice to have evidence of it so I am not forced to operate under assumptions.