actually did some more digging and i think this describes the same issue that i am seeing with these newer sd cards in uboot spl. https://lore.kernel.org/u-boot/20251031145951.535376-1-c.stoidner@phytec.de/

as far as i am understanding this is running off of the onboard spi-flash/eeprom on the orange pi board unless you're reflashing that on first boot U-Boot SPL board init U-Boot SPL 2017.09-orangepi (Aug 30 2024 - 22:09:16) i've also switched to using mainline uboot v2025.10 for my emmc and sd cards that i'm creating but previously had not been in a situation where i needed to update the spi-flash/eeprom for sd cards or emmc uboot proper to be able to be loaded. I was able to resolve my issue by building mainline uboot spl with a timeout in the mmc probing

T95 Mini H313 EMCP Board V1.0

U-Boot SPL 2025.10_armbian-2025.10-Se50b-P24f2-Hae98-V38b0-Bbf55-R448a (Nov 19 2025 - 09:08:53 +0000) which is in that image, has no btrfs support I saw for example on my NanoPi-R6C using: U-Boot SPL 2026.01-rc2_armbian-2026.01-rc2-S365a-Pb445-He3cc-V062a-Bbf55-R448a (Dec 03 2025 - 04:31:42 +0000) that it has btrfs support, so can load kernel etc directly from the rootfs partition when it is btrfs formatted. You can first write a newer U-Boot in SPI-Flash, then it should work.

Hi, how do you mount the share? It might be that systemd manages the mount in newer systems, then, to umount you have to simply systemctl stop your-share.mount You can check with: systemctl list-units --type=mount --all To see if the mount is systemd managed