Prior to receiving this warning, for probably about a year, I had been receiving a lot of these notifications:
A couple weeks ago, I started doing some transfers of photos on the hard drive and it just suddenly started bogging down to a crawl. I unmounted the drive and remounted it to find the "Mac can't repair the disk" message. I tried to just use Drag and Drop in finder to back up some of the files, but Finder would complain of not being able to read some files and abort the entire copy. I know some of the files still have to be good in those 2.6TB of data.
I wondered if I could blame on the reoccurring "Disk Not Ejected Properly" (DNEP) issue. I found a very lengthy discussion on Apple's discussion forums about the issue. What I found in my case was that I had too much power usage going on in my home office. I have mini fridge in my office and discovered that when it kicks on is when I see the DNEP message. I unplugged the fridge and haven't seen it since. So I guess I'll be moving my fridge to the garage.
Nonetheless, I would really like to get those files back. I resorted to good old `rsync` to transfer what could be read from the corrupted disk.
- -a :: archive mode: a full recursive backup of the folder and its subfolders including some metadata details like modified time and permissions.
- -h :: human-readable: if you have progress output, the transfer info will be "human readable" like in terms of MB or GB.
- --progress :: shows the progress as it works its way through each file.
Now maybe you already have a lot of the files from HD1 on HD2 (as I did), to only copy new files you can use the `--ignore-existing` option. Also, including the slash at the end of the path on the source will copy the contents of the directory and including the slash at the end of the path on the destination directory will copy into the directory.
- -i :: prevents idle sleep
- -m :: prevents disks from sleep
- -s :: prevents system sleep (requires AC power)
I also found that after these long data transfers, if I were to print out the time the process finished I could see how long it's been done just for peace of mind in my estimations. This can be done with any command line process by appending `&& Date` to the end of the command. So the last command would become: