Re: Broken loader on 7.1-STABLE?




On 1/21/09 6:23 PM, "John Rushford" <jjr@xxxxxxxxx> wrote:




On 1/21/09 9:52 AM, "jjr@xxxxxxxxxx" <jjr@xxxxxxxxxx> wrote:

On Tue, Jan 20, 2009 at 06:22:00PM -0700, John Rushford wrote:
Hello,

Perhaps mine is a different issue but I ran into this today.

I loaded FreeBSD 7.1-RELEASE from a DVD onto an Apple Mac Pro after
partitioning a drive with bootcamp. The install went quite well and the
machine came up with no issues. I configured networking, X, and got
gnome
working. I setup cvsup and loaded the STABLE sources, ran make
buildworld,
make kernel, etc...

I attempted to boot into single user to run mergemaster, installworld,
etc..
But the machine will not boot, I now get the following errror and
prompt:

Trying to mount root from ufs:/dev/ad9s1a

Manual root filesystem specification:
<fstype>:<device> Mount <device> using filesystem <fstype>
e.g. ufs:da0s1a
? List valid disk boot devices
<empty line> Abort manual input

I input ufs:/dev/ad9s1a to no avail and ? Does not list any other
devices.

I've booted from the DVD and gone into Fixit mode and can mount
/dev/ad9s1a
just fine. I thought that I'd try putting back loader.old on the off
chance
that might solve the problem but, I do not see a loader.old, just
loader.
The kernel.old directory is there.

Any ideas on what the issue might be and how to fix?

Appreciate the help as I'd like to get 7.1-STABLE running on this
machine.

Did the kernel probe messages prior to the mountroot prompt indicate that
the appropriate disk controllers were found/probed and that the
disk devices were found on the disk controllers? The lack of
any devices listed when you asked might indicate a kernel configuration
problem.

Regards,

Gary

P.S. Please do not top post.


I believe the appropriate disk controllers were found, I had no trouble
mounting the root filesystem while in Fixit. I'll double check this
evening and let you know. I have gone back and booted without issue from
kernel.old and the machine is running 7.1-RELEASE.

John

Hmm, I have 3 disks in this Mac Pro with FreeBSD installed on the disk in
Bay 3. When I boot the 7.1-RELEASE GENERIC kernel from the DVD install,
these 3 disks are named ad8, ad9, and ad10. The FreeBSD resides on ad9s1a.
I built 7.1-STABLE GENERIC kernel with no modifications except to comment
out the debug option. When I boot this kernel, the disks are re-named as
ad6, ad7, and ad8 and I'm dropped into this prompt:

Manual root filesystem specification:

<fstype>:<device> Mount <device> using filesystem <fstype>
e.g. ufs:da0s1a
? List valid disk boot devices
<empty line> Abort manual input

? Lists no valid disks.

Next I boot from DVD with the 7.1-RELEASE Kernel and the disks are named as
before, I can mount /dev/ad9s1a and switch back to the 7.1-RELEASE kernel in
/boot to get the machine back up.

Any ideas?

John


BTW, its a Mac Pro and an AMD64 kernel


_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Broken loader on 7.1-STABLE?
    ... I think the boot loader is ok, because I can load old amd64 kernel structures, but no newer one on this hardware. ... the appropriate disk controllers were found/probed and that the disk devices were found on the disk controllers? ...
    (freebsd-stable)
  • Re: maximum hard drive size in Latitude cpi
    ... > actually written a boot loader they won't be so adamant about how "Windows ... > of the disk, and while it is being read off of the disk the machine is ... > limitatoins of that BIOS. ... After that the kernel takes over. ...
    (comp.sys.laptops)
  • Re: Broken loader on 7.1-STABLE?
    ... make kernel, etc... ... I attempted to boot into single user to run mergemaster, installworld, etc.. ... the appropriate disk controllers were found/probed and that the ... I was wondering if anyone else was seeing loader break after updating ...
    (freebsd-stable)
  • Re: SCSI controller PCI slot change
    ... But with V5.1* it should be even easier and you don't have to hack the kernel configuration, because the device mapping is dynamic there. ... When you boot the kernel it walks through the hardware and maps all found hardware to appropriate device files. ... Therefore, if you have had a disk in your Tru64 V5.* machine at least once, it keeps that recorded until you delete it and whenever you bring that disk back into the machine and place it somewhere (on any SCSI bus) the OS will bring it up with the original device file mapping. ...
    (comp.unix.tru64)
  • Re: 0x0000007b error on install of SBS
    ... - I'll go get those drivers onto a disk and try again... ... I can boot from the DVD no problem and get ... the setup until it says press enter to install then it says there is no ...
    (microsoft.public.windows.server.sbs)