1

I am following this guide, but cannot add the virtual hard disk at step 6. I get a 'No permission' pop-up.

enter image description here

How do I grant myself permission?

Community
  • 1
HaloLamp
  • 23

1 Answers1

1

One of the commands, given in step 5 that prevents this error message from occurring, is repeated below.

sudo  chown  $USER  bootcamp*.vmdk

This command changes ownership from the root user to the current user. In your case, I assume the current user is named Nick. To verify you entered this command correctly, you can enter the command below. Here I assume your current directory still is ~/Documents/VirtualBox.

ls -l bootcamp*

In your case, the output should appear as shown below.

cd ~/Documents/VirtualBox
ls -l bootcamp*
-rw-------  1 Nick  staff  37376 14 sep 15:43 bootcamp-pt.vmdk
-rw-------  1 Nick  staff    682 14 sep 15:43 bootcamp.vmdk

From your comments, I assume this is what you currently would get.

cd ~/Documents/VirtualBox
ls -l bootcamp*
-rw-------  1 root  staff  37376 14 sep 15:43 bootcamp-pt.vmdk
-rw-------+ 1 root  staff    682 14 sep 15:43 bootcamp.vmdk

This output shows you are not the current owner of these files. Additionally, the + character indicates you have added extended security information such as an access control list.

Another one of the commands, given in step 5 that prevents this error message from occurring, is repeated below.

sudo  chmod  go+rw  $PARTID

In step 5, a warning is given, which is repeated below.

Note: This access granted by the chmod command will only last until OS X is rebooted.

BTW, the command without the variable is given below.

sudo  chmod  go+rw  /dev/disk0s4

One way, to verify you enter the chmod command correctly, would be to enter the following command. 

ls -l /dev/disk0s4

In your case, the expected output is shown below.

brw-rw-rw-  1 root  operator 1, 4 14 sep 15:38 /dev/disk0s4

The most likely causes of your problem are given below.

  • You are not using the default bash shell.
  • You did not enter the chown command.
  • You did not enter the chown command correctly.
  • You were the root user when you entered the chown command.
  • You added extended security information to the file entries.
  • You did not enter the chmod command.
  • You did not enter the chmod command correctly.
  • You rebooted the operating system.
David Anderson
  • 40,244
  • I am doing exactly what the guide tells me to do. No reboot, entered the code once more, got 'disk0s4 was already unmounted' as a result. I still get the same message afterwards. – HaloLamp Sep 15 '16 at 19:22
  • What does ls -l /dev/disk0s4 show the file mode (permissions) to be? – David Anderson Sep 15 '16 at 20:57
  • The result I get is:

    brw-rw-rw- 1 root operator 1, 4 14 sep 15:38 /dev/disk0s4

    Thank you for your help in the past few days, David. Really appreciate it, as it may seem whiney to keep asking questions.

     – HaloLamp Sep 15 '16 at 22:37
  • That looks OK. What does ls -l bootcamp* show for ownership? I assume your current directory is ~/Documents/VirtualBox. – David Anderson Sep 15 '16 at 23:16
  • ls -l ~/documents/virtualbox/bootcamp* gives -rw------- 1 root staff 37376 14 sep 15:43 /Users/Nick/documents/virtualbox/bootcamp-pt.vmdk as well as -rw-------+ 1 root staff 682 14 sep 15:43 /Users/Nick/documents/virtualbox/bootcamp.vmdk . – HaloLamp Sep 16 '16 at 13:51
  • This time you have the wrong output. Read my updated answer. – David Anderson Sep 16 '16 at 19:21