All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Hutchinson <b.hutchman@gmail.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: 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"
Date: Mon, 1 Aug 2016 09:21:01 -0400	[thread overview]
Message-ID: <CAFZh4h820UUrUORaVcnvHa_4EpUhhFXdCTNco102hs9qytSz7w@mail.gmail.com> (raw)
In-Reply-To: <CAFZh4h_h5mU9_dDRiu84p56y+x80_J85q=LjQsy=3DTZt4jw_Q@mail.gmail.com>

> 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.


  parent reply	other threads:[~2016-08-01 13:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2016-08-01 20:47     ` Brian Hutchinson
2016-08-02 13:05       ` Brian Hutchinson

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=CAFZh4h820UUrUORaVcnvHa_4EpUhhFXdCTNco102hs9qytSz7w@mail.gmail.com \
    --to=b.hutchman@gmail.com \
    --cc=yocto@yoctoproject.org \
    /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 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.