Date: Tue, 6 Jan 2009 11:12:41 -0600 From: Brooks Davis <brooks@freebsd.org> To: Brian Duke <brian@box201.com> Cc: FreeBSD-stable@freebsd.org Subject: Re: cvsup freebsd 6_2 to freebsd 7_1 not upgrading? Message-ID: <20090106171241.GH11721@lor.one-eyed-alien.net> In-Reply-To: <024201c9701c$572c3540$05849fc0$@com> References: <32085272.968201231189478546.JavaMail.root@wmail9.libero.it> <010e01c96f82$252875d0$6f796170$@com> <20090105223216.GE11721@lor.one-eyed-alien.net> <024201c9701c$572c3540$05849fc0$@com>
next in thread | previous in thread | raw e-mail | index | archive | help
--qVHblb/y9DPlgkHs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 06, 2009 at 09:31:48AM -0700, Brian Duke wrote: > This is very odd. > I got desperate last night and steeled myself for a reinstall. Copied all > the known keeper files to an alternate drive including /home, /etc, > /usr/local/etc and a couple others. It's on a completely separate drive w= ith > no OS just files on it. I downloaded what I thought was 7.1 iso and burned > the image to disks from my spare windows machine. I sure of it as I made a > point to upgrade to 7.1 >=20 > I stuck in the install disk and rebooted.=20 > I didn't mess with fdisk left it the same.=20 > Used disk druid to set the mount points like they were before and toggle > newfs to Yes. >=20 > I watched the install perform a newfs on the mount points. As it was load= ing > the new kernel and support files I kept seeing snippets saying file for > FreeBSD 7.0 loaded. I figured there were legacy files being added and let= it > continue. The install disks loaded everything with success. The > congratulation screen popped up and set the final options. I got to the > reboot and it warned me to take out the disk before rebooting. I suspect the 7.0 stuff is a bug in the release media, but almost certainly a red herring in this case. > While booting I saw right after choosing normal boot it said proudly > "FreeBSD 6.2-RELEASE". >=20 > My question is this, after a system boots from the CD, performs a newfs, > loads everything in /usr perfectly as all my /home directories are gone a= nd > /root is empty. How can a kernel continue to exist? >=20 > I'm done with newfs as that seems to have no effect. I'm going to fdisk t= he > system now and seriously mess with the MBR. But just before I do, anyone > have any idea how install disks doing a standard install do not overwrite > the kernel? =20 This is really odd. It sounds like you are somehow booting from one root file system (with the 6.2 kernel) and then mounting another one over the top of it. I'm not sure quite how I'd go about tracking this down. A dmesg might help and the output lsdev in the loader might be interesting. -- Brooks --qVHblb/y9DPlgkHs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iD8DBQFJY5EJXY6L6fI4GtQRAue0AKDdSdryNsHDrYaesOnsQ43VClkGIQCbBJdd 7fL2di9xOl7Wbe4iEsVZDPA= =2alO -----END PGP SIGNATURE----- --qVHblb/y9DPlgkHs--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090106171241.GH11721>