Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 31 Jul 2017 11:49:52 -0400
From:      "James B. Byrne" <byrnejb@harte-lyne.ca>
To:        "Polytropon" <freebsd@edvax.de>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Unable to mount USB Flash memory created on CentOS
Message-ID:  <72688c988dae728f8fe92593aa464dc7.squirrel@webmail.harte-lyne.ca>
In-Reply-To: <20170729110144.1cce7c70.freebsd@edvax.de>
References:  <a491848b72ef4dc2282175cccf09e115.squirrel@webmail.harte-lyne.ca> <20170728223744.a94ce254.freebsd@edvax.de> <fc164e1b20c58429cb8f5dbb5ae876b5.squirrel@webmail.harte-lyne.ca> <20170729110144.1cce7c70.freebsd@edvax.de>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
Lest it be lost in the minutiae of solving this difficulty I thank you
for all your help.


On Sat, July 29, 2017 05:01, Polytropon wrote:
>
> I'd suggest you use the Linux native fsck (e2fsck). If I
> remember correctly, there is also an "ext2 fsck" in the
> port e2fsprogs with the same name.
>
> Or maybe it came with FUSE?
>
> Basically, you'd so something like
>
> 	# fsck -t ext2 /dev/da1
>
> or, as I mentioned,
>
> 	# e2fsck /dev/da1
>
> An automatic file system type detection relies on an entry
> in /etc/fstab, which you don't have, so you need to specify
> the FS type manually.
>
>

When I try to verify the flash drives I see this:

# e2fsck /dev/da1
e2fsck 1.43.4 (31-Jan-2017)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/da1
. . .

So I redid the command using the partition values instead:

# e2fsck /dev/da0s1
e2fsck 1.43.4 (31-Jan-2017)
CA_HLL_2016_BKUP has gone 267 days without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Error writing file system info: Invalid argument

CA_HLL_2016_BKUP: ***** FILE SYSTEM WAS MODIFIED *****

However, the device remains unmountable in Mate.

This issue is not critical as I am able to manually mount both devices
and have successfully moved their contents onto new media.  But I do
find it annoying that Mate, or whatever process caused the initial
problem, was able to create the problem and yet there is no
self-evident way of correcting whatever injury was done to the
filesystems.

-- 
***          e-Mail is NOT a SECURE channel          ***
        Do NOT transmit sensitive data via e-Mail
 Do NOT open attachments nor follow links sent by e-Mail

James B. Byrne                mailto:ByrneJB@Harte-Lyne.ca
Harte & Lyne Limited          http://www.harte-lyne.ca
9 Brockley Drive              vox: +1 905 561 1241
Hamilton, Ontario             fax: +1 905 561 0757
Canada  L8E 3C3




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?72688c988dae728f8fe92593aa464dc7.squirrel>