@polezaivsani it tries to boot from sd0, fails to do so and says “No O/S”.
$ sysctl hw.disknames
hw.disknames=cd0:,sd0:58e0235963f7e753,sd1:80ff106d7743a311,fd0:
Top-level
@polezaivsani it tries to boot from sd0, fails to do so and says “No O/S”. $ sysctl hw.disknames 5 comments
@polezaivsani oh yes, I'll get back to OpenBSD eventually for sure! I like it! The problem with sd0 is that it's too small to fit OpenBSD :-( @bouncepaw a virtual floppy, a small sd0... is this a virtual 486 machine? Like a virtual appliance for those taking up the old computer challenge ;) @polezaivsani it is a regular x86 I want to take up the old computer challenge someday. I don't the hardware for it though haha @bouncepaw *jotting down* organize a local hardware exchange with a dedicated stall for older thinkpads suited for the occ :). |
@bouncepaw Once you'd get fed up with Fedora and decide to give OpenBSD another try, :), and assuming you don't want messing with bios boot order, make sure you'd be installing to the disk with the duid of 58e02***.
Within installer you can exit to shell (entering ! at the installer prompts) and using either sysctl or disklabel to see which disk has the needed duid.