RE: Part #1 - Newbie Help Determining Lost Root After Upgrade = From 4. 0 to 4.1

From owner-freebsd-questions Fri Sep 15 10:26: 6 2000 Delivered-To: freebsd-questions@freebsd.org Received: from lcmail2.lc.ca.gov (lcmail2.lc.ca.gov [165.107.12.11]) by hub.freebsd.org (Postfix) with ESMTP id 0FFAC37B424; Fri, 15 Sep 2000 10:25:54 -0700 (PDT) Received: from CONVERSION-DAEMON by lcmail2.lc.ca.gov (PMDF V5.2-27 #40821) id <0G0X00C01V23SE@lcmail2.lc.ca.gov>; Fri, 15 Sep 2000 10:25:17 -0700 (PDT) Received: from ldcmsx01.lc.ca.gov ([165.107.11.191]) by lcmail2.lc.ca.gov (PMDF V5.2-27 #40821) with ESMTP id <0G0X00AOAV210W@lcmail2.lc.ca.gov>; Fri, 15 Sep 2000 10:25:13 -0700 (PDT) Received: by ldcmsx01.lc.ca.gov with Internet Mail Service (5.5.2650.21) id ; Fri, 15 Sep 2000 10:25:44 -0700 Content-return: allowed Date: Fri, 15 Sep 2000 10:25:34 -0700 From: "Tomlinson, Drew" Subject: RE: Part #1 - Newbie Help Determining Lost Root After Upgrade Fro m 4. 0 to 4.1 To: 'Mark Ovens' , 'Kent Stewart' Cc: "'FreeBSD Questions (E-mail)'" Message-id: <8C224DC088D8D111B67D0000F67AC17E029C4C66@ldcmsx01.lc.ca.gov> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: MULTIPART/ALTERNATIVE; BOUNDARY="Boundary_(ID_65k1I509w1uQdLJE3Qjx+A)" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --Boundary_(ID_65k1I509w1uQdLJE3Qjx+A) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 8BIT Thank you both for your help. I am compiling a new kernel right now. I'm actually in California but I use a dynamic IP (dynip.com) DNS service that is located in Canada. So would this be why I had an error using CVSup with the "cvs-crypto" tag? I don't remember the exact error but it was something along the lines of it not being available. When I commented out the "cvs-crypto" and uncommented the individual collections, I didn't get the unavailable error. So what problems am I likely to encounter once I get a good kernel? Also, you are correct, mergemaster didn't actually update anything as the default is to leave it for later. I've read the man page but don't understand why/when I want to keep, replace, or merge. I am completely new to Unix and am having a difficult time grasping concepts. Thank you both again for your time. I really appreciate it. Drew -----Original Message----- From: Mark Ovens [mailto:marko@freebsd.org] Sent: Friday, September 15, 2000 9:42 AM To: Kent Stewart Cc: Tomlinson, Drew; 'FreeBSD Questions (E-mail)' Subject: Re: Part #1 - Newbie Help Determining Lost Root After Upgrade From 4. 0 to 4.1 On Fri, Sep 15, 2000 at 09:33:30AM -0700, Kent Stewart wrote: > > > Mark Ovens wrote: > > > > On Fri, Sep 15, 2000 at 09:13:36AM -0700, Kent Stewart wrote: > > > > > > > > > Mark Ovens wrote: > > > > > > > > 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? > > > > > > > I spotted that, but since -crypto doesn't exist as a separate > > collection anymore I would expect an error message from cvsup to that > > effect, which is what I saw when -crypto became part of src-all > > (judging by his domain he's in Canada so the USA-specific crypto > > issues wouldn't apply) > > > > > Also, isn't the default on mergemaster todo nothing, which didn't > > > upgrade any of his /etc files. > > > > > > > Yes, but that wouldn't prevent the kernel finding the root partition. > > You got that part covered. I was thinking of the next set of problems > that he is going to have after he remakes a good kernel. > Ah right. Well, as long as he hasn't nuked /usr/obj he can just boot single-user and re-run mergemaster (with our guidance :)). BTW, looking back at the original post I notice: # The easiest way to get the export-restricted code is to use the # "cvs-crypto" mega-collection. #cvs-crypto -- This is commented as I got errors when trying to fetch # # These are the individual collections that make up "cvs-crypto". If # you use these, be sure to comment out "cvs-crypto" above. -- I didn't get errors. src-crypto src-secure src-sys-crypto So he did get the error about cvs-crypto, as I expected, but I missed src* lines after. I guess that this would get -current crypto stuff, but is all of the crypto stuff MFC'd so it wouldn't make any difference? > KEnt > > > > > > 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/ > > > > -- > > 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 > > -- > Kent Stewart > Richland, WA > > mailto:kbstew99@hotmail.com > http://kstewart.urx.com/kstewart/index.html > FreeBSD News http://daily.daemonnews.org/ -- 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 --Boundary_(ID_65k1I509w1uQdLJE3Qjx+A) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: quoted-printable RE: Part #1 - Newbie Help Determining Lost Root After Upgrade = From 4. 0 to 4.1

Thank you both for your help. I am compiling a = new kernel right now.

I'm actually in California but I use a dynamic IP = (dynip.com) DNS service that is located in Canada. So would this = be why I had an error using CVSup with the "cvs-crypto" = tag? I don't remember the exact error but it was something along = the lines of it not being available. When I commented out the = "cvs-crypto" and uncommented the individual collections, I = didn't get the unavailable error.

So what problems am I likely to encounter once I get = a good kernel? Also, you are correct, mergemaster didn't actually = update anything as the default is to leave it for later. I've = read the man page but don't understand why/when I want to keep, = replace, or merge. I am completely new to Unix and am having a = difficult time grasping concepts.

Thank you both again for your time. I really = appreciate it.

Drew

-----Original Message-----
From: Mark Ovens [mailto:marko@freebsd.org]
Sent: Friday, September 15, 2000 9:42 AM
To: Kent Stewart
Cc: Tomlinson, Drew; 'FreeBSD Questions = (E-mail)'
Subject: Re: Part #1 - Newbie Help Determining Lost = Root After Upgrade
From 4. 0 to 4.1

On Fri, Sep 15, 2000 at 09:33:30AM -0700, Kent = Stewart wrote:
>
>
> Mark Ovens wrote:
> >
> > On Fri, Sep 15, 2000 at 09:13:36AM -0700, = Kent Stewart wrote:
> > >
> > >
> > > Mark Ovens wrote:
> > > >
> > > > 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=3DYOUR_KERNEL_HERE
> > > = >         make installkernel = KERNEL=3DYOUR_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=3D. and then lines later he has
> > > the crypto souces. Did he get = RELENG_4 crypto's or did he get
> > > -current?
> > >
> >
> > I spotted that, but since -crypto doesn't = exist as a separate
> > collection anymore I would expect an error = message from cvsup to that
> > effect, which is what I saw when -crypto = became part of src-all
> > (judging by his domain he's in Canada so = the USA-specific crypto
> > issues wouldn't apply)
> >
> > > Also, isn't the default on = mergemaster todo nothing, which didn't
> > > upgrade any of his /etc files.
> > >
> >
> > Yes, but that wouldn't prevent the kernel = finding the root partition.
>
> You got that part covered. I was thinking of = the next set of problems
> that he is going to have after he remakes a = good kernel.
>

Ah right. Well, as long as he hasn't nuked /usr/obj = he can just boot
single-user and re-run mergemaster (with our = guidance :)).

BTW, looking back at the original post I = notice:

# The easiest way to get the export-restricted code = is to use the
# "cvs-crypto" mega-collection.
#cvs-crypto -- This is commented as I got errors = when trying to fetch
#
# These are the individual collections that make up = "cvs-crypto". If
# you use these, be sure to comment out = "cvs-crypto" above. -- I didn't get
errors.
src-crypto
src-secure
src-sys-crypto

So he did get the error about cvs-crypto, as I = expected, but I missed
src* lines after. I guess that this would get = -current crypto stuff,
but is all of the crypto stuff MFC'd so it wouldn't = make any
difference?

> KEnt
>
> >
> > > 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]
> > > >
> > > > --
> > > = >           &n= bsp;     4.4 - The number of the Beastie
> > > > = ________________________________________________________________
> > > > 51.44=B0N FreeBSD - The = Power To Serve http://www.freebsd.org
> > > > 2.057=B0W My Webpage http://ukug.uk.freebsd.org/~mark
> > > > mailto:marko@freebsd.org &nbs= p;           &nbs= p; 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/
> >
> > --
> = >           &n= bsp;     4.4 - The number of the Beastie
> > = ________________________________________________________________
> > 51.44=B0N FreeBSD - The Power To = Serve http://www.freebsd.org
> > 2.057=B0W My Webpage http://ukug.uk.freebsd.org/~mark
> > mailto:marko@freebsd.org &nbs= p;           &nbs= p; http://www.radan.com
>
> --
> Kent Stewart
> Richland, WA
>
> mailto:kbstew99@hotmail.com
> http://kstewart.urx.com/kstewart/index.html=
> FreeBSD News http://daily.daemonnews.org/

--
= 4.4 - The = number of the Beastie
_______________________________________________________________= _
51.44=B0N FreeBSD - The Power To Serve http://www.freebsd.org
2.057=B0W My Webpage http://ukug.uk.freebsd.org/~mark
mailto:marko@freebsd.org &nbs= p; &nbs= p; http://www.radan.com

--Boundary_(ID_65k1I509w1uQdLJE3Qjx+A)-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message