This guide will talk about rebuilding a failed RAID 1 disk with WD My Book Duo on macOS, it should also works on Thunderbolt Duo or other RAID 1 setup.
Many other guides only tell you how to replace the whole two disks without restoring / rebuilding data for this common situation:
In a common case, your RAID 1 setup could fail with only one defective disk, while the other is online. If you see this status on your macOS:
- Buy a brand new disk, same size and model as your failed disk.
- Reboot your mac in recovery mode, this step is very important to make sure your disks are not used by macOS.
- In recovery boot, open Disk Utility.
- Rename your RAID set, for example if your RAID set is
External-Raid, rename it to something like
External-Raid-Rebuild or just some names different than your original, this is the most important step to make sure your RAID set wouldn’t be using after entering macOS system.
- Restart your system in normal mode.
- Login to your system, then open Disk Utility, congrats, you will see the new disk is now rebuilding.
- Restraint editing/adding/removing files on your RAID set while rebuilding.
- The rebuild process could take hours depends on your disk size (10-20 hours for a 4 TB + 4 TB RAID 1 setup).
- After the rebuild complete, you can rename your RAID volume name back to original.
This is not the only way to rebuild your RAID with a failed disk. According to WD documentation, you can power on your My Book Duo without connecting to macOS (remove the thunderbolt cable), then the My Book Duo should rebuild it automatically. However, it’s really hard to know when the rebuild process will finish, there’s no special indicator status for this situation, so I prefer rebuilding in macOS. This could be the best method for me.
sudo vi /etc/services
5900 and edit it.
sudo launchctl unload /System/Library/LaunchDaemons/com.apple.screensharing.plist
sudo launchctl load /System/Library/LaunchDaemons/com.apple.screensharing.plist
It was available at
If you like me owning more than one Mac and using one of them to control the other via macOS built-in Screen Sharing feature, you may occur this issue after you upgrade your macOS to Sierra.
macOS Sierra introduces a new feature Universal Clipboard which can share the same clipboard among iOS and macOS devices. This sounds cool, but as it’s technically a part of Continuity feature, it would require Bluetooth to work.
So the problem is, when I control my Mac mini from my MacBook Pro via Screen Sharing in the same network, with the Shared Clipboard enabled, the Universal Clipboard would still always try to “sync” copied content via Bluetooth instead of using Screen Sharing Shared Clipboard.
It’s ok if both of your Macs are at your hand, but it’s a disaster if they’re in different rooms, Universal Clipboard via Bluetooth would become really slow to connect to each other, and this issue could even make your VNC drop connection if you copy images to your clipboard.
So here’s the solution, just disable Bluetooth on your Mac mini, and wait Apple to fix this bug.
$ sudo /usr/libexec/repair_packages --verify --standard-pkgs /
$ sudo /usr/libexec/repair_packages --repair --standard-pkgs --volume /
Install required packages via Homebrew:
$ brew install gpg gpg-agent pinentry-mac
Edit and add the following lines in
Edit and enable
Then add the following line to your shell profile:
eval $(gpg-agent --daemon --sh)
Apple introduces System Integrity Protection (SIP) as a security feature for OS X El Capitan (10.11), which prevent ProxyChains-NG working as before, you have to disable SIP to make it work:
- Reboot your Mac into Recovery Mode by pressing command-R
- Open Terminal and type
csrutil enable --without debug:
$ csrutil enable --without debug
$ csrutil: requesting an unsupported configuration. This is likely to break in the future and leave your machine in an unknown state.
$ Successfully enabled System Integrity Protection. Please restart the machine for the changes to take effect.
Just ignore the warnings and then restart your Mac.
You can get all proxy bypass domains using:
$ networksetup -getproxybypassdomains "Wi-Fi"
Wi-Fi should be your current interface, you can also update it using:
$ networksetup -setproxybypassdomains "Wi-Fi" \
man networksetup for more information
If you have the environment variable
XDG_DATA_HOME set, the installation is located at
$XDG_DATA_HOME/letsencrypt. Otherwise, it is located at
~/.local/share/letsencrypt. You can simply delete this directory. You can also delete configuration, work, and log directories which by default are stored at
/var/log/letsencrypt respectively. The directory where you cloned our git repo can also be deleted.
Let’s Encrypt also installs some OS dependencies and how you remove these would be very OS specific. To see what dependencies were installed, take a look at the files in the bootstrap folder at the root of our git repo (link). Take a look at the shell script for your OS to see what packages are required. You can uninstall these packages through the normal means of your OS, but make sure they aren’t required by any other programs on your system.
Source: Uninstalling letsencrypt – Let’s Encrypt Community Support