[DragonFlyBSD - Bug #2822] (New) USB 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

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Wed Jun 3 13:54:53 PDT 2015


Issue #2822 has been reported by revuwa.

----------------------------------------
Bug #2822: USB 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
http://bugs.dragonflybsd.org/issues/2822

* Author: revuwa
* Status: New
* Priority: Normal
* Assignee: 
* Category: Unverifiable
* Target version: Unverifiable
----------------------------------------
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

now I have to wait a few seconds and get the rest of the usual messages:
# 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)

after a few seconds more I get the final message:
# 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--------------------------------
dmesg.txt (12.3 KB)
pciconf.txt (5.51 KB)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



More information about the Bugs mailing list