Mac: NFS Mount set to read-only

Recently I had an old external drive I wanted to mount use as a backup target, unfortunately when mounted it was set to read-only to resolve this i used the following  packages and commands : 

Write to an NTFS Drive With NTFS-3G:
Pre-Req: the following packages require installation, using brew :

  • #brew install ntfs-3g
  • #brew cask install osxfuse

NTFS-3G enables your Mac to write to NTFS drives, 
First, find the address of your mounted read-only drive, using the command:

#diskutil list

Before you try to mount the new volume, you need to unmount the existing read-only NFS drive, otherwise you will get the following:

  • Error opening ‘/dev/disk3s1’: Resource busy
  • Failed to mount ‘/dev/disk3s1’: Resource busy
  • Mount is denied because the NTFS volume is already exclusively opened.
  • The volume may be already mounted, or another software may use it which could be identified for example by the help of the ‘fuser’ command

#sudo umount /Volumes/YOURDRIVE/

You need to run the following commands each time that you want to mount a drive with write permissions.

Replace /dev/disk1s1 with the drive address that you found above:

#sudo mkdir /Volumes/NTFS
#sudo /usr/local/bin/ntfs-3g /dev/disk1s1 /Volumes/NTFS -olocal -oallow_other

Error: I received the following error on first run:

  • dyld: Library not loaded: /usr/local/lib/libosxfuse.2.dylib
  •   Referenced from: /usr/local/bin/ntfs-3g
  •   Reason: image not found, 

The Fuse library had an issue, I had an older version of fuse installed, so I reinstalled with: #brew cask reinstall osxfuse

If you don’t want to run these commands each time, there’s a fix.
You can boot your Mac into single-user mode, and replace the built-in Mac NTFS tools with NTFS-3G.
There are some warnings about security on the project site; you can check out the steps to enable it on the developer’s GitHub page.
The devs make it clear that this opens up your Mac to potential exploitation, so this step is not for the faint of heart.


Ref :


VMworld 2019 US- Sessions

VMworld US Playback URLs:

Download and stream Links

VxRail root password reset

  • Restart Guest (Not Reset) for VRM VM from vCenter
  • Press “e” at during boot sequence 
User-added image
  • Adding init=/bin/bash as below screen , then press F10
User-added image
  • Try to change password by #passwd   
User-added image
  •  If you get an Authentication token lock busy,  popup,you need to mount the file system     
  • #mount -o remount rw -t ext3 /   
  •  #chmod -v 4711 /usr/bin/passwd     
User-added image
  • Try change password again by #passwd     
User-added image
  •   Exit from VRM Console, then click “Restart Guest” on VRM VM from vCenter.     

Kubernetes/MiniKube on macOS Sierra 10:12

Before you begin, update Brew with :
#Brew update && brew upgrade

Install Minikube:
#Brew cask install minikube

Starting minikube:
#minikube start
😄  minikube v1.2.0 on darwin (amd64)
💿  Downloading Minikube ISO …
 129.33 MB / 129.33 MB [============================================] 100.00% 0s
🔥  Creating virtualbox VM (CPUs=2, Memory=2048MB, Disk=20000MB) …
E0701 16:09:52.739043   97475 start.go:559] StartHost: create: precreate: VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path
💣  Unable to start VM
❌  Error:         [VBOX_NOT_FOUND] create: precreate: VBoxManage not found. Make sure VirtualBox is installed and VBoxManage is in the path
💡  Advice:        Install VirtualBox, ensure that VBoxManage is executable and in path, or select an alternative value for –vm-driver

minikube looking for virutal box, locally i’m using with vmware fusion os we need to tell minikube to use that.
#minikube start –vm-driver vmware

Unable to start VM: new host: Driver “vmware” not found. Do you have the plugin binary “docker-machine-driver-vmware” accessible in your PATH?

To install the latest vmware driver :

#export LATEST_VERSION=$(curl -L -s -H 'Accept: application/json' | sed -e 's/."tag_name":"([^"])".*/\1/') \

&& curl -L -o docker-machine-driver-vmware$LATEST_VERSION/docker-machine-driver-vmware_darwin_amd64 \

&& chmod +x docker-machine-driver-vmware \

&& mv docker-machine-driver-vmware /usr/local/bin/

Start Minikube with the vmware driver
#minikube start –vm-driver vmware

  😄  minikube v1.2.0 on darwin (amd64)  
🔥  Creating vmware VM (CPUs=2, Memory=2048MB, Disk=20000MB) ... 🐳  Configuring environment for Kubernetes v1.15.0 on Docker 18.09.6 💾  Downloading kubeadm v1.15.0
💾  Downloading kubelet v1.15.0
🚜  Pulling images ...
🚀  Launching Kubernetes ... 
⌛  Verifying: apiserver proxy etcd scheduler controller dns
🏄  Done! kubectl is now configured to use "minikube"
Enable & Start Minikube dashboard:  
#minikube dashboard
 🔌  Enabling dashboard …
🤔 Verifying dashboard health …
🚀 Launching proxy …
🤔 Verifying proxy health …
🎉 Opening in your default browser…

Now the next time I start minikube it starts with the vmware driver

#minikube start
😄  minikube v1.2.0 on darwin (amd64)
⚠️  Ignoring --vm-driver=virtualbox, as the existing "minikube" VM was created using the vmware driver.
⚠️  To switch drivers, you may create a new VM using `minikube start -p <name> --vm-driver=virtualbox`
⚠️  Alternatively, you may delete the existing VM using `minikube delete -p minikube`

🔄  Restarting existing vmware VM for "minikube" ...
⌛  Waiting for SSH access ...
🐳  Configuring environment for Kubernetes v1.15.0 on Docker 18.09.6
🔄  Relaunching Kubernetes v1.15.0 using kubeadm ... 
⌛  Verifying: apiserver proxy etcd scheduler controller dns
🏄  Done! kubectl is now configured to use "minikube"

The Dashboard should open automatically in your browser