I'd also recommend testing with RPiOS and current "rpi-update" kernel, this will be the same as current LE11 nightly build and if there's an actual issue with the mmc driver (which is not caused by wearing out SD card, overclock, undervoltage etc) then RPi engineers would be the ones who could analyze and fix the issue - so posting on RPi forums would be best.
TY for confirming. Can I run 'sudo rpi-update' or should I use the build number as frakkin64 suggested?
Just thought of something...
Is 'mmc' how linux identifies a small card, and 'sdhc' how it identifies a large card? If so, then it looks like the problem is that it's trying to read a large card as a small one, which would totally make sense.
How would I "force" it to identify the card as an sdhc?
Thank you for your reply and suggestions, frakkin64 .
1. Try "blkid" and report back what that shows in the shell.
I assume you mean run these commands from the debug shell? And that's B L K I D in lowercase, correct? If so, then nothing returns from that command.
2. Try "dmesg" and see if you can capture the output in any meaningful way, looking to see if the mmc is detected. Alternatively you can try to filter it down to things that say mmc or sdhc with "dmesg|egrep -i '(mmc|sdhc)'" (without double quotes). You can also try piping dmesg output into more with "dmesg |more" if you want to capture each page on the display with a camera.
nothing comes back for sdhc but for this command:
dmesg | grep mmc | lessI see something that might be helpful...
mmc0: ============================================
mmc0: error -110 reading general info of SD ext reg
mmc0: error -110 whilst initialising SD card
mmc0: host does not support reading read-only switch, assuming write-enable
mmc0: timeout waiting for hardware interrupt.
mmc0: cmd op 48 arg Oxiff flags Oxb5 - resp 00000900 00000000 00000000 00000000, err 0
mmc0: data blocks 1 blksz 200 - err 0
mmc0: =========== REGISTER DUMP ===========3. Try adding " sdhci.debug_quirks2=4" to the end of /flash/cmdline.txt (without quotes, same line). This drops 1.8V signaling for UHS cards and runs them at a lower speed, it's worth a shot if only to narrow down the problem.
For this I have to mount the sd card in another computer to read, and the file is in the root folder of that sd card, i.e. /cmdline.txt, correct?
Currently, cmdline.txt has only one line:
boot=UUID=2802-3558 disk=UUID=39f82505-54be-4c3c-946f-10a7d42304f1 quietAdding sdhci.debug_quirks2=4 changes the first error message, it now shows:
*** Error in mount_flash: mount_common: Could not mount UUID=2802-3558 ***
### Starting debugging shell for boot step: mount_flash... type exit to quit ###However, removing that line does not change the error message, it shows this same message instead of the earlier
*** Error in mount_sysroot: mount_common: Could not mount /flash/SYSTEM ***Lastly, it might be a good idea to test with Raspberry Pi OS and use "sudo rpi-update 889323" to bump to the 6.1.14 kernel (should be similar/close to what LE11 is running) and reboot/test to see. If it's a problem there, then I would report it over on their Github. You can also bump around different kernel versions on Raspberry Pi OS with rpi-update to try and pin-point where it started by using the commit id's from the commit log here.
I might try this if I get time, but the fact that this is a VERY repeatable error (this same sd card works fine with LE9 and LE10 but once upgraded to LE11, fails) leads me to believe there's a change somewhere between 10 and 11 that affects it's ability to read larger sd cards.
Hopefully a dev at some point who has an RPI3 and large SD card can give this a whirl and see what they find.
It doesn't seem like it is a known issue, or a common issue -- but one of the developers might be in the know. I only use Raspberry Pi 4's, and only 1 of them has a 128GB SD card (and it's using Raspberry Pi OS with 6.1.15 kernel) and no problems there. The rest are all 16GB or 32GB cards.
Understood, thank you for your help so far!
Thank you for your reply, petediscrete , but I'm not sure how that article is relevant?
This same card works perfectly in everything I use it on, including this particular RPI3 when running LE9 or LE10.
Ok, even more troubleshooting while I'm waiting to see if anyone finds a solution...
Taking the working 16gb card which had already expanded itself and was running LE11 with no issues, I cloned that card to my 256gb card. Put it in the RPI3 and tried to boot it up, but sadly had the same result as earlier.
Seems LE11 is having trouble reading the boot record on larger µSD cards?
Hopefully it's just a configuration switch to get it up and running again.
More info...
Installed LE10 on the 256g card. Boots and runs fine.
Selected the "Upgrade" function in LE, and upgraded the install to LE11.
Upon boot, here's what I see:
*** Error in mount_sysroot: mount_common: Could not mount /flash/SYSTEM *** wit Starting debugging shell for boot step: mount_sysroot... type exit to quit ###Then, I see the LE Logo, and soon after:
*** Error in mount_sysroot: mount_common: Could not mount /flash/SYSTEM ***
### Starting debugging shell for boot step: mount_sysroot... type exit to quit ###
# exit
*** Error in mount_storage: mount_common: Could not mount UUID-9936eede-ceOf-492a-b25e-953244149f4? ***
### Starting debugging shell for boot step: mount_storage... type exit to quit ###
# exit
mount: mounting /flash on /sysroot/flash failed: No such file or directory mount: mounting /storage on /sysroot/storage failed: No such file or directory
*** Error in prepare_sysroot: final_check: Could not find systemd! ***
### Starting debugging shell for boot step: prepare_sysroot..
.. type exit to quit ###The "exit"s are what I typed to see if I could get any further.
Eventually it fails with a kernel panic error.
Hopefully this info helps in figuring out what needs to be done.
Update... Looks like the error only happens on large µSD cards. On a 16gb card it loads fine, on my 256gb card I always get this error. Hopefully someone who knows more than I do can take a look and see what's up with larger cards and LE11.
LE 9 & 10 are working just fine on this RPI3. Tried several times to get v11 to work, but it always stops on loading with the following error:
error in mount storage: mount_commonand then goes into a debug mode waiting for input.
Is this a known issue?