Hah! I got an err M again 3 years later. I was running multiboot whereby you do a dd from wd0 into a file. So I booted from an install disk, shelled out, did fsck on the hard drive partitions then used dd to copy back the bootsector file. It worked.
I just did: dd of=/dev/wd0 if=obsd.bin and rebooted, everything came back. On 3/6/14, Alan Corey <alan01...@gmail.com> wrote: > Got it. Thanks. I burned a 5.2 install and used the ramdisk > /usr/mdec/installboot from that. I don't have 5.5 and it would take > weeks by modem to get it. > > On 3/6/14, Chris Cappuccio <ch...@nmedia.net> wrote: >> Alan Corey [alan01...@gmail.com] wrote: >>> I'm at 5.2. Booting from a 5.4 install image I mounted my / as /mnt >>> then my /usr as /mnt2. Then I did: >>> >>> /mnt2/mdec/installboot -n -v /mnt/boot /mnt2/mdec/biosboot /dev/wd0c >>> and get: Bad system call >>> >>> There's a /mnt/boot in place copied from /mnt2/mdec >>> >> >> You need to run installboot from /usr/mdec (or /usr/sbin on 5.5) >> on the install image ramdisk, not the 5.2 host. >> >> And you really need to use the installer and let it do all >> this for you, or else you should read the install/upgrade scripts >> and figure out the stuffs. >> > > > -- > Credit is the root of all evil. - AB1JX > -- ------------- No, I won't call it "climate change", do you have a "reality problem"? - AB1JX Impeach Impeach Impeach Impeach Impeach Impeach Impeach Impeach
