Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 1 Dec 2004 06:05:56 +0000
From:      Stacey Roberts <stacey@vickiandstacey.com>
To:        Christian Hiris <4711@chello.at>
Cc:        Stacey Roberts <stacey@vickiandstacey.com>
Subject:   Re: How to capture "make installworld" error during migration from 5.1 to 5-Stable?
Message-ID:  <20041201060556.GZ12622@crom.vickiandstacey.com>
In-Reply-To: <200412010641.13984.4711@chello.at>
References:  <20041130224957.GW12622@crom.vickiandstacey.com> <200412010023.15447.4711@chello.at> <20041201011241.GY12622@crom.vickiandstacey.com> <200412010641.13984.4711@chello.at>

next in thread | previous in thread | raw e-mail | index | archive | help

--y9PDtDHaFrXNoMPU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hello Christain,

----- Original Message -----
From: "Christian Hiris <4711@chello.at>"
To: To freebsd-questions@freebsd.org
Date: Wed, 01 Dec, 2004 05:40 GMT
Subject: Re: How to capture "make installworld" error during migration from 5.1 to 5-Stable?

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Wednesday 01 December 2004 02:12, Stacey Roberts wrote:
> > Okay.., I've just scripted the output from "make installworld" at step 15
> > of the migration guide, and its failed as before.
> >
> > I've got the output redirected to a file: /var/tmp/installworld.log,
> > however, I'm in single-user mode, and nothing works: ls, mount, etc.., how
> > do I get this file off this system so that I can post it to the list for
> > assistance?
> >
> > At this point, I can (manually) show the last bit of the failed attempt for
> > make installworld:
> >
> > ===> bin/test
> > install -s -o root -g wheel -m 555  test /bin
> > install -o root -g wheel -m 444 test.1.gz /usr/share/man/man1
> > pid 45090 (sh), uid 0: exited on signal 10 (core dumped)
> > *** Signal 10
> > Stop in /usr/src/bin/test.
> > *** Error code 1
> > Stop in /usr/src.
> > *** Error code 1

I've managed to get the log file off the machine. I've attached it here in gzipped format for anyone that is able (including yourself, if you like) to be able to look at it in its entirety.

> 
> This eventually points out a problem in your memory or harddisk subsystem, I 
> had such errors on incompatible disk controllers starting at 5.1. This kind 
> of errors silently destroyed the data on my system (happened with HPT onboard 
> controllers on an Via-KT600 board). Double, better, triple fsck your 
> filesystems and check CFLAGS and COPTFLAGS settings in /etc/make.conf.

I've found that I can reboot the system into multiuser mode, however there *are* lots of programs core-dumping all over the place (sendmail, exited on signal 11 - for instance)..,

> Did you set your kernel timezone with "adjkerntz -i"? 

Yes.., followed the migration guide to the letter, save for scripting step 15 as I originally asked about here..,

I'm actually preparing to head off-site here at present, but will get back to this later on today.., hopefully there'd be more information on the situation after examination of the log file output by a kind soul..,

Thanks again for the assistance..,

Regards,

Stacey


> 
> There are several ways to repair a system that failed during upgrade:
> 
> - - Use the emergency shell on the 5.3-Live-Filesystem-CD. 
> 
> - - Try statically linked /rescue/sh instead of dynamically linked /bin/sh  
>   (if the 5-STABLE version of /rescue has been already installed). 
> 
> - - Do a minimal install from a 5.3-RELEASE-i386-miniinst.iso to your swap
>   partition or to an additional disk.
> 
> 
> > I'd appreciate some help with this.., If there is a way to get the log file
> > off (to floppy, for instance), I'd like to post it so that folks cleverer
> > than I could take a look, please.
> 
> If kernel and world are not in sync it's maybe easier, if you try to boot via 
> serial console and copy the output from there.
> 
> To setup the serial console enter the command "echo -Dh > /boot.config" and 
> connect COM ports via serial cable. Connecting to the serial console works 
> via "cu -l cuaa0" (assuming the terminal machine is connected via the first 
> COM port). You will find some more sophisticated infos about serial console 
> setup in the FreeBSD handbook:     
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html
> 
> Most common tasks are described in the FreeBSD Handbook, for floppy disk 
> handling please refer to
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/floppies.html
> 
> - -- 
> Christian Hiris <4711@chello.at> | OpenPGP KeyID 0x3BCA53BE 
> OpenPGP-Key at hkp://wwwkeys.eu.pgp.net and http://pgp.mit.edu
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.6 (FreeBSD)
> 
> iD8DBQFBrVl509WjGjvKU74RApgtAJwM9Gkon0WR/veuVHkI15BA5NFnIwCfaA0u
> YXmAzwW3pnfmYiLNgj7DNoY=
> =bh9U
> -----END PGP SIGNATURE-----

--y9PDtDHaFrXNoMPU--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041201060556.GZ12622>