Date: Sat, 29 Jul 2017 11:08:46 +0200 From: Polytropon <freebsd@edvax.de> To: byrnejb@harte-lyne.ca Cc: freebsd-questions@freebsd.org Subject: Re: Unable to mount USB Flash memory created on CentOS Message-ID: <20170729110846.1aee813d.freebsd@edvax.de> In-Reply-To: <2fa4faefe556b51407e49f7e4cf7ca25.squirrel@webmail.harte-lyne.ca> References: <aa1eadff2a815bacb69dc015b4aa1f4f.squirrel@webmail.harte-lyne.ca> <20170728205144.c1fc18df.freebsd@edvax.de> <4a5c3fd942ff8566eefaaf9c990abba0.squirrel@webmail.harte-lyne.ca> <20170728212432.7be758bc.freebsd@edvax.de> <32ee693f24a1725290b47822cfd8bc9e.squirrel@webmail.harte-lyne.ca> <20170728220016.21aa7c83.freebsd@edvax.de> <1686132f906448c4e88d02f865da9a14.squirrel@webmail.harte-lyne.ca> <04a03226734f7cefe427b492a733b329.squirrel@webmail.harte-lyne.ca> <2fa4faefe556b51407e49f7e4cf7ca25.squirrel@webmail.harte-lyne.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 28 Jul 2017 17:19:51 -0400, James B. Byrne wrote:
>
> On Fri, July 28, 2017 17:16, James B. Byrne wrote:
>
> >
> > fstyp /dev/da0s1
> > msdosfs
> >
> > But that does not seem right. This usb stick was filled using rsync.
> >
>
>
> Nonetheless, this works:
>
> # mount -t msdosfs -o ro /dev/da0s1 /mnt/usb01
> # ll /mnt/usb01
> total 112
> drwxr-xr-x 1 root wheel 16384 Jun 17 2016 .Spotlight-V100
> drwxr-xr-x 1 root wheel 16384 Jun 17 2016 .Trashes
> -rwxr-xr-x 1 root wheel 4096 Jun 17 2016 ._.Trashes
> drwxr-xr-x 1 root wheel 16384 Jun 17 2016 .fseventsd
> drwxr-xr-x 1 root wheel 16384 Mar 23 14:55 System Volume Information
> drwxr-xr-x 1 root wheel 16384 Jul 5 08:24 vhost04
> drwxr-xr-x 1 root wheel 16384 Jul 5 08:23 xnet241
So do you expect _two_ partitions on that USB stick, one with
some MS-DOS stuff, one with Linux data? Or maybe this is some
manufacturer-supplied "recovery partition"? Or even worse, the
Linux data files are now somehow accessible via a MS-DOS file
system? I have _no_ idea if (or how) this is possible... still
if you look at the file sizes, they look all the same. Maybe
this is a mix of things that were present on the stick upon
production ("pre-formatted")?
I'll say it again: You could try to repair or reinstantiate
the ext2 file system (using Linux, it's the best guess I have),
or completely reinitialize (reformat) the file system (with
data loss).
That is how it looks to me.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170729110846.1aee813d.freebsd>