Upgrading to 6.2-RELEASE from 6.2-STABLE

[Brian A. Seklecki]

entering:

mountroot> ufs:da0s1a

...doesn't work

What does "?" command list.

~BAS

On Tue, 2007-06-12 at 19:37 -0700, Mark Stout wrote:
> I couldn't load da0s1a even though /dev/da0s1a is my root drive.  Manually load my old kernel from the prompt worked.
> 
> I believe the mountroot is during the boot load.  I'm not anywhere near being able to do anything.
> 
> I have no idea what the problem is.
> 
>  [jackbarnett at gmail.com] wrote:
> 
> no idea, but maybe:
>     boot /boot/kernel/kernel   
> or
>     boot /boot/kernel.old/kernel
> 
> What is 'mountroot' - is that the boot loader or the kernel/system 
> giving you that?
> 
> try mounting your root drive!
> 
> do a `df -k`, anything already mounted?
> 
> oh!  or try:
>     fsck
> 
> did it ask you to login?
> 
> 
> Mark Stout wrote:
> > I followed all the steps in the handbook as well as UPDATED and after a installworld and mergemaster its booting into 'mountroot>' and nothing I type mounts.  This is a production machine so I'm in dire need of assistence.
> >
> >  [illoai at gmail.com] wrote:
> > On 11/06/07, Mark Stout <mcs at vpm.com> wrote:
> >
> >   
> >>> Following the tasks in Rebuilding "world" in the handbook
> >>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html I removed the
> >>> /usr/obj directory and did a buildworld.  When tryinmg to compile the kernel its failing on
> >>> unknown option "MD5".  Commenting that out it fails on the line above MD5,  options LKM.
> >>>  What's happening here?  These two options papear in the LINT file.  I can't find anything
> >>> that explains why this would happen.
> >>>       
> >> A follow-up to my last email.  I copied GENERIC to RADIUS2 and
> >> symlinked to /root/kernel.  Then added the various LINT options.
> >>
> >> I started commenting out what is failing when I try to compile a new
> >> kernel.  All are from the LINT file.  Is MD5 a default that does not
> >> need to be specifically added?  What about ICMP_BANDLIM?  And
> >> support for IDE drives. Are these already handed elsewhere in GENERIC?
> >>
> >> # These all failed as unknown options:
> >> unknown option "MD5"
> >> unknown option "LKM"
> >> unknown option "CD9660_ROOTDELAY"
> >> unknown option "NSWAPDEV"
> >> unknown option "TCP_COMPAT_42"
> >> unknown option "ICMP_BANDLIM"  (found in Handbook in Chapter 14 Securing FreeBSD)
> >>
> >>
> >> # Do not understand why these are fialing
> >> config: Error: device "acd0" is unknown
> >> config: Error: device "wfd0" is unknown
> >> config: Error: device "wst0" is unknown
> >>
> >> # This failed as a syntax error
> >> controller      wdc0    at isa? port "IO_WD1" bio irq 14
> >>
> >>     
> >
> > Most of the above looks like old, deprecated
> > stuff from 5.x and earlier (the "controller wdc0"
> > line reminds me of 3.x or maybe NetBSD).
> >
> > IDE drive support is all handled by ata(4), all
> > you should need for those in your kernel config
> > is:
> > device          ata
> > device          atadisk
> > device          atapicd
> > (and obviously:)
> > device eisa
> > device pci
> > Which are already part of GENERIC.
> >
> > /usr/src/sys/<arch>/conf/LINT doesn't exist in 6.x.
> > Try looking at /usr/src/sys/<arch>/conf/NOTES
> > and /usr/src/sys/conf/NOTES for knobs to twist
> > and buttons to push.
> >
> >   
> 
> 
> 
> 
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
-- 
Brian A. Seklecki <bseklecki at collaborativefusion.com>
Collaborative Fusion, Inc.




IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited.  Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.