terminal could not unmount disk resource busy

Gpt recover: /dev/disk1: recovered primary GPT table from secondary

To proceed, enter your password, or type Ctrl-C to abort. Or the deletion of important system files. WARNING: Improper use of the sudo command could lead to data loss IronMan:~ nbalkota$ sudo gpt recover /dev/disk1 If the last command was successful, disconnect and reconnect your disk, which should now be OKģ: Apple_Boot Recovery HD 650.0 MB disk0s3.Start terminal and use the 3 commands in bold red below (make sure to change the disk number to match your setup based on the first command).I would guess the disk did not like being unplugged without using the eject command…Īnyway, salvation can come at no cost by using the Terminal in Mac OS X (assuming you have administrative rights): Don’t ask me how it got corrupted in the first place. In Disk Utility the drive device was listed, but no volume could be mounted due to a corrupted partition map. Now, I take pride in having never ever lost any data on my Macs since 1998, so I was concerned this might be the end of my record… The disk you inserted you inserted was not readable by this computer. Today, as I intended to perform my regular Time Machine backup, I got welcomed by a very scary message when I connected my external hard disk to my MacBook.

Terminal could not unmount disk resource busy