Doesn't find root booting from memstick.img

[loveydovey]

Wrote memstick.img to a USB. Booting from it, I get the menu, it loads kernel, then stuck at mountroot>

? shows cd0 diskid/DISK-XX..XX ada0

Tried a few things, but no luck. There's some xhci0 error in console output. I tried booting with hint.xhci.0.disabled=1 - it gets rid of the error, but still same problem.

 

[loveydovey]

I'm burning a DVD now to see if it'll boot from a DVD as there are some USB issues (a USB driver issue or a hardware fault? - would've been nice to troubleshoot it from the installer).

 

[loveydovey]

Booting from DVD works. It must be some hardware issue with the USB. We'll see how USB runs once I install everything.

 

[gomadtroll]

I'm burning a DVD now to see if it'll boot from a DVD as there are some USB issues (a USB driver issue or a hardware fault? - would've been nice to troubleshoot it from the installer).

My experience it was bad USB sticks, more than one. Threw out the old bought all new, no issues.

 

[USerID]

It must be some hardware issue with the USB.

What’s stopping you from writing OpenBSD to a USB drive and simply checking if it boots? If you get the installation prompt, then the issue might not be the flash drive. That’s exactly how I test it. Which program do you use to create a DOS partition table on the flash drive? What do you use to format it to FAT32?

 

[sko]

Which program do you use to create a DOS partition table on the flash drive? What do you use to format it to FAT32?

You are not supposed to do that.
Just dd the image to the drive; it already contains all partitions and filesystems.

 

[USerID]

You are not supposed to do that.

Why is that? Doing this often reveals errors during the creation of the partition table and the partitions themselves. It serves as an extra check for the flash drive's reliability and wear level. GParted is an excellent program. For me, this serves as a sanity check for the flash drive. If errors occur, the flash drive is the first thing I look at.

 

[loveydovey]

Ther'es smth with the xhci on that machine. I did hint.xhci.0.disabled=1, but it still tries to talk to the xhci and errors out as seen in dmesg. So I should compile kernel without xhci and see?

 

[SirDice]

There's often an option in the BIOS/UEFI regarding XHCI handoff. That might default to disabled, it should be enabled. Also make sure things like "Safe boot" are turned off. Although I would expect it to bail out very early on in the boot process if it was enabled.