[DragonFlyBSD - Bug #2917] da8: reading primary partition table: error accessing offset 000000000000 for 512

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #2917 has been updated by swildner.


How was the stick written exactly?


----------------------------------------
Bug #2917: da8: reading primary partition table: error accessing offset 000000000000 for 512
http://bugs.dragonflybsd.org/issues/2917#change-12911

* Author: liweitianux
* Status: New
* Priority: Normal
* Assignee: 
* Category: Driver
* Target version: 
----------------------------------------
Hello,

Recently, I tried to install DragonFly BSD on my old ThinkPad X200 with both the 20160512-snapshot and 4.4.3-release USB image.  However, DragonFly failed to mount root from the USB device.

I enabled the verbose boot, and got the following error message:
----------------------------------------------------------------
(da8:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR
(da8:umass-sim0:0:0:0): Retrying Command
...
(da8:umass-sim0:0:0:0): error 5
(da8:umass-sim0:0:0:0): Retries Exhausted
da8: reading primary partition table: error accessing offset 000000000000 for 512
Mounting root from ufs:da8s1a
no disk named 'da8s1a'
setrootbyname failed
ffs_mountroot: can't find rootvp
kthread 0xffffffe02050d700 syncer3 has exited
Root mount failed: 6
----------------------------------------------------------------

And there does not exist the 'da8s1a' device when listing:
----------------------------------------------------------------
mountroot> ?
Possibly valid devices for root FS:
 "vn0"  "vn1"  "vn2"  "vn3"  "md0"  "md0s0"  "sg8"  "sg0"  "da8"  "da0"  "da0s1"  "da0s2"  "da0s5"  "da0s6"  "da0s7"  "mapper/control"
----------------------------------------------------------------

I also tried to disable the "xhci" load, but the same issue remained.

On the other hand, I tried to install FreeBSD (11-current) on that laptop and succeeded.  And I can read the same USB device (with the DragonFly image dd'd into it) under FreeBSD (with the "geom_part_bsd64" module loaded).

P.S.:
I noticed there already existed a related bug report #2822 with this similar issue.  But I think this bug may not related with the USB3.0, but very likely due to the CAM, and that bug stalls for a long time.  Therefore I decide to open a new bug report.

It's my pleasure to provide any further information if necessary.


Best regards!
Aly



-- 
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