Re: buildworld, buildkernel, installkernel, shutdow now, fsck -p -- NO WRITE ACCESS
[EMAIL PROTECTED] wrote: Daniel Bye wrote: On Mon, Aug 04, 2008 at 06:37:28PM -0400, email wrote: I thank you. In addition, I am quite sure the command we are referred to in 23.4.5 Drop to Single User Mode is in fact 'shutdown now' and not 'shutdown -r now'. Yes. But that section relates to dropping to single user mode for the duration of the build, not for the installworld phase. To quote from 23.4.5: You may want to *compile* the system in single user mode. (Emphasis mine) It is merely a possible preparatory step that some people like to take before embarking on the rest of the process. Section 23.4.9 goes on to talk about what to do after the world and kernel build are complete, and you have installed the new kernel: You should reboot into single user mode to test the new kernel works. Do this by following the instructions in Section 23.4.5. This refers specifically to the part of 23.4.5 that talks about rebooting into single user mode, and not the part that talks about dropping to single user mode. (A subtle, but important, distinction.) I would suggest that the simplest approach would be something like: # cd /usr/src # make buildworld make buildkernel # make installkernel (reboot into single user mode) # fsck -p # mount -u / # mount -at ufs # swapon -a # cd /usr/src # make installworld # mergemaster (Just so we're clear - section 23.4.5 talks about going to single user mode for the duration of the *first 3 steps* of the above process. As I mentioned previously, I have never found this step necessary, but there is certainly no harm in it, and it may be the sensible thing to do if your system has a lot of users logged in during normal operations. Note that you must still reboot after installing the new kernel, and before continuing to installworld.) Dan I followed 'your' suggestion/recommendation and did 'shutdown -r now' with great results; -- fsck -p works fine. However allow me to say that the fbsd handbook section 23.4.9, which I was initially following referred me back/up to section 23.4.5. The entire section -- 23.4 Rebuilding “world” only mentioned 'shutdown -r now' one (1) time in section 23.4.12. Had the fbsd handbook mentioned 'shutdown -r now' instead of referring the reader to another section perhaps I wouldn't be discussing this with you. :-) Sorry to make this longer than it needed to be. I thank you once again. The handbook does say in section 23.4.2 that if /usr/src/UPDATING contradicts something you read in the handbook, UPDATING takes precedence so I guess it does cover itself. The steps in UPDATING seem to work pretty well. I sometimes do mergemaster -iU at the second mergemaster step in the To rebuild everything and install it on the current system step as I mostly don't change the files that get reviewed by mergemaster, otherwise I stick exactly to UPDATING and get almost no problems. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld, buildkernel, installkernel, shutdow now, fsck -p -- NO WRITE ACCESS
Polytropon wrote: On Mon, 04 Aug 2008 18:37:28 -0400, email [EMAIL PROTECTED] wrote: I thank you. In addition, I am quite sure the command we are referred to in 23.4.5 Drop to Single User Mode is in fact 'shutdown now' and not 'shutdown -r now'. While shutdown now puts you into SUM at once, not unmounting anything, shutdown -r now reboots the system and it's up to you to enter SUM via kernel interruption and boot -s, and in this state, nothing is mounted. Hi, thanks for your reply. I wasn't discussing the difference between 'shutdown now' and 'shutdown -r now'; my concern was it appears that the fbsd handbook section I was reading, with regards to REBUILDING WORLD, instructed the reader to do a 'shutdown now' instead of a proper 'shutdown -r now', which in turn caused me grief when attempting to run 'fsck -p'. Once again I thank you for your reply. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld, buildkernel, installkernel, shutdow now, fsck -p -- NO WRITE ACCESS
On Mon, Aug 04, 2008 at 04:00:56PM -0400, [EMAIL PROTECTED] wrote: I do not code in any way. With that being said, should you be able to help please do so with the knowledge that I can not code. I'm following the freebsd handbook when the following occurs. -- separate fresh 'dangerously dedicated' installs of both 7.0 and 6.3-RELEASE on the same machine, yield the following: In multi-user mode make buildworld, buildkernel and installkernel. Shutdown now This will only drop you to single user mode with all filesystems still mounted. It is not a good idea to run fsck on a mounted filesystem... Instead, you need to run # shutdown -r now to REBOOT the machine with the newly installed kernel. At the loader menu, press `4' to boot into single user mode (at this point, only / will be mounted, so your `fsck -p' should work just fine). Now procede with the next steps... -- fsck -p /dev/ad4s1a: NO WRITE ACCESS /dev/ad4s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY This happens each and everytime no matter if I install from iso -or- ftp (passive). After numerous attempts the only way to get past this is 'fsck -y'. Could the fbsd handbook section I'm following need updating or is there another issue taking place here? I think you're getting confused by the instructions (don't have a browser to hand so can't check the handbook, so apologies if this isn't the case). IIRC, the handbook suggests you drop to single user BEFORE you begin, in order to ensure nothing else is running while you run the build. In my experience, this has not been necessary. Even still, after the installkernel you MUST reboot the newly installed kernel before you continue. HTH Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgp37l6bYbf2D.pgp Description: PGP signature
Re: buildworld, buildkernel, installkernel, shutdow now, fsck -p -- NO WRITE ACCESS
Daniel Bye wrote: On Mon, Aug 04, 2008 at 04:00:56PM -0400, [EMAIL PROTECTED] wrote: I do not code in any way. With that being said, should you be able to help please do so with the knowledge that I can not code. I'm following the freebsd handbook when the following occurs. -- separate fresh 'dangerously dedicated' installs of both 7.0 and 6.3-RELEASE on the same machine, yield the following: In multi-user mode make buildworld, buildkernel and installkernel. Shutdown now This will only drop you to single user mode with all filesystems still mounted. It is not a good idea to run fsck on a mounted filesystem... Instead, you need to run # shutdown -r now to REBOOT the machine with the newly installed kernel. At the loader menu, press `4' to boot into single user mode (at this point, only / will be mounted, so your `fsck -p' should work just fine). Now procede with the next steps... -- fsck -p /dev/ad4s1a: NO WRITE ACCESS /dev/ad4s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY This happens each and everytime no matter if I install from iso -or- ftp (passive). After numerous attempts the only way to get past this is 'fsck -y'. Could the fbsd handbook section I'm following need updating or is there another issue taking place here? I think you're getting confused by the instructions (don't have a browser to hand so can't check the handbook, so apologies if this isn't the case). IIRC, the handbook suggests you drop to single user BEFORE you begin, in order to ensure nothing else is running while you run the build. In my experience, this has not been necessary. Even still, after the installkernel you MUST reboot the newly installed kernel before you continue. HTH Dan I thank you. In addition, I am quite sure the command we are referred to in 23.4.5 Drop to Single User Mode is in fact 'shutdown now' and not 'shutdown -r now'. I thank you for your response as I am going to redo this procedure as you described. If you don't mind I'll follow-up with you and/or conclude this thread with the results. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld, buildkernel, installkernel, shutdow now, fsck -p -- NO WRITE ACCESS
On Mon, 04 Aug 2008 18:37:28 -0400, email [EMAIL PROTECTED] wrote: I thank you. In addition, I am quite sure the command we are referred to in 23.4.5 Drop to Single User Mode is in fact 'shutdown now' and not 'shutdown -r now'. While shutdown now puts you into SUM at once, not unmounting anything, shutdown -r now reboots the system and it's up to you to enter SUM via kernel interruption and boot -s, and in this state, nothing is mounted. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld, buildkernel, installkernel, shutdow now, fsck -p -- NO WRITE ACCESS
On Mon, Aug 04, 2008 at 06:37:28PM -0400, email wrote: I thank you. In addition, I am quite sure the command we are referred to in 23.4.5 Drop to Single User Mode is in fact 'shutdown now' and not 'shutdown -r now'. Yes. But that section relates to dropping to single user mode for the duration of the build, not for the installworld phase. To quote from 23.4.5: You may want to *compile* the system in single user mode. (Emphasis mine) It is merely a possible preparatory step that some people like to take before embarking on the rest of the process. Section 23.4.9 goes on to talk about what to do after the world and kernel build are complete, and you have installed the new kernel: You should reboot into single user mode to test the new kernel works. Do this by following the instructions in Section 23.4.5. This refers specifically to the part of 23.4.5 that talks about rebooting into single user mode, and not the part that talks about dropping to single user mode. (A subtle, but important, distinction.) I would suggest that the simplest approach would be something like: # cd /usr/src # make buildworld make buildkernel # make installkernel (reboot into single user mode) # fsck -p # mount -u / # mount -at ufs # swapon -a # cd /usr/src # make installworld # mergemaster (Just so we're clear - section 23.4.5 talks about going to single user mode for the duration of the *first 3 steps* of the above process. As I mentioned previously, I have never found this step necessary, but there is certainly no harm in it, and it may be the sensible thing to do if your system has a lot of users logged in during normal operations. Note that you must still reboot after installing the new kernel, and before continuing to installworld.) Dan -- Daniel Bye _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ pgpnzbqKAcFb9.pgp Description: PGP signature
Re: buildworld, buildkernel, installkernel, shutdow now, fsck -p -- NO WRITE ACCESS
Daniel Bye wrote: On Mon, Aug 04, 2008 at 06:37:28PM -0400, email wrote: I thank you. In addition, I am quite sure the command we are referred to in 23.4.5 Drop to Single User Mode is in fact 'shutdown now' and not 'shutdown -r now'. Yes. But that section relates to dropping to single user mode for the duration of the build, not for the installworld phase. To quote from 23.4.5: You may want to *compile* the system in single user mode. (Emphasis mine) It is merely a possible preparatory step that some people like to take before embarking on the rest of the process. Section 23.4.9 goes on to talk about what to do after the world and kernel build are complete, and you have installed the new kernel: You should reboot into single user mode to test the new kernel works. Do this by following the instructions in Section 23.4.5. This refers specifically to the part of 23.4.5 that talks about rebooting into single user mode, and not the part that talks about dropping to single user mode. (A subtle, but important, distinction.) I would suggest that the simplest approach would be something like: # cd /usr/src # make buildworld make buildkernel # make installkernel (reboot into single user mode) # fsck -p # mount -u / # mount -at ufs # swapon -a # cd /usr/src # make installworld # mergemaster (Just so we're clear - section 23.4.5 talks about going to single user mode for the duration of the *first 3 steps* of the above process. As I mentioned previously, I have never found this step necessary, but there is certainly no harm in it, and it may be the sensible thing to do if your system has a lot of users logged in during normal operations. Note that you must still reboot after installing the new kernel, and before continuing to installworld.) Dan I followed 'your' suggestion/recommendation and did 'shutdown -r now' with great results; -- fsck -p works fine. However allow me to say that the fbsd handbook section 23.4.9, which I was initially following referred me back/up to section 23.4.5. The entire section -- 23.4 Rebuilding “world” only mentioned 'shutdown -r now' one (1) time in section 23.4.12. Had the fbsd handbook mentioned 'shutdown -r now' instead of referring the reader to another section perhaps I wouldn't be discussing this with you. :-) Sorry to make this longer than it needed to be. I thank you once again. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
