Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 28 Jul 2017 22:15:38 +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:  <20170728221538.0e3f67dd.freebsd@edvax.de>
In-Reply-To: <90e704300c61366098d9f0e53a66e35e.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> <90e704300c61366098d9f0e53a66e35e.squirrel@webmail.harte-lyne.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 28 Jul 2017 16:12:49 -0400, James B. Byrne wrote:
> I plugged in a different USB key and I see this message box:
> 
> Cannot mount volume
> Unable to mount the volume 'CA_HLL'
> 
> Details
> mount: /dev/ext2fs/CA_HLL: Operation not permitted
> 
> I then plugged in a FreeBSD installer image usb and that mounted
> without difficulty.
> 
> Looking at /var/log/messages I see this:
> 
> Jul 28 16:08:15 vhost04 kernel: umass0: <Kingston DataTraveler 2.0,
> class 0/0, rev 2.00/1.00, addr 2> on usbus3
> Jul 28 16:08:15 vhost04 kernel: umass0:  SCSI over Bulk-Only; quirks =
> 0xc100
> Jul 28 16:08:15 vhost04 kernel: umass0:5:0: Attached to scbus5
> Jul 28 16:08:15 vhost04 kernel: da0 at umass-sim0 bus 0 scbus5 target
> 0 lun 0
> Jul 28 16:08:15 vhost04 kernel: da0: <Kingston DataTraveler 2.0 6.00>
> Removable Direct Access SCSI-2 device
> Jul 28 16:08:15 vhost04 kernel: da0: Serial Number 09B17B4031F15E08
> Jul 28 16:08:15 vhost04 kernel: da0: 40.000MB/s transfers
> Jul 28 16:08:15 vhost04 kernel: da0: 489MB (1001472 512 byte sectors)
> Jul 28 16:08:15 vhost04 kernel: da0: quirks=0x3<NO_SYNC_CACHE,NO_6_BYTE>
> Jul 28 16:08:16 vhost04 kernel: WARNING: R/W mount denied.  Filesystem
> is not clean - run fsck

So here you have the answer: The file system needs to be brought
into a consistent state again (using fsck), and then it will
probably mount without problems again. You have now discovered
the "joy" of using magical automounters. ;-)



-- 
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?20170728221538.0e3f67dd.freebsd>