Yet another Time Machine issue

I had a failure in time machine several months ago, and did a full reset of time machine as instructed on the discussion boards. Today I noticed that not only had Time machine failed to Back up, but it had no back ups when I 'entered' it.
When I reset Time Machine (on a 4 T external hard drive, so space isn't an issue), it failed with an error message:
The backup was not performed because an error occurred while copying files to the backup disk.
The problem may be temporary. Try again later to back up. If the problem persists, use Disk Utility to repair your backup disk. WHen that volume is repaired (disk is partitioned) it says volume repair complete, and updating boot support partitions for the volume as required. Then it says Error: Couldn't unmount disk. When the second partition is repaired, it sends the same message.
I assume this is a problem with the Back Up Disk (a Lacie, purchased within the last few months). Or, is it a problem with Time Machine?
Any help out there?
THANKS
I have been running Lion for about a month.

Sounds like a problem with the drive like a corrupted directory or RDB. I would just erase the drive with Disk Utility and start over:
Drive Preparation
1. Open Disk Utility in your Utilities folder.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.

Similar Messages

Yet another TIme Machine hair-puller

What gives with this software? I've read on these forums that people have plugged in a FW/USB disk directly into their laptops, done an initial backup and then plugged the disk into either an AEBS or another Mac running Leopard and are happily, wirelessly backing up. Not me.
When I do the initial backup of my laptop over the FW, it works fine, creating the backups.backupd folders and everything. But when I plug the LaCie 500GB into my iMac and network it, Time Machine tries to back up to it as if it's never seen it before and writes a sparse image file to the external drive. This isn't what I wanted, is it? I just wanted to do an hourly backup, and it's trying to back up my entire disk of about 100GB of data.
Any ideas? 10.5.1 can't come soon enough at this rate.

Try searching the forum for "sparse image" and/or "backing up two Macs on one external disk" (or something similar. There were a few threads in the last week or so that spoke to this issue - I haven't had the pleasure, so I can't help you...

Time Machine issues (16030) sparsebundle" is already in use for Time Capsule backup

Time Machine issues (16030) sparsebundle” is already in use for Time Capsule backup process. Just started happeing been using it for over two years.

First, restart the computer and the Time Capsule. In most of the cases, this solve the problem.
If it doesn't work, see > http://pondini.org/TM/C12.html

Time Machine issues with OS 10.6.8

Hi all,
after updating to 10.6.8 I noticed a Time Machine issue.
Backup takes very long but only a few MB were backed up.
And after it was finished, Finder crashed and I had to do a hard reset.
There´s also a "in progress" file on my USB Backup HDD after finishing.
Checking my HDD´s and repairing it wasn´t the problem.
Today I tried a new USB HDD to make a fresh Backup via Time Machine.
After a few hours it was finished, but only 7,8MB were backed up and still there is an "in progress" file on my new Backup HDD.
Here´s a troubleshoot:
Starting standard backup
Backing up to: /Volumes/My Book/Backups.backupdb
Ownership is disabled on the backup destination volume. Enabling.
Backup content size: 368.5 GB excluded items size: 75.7 GB for volume Macintosh HD
No pre-backup thinning needed: 351.34 GB requested (including padding), 930.54 GB available
Waiting for index to be ready (101)
CarbonCore.framework: coreservicesd process died; attempting to reconnect but future use may result in erroneous behavior.
Copied 7.2 MB of 292.8 GB, 5 of 1058420 items
Copied 11 files (27.1 MB) from volume Macintosh HD.
No pre-backup thinning needed: 100.0 MB requested (including padding), 930.52 GB available
Copied 165 bytes of 0 bytes, 4 of 0 items
Error: (-36) SrcErr:YES Copying / to (null)
Copied 7 files (236 bytes) from volume Macintosh HD.
Error -50 deleting backup: /Volumes/My Book/Backups.backupdb/Computer/2011-07-19-180247.inProgress
Starting post-backup thinning
No post-back up thinning needed: no expired backups exist
Backup completed successfully.
Can anyone help me?

A whole lot about Time Machine for help with TM problems. Also you can select Mac Help from the Finder's Help menu and search for "time machine" to locate articles on how to use TM. See also Mac 101- Time Machine.
There are two important errors noted in the backup:
I-O error -36 « fuzzybrain|daisychain|blogdrain
The following comes from the LaCie web site but is applicable to any other external drives whether home brew or commercial.
Getting error -50 when copying data in OS X.
Some LaCie drives ship out formatted FAT32 so they will be ready to use on either a Mac or a PC. If you are getting error -50 when copying to a LaCie drive, or any drive formatted for PC, it is because of the following:
Certain characters that can be used in a Mac OS X filename are not allowed in MS-DOS filenames. This can prevent the file from being copied, and can occur when a filename contains non-printing ASCII characters, or any of these characters: ? / \ < > " | > *.
Either copy the data off of the drive and use Apple's Disk Utility to erase the drive in Mac OS Extended format, or change the filenames of the documents that cannot be copied.

Time machine issue after Yosemite install

After performing a clean install of Yosemite and migration from my TimeMachine backup I experienced the following:
I opened iTunes and selected some music to play, then got a dialog box saying the files could not be found. Spotlight couldn't find them either... they were just gone. Naturally I went to my Time Machine backups and was surprised the music was gone from the backups, all the way back to the first backup. Very wierd. During the migration I went through the "Cleaning up old backups" process, not sure exactly what this process is.
I was pretty bummed that I had permanently lost a lot of music, some was recordings of friends playing live that could never be replaced. I then remembered that some time ago, just for the **** of it, I copied my sparsebundle backups to an external drive and stashed it in a drawer. I browsed it, and lo and behold there were the missing files. So I narrowly escaped a big problem, but wy did this happen? What are they doing over at Apple?

Hatrabbit wrote:
Naturally I went to my Time Machine backups and was surprised the music was gone from the backups, all the way back to the first backup. Very wierd.
This is really bad luck. And what can be seen here, it is not related to Yosemite but Mavericks, since I asume your backups were made with Mavericks. Though, it is possible that this bug still persists with Yosemite.
I have a similar problem. I am still on Mavericks. I see missing files in ~/Library/Preferences on a regular basis. When I come aware of it, I fix it manually by excluding Preferences folder from backup, run backup, include folder Preferences and finally backup again. But this fix does not last for long. Suddenly after some weeks I see a again missing files in that folder, when browsing the "Latest" backup.
I have found some related discussion:
Time machine missing files
http://forums.macnn.com/90/mac-os-x/509489/potential-time-machine-issue-maverick s-leaving/
http://apple.stackexchange.com/questions/130955/some-files-are-gone-after-recove ry-from-time-machine-backup-why/150230
http://apple.stackexchange.com/questions/136453/time-machine-not-detecting-chang es-in-certain-folders
https://twitter.com/ThatDJJP/status/526429152153714690
missing mail after installation
No solution until today. Very frustrating.
My feeling is, that many users do not recognize, that they are victim of this horrible bug, cause in most cases only few folders are hit by this bug.
And now since Yosemite is out, people are actually using there backups for the first time since Mavericks and run into a disaster.
Atm I am trying to test, if maybe fsevent daemon is the problem, in the past there have been issues like http://openradar.appspot.com/10207999
I did a check on my drive, and I found issues with realpath()/readdir(). Though, those issues may just be old and have not been detected by me for a very long time. My MBP is 5 years old and I upgraded all the way from 10.5 to 10.6 to 10.9.
With 10.6 I never had such an issue.
But more likely, the issue is related to the "Cleaning up old backups" process. Cause I also have the feeling, that when my backup drive gets full and the shrink process took place, then the result are missing files in younger backups then the ones cleaned. If that is true, then maybe the hard-link-approach of Time Machine is somehow involved.

Time Machine Issues

Time Machine Issues
Receiving "Can't connect to a current Time Machine backup disk" error when entering Time Machine
Hello, there! Austin here. I started receiving this error after I completed my first Time Machine backup. It happens every time I try to enter time machine. Any solutions would be greatly appreciated.

Time Machine Issues
Receiving "Can't connect to a current Time Machine backup disk" error when entering Time Machine
Anyone?

Time Machine Issue -- Error not found anywhere

I am having a Time Machine issue in which the error displayed cannot be found anywhere: Google, Bing, Apple, etc.
The error message is: "Time Machine couldn't find some of its settings on the backup disk "BACKUP". Make sure the backup disk is connected, and that other connected disks don't use the same name as the backup disk. Last success backup: 6/21/10 at 2:52 PM"
The other odd thing is that my Time Machine folders are empty. The directory structure is: BACKUP > Backups.backupdb > TIGERMASTER > {empty}. (TIGERMASTER is my MacBook Pro's name.)
When I do a Get Info on the directories, it reports Zero kb on disk with 0 items. When I do a Get Info on BACKUP, it reports 833GB used, with about 140GB free (it's a 1TB external HDD).
Disk Utility sees folders and files, however: "Number of Folders:583,061 / Number of Files:3,725,350"
Um, help?!
My Mac's Info:
*Model Name: MacBook Pro*
*Model Identifier: MacBookPro3,1*
*Processor Name: Intel Core 2 Duo*
*Processor Speed: 2.4 GHz*
*Number Of Processors: 1*
*Total Number Of Cores: 2*
*L2 Cache: 4 MB*
*Memory: 4 GB*
*OS: 10.6.4*
*Ext. HDD: LaCie 1TB*

Here are the last few lines of the error output. The entire output was laden with red text, which indicates errors:
+Invalid node structure+
+Invalid record count+
+Rechecking volume.+
+Checking Journaled HFS Plus volume.+
+Invalid node structure+
+The volume could not be verified completely.+
+Volume repair complete.Updating boot support partitions for the volume as required.Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.+
The most common output error (there must have been over a hundred) looked like these:
+Overlapped extent allocation (id = 10715055, /.HFS+ Private Directory Data+
+/dir_10712993/Mobile Backups/8884195JY7H/Structured/4eea38a1ac5f110bcb3d0a10ce4d571300ab85aa.mddata) +
+Overlapped extent allocation (id = 10715056, /.HFS+ Private Directory Data+
+/dir_10712993/Mobile Backups/8884195JY7H/Structured/4eea38a1ac5f110bcb3d0a10ce4d571300ab85aa.mdinfo) +
+Overlapped extent allocation (id = 10715057, /.HFS+ Private Directory Data+
+/dir_10712993/Mobile Backups/8884195JY7H/Structured/4f01e5e3411040bbec70277a704bfeb5b735d336.mddata) +
+Overlapped extent allocation (id = 10715058, /.HFS+ Private Directory Data+
+/dir_10712993/Mobile Backups/8884195JY7H/Structured/4f01e5e3411040bbec70277a704bfeb5b735d336.mdinfo) +
I tried to mount the disk, but it gives me the error: "The disk BACKUP could not be mounted. Try First Aid on the disk and then retry mounting." Of course, I can't back up any of the files because I can't mount the disk.

[SOLVED] Yet another time issue...

Hi there,
I'm having some crazy, hair pulling, head banging UTC time issues on both my dual boot (Arch & Windows 8) desktop and single boot laptop.
I've been searching and following a mulitude of old threads and the official Wiki guide, however, I simply cannot get UTC time to stay correct between reboots. I've installed Arch a fair few times now, both before and after the switch to systemd and in dual and single boot setups and have never had time related issues like this before...
Here's a run down of the whole sorry story....
Fresh install - set time with hwclock --systohw utc as suggested in the beginners guide.
First boot - time an hour out - huh? cat /etc/adjtime and ls -l /etc/localtime - everything as it should be... UTC and symlink to /usr/share/zoneinfo/Europe/London. Nonetheless I duly follow the Time guide on the wiki, get to know timedatectl a bit, and soon after, time is set to be correct. Great.
Reboot. Time an hour out. Whaaaa??. Start googling, finding a plethora of bbs links to others with similar issues, decide to use NTP. Install, ntpd -qg. All good again. Time right. Phew...
Reboot. Nope. Arrrrgggghhhh. (Bare in mind - at this point I haven't even booted the Windows 8 disc, and I went through the exact same process on my Arch only laptop...)
More googling, thread reading. Find out that hwclock and ntp might be in conflict. Delete /etc/adjtime, reinstall tzdata, re-follow Time article to the letter and reenable NTP to start at boot.
Reboot - time is foward an hour yet again. Bang head repeatedly on desk. Then suddenly - 10 mins or so after boot - NTP kicks in, and time is magically goes back an hour to the correct time! Surely NTP should be doing this early in the boot process, not 10 minutes after? But OK, at least something is happening...
Next I dare to boot into Windows, and yup, time an hour out. Expected, but frustrating nonetheless. Add the registry tweak as suggested in the guide, and turn off the Windows time synchronisation. During which I noticed that Windows 8 time is set to UTC by default, not localtime, which is what the wiki says. Is this a Windows 8 thing?
I can't help thinking, that if this is the case, and the Wiki advise is written under the assumption that Windows time is always localtime, that perhaps this is the route of my problem....
Anyway, Windows time all good now, reboot Arch, time again wrong untill NTP finally kicks in - sigh. Reboot to Windows. Time an hour back. Gaaaahhhh - WTF?!! reset it to be correct. Try again. Same thing. Oops, forgot to mention that on each reboot, I check the BIOS clock, which remains persistently correct during the whole debarkle...
Ok, so I try without the registry hack and turn Windows sync back on. Still fucked. I try various combinations of the two, I try resetting Arch time over and over again. With NTP - late sync. With hwclock only, or both hwclock & NTP - totally fucked! Eventually, I give up on UTC in Arch, set it localtime, delete registry key, turn Windows time sync back on, and thus far all good......
TL;DR - couldn't get hwclock to set UTC time correctly across reboots. NTP worked (sort of), but after each reboot it would take ten minutes for the time to sync and the clock to move back an hour to the correct time. Localtime just works...
My question is - why is the wiki (and the timedatectl status output for that matter) - so adamant that we should use UTC? From what I can gather, as long as I boot Windows around the DST time. or manually move the clock forward or back an hour - all should be well, no? Or are there other issues that I may run into that I've missed? The thing I'm most concerned about is data corruption due to timestamp issues...
Also, why does the wiki repeatedly say that Windows uses localtime, when this doesn't appear to be the case in Eight? Does the wiki need updating or is Windows lying to me? I know which I'd put my money on ;-)
Finally can anyone explain why my time was always an hour forward after a reboot, even when the time was set correctly before, the BIOS showed the correct time, and NTP was in use?
Sorry for the crazy long posting, but this issue has been driving me totally batty!! Any light-shedding greatfully appreciated :-)
Last edited by knowayhack (2013-08-10 15:24:09)

Ok, so I set the clock back an hour in the BIOS, booted Windows - time right - YAY.
Rebooted Arch - time right. OMFG - pure joy!!!
I have to say, I still find it odd that this is how it works, and would like to confirm that things are looking as they should in the output from the following commands....
toby@archy ~ > timedatectl status
Local time: Sat 2013-08-10 15:42:56 BST
Universal time: Sat 2013-08-10 14:42:56 UTC
Timezone: Europe/London (BST, +0100)
NTP enabled: n/a
NTP synchronized: no
RTC in local TZ: no
DST active: yes
Last DST change: DST began at
Sun 2013-03-31 00:59:59 GMT
Sun 2013-03-31 02:00:00 BST
Next DST change: DST ends (the clock jumps one hour backwards) at
Sun 2013-10-27 01:59:59 BST
Sun 2013-10-27 01:00:00 GMT
toby@archy ~ > sudo hwclock --debug
sudo: timestamp too far in the future: Aug 10 16:39:24 2013
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
[sudo] password for toby:
hwclock from util-linux 2.23.2
Using /dev interface to clock.
Last drift adjustment done at 1376148264 seconds after 1969
Last calibration done at 1376148264 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2013/08/10 14:43:20
Hw clock time : 2013/08/10 14:43:20 = 1376145800 seconds since 1969
Sat 10 Aug 2013 15:43:20 BST -0.953640 seconds
Is it OK to now reinstall NTP to keep the clock in sync on Arch, and are the Windows reg tweaks still necessary on Windows 8?
Thank you guys SOOO much for all the unbelievabley speedy help on this issue - you have no idea how much this has been stressing me out!!
Last edited by knowayhack (2013-08-10 14:54:31)

Yet another Time Capsule /Time Machine / Aperture / Vault Question

OK - It is recommended that the Aperture Library be excluded from the Time Machine backups, and to create vaults instead. Fine.
Has anyone tried including the vaults instead of the library in their TM backups? Any issues? Does TM backup only the changes to the vault, or does it see the vault file as one file, and backup the whole thing after the vault has been updated?

I haven't experienced it personally. That's because I have my Aperture library excluded -- I'm using SuperDuper to clone the entire library once a week (Aperture isn't open when this happens), and I also use vaults.
There were numerous threads here about it, though. Or, I should say, they were in this forum, or they were in the Leopard/Time Machine forum. There was a fair bit of complaining about it... so I take it that some people have been affected.
I doubt there's any danger of data loss, given TM won't back up the Aperture library when it's open -- which is when the database is in use and there could be open journal files. But... if you try it, and you notice that TM is taking 2-3 hours of crunching on your drive to back up the whole library, don't come yelling to me. I'll just say "known issue" and point to the Kbase article.
Deal?

Time machine issue, trying to recover a file

OK,
Haven't needed to use time machine but now is the case and am having trouble ;-( !
My computer is backing upto the external drive with no issues.( Just did it a minute ago)
I can see the backups correctly dated on the external drive.
BUT....
When I "enter" time machine I cannot go back in time!
It shows me "today" and the arrow doesn't want to go back in time.
Also no timeline dates on the right side.
How can I "fix" this? I'm sure the data is on the drive but how can I get timemachine to find it again?
Thanks,
Phillyman

OK.. Solved the problem but sadly can't say what it was! Last night my computer completely froze while I was transferring files to another external hd. I could only shut the iMac off with pressing and holding the power button on the back. After starting up, during the white screen with apple logo it ran something with a progress bar (fsck?) .After the startup the timemachine program scanned all files and then worked without a hitch... Maybe the restart did the trick? No clue.
But at least it now works
Message was edited by: Phillyman

I know, another Time Machine help request

I get the Time Machine back up error. I recently purchased a Seagate GoFlex Desk external drive. Time Machine seemed to recognize it right away. The following morning I found the dreaded "Time Machine could not complete the backup. Unable to complete backup. An error occurred while creating the backup folder."
I have formatted the external drive per Pondini's step by step; MAC OS Extended (Journaled). No luck. Then I downloaded Time Machine Buddy Widget. I don't know how to copy the error messages in the pop-up. Apparently it is having an issue with a movie that was downloaded from Itunes. I proceeded to exclude it (band-aid). However, I will run Time Machine again and it will have a problem with another file. The error code is consistent; Error (-36)
Starting standard backup
Backing up to: /Volumes/TM Backups/Backups.backupsdb
Event store UUIDs don't match for volume
No pre-backup thinning needed 135.88 GB requested (including padding), 1.80 TB available
Your help will be greatly appreciated!

kenfromlo wrote:
I get the Time Machine back up error. I recently purchased a Seagate GoFlex Desk external drive. Time Machine seemed to recognize it right away. The following morning I found the dreaded "Time Machine could not complete the backup. Unable to complete backup. An error occurred while creating the backup folder."
See #C10 in Time Machine - Troubleshooting (but see the next item first).
I have formatted the external drive per Pondini's step by step; MAC OS Extended (Journaled).
Did you select the GUID Partition Map Scheme? If not, reformat it that way.
Then I downloaded Time Machine Buddy Widget. I don't know how to copy the error messages in the pop-up.
Click in the message area, select Cmd+A (to select All), then Cmd+C to copy.
(Or, if you mean the TM failure message, a screen print is fine.)
Apparently it is having an issue with a movie that was downloaded from Itunes. I proceeded to exclude it (band-aid). However, I will run Time Machine again and it will have a problem with another file. The error code is consistent; Error (-36)
See the pink box in #C3 of Time Machine - Troubleshooting.

Another Time Machine problem after 10.5.3 update

OK, I have another problem, that I haven't seen listed here. Time Machine will no longer back up my MacBook Pro after the 10.5.3 update. The error message I get in the Console log is:
6/1/08 3:44:42 PM /System/Library/CoreServices/backupd[1395] Volume at path /Volumes/Dave's backup does not appear to be the correct backup volume for this computer. (Cookies do not match)
How do I change the cookies for my backup disk?
Thanks in advance.

I believe I have isolated the problem as a permissions issue which I have logged as bug 5990628:
Summary:
Unable to backup over network after upgrading to 10.5.3.
Steps to Reproduce:
Configure Time Machine to back up Leopard machine over AirPort to another Leopard machine (with external drive and .Mac account configured in this case)
Expected Results:
Backups complete as usual.
Actual Results:
Backups are 'Delayed' with errors like this in the console:
6/6/08 4:25:57 AM /System/Library/CoreServices/backupd[2334] Volume at path /Volumes/Time Machine-1 does not appear to be the correct backup volume for this computer. (Cookies do not match)
Regression:
Yes
Notes:
There are many threads on the subject:
http://discussions.apple.com/thread.jspa?threadID=1538633
http://discussions.apple.com/thread.jspa?threadID=1543033
http://discussions.apple.com/thread.jspa?threadID=1547134
http://discussions.apple.com/thread.jspa?threadID=1546079
The problem appears to relate to being unable to read the cookie:
6/6/08 4:20:23 AM System Preferences[2315] Failed to create remote cookie file at path: /Volumes/Time Machine/.001b63abcdef
And this appears to be because the cookie was owned by a different user (likely due to it wanting to connect using a .Mac username instead of a local one), per my explanation below:
I only ever used Time Machine after upgrading to 10.5.3 so my first experience with it has been fairly ordinary, as the backups were constantly being 'Delayed' with this error in the Console:
6/6/08 4:25:57 AM /System/Library/CoreServices/backupd[2334] Volume at path /Volumes/Time Machine-1 does not appear to be the correct backup volume for this computer. (Cookies do not match)
The first thing I discovered from a blog post was that my .Mac 60 day trial was causing it to connect using my .mac username (which appeared in the username field in the UI as a string of hex characters); disconnecting and reconnecting using a local user seemed to work but the issue remained.
I then spotted this in the console:
6/6/08 4:20:23 AM System Preferences[2315] Failed to create remote cookie file at path: /Volumes/Time Machine/.001b63abcdef
The 'random' characters are your MAC address and the binary inside is likely this 'cookie' - a random value used to transparently and reliably link backups to machines. Curiously I couldn't modify this file over the network despite apparently owning it (in Terminal):
$ cd /Volumes/Time\ Machine
$ ls -la .00*
-r-------- 1 samj staff 16 Jun 6 04:33 .001b63abcdef
But when looking at it on the Mac Mini 'server' I saw that the owner was in fact another user:
-r-------- 1 otheruser staff 16 Jun 6 04:33 .001b63abcdef
So I ran these commands:
sudo chown samj .001b63abcdef
sudo chgrp staff .001b63abcdef
And sure enough I was able to configure Time Machine as expected and it is as we speak backing up my MacBook over Airport to a USB drive attached to my Mac Mini.
Cheers,
Sam
Sam Johnston
Australian Online Solutions
http://www.aos.net.au/

TS1550 Time Machine issue with Mountain Lion. Can you help?

I have an Iomega Mac Companion used as an external backup drive for my Imac running Mountain Lion. After launching Time Machine, I got an error message that said the backup couldn't' be completed because an error occurred while creating the backup folder. I rebooted and everything was fine for 24 hours. Since then, I get the same error message even after another reboot. In Time Machine preferences it says "oldest backup none" and "latest backup none."
Any suggestions?
GR

Finally have it solved!! Sort of... I spoke with Mac support on two occasions and they were extremely helpful. Thought the issue was with the firewire 800 connection. Switched to a USB connection and everything worked great...for about 24 hours. Then had the same error messages. Chatted with Iomega tech support and they finally admitted that there are known issues with Mountain Lion, there is no work around and they have no intention of making it compatible with 10.8.
I'm returning the drive today. Thanks for your help and suggestions. Suggestions for a decent back up hard drive that will work with Mountain Lion?

Time Machine Issue with Western Digital Hard Drive

I'm running snow leopard with a 300 GB WD External HD using TIme Machine. About every 4 months or so Time Machine gives me an error and says to repair the disk to fix the problem. I go to Disc Utility and try to repair it but it says "Disc cannot be mounted" I try reformatting the drive but it gives me the same error. I have even taken it over to a PC and tried reformatting it there but same issue. Is the HD dead? Time to move on?

I am having similar issues with Wd drive. I found out is the housing of drive but not drive. How is the external drive connected to your mac? I found out after I bought my My Book and My Book Studio is at fault. Many people in discussion have reported failures. If you are using either one, get another drive. But do not buy another WD My Book or WD My Book Studio. Try an different brand. Like G-Drive is good brand for time machine.
Lastly and oddly, I do own WD passport hd and it works like charm, no problems with it.

Yet another CC billing issue

I had to update the credit card on file with my Creative Cloud account. Since then, the card has not been billed. The last payment was made on October 6. The information on file is correct, and has been for quite some time (even with multiple attempts to re-update it). Now access to my Adobe products has been suspended. I tried calling Adobe multiple times ... once hanging up after 45 minutes of being on hold, another time choosing the call-back option and never receiving a call back, and finally getting the recording that the wait time was between 90 and 120 minutes. One time I got through on chat, but after the unsuccessful session I was told to call Customer Support. Yet a connection to sales was near instantaneous.
These wait times are completely unacceptable. I understand that the attack on your servers has caused big headaches, but hire some temporary support staff to get through this.
Please, Adobe, help me out. I need to use your products for work.
-Jon-

Hi Jon,
I am so sorry for the inconvenience faced by you, please provide me your contact number, if possible with an alternate contact number. I will follow up the issue.
I have send an email to you also, please respond.
Regards,
Rajshree

Yet another Time Machine issue

Similar Messages

Maybe you are looking for