Unable to mount USB Flash memory created on CentOS
bourne.identity at hotmail.com
Sat Jul 29 10:26:40 UTC 2017
On 07/29/17 14:31, Polytropon wrote:
> On Fri, 28 Jul 2017 16:58:15 -0400, James B. Byrne wrote:
>> This is the second (of three) stick involved.
>> ugen3.3: <Kingston> at usbus3
>> umass1: <Kingston DataTraveler 2.0, class 0/0, rev 2.00/1.00, addr 3>
>> on usbus3
>> umass1: SCSI over Bulk-Only; quirks = 0xc100
>> umass1:6:1: Attached to scbus6
>> da1 at umass-sim1 bus 1 scbus6 target 0 lun 0
>> da1: <Kingston DataTraveler 2.0 6.00> Removable Direct Access SCSI-2
>> da1: Serial Number 09B17B4031F15E08
>> da1: 40.000MB/s transfers
>> da1: 489MB (1001472 512 byte sectors)
>> da1: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>
>> WARNING: R/W mount denied. Filesystem is not clean - run fsck
>> # gpart show da1
>> => 32 1001440 da1 MBR (489M)
>> 32 31 - free - (16K)
>> 63 1001409 1 linux-data [active] (489M)
> And here you can see the correct identification for the
> Linux partition (compared to the initial example).
>> fsck /dev/da1
>> fsck: Could not determine filesystem type
>> So, what argument to I pass to fsck -t ??? /dev/da1 ?
> 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.
I am not trying to reply to OP - you can do that better. But there is
something relevant that I would like to mention for this issue.
There is a significant problem with the ext2fs driver under FreeBSD. I
earlier thought this was perhaps a niggling issue, but this post
inclines me to mention it.
Create an ext2 partition and use it for a while. When there is an
improper shutdown/unclean umount, I experienced this syndrome 3 times in
the last 3 months : FreeBSD will refuse to mount the partition RW (which
is correct) - but then FreeBSD e2fsck will not be able to complete a
successful fsck. I think the error message from e2fsck used to be :
failed + run fsck. No further details. I don't remember what fsck used
to report, but nothing worked.
The only way to correct the situation always was - boot into Linux (I
use Parrot Lite), run e2fsck therein, and then mount it RW. Then get
back to FreeBSD, and now the partition gets mounted coolly.
If OP continues to suffer something similar, perhaps he can try fixing
things under Linux ?
More information about the freebsd-questions