Where does one get this mythical WD Drive Utilities app?
Found it, but it only works with OSX 10.8 and above:
My Mom is having issues on an older OS. Can I adjust the settings with this drive connected to my newer mac… and will the settings stick when we put the drive back on her computer?
There are a few different theories rolling around this thread:
- That the issue happens when the Mac computer is asleep
- That the issue happens when the WD Drive goes to sleep
- That the issue happens when OS X Power Nap is either on or off
Does anyone know why different people are getting results with various solutions?
I would try changing the settings on your newer Mac and then (re-)connecting to your Mom’s. I don’t think it could hurt – just may not help.
Can’t say for sure why different people are having different results. I do know that the Mac has been known to have waking-up problems with all kinds of drives, including SD cards. My guess is, that problem is exacerbated by WD’s default Sleep Timer setting of 30 minutes. So, the Mac might try to wake up but the drive, in the meantime, has gone to sleep because of WD’s setting, regardless of the Mac’s setting(s) to not let the drive sleep. The drive will sleep if the WD utils setting tells it to, by default. That’s my guess.
It’s been a month since I changed that setting in the WD Utils and I haven’t had any recurrence of the problem. All Time Machine backups have run without fail or error.
Hope this helps!
I purchased a My Passport for Mac 2TB a couple of weeks ago and had the same exact problem. The drive connects very easily to Time Machine and a few to several hourly backups work fine and then the error message pops up. WD tech support advised me to erase the drive and reformat it, I’m not sure what good that did as the box said it was Mac ready and compatible with Time Machine but whatever.
It made no difference, the error came back later that day. I exchanged it at Best Buy for another new one and it had the same issue so I returned it a for a refund. There are over 850 reviews on Best Buy for this drive and about 98% of them are 4 and 5 stars so this must be working fine for most people.
After talking to WD on the phone, they sent a follow up e-mail with a link to this forum. It was here that I found I wasn’t the only one having this problem. I mentioned to the support tech on a second call that this was a topic of concern on their own forum but she seemed completely unaware of it.
I ended up purchasing a 1TB G-Drive from the Apple Store and it has been working fine for about 6 days now, I’ll feel better after 6 months with no problems but so far so good. I was surprised to find after opening the box that G-Drive is owned by WD.
Like so many others, this was the error message for the My Passport backup.
Edit: I forgot to mention, High Sierra 10.13.4
This is rubbish. Exact same problem. Reboot Mac and works fine. Sleep off on drive settings. Still get the above. Is there really no way to counteract this???
Hi all. Same problem but with G Drives. As far as I can tell it only happens when the drive is connected via Firewire but works fine over USB (in my case USB2).
Originally wanted to connect 2 drives to the single firewire port so daisy chained both drives. Had the error and failed Time Machine backup. Thought it was because of the daisy chaining but have now had the problem with just one of the drives. Connected it via USB and problem gone.
Frustrating as firewire 800 is 3/4 times faster than my USB2 and so far haven’t found a solution.
May not be any help to anyone but thought I would mention.
I initially had the same issue, so I followed the advice of removing the password from the HD. I then restarted the computer and have had no issues with auto-backups since. I hope this works for you! Good luck.
I turned off Power Nap after noticing that the My Book failed overnight and would not back up manually this morning. I also had to just pull out the USB cable from my iMac because it wouldn’t eject. I got a message that the My Book was being used. Pulled it anyway since I was disgusted. This was the second My Book; I returned the first. Soon as I turned off power nap in System Preferences, I could back up.
One would think …surely … that with all of this correspondence going on about their crummy product, that someone from the company would finally have something to say!
But No … And So … shall we say “Never Again”
Returning the My Book to Best Buy after I erase it. I just hate getting a La Cie from Apple because they always break.
This issue is not specific to WD external drives. I’ve experienced it using my WD external drive and Synology NAS Time Machine Backup drive. This is an Apple issue. Try the following solution which worked for me.
I have the exact same problem. Using Porsche Design external drive, Firewire, Mac O/S 10.12.6
I believe I found a possible solution that may help a future searcher.
If you use your hard disk for both mac and PC, you shall know that it must be partitioned in a special format for each. and time machine did not work when I tried to backup (mistakingly I guess) to the volume allotted for PC. Please look up partition formats and make sure you are backing up to the one for Mac (Or make sure the format is right to begin with for Mac.) Best of luck.
EDIT: Nevermind, this only worked temporarily, it failed during sleep, I think.
Ok, So here’s what worked for me,
I’m running Mojave 10.14.3
I Set Sleep In Utilities to Off
I turned off Nap
Nothing so far,
I opened Time Machine
Unplugged the disk from the computer
Removed the disk from the selection on the Time Machine
Restarted my computer
Plugged the disk back in
It went through the “Use this Disk for Backup” process again
and now it’s working, hope this helps
Where on the mac do you find utilities?
You can download the WD Drive Utilities app from the WD website, open it, and select settings/ Sleep Timer OFF. However, my auto-backup failed even with the WD Sleep Timer off. It worked for a month, and then failed. At that point I had to unmount & unplug the drive, remount, give it the password again, and then it worked again. I’m hoping it works for a while before the next failure.