Bug #2917
open
da8: reading primary partition table: error accessing offset 000000000000 for 512
0%
Description
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
Files
Updated by liweitianux over 8 years ago
- Related to 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 added
Updated by
Updated by liweitianux over 8 years ago
I wrote the DragonFly image to the USB stick under Linux (openSUSE Tumbleweed) with the "dd" command:
$ dd if=DragonFly-x86_64-20160512-IMG.img of=/dev/sdb bs=1M
where the "/dev/sdb" is my USB stick, and no other extra options used except the "bs=1M".
(The FreeBSD image was written using the same "dd" command under the same Linux system, and it worked well.)
I will give the latest DragonFly snapshot a try tonight and report back. (I'm in China, UTC+8:00)
Updated by liweitianux over 8 years ago
Hello,
I just tried the latest DragonFly snapshot (20160531) on my ThinkPad X200 but without luck, and the above issue remains the same. I checked the BIOS but found nothing special related to the USB.
On the other hand, I booted my new ThinkPad T450s with the same USB stick, and it worked and gave me the login.
The following information about my USB stick is extracted from the "dmesg.boot" with the working ThinkPad T450s:
------------------------------------------------------
da8: si_iosize_max:131072
da8 at umass-sim0 bus 0 target 0 lun 0
da8: <Netac OnlyDisk 1100> Removable Direct Access SCSI-4 device
da8: Serial Number AATN6P9DAV56PURL
da8: 40.000MB/s transfers
da8: 15474MB (31690752 512 byte sectors: 255H 63S/T 1972C)
da8: type 0xa5, start 63, end = 3887729, size 3887667 : OK
Mounting root from ufs:da8s1a
------------------------------------------------------
Hope it helps this issue.
Regards!
Aly
Updated by liweitianux over 8 years ago
Hello, I just tried to boot my ThinkPad X220 (another old laptop of mine) with the same prepared DragonFly USB stick. However, the same issue occurred on this ThinkPad X220 as that X200, and the boot process hung at the.
On the other hand, I checked the dmesg.boot from the working T450s, and there are many duplicated messages of "boundary check failed" (about 220 times) and "alignment check failed" (about 90 times). I do not known whether these messages are related to this issue.
- ThinkPad X200 (7457-4AC): Intel Core 2 Duo P8400, Intel GM45+ICH9M
- ThinkPad X220 (4290-LY3): Intel Core i5-2430M, Intel QM67; (no USB3.0 support)
- ThinkPad T450s (20BX): Intel Core i3-5200U, USB3.0
Updated by liweitianux about 8 years ago
I think I found this bug is related to the "ehci" driver in DFly.
I took some efforts to make DFly run on my X220. Then I try to read the USB (2.0) stick from it, but it doesn't work with "ehci" driver loaded.
I tried following cases:
1. load "ehci" and "xhci"
2. load "ehci" only
3. load "xhci" only
4. neither "ehci" nor "xhci" loaded (i.e., only "ohci" which is built-in to the kernel)
The USB stick has "I/O error" for cases 1 and 2 (with "ehci"), but works for cases 3 and 4 (without "ehci")
The following is the dmesg for loading the "ehci" driver (I got these messages by first unloading and then loading the "ehci" driver):
------------------------------------------------------
Sep 2 00:20:28 aly-x200 kernel: ehci0: <Intel 82801I (ICH9) USB 2.0 controller> mem 0xf2826c00-0xf2826fff irq 23 at device 26.7 on pci0
Sep 2 00:20:28 aly-x200 kernel: usbus3: EHCI version 1.0
Sep 2 00:20:28 aly-x200 kernel: usbus3 on ehci0
Sep 2 00:20:38 aly-x200 kernel: WARNING waiting for the following device to finish configuring:
Sep 2 00:20:38 aly-x200 kernel: usb: func=0xffffffff808c4d37 arg=0xffffffe094e92cd8
Sep 2 00:20:38 aly-x200 kernel: Giving up, interrupt routing is probably hosed
Sep 2 00:20:38 aly-x200 kernel: usbus3: 480Mbps High Speed USB v2.0
Sep 2 00:20:38 aly-x200 kernel: ugen3.1: <Intel> at usbus3
Sep 2 00:20:38 aly-x200 kernel: ehci1: <Intel 82801I (ICH9) USB 2.0 controller> mem 0xf2827000-0xf28273ff irq 19 at device 29.7 on pci0
Sep 2 00:20:38 aly-x200 kernel: uhub3: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus3
Sep 2 00:20:38 aly-x200 kernel: usbus7: EHCI version 1.0
Sep 2 00:20:38 aly-x200 kernel: usbus7 on ehci1
Sep 2 00:20:40 aly-x200 kernel: uhub3: 6 ports with 6 removable, self powered
Sep 2 00:20:48 aly-x200 kernel: WARNING waiting for the following device to finish configuring:
Sep 2 00:20:48 aly-x200 kernel: usb: func=0xffffffff808c4d37 arg=0xffffffe094e9bcd8
Sep 2 00:20:48 aly-x200 kernel: Giving up, interrupt routing is probably hosed
Sep 2 00:20:48 aly-x200 kernel: usbus7: 480Mbps High Speed USB v2.0
Sep 2 00:20:48 aly-x200 kernel: ugen7.1: <Intel> at usbus7
Sep 2 00:20:48 aly-x200 kernel: uhub7: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus7
Sep 2 00:20:51 aly-x200 kernel: uhub7: 6 ports with 6 removable, self powered
------------------------------------------------------
This is the attaching messages of the USB stick with "ehci" driver loaded:
------------------------------------------------------
Sep 2 00:15:55 aly-x200 kernel: ugen7.2: <Netac> at usbus7
Sep 2 00:15:55 aly-x200 kernel: umass0: <Netac OnlyDisk, class 0/0, rev 2.00/11.00, add
Sep 2 00:15:55 aly-x200 kernel: r 2>
Sep 2 00:15:55 aly-x200 kernel: on us
Sep 2 00:15:55 aly-x200 kernel: bus7
Sep 2 00:15:55 aly-x200 kernel: da8 at umass-sim0 bus 0
Sep 2 00:15:55 aly-x200 kernel: target
Sep 2 00:15:55 aly-x200 kernel: 0 lun
Sep 2 00:15:55 aly-x200 kernel: 0
Sep 2 00:15:55 aly-x200 kernel: da8: <Netac OnlyDisk 1100> Removable Direct Access SCSI-4 device
Sep 2 00:15:55 aly-x200 kernel: da8: Serial Number AATN6P9DAV56PURL
Sep 2 00:15:55 aly-x200 kernel: da8: 40.000MB/s transfers
Sep 2 00:15:55 aly-x200 kernel: da8: 15474MB (31690752 512 byte sectors: 255H 63S/T 1972C)
------------------------------------------------------
Then, the following messages also appeared in "/var/log/messages":
------------------------------------------------------
Sep 2 00:16:17 aly-x200 kernel: da8: reading primary partition table: error accessing offset 000000000000 for 512
Sep 2 00:16:45 aly-x200 kernel: da8: open removable media: no media present
Sep 2 00:17:29 aly-x200 kernel: da8: open removable media: no media present
------------------------------------------------------
This is the attaching messages of the USB stick WITHOUT "ehci" driver loaded:
------------------------------------------------------
Sep 2 00:18:47 aly-x200 kernel: ugen4.2: <Netac> at usbus4
Sep 2 00:18:47 aly-x200 kernel: umass0: <Netac OnlyDisk, class 0/0, rev 2.00/11.00, addr 2> on usbus4
Sep 2 00:18:48 aly-x200 kernel: da8 at umass-sim0 bus 0 target 0 lun 0
Sep 2 00:18:48 aly-x200 kernel: da8: <Netac OnlyDisk 1100> Removable Direct Access SCSI-4 device
Sep 2 00:18:48 aly-x200 kernel: da8: Serial Number AATN6P9DAV56PURL
Sep 2 00:18:48 aly-x200 kernel: da8: 1.000MB/s transfers
Sep 2 00:18:48 aly-x200 kernel: da8: 15474MB (31690752 512 byte sectors: 255H 63S/T 1972C)
------------------------------------------------------
Cheers,
Aly
Updated by Johannes.Hofmann almost 8 years ago
I was also seeing this issue on my Thinkpad x201.
After flashing the alternativ coreboot BIOS all my USB sticks work perfectly.
Interestingly, FreeBSD and stock BIOS also worked ok.
Updated by ollehar about 7 years ago
liweitianux wrote:
I think I found this bug is related to the "ehci" driver in DFly.
I took some efforts to make DFly run on my X220. Then I try to read the USB (2.0) stick from it, but it doesn't work with "ehci" driver loaded.
How did you manage to boot dfly without the ehci driver? I'm facing this exact problem with my X220.
Updated by liweitianux about 7 years ago
ollehar wrote:
liweitianux wrote:
I think I found this bug is related to the "ehci" driver in DFly.
I took some efforts to make DFly run on my X220. Then I try to read the USB (2.0) stick from it, but it doesn't work with "ehci" driver loaded.
How did you manage to boot dfly without the ehci driver? I'm facing this exact problem with my X220.
In fact, it took me quite some effort to install DFly on my X200 (also X220), then I managed to find that this issue is in the "ehci" driver from the installed DFly system (I can kldload and kldunload the "ehci" and "xhci" drivers and check the logging messages).
By reading the loader(8) man page, there is a description on how to disable the auto loading of "ehci" (USB2.0) driver: go to the loader prompt, and input:
------------------------------------------------------------------
lunset ehci_load
set hint.ehci.0.disabled=1
------------------------------------------------------------------
WARNING: This issue of course exists in the installed DFly system, thus you can only work with the slow "ohci" (USB1.1) driver on X200/X220.
NOTE: I tried install FreeBSD and OpenBSD on my X200 (X220 should be similar), and both of them works well (w.r.t. the USB2.0 driver). However, DFly runs much faster compared to them, especially to OpenBSD.
Cheers,
Aly
Updated by falsifian over 3 years ago
I got the same error trying to install 6.0 on my Lenovo T430s.
Disabling ehci (per liweitianux's instructions above) didn't help: da8 just completely disappeared.
Fortunately, switching to a different USB port solved the problem. (The working one has an "SS" logo beside it.)
Attached: dmesg, including boots into 6.0 and, later, master.
Updated by falsifian over 3 years ago
(To be clear, the dmesg I attached doesn't include any attempts to use a USB device.)
Updated by liweitianux over 3 years ago
falsifian wrote:
I got the same error trying to install 6.0 on my Lenovo T430s.
Disabling ehci (per liweitianux's instructions above) didn't help: da8 just completely disappeared.
Fortunately, switching to a different USB port solved the problem. (The working one has an "SS" logo beside it.)
Thank you for the follow-up. Actually, the USB port with "SS" logo should be an USB 3.x port, which uses the `xhci` module and works fine in DragonFly.
I've tried to track this `ehci` issue quite some time ago, but failed to identify the cause ...