mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Philippe Leduc <ledphilippe@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: mount fat regression
Date: Thu, 25 Feb 2016 11:52:32 +0100	[thread overview]
Message-ID: <CABQt-Uk2HA52EHFwB3QtQ7rK3CrKs-Ad-XoOuQ_3ct8xfVGekg@mail.gmail.com> (raw)
In-Reply-To: <CABQt-Um_GjFByhbMocKc3x1E9Wd=_gQenAPNYN66tFzFAjKQdQ@mail.gmail.com>

Hi again,

Thanks to you (and the filetype command), I found the root of the
problem and what happened in barebox that change the behavior.
The commit bc87f4399c6a290d820f2dd00ef772f0f3ef8767 change the
behavior of the MBR detection, and it is the right thing to do. I
discover that fatfs default behavior is to create a fdisk partition
table while I though it was a SFD one, so my addpart was wrong.

Modifiying the f_mkfs option resolve the problem.

Thank you for the help and sorry to bother you with this report.

Best regards,

--
Philippe LEDUC
ledphilippe@gmail.com


2016-02-25 11:23 GMT+01:00 Philippe Leduc <ledphilippe@gmail.com>:
>> Can you mount the same device with the -tfat option to mount?
> Well same problem: mount: No such file or directory
>
>> I assume it's a GPT partition, right?
> It isn't: there is no partition table, it is directly the FS on it.
>
>> That's your problem.With /dev/mmc2.netcom detected as MBR barebox won't
> automatically try to mount a FAT filesystem.
> Of course it is, and if the method I am currently using to create the
> FS is wrong, I'll change that, don't worry :)
>
> Regards,
>
> --
> Philippe LEDUC
> ledphilippe@gmail.com
>
>
> 2016-02-25 10:51 GMT+01:00 Sascha Hauer <s.hauer@pengutronix.de>:
>> On Thu, Feb 25, 2016 at 10:37:35AM +0100, Philippe Leduc wrote:
>>> Hi,
>>>
>>> This was working before :) (at least with barebox version 2015.10).
>>> Honestly , this may be a misconfiguration on our part (and the fact
>>> that it worked doesn't mean that it was a normal behavior).
>>>
>>> Here is the output:
>>> filetype  /dev/mmc2.netcom
>>> /dev/mmc2.netcom: MBR sector (mbr)
>>
>> That's your problem. With /dev/mmc2.netcom detected as MBR barebox won't
>> automatically try to mount a FAT filesystem.
>> What is /dev/mmc2.netcom anyway? I assume it's a GPT partition, right?
>>
>> Can you mount the same device with the -tfat option to mount?
>>
>> Sascha
>>
>> --
>> Pengutronix e.K.                           |                             |
>> Industrial Linux Solutions                 | http://www.pengutronix.de/  |
>> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
>> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2016-02-25 10:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 16:44 Philippe Leduc
2016-02-25  8:56 ` Sascha Hauer
2016-02-25  9:37   ` Philippe Leduc
2016-02-25  9:42     ` Philippe Leduc
2016-02-25  9:51     ` Sascha Hauer
2016-02-25 10:23       ` Philippe Leduc
2016-02-25 10:52         ` Philippe Leduc [this message]

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=CABQt-Uk2HA52EHFwB3QtQ7rK3CrKs-Ad-XoOuQ_3ct8xfVGekg@mail.gmail.com \
    --to=ledphilippe@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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