Hello Sascha. The error occurs in the cdev_mount_default() function. cdev_get_mount_path() returns "/boot". And indeed, the partition is mounted here for some reason... I don't understand yet why this happens. barebox@Mega-Milas Informer SAMA5D2:/ mount none on / type ramfs none on /dev type devfs /dev/mmc1.0 on /boot type fat Update: I found that this happens if the CONFIG_OF_BAREBOX_ENV_IN_FS option is used. When disabled, mounting occurs as expected, but in this case I cannot use environments from a file from a partition on the SD card. It is not yet clear how to get out of this situation... Thanks! чт, 27 февр. 2025 г. в 20:01, Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>: > > Hi ALexander, > > On Thu, Feb 27, 2025 at 09:37:37AM +0300, Alexander Shiyan wrote: > > Hello All. > > > > I found that automounting does not work without a GPT table. > > So you mean it doesn't work when the device has a MBR instead of a GPT? > > > In the example below, it is not possible to automatically mount a > > partition from an MMC card. > > However, if I add the full paths to the command manually, everything works. > > > > barebox 2025.02.0-00690-ga6a0a0ba4f61 #12 Thu Feb 27 08:27:56 MSK 2025 > > Board: Mega-Milas MM-SM-SAMA5D2 > > AT91: Detected soc type: sama5d2 > > AT91: Detected soc subtype: sama5d27c_d1g > > ... > > sdhci-at91 b0000000.sdio-host@xxxxxxxxxxx: registered as mmc1 > > mmc1: detected SD card version 2.0 > > mmc1: registered mmc1 > > ... > > barebox@Mega-Milas Informer SAMA5D2:/ ls /mnt/mmc1.0 > > mount: Device or resource busy > > -EBUSY is a strange error code from mount(). Can you follow where it > comes from? > > I can't reproduce it here. I tried both with a MBR and a GPT. > > Sascha > > > -- > Pengutronix e.K. | | > Steuerwalder Str. 21 | http://www.pengutronix.de/ | > 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
