From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alexander Shiyan <eagle.alexander923@gmail.com>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: automount doesn't work without GPT table
Date: Thu, 27 Feb 2025 18:00:59 +0100 [thread overview]
Message-ID: <Z8CaS4gLesWjG81q@pengutronix.de> (raw)
In-Reply-To: <CAP1tNvToG8WGLUo4_e2dSdovFZBAbcdOFUqm+F+W4gWoaVnrgQ@mail.gmail.com>
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@b0000000.of: 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 |
next prev parent reply other threads:[~2025-02-27 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 6:37 Alexander Shiyan
2025-02-27 17:00 ` Sascha Hauer [this message]
2025-02-28 6:06 ` Alexander Shiyan
2025-02-28 8:05 ` Sascha Hauer
2025-02-28 8:18 ` Alexander Shiyan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z8CaS4gLesWjG81q@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=eagle.alexander923@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox