Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 23 Jun 2012 09:21:28 +0200
From:      "O. Hartmann" <ohartman@zedat.fu-berlin.de>
To:        Hans Petter Selasky <hselasky@c2i.net>
Cc:        Garrett Cooper <yanegomi@gmail.com>, freebsd-current@freebsd.org, freebsd-questions@freebsd.org
Subject:   Re: USB system: FreeBSD 9-STABLE and 10-CURRENT do not recognize 64GB USB drive while Linux and Windows do
Message-ID:  <4FE56E78.8010000@zedat.fu-berlin.de>
In-Reply-To: <201206220822.19486.hselasky@c2i.net>
References:  <4FE40A42.6010503@zedat.fu-berlin.de> <201206220822.19486.hselasky@c2i.net>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig584D47E519C615C3D36026F7
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

On 06/22/12 08:22, Hans Petter Selasky wrote:
> On Friday 22 June 2012 08:01:38 O. Hartmann wrote:
>> I have a USB drive/stick, Lexar USB Flash drive as reported by FreeBSD=

>> shown below.
>> When first used, I was able to put approx. 30 GB of data on it - it wa=
s
>> visible to FreeBSD 9 and 10 as expected.
>> A Linux system at the lab was also capable of recognizing it. After
>> that, I tried to operate on the stick on a Notebook, FreeBSD 9, and
>> another station, FreeBSD 10. But FreeBSD didn't recognize the USB driv=
e
>> anymore - sometimes, but this seems to be a gambling issue :-(
>>
>> Trying Linux on different hardware platforms and even those machines
>> prior not recognizing the USB drive do recognize the drive as Lexar US=
B
>> Flash drive with 64GB. That is Suse Linux (some 12.XX), that is Ubuntu=

>> 12.04, that is Windows 7 Pro/x64. I can format the drive, I can push a=
nd
>> pull data from it.
>>
>> So, since the USB drive won't work with three different FreeBSD boxes
>> (one running 9-STABLE, two 10-CURRENT, all systems most recent sources=

>> and buildworld from a day ago).
>> I suspect either a weird configuration issue I use on all platforms in=

>> questions in common triggering the weird beviour - or FreeBSD is simpl=
y
>> incapable of handling the 64GB drive. I do not have issues with USB
>> drives with capacities of 32, 8 or 4 GB of different brands.
>>
>> As shown in the portion of the dmesg below, the USB drive is recognize=
d
>> physically. It doesn't matter whether USB port I use (I tried all
>> available on all boxes and in most cases I use a Dell UltraSharp power=
ed
>> in-screen HUB). Since other OSes handle the drive as expected, I exclu=
de
>> hardware issues.
>>
>> All FreeBSD in common is the fact I use the new device ahaci/device at=
a
>> CAM/ATA scheme with devcie scbus in the kernel (I use custom kernels!)=
=2E
>>
>> Apart from trying a GENERIC kernel (which is next I will do this
>> weekend), does anyone have similar experiences and probably solutions?=

>>
>> Regards,
>> oh
>>
>> ugen7.6: <Lexar> at usbus7
>> umass1: <Lexar USB Flash Drive, class 0/0, rev 2.00/11.00, addr 6> on
>> usbus7 (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0
>> (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an e=
rror
>> (probe0:umass-sim1:1:0:0): Retrying command
>> (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0
>> (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an e=
rror
>> (probe0:umass-sim1:1:0:0): Retrying command
>> (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0
>> (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an e=
rror
>> (probe0:umass-sim1:1:0:0): Retrying command
>> (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0
>> (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an e=
rror
>> (probe0:umass-sim1:1:0:0): Retrying command
>> (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12 0 0 0 24 0
>> (probe0:umass-sim1:1:0:0): CAM status: CCB request completed with an e=
rror
>> (probe0:umass-sim1:1:0:0): Error 5, Retries exhausted
>=20
> Hi,
>=20
> After plugging the device, try:
>=20
> usbconfig -d 7.6 add_quirk UQ_MSC_NO_INQUIRY
>=20
> Then re-plug it.
>=20
> I'm sorry to say a lot of USB flash sticks out there are broken and onl=
y=20
> tested with the timing of MS Windows. Part of the problem is that it is=
=20
> difficult to autodetect these issues, because once you trigger the non-=

> supported SCSI command, then the flash key stops working like you exper=
ience.
>=20
> I would be more than glad to open up an office to certify USB devices f=
or use=20
> with FreeBSD :-)
>=20
> --HPS
>=20

I tried the USB drive this morning with the recommended quirk shown
above on FreeBSD 10.0-CURRENT #1 r237462: Sat Jun 23 01:00:35 CEST 2012
without success. I get the same error message as shown above. With or
without quirk.

I then started Windows 7 on the same box. The USB drive is seen as
expected and reflects what I experienced on every other non-FreeBSD box
and hardware in the lab on last week.
I reformatted the USB drive with extFAT and standard block size on
Windows 7. The USB drive is now seen again on FreeBSD and recognized as
a drive. "Seen" in my sloppy terminology means: recognized as a disk.
The hardware is recognized, but it is not recognized as a drive.

The fact, that the very first time after I bought that USB drive, I was
able to put several GB on it, use it on both FreeBSD 9-STABLE and
10-CURRENT, and then it broke, drives me nuts.
Using the very same pen drive on other OSes even on the same hardware
without issues makes me believe FreeBSD does have an issue, not the USB
drive.

I will fill the USB drive with data and try to use it very often on
FreeBSD. Last time the error occured, it was read by a Suse Linux box.
If I wouldn't know better I would say Linux tries to kill the USB drive
=2E.. But Linux did see it all the time. A "usual customer" would see it
the same way, I guess.

I will test and report next week when I have access to the other boxes
and OSes again.

Regards,
Oliver


--------------enig584D47E519C615C3D36026F7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iQEcBAEBAgAGBQJP5W5+AAoJEOgBcD7A/5N8S08IAMoRaVBo8yBtSqfevZxlO74I
sudU6TJxvi1OTgbo2C94dndlCiepIPypoB4b96V3oEoCnRyed5oWei+Z97q7kbcF
fQgOkWuG19GPfTGHpB6QZQhh5KVs/1U3sJliT01IYjyBnUwtTrnbE4i/l5yhfUXs
nvorZZORQBasx9MUldeD1CLnN3lVUhqyARMMgewmMCn5OhZtbK5EV6c4+sIiZ6ux
eFA1r25aK2TjsHzaJauGydRfveyeXwVP9+KSlrg5bYRb8/mZd/duoN8BARzqUg/b
LnoTLZ92lu8Fy0NnM5z1Eb4On/ifZJe0FwqRIvlDdgIxZpWFbERzlZyCVKrx0Ls=
=009J
-----END PGP SIGNATURE-----

--------------enig584D47E519C615C3D36026F7--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FE56E78.8010000>