While using your Mac device you can encounter more than one glitches with it. Error: -69877: couldn’t open device, is one of the common errors which you can encounter when you have no permission to repair directories or disk utilities. In this case, Mac fails to eliminate the partition of the drive. When this typical error occurs, then the Network deployment tools like Apple’s Netinstall service or the DeployStudio fails to perform it’s own work and leaves an error message “Error: -69877: couldn’t open device”. In case, you come across this error and want to resolve it, then you are in the perfect page. This article consists of some simple hacks, which will help you out. Now, at first, let’s know the causes due to which you are getting this error.
Causes for Error: -69877: Couldn’t Open Device
When you encounter this error on Mac then, you get an error message showing Error: -69877: Couldn’t Open Device. The main reason to encounter this error is the alteration of the boot drive. It can also happen when the same device is being used by some other application or process. In case, OS X Recovery exists as a partition in the physical disk then, the system becomes unable to modify or unmount the internal drive. As a result of which, you can encounter this error with your Mac device.
Well, after knowing the causes now, let’s start the troubleshooting process.
Fixes for Error: -69877: Couldn’t Open Device
Though you can encounter this error due to several reasons, you can fix it using simple hacks and tricks listed below.
Method 1: Using Boot Drive
This is one of the most popular methods which you can use to fix this issue. In this case, you will need an OS X boot drive to complete the task.
But, the important point which you should remember is that the installer or the recovery drive must be there on the drive, and it should be separated from the primary boot disk, with the help of the installed OS in it.
Now, you can try out these steps:
- First of all, you have to attach the Boot drive into the Mac and you have to reboot your device.
- After that, you have to hold down the OPTION key, as well as, you have to select the boot drive which has been selected.
- Now, you have to access the Disk Utility, with the help of the Boot menu. Basically, it is a Utility menu which is used for the Installer Disk Verification of the Disk.
- When done click on the “First Aid” option.
- In this way, you will be able to complete the repair process.
After performing all of these steps, you should try to check the status of the error. If it persists then, try to move on to the next step.
In order to perform this task, note that you have to use a boot device. Otherwise, the problem will remain unresolvable. So, you can use a bootable thumb drive which will be a great option for Mac error resolution. In case, if you are using older Mac OS X like 10.6 or earlier, then you can use SuperDrive and a bootable DVD, as it will offer the same resolution.
Method 2: Fix it using Recovery Partition
You can also get this particular error on your device due to the First Aid or while you are formatting a non-boot partition. In this case, you can use a recovery partition which is available in all of the versions of Mac OS X, to help you out. But, these processes are not applicable for the modification of the boot disk using the partitions or formatting. In this situation, you can try out these steps.
- At first, you have to reboot your Mac device. Now, you have to hold down the Option key and you will be able to see the recovery partition.
- From the Boot menu, you have to choose the Disk menu.
- After completing all of these steps, you will be able to complete the verification and repairing process with the “First Aid.”
Otherwise, you can also choose “Erase” to perform the disk formatting. But, in case, you use the disk as the same primary boot partition, then this method might not work. You will be able to overcome this issue if you use a separate USB drive for the troubleshooting process.
Final Words
Hopefully, using this hacks and tricks you will be able to troubleshoot this particular error without any hassle. In case, if you encounter any kind of system glitches then, you can leave a comment below. On that note, we are concluding this post.
