DaemonForums  

Go Back   DaemonForums > FreeBSD > FreeBSD Installation and Upgrading

FreeBSD Installation and Upgrading Installing and upgrading FreeBSD.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 7th February 2009
carpman carpman is offline
Shell Scout
 
Join Date: Jul 2008
Posts: 94
Thanked 0 Times in 0 Posts
Default upgrade installworld error

Hello, i am in process of upgrading server from 6.2 to 6.3 and get error when doing

make installworld

Quote:
install -o root -g wheel -m 444 crt1.o crti.o crtn.o gcrt1.o /usr/lib
===> lib/libc (install)
install -C -o root -g wheel -m 444 libc.a /usr/lib
install -C -o root -g wheel -m 444 libc_p.a /usr/lib
install -s -o root -g wheel -m 444 -fschg -S libc.so.6 /lib
install: rename: /lib/INS@nP0t to /lib/libc.so.6: Operation not permitted
*** Error code 71

Stop in /usr/src/lib/libc.
*** Error code 1

Stop in /usr/src/lib.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

any ideas?

Is it safe to continue?

many thanks
Reply With Quote
  #2   (View Single Post)  
Old 7th February 2009
carpman carpman is offline
Shell Scout
 
Join Date: Jul 2008
Posts: 94
Thanked 0 Times in 0 Posts
Default

Just wondering if this because i have rc.conf entry

Quote:
kern_securelevel="2"
Reply With Quote
  #3   (View Single Post)  
Old 7th February 2009
carpman carpman is offline
Shell Scout
 
Join Date: Jul 2008
Posts: 94
Thanked 0 Times in 0 Posts
Default

Ok i have searched for ref to error

Quote:
install: rename: /lib/INS@nP0t to /lib/libc.so.6: Operation not permitted
but can find no ref to this or '/lib/INS@nP0t'
Reply With Quote
  #4   (View Single Post)  
Old 7th February 2009
DutchDaemon's Avatar
DutchDaemon DutchDaemon is offline
Real Name: Ben
Spam Refugee
 
Join Date: Jul 2008
Location: Rotterdam, The Netherlands
Posts: 337
Thanked 32 Times in 30 Posts
Default

Drop your kern_securelevel when updating. Comment it out, reboot, upgrade your system, and turn it back on again (sysctl on a running system), and uncomment the entry in rc.conf. Hope it will still work, since you've done a partial installworld already ..
Reply With Quote
  #5   (View Single Post)  
Old 7th February 2009
carpman carpman is offline
Shell Scout
 
Join Date: Jul 2008
Posts: 94
Thanked 0 Times in 0 Posts
Default

Hello and thanks for reply, is it possible to turn it off without reboot and do make installworld again?
Reply With Quote
  #6   (View Single Post)  
Old 7th February 2009
DutchDaemon's Avatar
DutchDaemon DutchDaemon is offline
Real Name: Ben
Spam Refugee
 
Join Date: Jul 2008
Location: Rotterdam, The Netherlands
Posts: 337
Thanked 32 Times in 30 Posts
Default

No, you cannot lower the securelevel on a running system because it's tied in with the kernel itself. Lowering security is in contradiction with heightened security ...
Reply With Quote
  #7   (View Single Post)  
Old 7th February 2009
carpman carpman is offline
Shell Scout
 
Join Date: Jul 2008
Posts: 94
Thanked 0 Times in 0 Posts
Default

Umm ok looks like i am going to have to risk a reboot and hope it come back up, if not it is a trip to hosters

One more question, from your post it looks like on reboot i would have to run 'make installworld' again?

If is does not respond remotely then i take when i get access to it i will need to boot into single mode and do from there.

many thanks
Reply With Quote
  #8   (View Single Post)  
Old 7th February 2009
DutchDaemon's Avatar
DutchDaemon DutchDaemon is offline
Real Name: Ben
Spam Refugee
 
