Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 28 Jul 2017 22:37:44 +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:  <20170728223744.a94ce254.freebsd@edvax.de>
In-Reply-To: <a491848b72ef4dc2282175cccf09e115.squirrel@webmail.harte-lyne.ca>
References:  <a491848b72ef4dc2282175cccf09e115.squirrel@webmail.harte-lyne.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 28 Jul 2017 16:32:24 -0400, James B. Byrne wrote:
> I inserted one of the other usb sticks that were involved with the
> initial incident and see this:
> 
> ugen3.2: <Verbatim> at usbus3
> umass0: <Verbatim STORE N GO, class 0/0, rev 2.00/1.10, addr 2> on usbus3
> umass0:  SCSI over Bulk-Only; quirks = 0xc100
> umass0:5:0: Attached to scbus5
> da0 at umass-sim0 bus 0 scbus5 target 0 lun 0
> da0: <Verbatim STORE N GO 5.00> Removable Direct Access SCSI device
> da0: Serial Number 078610A01958
> da0: 40.000MB/s transfers
> da0: 1911MB (3913728 512 byte sectors)
> da0: quirks=0x2<NO_6_BYTE>

It does not detach - so far, so good.



> Looking at /var/log/messages I see this:
> 
> # tail /var/log/messages
> Jul 28 16:14:46 vhost04 kernel: ugen3.2: <Verbatim> at usbus3
> Jul 28 16:14:46 vhost04 kernel: umass0: <Verbatim STORE N GO, class
> 0/0, rev 2.00/1.10, addr 2> on usbus3
> Jul 28 16:14:46 vhost04 kernel: umass0:  SCSI over Bulk-Only; quirks =
> 0xc100
> Jul 28 16:14:46 vhost04 kernel: umass0:5:0: Attached to scbus5
> Jul 28 16:14:46 vhost04 kernel: da0 at umass-sim0 bus 0 scbus5 target
> 0 lun 0
> Jul 28 16:14:46 vhost04 kernel: da0: <Verbatim STORE N GO 5.00>
> Removable Direct Access SCSI device
> Jul 28 16:14:46 vhost04 kernel: da0: Serial Number 078610A01958
> Jul 28 16:14:46 vhost04 kernel: da0: 40.000MB/s transfers
> Jul 28 16:14:46 vhost04 kernel: da0: 1911MB (3913728 512 byte sectors)
> Jul 28 16:14:46 vhost04 kernel: da0: quirks=0x2<NO_6_BYTE>
> 
> 
> But this does not mount either.  However, the message is different:
> 
> Cannot mount volume
> Unable to mount the volume 'CA_HLL_2016'.
> 
> Mount: /dev/ext2fs/CA_HLL_2016: Operation not supported by device

I'm not sure if it's trying to mount da0 or da0s1.

Is manual mounting possible, for example

	# mount -t ext2fs -o ro /dev/da0s1 /mnt

with sufficient permissions (e- g- try as root first, then unmount,
and then try as regular user).



> gpart list da0
> Geom name: da0
> modified: false
> state: OK
> fwheads: 255
> fwsectors: 63
> last: 3913727
> first: 1
> entries: 4
> scheme: MBR
> Providers:
> 1. Name: da0s1
>    Mediasize: 2003522560 (1.9G)
>    Sectorsize: 512
>    Stripesize: 0
>    Stripeoffset: 31744
>    Mode: r0w0e0
>    rawtype: 131
>    length: 2003522560
>    offset: 31744
>    type: linux-data
>    index: 1
>    end: 3913191
>    start: 62
> Consumers:
> 1. Name: da0
>    Mediasize: 2003828736 (1.9G)
>    Sectorsize: 512
>    Mode: r0w0e0

Here, "linux-data" (type 131) is correct, and you need to mount
the partition da0s1.



-- 
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?20170728223744.a94ce254.freebsd>