 Due to the effective #unix_surrealism propaganda, installed OpenBSD on my new server. However, for some reason it ended up being installed on sd1, not sd0. Works fine when you select the booting device manually, but can't do that all the time. Modifying SeaBIOS boot order is like fighting the titans. Didn't succeed in merging the two. Severe skill issue. If I lose my interest tomorrow, I'll make a refund on the VPS and get a Fedora on a different machine. Next time, Puffy... 9 comments
@prahou I don't know if it has one or two physical disks. The machine itself is not very physical, quite ephemeral even โ it's a VPS! No encryption. @bouncepaw What does it do if you don't intervene in the boot at all? But then also, with OpebBSD you'd have to reboot like twice a year or less, so that should taper out to a no problem kind of problem :) @polezaivsani it tries to boot from sd0, fails to do so and says โNo O/Sโ. $ sysctl hw.disknames @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. @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 :). |
Gregory's Server
@bouncepaw ๐ค I don't get it. The machine has a single physical disk?
Did you encrypt the installation?