Date: Wed, 13 Jun 2007 09:13:01 -0700 From: "Mark Stout" <mcs@vpm.com> To: "Brian A. Seklecki" <bseklecki@collaborativefusion.com> Cc: jackbarnett@gmail.com, illoai@gmail.com, freebsd-questions@freebsd.org Subject: RE: Upgrading to 6.2-RELEASE from 6.2-STABLE Message-ID: <DOEDIFELHLGPGLILFJKMEEDFCMAA.mcs@vpm.com> In-Reply-To: <1181749911.1161.4.camel@soundwave.pgh.priv.collaborativefusion.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: Brian A. Seklecki [mailto:bseklecki@collaborativefusion.com] > Sent: Wednesday, June 13, 2007 8:52 AM > To: Mark Stout > Cc: jackbarnett@gmail.com; illoai@gmail.com; mcs@vpm.com; > freebsd-questions@freebsd.org > Subject: Re: Upgrading to 6.2-RELEASE from 6.2-STABLE > > > > 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@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@gmail.com] wrote: > > > On 11/06/07, Mark Stout <mcs@vpm.com> wrote: > > > > > > > > >>> Following the tasks in Rebuilding "world" in the handbook > > >>> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworl > d.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. > > > > > > entering: > > mountroot> ufs:da0s1a > > ...doesn't work > > What does "?" command list. > > ~BAS > It lists all available drives mount points and then some, e.g. fd0, da0, da01, da01s, da0s1a, da0s1b, da0s1c, etc., etc. None of which mounts. Below is my /etc/fstab. So obviously da0s1a or /dev/da0s1a should mount. But it doesn't. I had to go into the loader prompt, unload the kernel, load the old kernel and that booted the system. Now I've restored the backup copy of my /etc directory from /var/tmp/etc and I re-ran a new buildworld and buildkernel. Now I'm about to go and do the installworld and installkernel. But I'm hoping to get a better understanding of what happened before I do. # Device Mountpoint FStype Options Dump Pass# /dev/da0s1b none swap sw 0 0 /dev/da0s1a / ufs rw 1 1 /dev/da1s1e /data ufs rw 2 2 /dev/da0s1g /radius ufs rw 2 2 /dev/da0s1f /usr ufs rw 2 2 /dev/da0s1e /var ufs rw 2 2 /dev/wcd0c /cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?DOEDIFELHLGPGLILFJKMEEDFCMAA.mcs>