Re: Boot Loader Broken?

On 1/10/08, Lowell Gilbert <freebsd-questions-local@xxxxxxxxxxxxxxx> wrote:
Schiz0 <schiz0phrenic21@xxxxxxxxx> writes:

I recently upgraded from 6.3-PRERELEASE to 7.0-PRERELEASE. I had some
problem with the ports, but I got that taken care of.

Now I'm having another very odd problem.

I originally noticed something odd when I tried to shutdown from
multiuser mode into single user mode. I ran "shutdown now" as root in
multiuser. It said it was shutting down, etc. But then, it gave me the
normal multiuser login prompt. So then I tried rebooting completely,
and that's where the big error came up:

Note that rebooting completely *is* the normal procedure, so that you
know your kernel boots before you overwrite anything that depends on it.


-----------------------------------------------------
FreeBSD/i386 bootstrap loader, Revision 1.1
(root@Mercury, Tue Jan 8 14:22:21 EST 2008)
\
\: unknown command
-
/boot/kernel/kernel text=0x29e868 data=0x2db8c+0x23814
syms=[0x4+0x34c10+0x4+0x43ef1]
Hit [Enter] to boot immediately, or any other key for a command prompt.
Booting [/boot/kernel/kernel] in 4 seconds ...
-----------------------------------------------------

Why it trying to run the command "\" ? Right before I did this, I
rebuilt world, including the kernel. I installed the new kernel, and
was moving down to single user to install world.

Is my bootloader corrupt somehow?

I would suspect something more like some extra text in loader.conf.


I just did a fresh install from the iso for 7.0-RC1. It worked fine. I
csup'ed the RELENG_7 src, and compiled and installed world and a
kernel. All of this with no error. I rebooted into the new kernel, and
it was fine. Then I rebooted after "make installworld" and I'm getting
that same error. I did not modify any file at all. Looks like there's
a typo in the bootloader config for 7.0-RC1?
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: The sad demise of an etch.
    ... investigating what is causing the badness in the current install. ... If I knew how to do this (besides a few variations on rebooting and ... kernel version and hardware). ... Rebooted to etch. ...
    (Debian-User)
  • Re: The crippled resurrection of said etch.
    ... investigating what is causing the badness in the current install. ... If I knew how to do this (besides a few variations on rebooting and ... kernel version and hardware). ... Saw it was starting gdm. ...
    (Debian-User)
  • Re: The crippled resurrection of said etch.
    ... investigating what is causing the badness in the current install. ... If I knew how to do this (besides a few variations on rebooting and ... kernel version and hardware). ... Saw it was starting gdm. ...
    (Debian-User)
  • Re: The sad demise of an etch.
    ... investigating what is causing the badness in the current install. ... If I knew how to do this (besides a few variations on rebooting and ... kernel version and hardware). ... Rebooted to etch. ...
    (Debian-User)
  • Re: Boot Loader Broken?
    ... Now I'm having another very odd problem. ... multiuser mode into single user mode. ... know your kernel boots before you overwrite anything that depends on it. ... was moving down to single user to install world. ...
    (freebsd-questions)