On Mon, Aug 1, 2016 at 4:47 PM, Brian Hutchinson wrote:
> 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.
>
> W
On Mon, Aug 1, 2016 at 9:21 AM, Brian Hutchinson 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 simil
> 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
On 2016-08-01 15:06, Brian Hutchinson wrote:
On Mon, Aug 1, 2016 at 8:56 AM, Brian Hutchinson 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
On Mon, Aug 1, 2016 at 8:56 AM, Brian Hutchinson 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 /
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 c
