Date: Fri, 11 Mar 2011 07:58:19 +0100 From: Bas Smeelen <b.smeelen@ose.nl> To: freebsd-questions@freebsd.org Subject: Re: lost network during freebsd-update install Message-ID: <4D79C80B.5070805@ose.nl> In-Reply-To: <C99E4B74.F99A%fsb@thefsb.org> References: <C99E4B74.F99A%fsb@thefsb.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/10/2011 04=3A24 PM=2C Tom Worster wrote=3A =3E before resorting to cd=2E Hi=2C I=27ve read your last post=2C this sucks=2E I missed a point which you have thought about =28see below=29 The best thing would have been either rollback or reboot and continue=2C se= e below=2E =3E the handbook describes a procedure=3A =3E =3E A=29 1st freebsd-update install=3A The kernel and kernel modules will b= e =3E patched =3E =3E B=29 reboot =3E =3E C=29 2nd freebsd-update install=3A The state of the process has been sa= ved and =3E thus=2Cfreebsd-update will not start from the beginning=2C but will rem= ove all =3E old shared libraries and object files =3E =3E =3E i=27m just guessing=2E=2E=2E A=29 did not complete because its shell ex= ited=2E i was =3E left with a half-patched kernel=2E when i did =22freebsd-update install= =22 =3E again=2C instead of doing A=29 over from scratch=2C it attempted C=29 a= nd started =3E dumping cores all over the carpet=2E result=3A system can=27t get the k= ernel up =3E properly=2E =3E =3E or another guess=2E=2E=2E A=29 did complete while i was disconnected=2E= when i =3E repeated =22freebsd-update install=22 it attempted C=29 but because the= old =3E kernel was still running it didn=27t work and started dumping cores all= over =3E the carpet=2E result=3A system hangs attempting to start some userland= part=2E I guess you=27re right here=2E When ssh disconnects the shell does not immediatly exit=2C it takes some mi= nutes=2E So freebsd-update succesfully installed the kernel and when you got connected again and ran install the second time it tried to install a new= userland on top of the old running kernel which in case of this major version upgrade did not work=2E Why so much stuff is missing though is not= clear to me=2C I would think that freebsd-update just overwrites the old bi= naries=2E =3E it seems a pity now that freebsd-update chose to use the same command v= erb =3E for both A and C=2E It would be nice if freebsd-update had the same command sequence =28without= the build parts=29 as in a source upgrade=2E First fetch of course=2C then= freebsd-update installkernel with a message to reboot on succes or rollback= on failure=2C then after reboot freebsd-update installworld=2C with a check= if the new kernel is actually loaded=2C after that and rebuilding ports freebsd-update delete-old-libs I would like to know how others think about this approach=2C or am I thinki= ng completely wrong here=3F =3E real hw=2E =3E =3E i=27m considering going to the clouds=2E i could easily restore from a= vm =3E snapshot=2E but for that i need to learn linux=2C another big time sink= =2E =3E =3E add votes here=3A =3E http=3A//feedback=2Erackspacecloud=2Ecom/forums/71021-product-feedback/= suggestion =3E s/989519-create-a-freebsd-image Voted=2E I run FreeBSD on real hardware and in virtual machines=2C both work fine ov= er the years=2E Hope you have your server up and running again and from your posts I trust= you have good backups and a reliable fast way to restore=2E DISCLAIMER=3A This e-mail is for the intended recipient=28s=29 only=2E Acce= ss=2C disclosure=2C copying=2C distribution or reliance on any of it by anyone else is prohibited=2E If yo= u have received it by mistake please let us know by reply and then delete it from your system= =2E
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D79C80B.5070805>