* Yocto 1.8.1 - Insert USB VFAT thumb drive results in "Volume was not properly unmounted. Some data may be corrupt. Please run fsck"
@ 2016-08-01 12:56 Brian Hutchinson
2016-08-01 13:06 ` Brian Hutchinson
0 siblings, 1 reply; 6+ messages in thread
From: Brian Hutchinson @ 2016-08-01 12:56 UTC (permalink / raw)
To: yocto
If the USB drive is cold plugged (inserted before power on) it mounts
fine, it is only a hotplug that results in the message "Volume was not
properly unmounted. Some data may be corrupt. Please run fsck"
The drive is mounted under /run/media/sdb1 but a listing of the
directory just shows strange characters for the file names.
Installed dosfstools on target and running fsck.vfat doesn't report a
problem. Inserting the exact same USB drive in a Ubuntu 14.04 box
works fine so it isn't the USB drive.
Found this thread talking about the problem I'm seeing (link below)
and a bug report that sounds similar to what I'm seeing but I never
really saw what the issue is and it says it's been fixed in Yocto
1.8.3 but I don't see a Yocto 1.8.3 release ... only Yocto 1.8.2.
https://lists.yoctoproject.org/pipermail/yocto/2015-September/026563.html
https://bugzilla.yoctoproject.org/show_bug.cgi?id=9652/
When I run the mount command it says the USB drive is mounted as:
type vfat (rw,relatime,gid=6,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
I'm running a 4.4.1 kernel built outside of Yocto on a TI 816x SoC.
Anyone have any information on what the issue may be? I've played
around with my kernel .config thinking it was something there but that
didn't make any difference. Kinda stumped at the moment.
Regards,
Brian
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Yocto 1.8.1 - Insert USB VFAT thumb drive results in "Volume was not properly unmounted. Some data may be corrupt. Please run fsck"
2016-08-01 12:56 Yocto 1.8.1 - Insert USB VFAT thumb drive results in "Volume was not properly unmounted. Some data may be corrupt. Please run fsck" Brian Hutchinson
@ 2016-08-01 13:06 ` Brian Hutchinson
2016-08-01 13:15 ` Gary Thomas
2016-08-01 13:21 ` Brian Hutchinson
0 siblings, 2 replies; 6+ messages in thread
From: Brian Hutchinson @ 2016-08-01 13:06 UTC (permalink / raw)
To: yocto
On Mon, Aug 1, 2016 at 8:56 AM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
> If the USB drive is cold plugged (inserted before power on) it mounts
> fine, it is only a hotplug that results in the message "Volume was not
> properly unmounted. Some data may be corrupt. Please run fsck"
>
> The drive is mounted under /run/media/sdb1 but a listing of the
> directory just shows strange characters for the file names.
>
> Installed dosfstools on target and running fsck.vfat doesn't report a
> problem. Inserting the exact same USB drive in a Ubuntu 14.04 box
> works fine so it isn't the USB drive.
>
> Found this thread talking about the problem I'm seeing (link below)
> and a bug report that sounds similar to what I'm seeing but I never
> really saw what the issue is and it says it's been fixed in Yocto
> 1.8.3 but I don't see a Yocto 1.8.3 release ... only Yocto 1.8.2.
>
> https://lists.yoctoproject.org/pipermail/yocto/2015-September/026563.html
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=9652/
>
> When I run the mount command it says the USB drive is mounted as:
>
> type vfat (rw,relatime,gid=6,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
>
> I'm running a 4.4.1 kernel built outside of Yocto on a TI 816x SoC.
>
> Anyone have any information on what the issue may be? I've played
> around with my kernel .config thinking it was something there but that
> didn't make any difference. Kinda stumped at the moment.
>
> Regards,
>
> Brian
This is the output of running fsck.vfat in case anyone cares. It
doesn't report anything about a "dirty bit" being set. Could it be
this version of dosfsck is too old?
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Starting check/repair pass.
Starting verification pass.
/dev/sdb1: 284 files, 60465/62894 clusters
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Yocto 1.8.1 - Insert USB VFAT thumb drive results in "Volume was not properly unmounted. Some data may be corrupt. Please run fsck"
2016-08-01 13:06 ` Brian Hutchinson
@ 2016-08-01 13:15 ` Gary Thomas
2016-08-01 13:21 ` Brian Hutchinson
1 sibling, 0 replies; 6+ messages in thread
From: Gary Thomas @ 2016-08-01 13:15 UTC (permalink / raw)
To: yocto
On 2016-08-01 15:06, Brian Hutchinson wrote:
> On Mon, Aug 1, 2016 at 8:56 AM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>> If the USB drive is cold plugged (inserted before power on) it mounts
>> fine, it is only a hotplug that results in the message "Volume was not
>> properly unmounted. Some data may be corrupt. Please run fsck"
>>
>> The drive is mounted under /run/media/sdb1 but a listing of the
>> directory just shows strange characters for the file names.
>>
>> Installed dosfstools on target and running fsck.vfat doesn't report a
>> problem. Inserting the exact same USB drive in a Ubuntu 14.04 box
>> works fine so it isn't the USB drive.
>>
>> Found this thread talking about the problem I'm seeing (link below)
>> and a bug report that sounds similar to what I'm seeing but I never
>> really saw what the issue is and it says it's been fixed in Yocto
>> 1.8.3 but I don't see a Yocto 1.8.3 release ... only Yocto 1.8.2.
>>
>> https://lists.yoctoproject.org/pipermail/yocto/2015-September/026563.html
>>
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=9652/
>>
>> When I run the mount command it says the USB drive is mounted as:
>>
>> type vfat (rw,relatime,gid=6,fmask=0007,dmask=0007,allow_utime=0020,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
>>
>> I'm running a 4.4.1 kernel built outside of Yocto on a TI 816x SoC.
>>
>> Anyone have any information on what the issue may be? I've played
>> around with my kernel .config thinking it was something there but that
>> didn't make any difference. Kinda stumped at the moment.
>>
>> Regards,
>>
>> Brian
>
> This is the output of running fsck.vfat in case anyone cares. It
> doesn't report anything about a "dirty bit" being set. Could it be
> this version of dosfsck is too old?
>
> dosfsck 2.11, 12 Mar 2005, FAT32, LFN
> Starting check/repair pass.
> Starting verification pass.
> /dev/sdb1: 284 files, 60465/62894 clusters
>
BTW, this behavior still exists in Poky/Yocto 2.1+ I was thinking
of filing a bug myself (I tried to look into the details, but I
could not figure out why the 'fsck' step didn't make the kernel
happy)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Yocto 1.8.1 - Insert USB VFAT thumb drive results in "Volume was not properly unmounted. Some data may be corrupt. Please run fsck"
2016-08-01 13:06 ` Brian Hutchinson
2016-08-01 13:15 ` Gary Thomas
@ 2016-08-01 13:21 ` Brian Hutchinson
2016-08-01 20:47 ` Brian Hutchinson
1 sibling, 1 reply; 6+ messages in thread
From: Brian Hutchinson @ 2016-08-01 13:21 UTC (permalink / raw)
To: yocto
> dosfsck 2.11, 12 Mar 2005, FAT32, LFN
> Starting check/repair pass.
> Starting verification pass.
> /dev/sdb1: 284 files, 60465/62894 clusters
Another update. After seeing guys on the Raspberry Pi forums
complaining about a similar thing they hinted that dosfstools was tool
old. Sure enough, I ran fsck.fat on the USB drive from my Ubuntu
machine and it came back with:
$ sudo fsck.fat -a /dev/sdg1
fsck.fat 3.0.26 (2014-03-07)
0x25: Dirty bit is set. Fs was not properly unmounted and some data
may be corrupt.
Automatically removing dirty bit.
Performing changes.
/dev/sdg1: 142 files, 60465/62894 clusters
... and now the USB drive mounts without complaint but I modified my
box with a mount.sh from a previous release trying to get to the
bottom of what was going on. Now I need to put everything back the
way it was (restore mount.sh from 1.8.1) and see if it is still a
problem.
My kernel had the USB-persist feature turned on when I first noticed
the problem so I'm not sure if left over files (not quite sure how the
feature keeps track of things) from that could cause problems.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Yocto 1.8.1 - Insert USB VFAT thumb drive results in "Volume was not properly unmounted. Some data may be corrupt. Please run fsck"
2016-08-01 13:21 ` Brian Hutchinson
@ 2016-08-01 20:47 ` Brian Hutchinson
2016-08-02 13:05 ` Brian Hutchinson
0 siblings, 1 reply; 6+ messages in thread
From: Brian Hutchinson @ 2016-08-01 20:47 UTC (permalink / raw)
To: yocto
On Mon, Aug 1, 2016 at 9:21 AM, Brian Hutchinson <b.hutchman@gmail.com> wrote:
>> dosfsck 2.11, 12 Mar 2005, FAT32, LFN
>> Starting check/repair pass.
>> Starting verification pass.
>> /dev/sdb1: 284 files, 60465/62894 clusters
>
> Another update. After seeing guys on the Raspberry Pi forums
> complaining about a similar thing they hinted that dosfstools was tool
> old. Sure enough, I ran fsck.fat on the USB drive from my Ubuntu
> machine and it came back with:
>
> $ sudo fsck.fat -a /dev/sdg1
> fsck.fat 3.0.26 (2014-03-07)
> 0x25: Dirty bit is set. Fs was not properly unmounted and some data
> may be corrupt.
> Automatically removing dirty bit.
> Performing changes.
> /dev/sdg1: 142 files, 60465/62894 clusters
>
>
> ... and now the USB drive mounts without complaint but I modified my
> box with a mount.sh from a previous release trying to get to the
> bottom of what was going on. Now I need to put everything back the
> way it was (restore mount.sh from 1.8.1) and see if it is still a
> problem.
>
> My kernel had the USB-persist feature turned on when I first noticed
> the problem so I'm not sure if left over files (not quite sure how the
> feature keeps track of things) from that could cause problems.
I restored the original version of /etc/udev/scripts/mount.sh and now
that I've cleared the "dirty bit" with the newer version of fsck.fat
on my Ubuntu box ... inserting the USB drive works but it is mounted
in /run/media/sdb1.
What's up with this run directory? Is this some new convention that
is to be preferred over the previous mount point which before was
/media/sdb1???
Regards,
Brian
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2016-08-02 13:05 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-08-01 12:56 Yocto 1.8.1 - Insert USB VFAT thumb drive results in "Volume was not properly unmounted. Some data may be corrupt. Please run fsck" Brian Hutchinson
2016-08-01 13:06 ` Brian Hutchinson
2016-08-01 13:15 ` Gary Thomas
2016-08-01 13:21 ` Brian Hutchinson
2016-08-01 20:47 ` Brian Hutchinson
2016-08-02 13:05 ` Brian Hutchinson
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.