Actions
Bug #2822
openUSB 3.0 stick throws "reading primary partition table: error accessing offset 000[...] for 152" error, while the stick works on any other OS I tested
Start date:
06/03/2015
Due date:
% Done:
0%
Estimated time:
Description
My USB 3.0 stick (fat32 formatted) works great on other Windows / Linux and OpenBSD operating systems. On the stable DragonFly (and after that on "DragonFly-x86_64-20150601-DEV-v4.1.0.1545"-image, I get the usual message instantly after putting it into one of my USB 2.0 ports (of my ThinkPad X200s):
- umass0: <vendor 0x13fe Patriot Memory, class 0/0, rev 2.10/1.00, addr 2> on usbus3
- disk scheduler: set policy of da8 to noop
- da8 at umass-sim0 bus 0 target 0 lun 0
- da8: < Patriot Memory PMAP> Removable Direct Access SCSI-6 device
- da8: 40.000MB/s transfers
- da8: 30176MB (61800448 512 byte sectors: 255H 63S/T 3846C)
- da8: reading primary partition table: error accessing offset 000000000000 for 512
which prevents me from mounting/using the stick.
Other (USB 2.0 sticks) working great instead.
I've attached dmesg and pciconf -lv output. Please let me know I I could provide any more details.
Over IRC I got a hint that it could be "an unfortunate collaboration of the usb stack and our cam", which could probably helpful.
Thanks in advance for any help.
Files
Updated by revuwa almost 10 years ago
- File usbconfig.txt usbconfig.txt added
added: usbconfig attachment. The USB 3.0 stick ist the "Patriot Memory" one.
Updated by revuwa almost 10 years ago
Of course I tried USB 3.0 ports, too (with the same problem).
This was my first idea, because I tried to put my USB 2.0 stick into USB 3.0 port and this doesn't work, too (but is not my problem here).
Updated by liweitianux almost 9 years ago
- Related to Bug #2917: da8: reading primary partition table: error accessing offset 000000000000 for 512 added
Actions