Join Date: Jul 2008
Location: Rotterdam, The Netherlands
Posts: 337
Thanked 32 Times in 30 Posts
Default

If everything leading up to 'make installworld' went fine (did 'make installkernel' actually work?), just continue where you left off, i.e. run 'make installworld' again. In fact, though I hardly ever take the effort to drop into single-user mode, that's where you really should be doing it. If you look at /usr/src/Makefile, you will notice that you're supposed to reboot into single-user mode after installing the new kernel, followed by mergemaster -p and make installworld, etc.

To be on the safe side, I would start over again after rebooting without a securelevel. Just clear /usr/obj and work off the list in /usr/src/Makefile. You may get away with just running 'make installworld', but that depends on how much risk you want to take. Installing a new world without an updated kernel can be fatal.
Reply With Quote
  #9   (View Single Post)  
Old 7th February 2009
carpman carpman is offline
Shell Scout
 
Join Date: Jul 2008
Posts: 94
Thanked 0 Times in 0 Posts
Default

yep kernel all went fine, so i will just try running

Quote:
make installworld
mergemaster -p
If system does not come up and have to attend it i will start afresh.

Trouble with single mode is it is not possible on remote server, well if it is i never found out how.


I will do a reboot in the morning and see what occurs.

many thanks
Reply With Quote
Old 7th February 2009
DutchDaemon's Avatar
DutchDaemon DutchDaemon is offline
Real Name: Ben
Spam Refugee
 
Join Date: Jul 2008
Location: Rotterdam, The Netherlands
Posts: 337
Thanked 32 Times in 30 Posts
Default

Please reverse the order to mergemaster -p and make installworld Frankly, if you made it to make installworld, you probably either already did mergemaster -p or you didn't need to because there were no new system accounts/groups that needed adding. Anyway, don't forget to run everything after that make installworld, esp. mergemaster (-U|-ai).
Reply With Quote
Old 8th February 2009
carpman carpman is offline
Shell Scout
 
Join Date: Jul 2008
Posts: 94
Thanked 0 Times in 0 Posts
Default

Ok did a reboot this morning and with great relief the server came back on line

It reported system as being 6.3.

I did:

Quote:
mergemaster -p
make installworld
mergemaster -viU
turned kern_securelevel=2 back on
reboot
uname -a reports 6.3-RELEASE-p9

Looks like everything has gone ok !

A question about mergemaster, with -p option it asks about

/tmp/temproot

i accept default which is to keep, after i run it with -viU option at the end it again asked if /tmp/temproot should be deleted!

I still have couple of file that i need to go through by hand so did not, i take this should be deleted when i have sorted those out?

cheers
Reply With Quote
Old 8th February 2009
DutchDaemon's Avatar
DutchDaemon DutchDaemon is offline
Real Name: Ben
Spam Refugee
 
Join Date: Jul 2008
Location: Rotterdam, The Netherlands
Posts: 337
Thanked 32 Times in 30 Posts
Default

Not deleting temproot just saves a little bit of time when you run mergemaster again. If you delete it, mergemaster will simply repopulate it. I usually just delete temproot after mergemaster -p and mergemaster -U/ai/whatever. It is advisable to 'finish' mergemaster before csupping again.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
freebsd 7.1 upgrade buildworld error map7 FreeBSD Installation and Upgrading 9 30th October 2008 06:54 PM
installworld fails - because I deleted master.passwd? TomAmundsen FreeBSD Installation and Upgrading 4 22nd September 2008 07:51 PM
How do I upgrade? wubrgamer FreeBSD Ports and Packages 2 27th August 2008 07:18 PM
FreeBSD 7.0 amd64 make installworld fails. KernelPanic FreeBSD Installation and Upgrading 8 11th June 2008 04:34 PM
upgrade from 5.5 to 6.3 keithlybsd FreeBSD Installation and Upgrading 9 27th May 2008 06:21 PM


All times are GMT. The time now is 11:40 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick