From owner-freebsd-questions@freebsd.org Sat Jul 29 09:08:51 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E86EADBF06F for ; Sat, 29 Jul 2017 09:08:51 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay15.qsc.de (mailrelay15.qsc.de [212.99.187.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 54E65651FB for ; Sat, 29 Jul 2017 09:08:50 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay15.qsc.de; Sat, 29 Jul 2017 11:08:47 +0200 Received: from r56.edvax.de (port-92-195-203-176.dynamic.qsc.de [92.195.203.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id C18723CC42; Sat, 29 Jul 2017 11:08:46 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id v6T98k7l002035; Sat, 29 Jul 2017 11:08:46 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sat, 29 Jul 2017 11:08:46 +0200 From: Polytropon 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: <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> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay15.qsc.de with 0C7FB6834DA X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1349 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Jul 2017 09:08:52 -0000 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, ...