From owner-freebsd-questions Fri Sep 15 9:13:46 2000 Delivered-To: freebsd-questions@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 0A18C37B423; Fri, 15 Sep 2000 09:13:43 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id JAA03581; Fri, 15 Sep 2000 09:13:36 -0700 Message-ID: <39C24AB0.A9AD3EAE@urx.com> Date: Fri, 15 Sep 2000 09:13:36 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Mark Ovens Cc: "Tomlinson, Drew" , "'FreeBSD Questions (E-mail)'" Subject: Re: Part #1 - Newbie Help Determining Lost Root After Upgrade From 4. 0 to 4.1 References: <8C224DC088D8D111B67D0000F67AC17E029C4C4A@ldcmsx01.lc.ca.gov> <20000915145333.E257@parish> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Ovens wrote: > > On Fri, Sep 15, 2000 at 06:29:37AM -0700, Tomlinson, Drew wrote: > > I've sent this message twice but never saw it post to the group. I haven't > > received any errors but shorter messages go through fine. Thus, I assume > > it's too long and have broken it into parts. > > > > I have attempted to upgrade from 4.0-S to 4.1-S using CVSup and compile > > instructions from the Handbook. I have to admit that I don't exactly > > understand what I'm doing at each step but I following the directions > > explicitly. > > > > In summary I: > > 1. Used CVSup to update my source. > > > > 2. Ran "make buildworld" (took about 36 hours on my 486DX4 120mhz -- Is this > > normal?) > > > > 3. Ran "make installworld" > > > > 4. Ran "make buildkernel" > > > > 5. Ran "make installkernel" > > > > 6. Ran "mergemaster" but took the "leave it alone" default on everything as > > I didn't understand what it was really doing. > > > > 7. Ran "sh MAKEDEV all" to update /dev. > > > > 8. Ran "make all install" to update /stand. > > > > 9. Rebooted. > > > > Hmm, the file you really should consult here is /usr/src/UPDATING. You > got the sequence slightly wrong (the handbook doesn't always get > updated immediately, UPDATING does). From /usr/src/UPDATING: > > To update from 4.0-RELEASE or later to the most current > 4.x-STABLE > ---------- > make buildworld > make buildkernel KERNEL=YOUR_KERNEL_HERE > make installkernel KERNEL=YOUR_KERNEL_HERE > reboot (in single user) [1] > make installworld > mergemaster > reboot > > > When I reboot, the system is unable to mount the root device. I am able to > > unload the new kernel, load the old one and boot without error. > > Good, at least you can boot the system.... > > > I'm sure > > I've done something wrong and would like to know what it is. I could take > > the easy way out and just install 4.1 from scratch but I wouldn't learn > > anything that way. > > > > Looking at the boot messages it is finding ata0 and ata1, the IDE > controllers, but it isn't even probing for the disks. In the config > file for your custom kernel you have commented out important IDE > devices: > > # ATA and ATAPI devices > device ata0 at isa? port IO_WD1 irq 14 > device ata1 at isa? port IO_WD2 irq 15 > #device ata > #device atadisk # ATA disk drives > #device atapicd # ATAPI CDROM drives > #device atapifd # ATAPI floppy drives > #device atapist # ATAPI tape drives > #options ATA_STATIC_ID #Static device numbering > #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices > > uncomment ata, atadisk, atapicd (if you have a CD-ROM), and atapifd > and re-build your custom kernel. If that fails, build a GENERIC kernel > and see if that boots. In his cvsup file he has ports-all tag=. and then lines later he has the crypto souces. Did he get RELENG_4 crypto's or did he get -current? Also, isn't the default on mergemaster todo nothing, which didn't upgrade any of his /etc files. Kent > > WARNING: Make a copy of your working kernel (e.g. /kernel.ok). I > suspect it is currently called kernel.old, if so it will get > overwritten (with the broken /kernel) when the next kernel you build > is installed. > > > Thank you in advance for your help. > > You're welcome. > > > I really want to learn this operating system! > > > > Good for you :) > > > Drew > > > [snip] > > -- > 4.4 - The number of the Beastie > ________________________________________________________________ > 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org > 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark > mailto:marko@freebsd.org http://www.radan.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message