Re: Problem after upgrade 4.5 to 4.6: ERR M [Solved]

2010-03-22 Thread Uwe Dippel
Nick Holland wrote: And in the end, a '0'-sized bsd.sp after moving in a healthy bsd.mp. I would not totally exclude an interference of this (new?) code that lead to the described situation. Honestly, nothing at all done in that session aside from what I wrote, between the 2 boots. I guess, not

Re: Problem after upgrade 4.5 to 4.6: ERR M

2010-03-22 Thread Nick Holland
Uwe Dippel wrote: Tobias Ulmer wrote: As explained above, no, you likely moved around/corrupted /boot in a way that doesn't work for biosboot. Hmm. Actually I didn't. Through serial console, I had rebooted the server, just 'to make sure', before booting to bsd.rd, and everything went thr

Re: Problem after upgrade 4.5 to 4.6: ERR M

2010-03-22 Thread Tobias Ulmer
On Mon, Mar 22, 2010 at 09:59:20PM +0800, Uwe Dippel wrote: [..] > > Thanks for the reply. I'll go there next to try what has been > proposed. Before I try, in case the > # /usr/*m*dec/installboot -v boot /*usr/mdec*/biosboot sd0 > does NOT work, what else could I do? (I am asking, because it is a

Re: Problem after upgrade 4.5 to 4.6: ERR M

2010-03-22 Thread Uwe Dippel
Tobias Ulmer wrote: As explained above, no, you likely moved around/corrupted /boot in a way that doesn't work for biosboot. Hmm. Actually I didn't. Through serial console, I had rebooted the server, just 'to make sure', before booting to bsd.rd, and everything went through. I rebooted ag

Re: Problem after upgrade 4.5 to 4.6: ERR M

2010-03-22 Thread Tobias Ulmer
On Mon, Mar 22, 2010 at 04:41:39PM +0800, Uwe Dippel wrote: > Having done upgrades from 4.0 onwards, on a OpenBSD-only server > (amd64), this time something must have gone wrong: Despite of the > (remote, I have no physical access, via serial console) 'successful' > upgrade (no error messages), whe

Re: Problem after upgrade 4.5 to 4.6: ERR M

2010-03-22 Thread Chris Bennett
Uwe Dippel wrote: Having done upgrades from 4.0 onwards, on a OpenBSD-only server (amd64), this time something must have gone wrong: Despite of the (remote, I have no physical access, via serial console) 'successful' upgrade (no error messages), when I was asked to reboot, I did, as always. A

Problem after upgrade 4.5 to 4.6: ERR M

2010-03-22 Thread Uwe Dippel
Having done upgrades from 4.0 onwards, on a OpenBSD-only server (amd64), this time something must have gone wrong: Despite of the (remote, I have no physical access, via serial console) 'successful' upgrade (no error messages), when I was asked to reboot, I did, as always. Alas, it came up wit