On 2018-01-17, Randall Gellens <obsd.t...@randy.pensive.org> wrote: > I have a pretty old OpenBSD that's been running on a Soekris Net5501, > an AMD Geode LX single chip processor with CS5536 companion chip, > classified as a "586 class processor". > > I have a new box, a Protectli with a dual core Intel Celeron 3865U. > > I want to first move the existing OpenBSD system to the new box, then > after that's working, I can step through the upgrades to get current. > > I naively thought I could move my OpenBSD from the old box to the new > by cloning the old disc (a camera flash card) onto the new disc (a > modern SSD). I cloned the discs and installed the new disc in the > new box. When I boot the new box, OpenBSD kernel panics, probably > because I switched it from a single-core AMD Geode to a dual-core > Intel Celeron. > > Is there an easy way to fix this? I tried halting from the kernel > panic debugger and booting /bsd.rd and doing an 'upgrade' (thinking I > could 'upgrade' to the same version currently installed), but it says > there are no disks. I tried going into the /bsd.rd shell and > entering 'mount /dev/sd0a /mnt' but it says "Device not configured." > An 'ls /dev/sd*' shows the various partitions of /dev/sd0.
First things first, does a new clean installation boot OK on the new machine? (amd64 would be a better choice than i386). How does a dmesg from this look, and what version were you running before? What is the panic message? (or better, complete dmesg up to the failure). It won't be the cpu, but it may be that the new machine just won't run with the older kernel. You might well have an easier time moving config to a new installation than stepping through the upgrades.
