View Single Post
  #5   (View Single Post)  
Old 13th May 2012
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,983
Default

Quote:
Originally Posted by daemonfowl View Post
Thanks jgimmi !
( I tried single-user mode but received the same error : unable to write label
and the mount point for wd0d (/tmp) was an empty place when I tried resizing or deleting .. so I ended up with x , losing changes.)
Sigh.
  • Post your disklabel.
  • Post the disklabel you want to have, or the changes you want to make.
  • Post the disklabel(8) command/commands you are using.
  • POST THE EXACT ERROR MESSAGES YOU RECEIVE.
I keep asking, and I never get this information. I'm tired of guessing. Here is some spoon-feeding. If this helps, great. If you cannot follow this .... you are on your own.
  1. Boot single-user mode. How you do this varies by architecture.
  2. Mount all partitions. You will need /usr directories mounted for script(1) and col(1).

    # mount -a
  3. Dismount /tmp.

    # umount /tmp
  4. Run script(1):

    # script
  5. Obtain the current disklabel.

    # disklabel wd0
  6. Edit the disklabel with the built-in command driven editor.

    # disklabel -E wd0
  7. use the "m" command to modify the /tmp partition. That might be "d", but I have no clear idea if that is so.

    > m d
  8. Press Enter in response to the Offset:prompt. You do not want to change the starting location.
  9. Type a size in response to the Size: prompt. Append with "g" or "m" for gigabytes or megabytes.
  10. Press Enter in response to the FS type: prompt.
  11. Use the "w" command to write the modified disklabel.

    > w
  12. Use the "q" command to exit the command driven editor.

    > q
  13. If you were actually successful in changing the disklabel, format the newly resized partition with newfs(8).

    # newfs wd0d
  14. Use CTRL-D or the "exit" shell command to leave script(1).
  15. Clean control characters from the script log with col(1).

    # col -b < typescript > myscript.output.file
  16. Reboot in multiuser mode, copy and paste /myscript.output.file into this thread. We will then finally know what your disklabel looks like now, what error message(s) you receive when you try to change it, and what your disklabel will look like should you end up being successful, after all.

Last edited by jggimi; 13th May 2012 at 05:17 PM. Reason: typo, added newfs
Reply With Quote