Getting Time Machine to work with NAS Drives

Connect the drive and format it HFS+
for this example I will name it backup
Set it up as the Time Machine drive once formatted.
Go into system preferences and turn off Time Machine.
Go into FrontView and create a share, for this example I will name it backups, set a quota you want to use I did double my Mac's hard drive
Open terminal
type the following commands
cd /
cd Volumes
ls -a -l (make note of .00 filename)
cp ./backup/.00filename ./backups/.00filename
cp ./backup/.com.apple.timemachine.supported ./backups/.com.apple.timemachine.supported
sudo umount backup
sudo umount backups
then go back into Frontview and rename backups volume to backup
connect to ReadyNAS through finder afp://IPADDRESS
choose backup volume to connect to
Relaunch TimeMachine...
BAM!
From a link on xlr8yourmac.com
William

Eric S wrote:
Can anyone comment on whether this works reliably? I mean, it looks like Apple doesn't officially support it (given the complexity of the setup).
Eric
Previous posts from some users who have tried this found some problems (others have not). The conclusion stated by experienced users was that Apple pulled the NAS support at the last minute (also the Airport extreme limitation) due to less than reliable operation. Everyone seems to be waiting for Apple to solve the problem and issue

Similar Messages

  • How Do you get Time Machine to work with a network drive?

    I have not been able to choose a Drive for Time Machine on a Network Drive. The network drive is active and shown on my desktop. How Do I use it?

    Correct. Back up to a network volume (other than Time Capsule) is not supported, so if you want to do it you have to use the command line to set something as shown in the article.
    Another option you could do would be to create a large disk image file on the NAS device and mount it on your client and back up to that. You'd use Disk Utility to create a large (say, 200 GB) sparse image on the network storage and then double click it to mount it on your machine and set TM to back up to that. I could show you how to do this in 30 seconds but instructing it over a forum post... not so easy

  • Cannot get Time Machine to work

    I just installed Leopard on my Power MacG4. I can't get Time Machine to work. I have gone to Utilities and repaired partitions twice. That doesn't seem to be the problem. I have no idea what to do. Any ideas?

    Pondini wrote:
    Maybe, maybe not. Via Disk Utility, when you click the first line for the drive (Make, Size), does it show the +Apple Partition Map+ down near the bottom, and when you click the second line, show +Mac OS Extended (journaled)?+ If not, that's at least part of the problem.
    There should be better messages in your logs. Download the +Time Machine Buddy+ widget. It shows the messages from your logs for one TM backup run at a time, in a small window. Navigate to the failed backup, then copy and post the messages here (be sure to get them all, as sometimes they overflow the small window).
    Checked the disk utility and everything shows as you say it should. Here's the log:
    Starting standard backup
    Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    Event store UUIDs don't match for volume: Macintosh HD
    Backup content size: 35.1 GB excluded items size: 144 KB for volume Macintosh HD
    No pre-backup thinning needed: 42.14 GB requested (including padding), 931.15 GB available
    Error: (-36) SrcErr:NO Copying /Adobe Acrobat 3.0/Acrobat™ Distiller™ 3.01 to /Volumes/Time Machine Backups/Backups.backupdb/Kathy Miller’s Computer/2009-03-08-153448.inProgress/62856C2A-1F0A-438D-925C-B5A18D6E5416/Maci ntosh HD/Adobe Acrobat 3.0
    Stopping backup.
    Error: (-8062) SrcErr:NO Copying /Adobe Acrobat 3.0/Acrobat™ Distiller™ 3.01 to /Volumes/Time Machine Backups/Backups.backupdb/Kathy Miller’s Computer/2009-03-08-153448.inProgress/62856C2A-1F0A-438D-925C-B5A18D6E5416/Maci ntosh HD/Adobe Acrobat 3.0
    Copied 0 files (2.7 MB) from volume Macintosh HD.
    Copy stage failed with error:11
    Backup failed with error: 11

  • HT1338 I have mountain lion and cant get time machine to work. the disk keeps getting ejected.

    I just installed Mountain lion and i can't get time machine to work. every time i connect it time machine starts but then ejects the drive. I also tried to back up direct to the hard drive with the software that came with the drive and the same thing happens. Does anyone have a clue as to what may be wrong?

    When that happens, you should get some sort of message.  If you don't remember it exactly, go to the Time Machine Preferences window -- there should be a red "Failed" message and icon there.  Click the icon to see the message.  Either report the wording or post a screenshot.
    If not, a clue may be lurking in your logs.  Use the widget in #A1 of Time Machine - Troubleshooting to display the backup messages from your logs.  Locate the backup in question, then copy and post all the messages here.

  • Time Machine restore problem with network drive

    Hi, I switched from PC to Mac. I bought a Lacie Network Space 2 (network hd) in an apple store (turns out it's NOT an apple store, it's an apple premium reseller according to the 90 days free telephone support guy, and apple's policy is then: you should have bought a 'time capsule' then.) That doesn't help me now. So I'm hoping some of you might have had this or similar trouble before. The Lacie drive is able to back up my macbook through time machine. It recognizes the drive and it does my backups on a time machine enable share on the hard drive. So I thought it worked like a charm. Until i wanted to go back to a previous date and restore all my data. I read you gotta start from the mac os install dvd and choose the restore option in utility. It recognizes the lacie harddrive. But when i want to connect to it it will say connection failed! I tried this over wifi (the hard drive connect to my linksys router with ethernet cable) and i tried this with the hard drive directly connected to the macbook with ethernet cable. It always finds the harddrive but when i want to connect to it to choose a previous date to restore, i can't even get there because it will say the connection failed. I'd really appreciate some help, because I tried to go on support pages and look up an answer, called apple, but can't really figure out what's wrong. So it can backup, it can restore single or multiple files in time machine, but it can't restore the whole OS when used with the install disc? Also made a dmg file with disk utility, but this one doesn't recognize the network drive. Finder does however. Any tips? Any at all, please?

    Fototom wrote:
    I had to mark a 'time machine' checkbox in the Lacie UI for it to be able to work as a time machine drive. So the backups work fine without special terminal commands. It's just weird that it won't restore the full OS back when started up with the install DVD.
    Whatever the +LaCie UI+ is, that's probably why you can't do the full restore. That may be doing the equivalent of the Terminal command, to "fool" Time Machine into thinking it's backing-up to a supported destination. But you can't do that when booted from your SL Install disc, so Time Machine can't find the network drive.
    I tried the option during Setup Assistant to transfer data earlier, but it won't recognize the drive at that time.
    Yes, that's likely for the same reason.
    BUT I didn't know about *migration manager*. So the option of installing mac osx again and then creating another user and using the migration assistant, that DOES recognize the time machine backups, will surely work.
    Never say "surely" until you know
    It would be nice to skip the extra step of having to install the OS first, but this will definitely be a valid option to restore. So for now i'll mark this item solved.
    Let us know how it turns out.
    If anyone has even a speedier, better option to backup and restore a total disc image (or time machine backup), please let me know.
    The time involved is probably about the same; it's just in two steps instead of one.
    And there's only one step if you use a "supported" destination: Disks that can be used with Time Machine.

  • Time Machine backup to my NAS drive (MyBookLive from WD) stopped working after Lion Upgrade

    After my upgrade to Lion OS, I noticed that Time Machine backup failed to connect to my MyBookLive WD NAS drive. It was perfectly working while the machine was still on Snow Leopard. This is the error I am getting.
    "The network backup disk does not support the required AFP features.
    Open Time Machine preferences to select a different backup disk."
    Any help with workaround would be greatly aprreciated. Thx for your help and support.

    OK I ran into issues.  I'm doing the play by play on Q18 for copying a locally connected backup to a network connected backup - so I start the backup with the backup disk connected to the TC and then stop it when the XXX of YYY copied shows up.  I disconnect and connect the disk directly.  The problem is I don't seem to have permission to mount the sparsebundle:
    So I get info and click the lock and enter my admin password and change the everyone from no access to read and write.  Then I try to open the sparsebundle and I get:
    So I did that twice with the same effect.  Then I noticed I can mount the sparsebundle if I leave it connected to the time capsule.  So its mounted - good.  Then I go into disk utility and try to erase the mounted "time machine backups" drive and it didn't like that much - I wish I took a screenshot but I didn't.  It basically said I can't do that.
    So now I don't know what to do.  I'm currently starting a backup set fresh and this time letting it run to completion however I excluded my entire user account so the backup size is only 25 GB.  When it finishes then maybe I can move the disk local and go in and see if I can mount the partition and erase the contents and copy over my backup file into the sparsebundle.
    So does anyone know why I can't access that sparsebundle the way Pondini says I should be able to?  Any suggestions?  If my latest attempt doesn't work then I'll just do a full backup and say to heck with my history although that would be unfortunate.

  • How do I set up Time Machine to work with an Iomega network hard drive?

    I have just bought a new iMac having switched from Windows, and am very much a beginner when it comes to all things Apple. Previously I had used my NAS hard drive with my old windows pc. i successfully used it to transfer a lot of data from the old pc to the iMac but can't seem to get it recognised when I try to configure time machine. I have downloaded the latest version of Iomega Home storage manager which appears in the application folder in the dock, but when I click on The HSM icon it just disappears and nothing happens. I can access the drive through the Bonjour service and can see its contents in Finder. I have looked through the forums here but much of the info assumes a level of knowledge that i don't have. Is there an 'idiot's guide' anywhere to enable me to set up time machine to use the network hard drive?

    You would probably benefit from a couple of things, first going through these 2 links
    Time Machine FAQs & Time Machine Troubleshooting.
    If you still have questions there is a TM forum, because TM is part of OS X you will find the forum in the Snow Leopard forum. Click Apple Support Communities and in the search field type Snow Leopard. Once you are in the correct forum you can narrow your search by clicking Refine this list.
    Roger

  • Time Machine not working with Verbatim USB2TB External HDD

    MacBook Pro
    15-inch, Mid 2010
    8GB Ram
    OS 10.8.2
    No updates available ATT.
    Problem with Time Machine using Verbatim USB2TB (Verbatim # 96865) external hard drive in regular and safe boot. According to the Verbatim website, this external drive is compatiable with MAC OS 10+ and can be formatted to the specific Mac filesystems.
    The following list of events below happen irregardless of running in regular or safe boot, so I noted my last attempt at a backup while in Safe Boot.
    Before this last attempt, I successfully zeroed out the data on the drive in regular boot.
    As you will see below, the drive works just fine until Time Machine gets it grimy digits on it and kills it like South Park kills Kenny.
    ---- Begin ----
    Started in Safe Boot
    Connected and powered on the external drive.
    Erased the drive and formatted it to Extended Journaled. Partition was successfully created.
    Verifying partition map for “SAMSUNG HD203WI Media”
    Checking prerequisites
    Checking the partition list
    Checking for an EFI system partition
    Checking the EFI system partition’s size
    Checking the EFI system partition’s file system
    Checking all HFS data partition loader spaces
    Checking Core Storage Physical Volume partitions
    The partition map appears to be OK
    Verifying volume “Big2TB”
    Checking file systemChecking Journaled HFS Plus volume.
    Checking extents overflow file.
    Checking catalog file.
    Checking multi-linked files.
    Checking catalog hierarchy.
    Checking extended attributes file.
    Checking volume bitmap.
    Checking volume information.
    The volume Big2TB appears to be OK.
    Successfully copied over 2.8 GB of random data. (Screenshot)
    Deleted the data and then emptied the Trash.
    Started Time Machine backup.
    Time Machine Created a backup folder on the external drive.
    Time Machine started to transfer data then hung at 452.1 MB of 257.66 GB.
    Backup failed.
    --- Console ---
    1/13/13 11:57:59.988 AM com.apple.backupd[1558]: Starting manual backup
    1/13/13 11:58:04.581 AM com.apple.backupd[1558]: User continued after being warned of changed destination volume identity
    1/13/13 11:58:04.623 AM com.apple.backupd[1558]: Backing up to: /Volumes/Big2TB/Backups.backupdb
    1/13/13 11:58:04.628 AM com.apple.backupd[1558]: Ownership is disabled on the backup destination volume.  Enabling.
    1/13/13 11:58:05.156 AM mds[34]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"
    1/13/13 11:58:06.336 AM com.apple.backupd[1558]: Forcing deep traversal on source: "MainMan" (mount: '/' fsUUID: 8A3A5598-7C8B-3753-ABA8-D980E60299A3 eventDBUUID: 23107488-4BC9-49FB-818D-226AE695DE06)
    1/13/13 11:58:23.346 AM com.apple.backupd[1558]: Backup content size: 246.45 GB excluded items size: 12.21 GB for volume MainMan
    1/13/13 11:58:23.368 AM com.apple.backupd[1558]: Found 910640 files (234.23 GB) needing backup
    1/13/13 11:58:23.370 AM com.apple.backupd[1558]: 281.08 GB required (including padding), 2 TB available
    1/13/13 11:58:23.388 AM com.apple.backupd[1558]: Waiting for index to be ready (100)
    1/13/13 11:59:23.443 AM com.apple.backupd[1558]: Waiting for index to be ready (100)
    1/13/13 12:00:02.530 PM WindowServer[114]: CGXGetWindowInfo: Invalid window 1045
    1/13/13 12:00:02.530 PM Dock[259]: CGSBindWindow: Unable to obtain window information
    1/13/13 12:00:02.531 PM Dock[259]: CGSGetWindowTags: Invalid window 0x415
    1/13/13 12:00:02.531 PM Dock[259]: find_shared_window: WID 1044
    1/13/13 12:00:02.531 PM Dock[259]: CGSGetWindowTags: Invalid window 0x414
    1/13/13 12:00:02.532 PM Dock[259]: find_shared_window: WID 1043
    1/13/13 12:00:02.532 PM Dock[259]: CGSGetWindowTags: Invalid window 0x413
    1/13/13 12:00:04.481 PM WindowServer[114]: CGXGetWindowType: Invalid window 1066
    1/13/13 12:00:04.481 PM Dock[259]: find_shared_window: Invalid depth WindowID 0x42a
    1/13/13 12:00:04.481 PM Dock[259]: CGSGetWindowTags: Invalid window 0x42a
    1/13/13 12:00:04.482 PM Dock[259]: find_shared_window: WID 1065
    1/13/13 12:00:04.482 PM Dock[259]: CGSGetWindowTags: Invalid window 0x429
    1/13/13 12:00:04.482 PM Dock[259]: find_shared_window: WID 1064
    1/13/13 12:00:04.482 PM Dock[259]: CGSGetWindowTags: Invalid window 0x428
    1/13/13 12:00:23.497 PM com.apple.backupd[1558]: Waiting for index to be ready (100)
    1/13/13 12:01:23.549 PM com.apple.backupd[1558]: Waiting for index to be ready (100)
    1/13/13 12:01:44.830 PM com.apple.launchd[1]: (com.apple.xpcd.F5010000-0000-0000-0000-000000000000[1541]) Exited: Killed: 9
    1/13/13 12:01:44.000 PM kernel[0]: memorystatus_thread: idle exiting pid 1541 [xpcd]
    1/13/13 12:01:49.000 PM kernel[0]: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT
    1/13/13 12:01:49.000 PM kernel[0]: macx_swapon SUCCESS
    1/13/13 12:02:15.000 PM kernel[0]: USBF:          7419.448          AppleUSBEHCI[0xffffff8008e26000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 5, EP: 2)
    1/13/13 12:02:21.000 PM kernel[0]: USBF:          7425.451          AppleUSBEHCI[0xffffff8008e26000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 5, EP: 0)
    1/13/13 12:02:27.000 PM kernel[0]: USBF:          7431.454          AppleUSBEHCI[0xffffff8008e26000]::Found a transaction which hasn't moved in 5 seconds on bus 0xfd, timing out! (Addr: 5, EP: 0)
    1/13/13 12:02:58.000 PM kernel[0]: USBF:          7462.473          AppleUSBEHCI[0xffffff8008e26000]::Found a transaction past the completion deadline on bus 0xfd, timing out! (Addr: 5, EP: 2)
    1/13/13 12:05:37.068 PM WindowServer[114]: CGXGetWindowInfo: Invalid window 1196
    1/13/13 12:05:37.068 PM Dock[259]: CGSBindWindow: Unable to obtain window information
    1/13/13 12:05:37.068 PM Dock[259]: CGSGetWindowTags: Invalid window 0x4ac
    1/13/13 12:05:37.069 PM Dock[259]: find_shared_window: WID 1195
    1/13/13 12:05:37.069 PM Dock[259]: CGSGetWindowTags: Invalid window 0x4ab
    1/13/13 12:05:37.070 PM Dock[259]: find_shared_window: WID 1194
    1/13/13 12:05:37.070 PM Dock[259]: CGSGetWindowTags: Invalid window 0x4aa
    1/13/13 12:06:34.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:06:39.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:06:44.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:06:50.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:06:55.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:07:01.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:07:11.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:07:17.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:07:22.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:07:27.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:07:27.000 PM kernel[0]: jnl: disk1s2: do_jnl_io: strategy err 0x5
    1/13/13 12:07:27.000 PM kernel[0]: jnl: disk1s2: end_transaction: only wrote 0 of 389120 bytes to the journal!
    1/13/13 12:07:54.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:08:21.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:08:21.820 PM com.apple.backupd[1558]: Error: (-36) SrcErr:NO Copying /Applications/Adobe/AdobePatchFiles/{CFA1AAD1-DC10-413D-875E-2F5B8A78CB3B}.zip to /Volumes/Big2TB/Backups.backupdb/numeroeins/2013-01-13-115805.inProgress/376C91 FB-29D6-47F1-A29B-67D94CBD01BA/MainMan/Applications/Adobe/AdobePatchFiles
    1/13/13 12:08:23.122 PM com.apple.backupd[1558]: Stopping backup.
    1/13/13 12:08:23.122 PM com.apple.backupd[1558]: Error: (-8062) SrcErr:NO Copying /Applications/Adobe/AdobePatchFiles/{CFA1AAD1-DC10-413D-875E-2F5B8A78CB3B}.zip to /Volumes/Big2TB/Backups.backupdb/numeroeins/2013-01-13-115805.inProgress/376C91 FB-29D6-47F1-A29B-67D94CBD01BA/MainMan/Applications/Adobe/AdobePatchFiles
    1/13/13 12:08:23.136 PM com.apple.backupd[1558]: Copied 817 files (572.1 MB) from volume MainMan.
    1/13/13 12:08:23.136 PM com.apple.backupd[1558]: Copy stage failed with error:11
    1/13/13 12:08:23.174 PM com.apple.backupd[1558]: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Big2TB/Backups.backupdb/numeroeins size:37
    1/13/13 12:08:33.228 PM com.apple.backupd[1558]: Backup failed with error: 11
    1/13/13 12:08:48.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:09:15.000 PM kernel[0]: disk1s2: I/O error.
    ---- End console ---
    Attempted to copy over 2.8 GB of random data again. Failed. 
    Now the drive is completely useless until it is erased. Also will not eject properly anymore. Force eject took 3 minutes.
    --- Console ---
    1/13/13 12:19:00.248 PM mtmfs[1555]: filesystem unmount attempted from stopFS
    1/13/13 12:19:31.946 PM fseventsd[44]: disk logger: failed to open output file /Volumes/Big2TB/.fseventsd/0000000000048e11 (Invalid argument). mount point /Volumes/Big2TB/.fseventsd
    1/13/13 12:19:31.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:19:32.187 PM fseventsd[44]: disk logger: failed to open output file /Volumes/Big2TB/.fseventsd/0000000000048e11 (Invalid argument). mount point /Volumes/Big2TB/.fseventsd
    1/13/13 12:19:32.910 PM WindowServer[114]: CGXDisableUpdate: UI updates were forcibly disabled by application "Disk Utility" for over 1.00 seconds. Server has re-enabled them.
    1/13/13 12:19:35.129 PM WindowServer[114]: reenable_update_for_connection: UI updates were finally reenabled by application "Disk Utility" after 3.22 seconds (server forcibly re-enabled them after 1.00 seconds)
    1/13/13 12:20:05.375 PM fseventsd[44]: disk logger: failed to open output file /Volumes/Big2TB/.fseventsd/0000000000048e11 (Invalid argument). mount point /Volumes/Big2TB/.fseventsd
    1/13/13 12:20:05.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:20:05.390 PM fseventsd[44]: disk logger: failed to open output file /Volumes/Big2TB/.fseventsd/0000000000048e11 (Invalid argument). mount point /Volumes/Big2TB/.fseventsd
    1/13/13 12:20:37.153 PM fseventsd[44]: disk logger: failed to open output file /Volumes/Big2TB/.fseventsd/0000000000048e11 (Invalid argument). mount point /Volumes/Big2TB/.fseventsd
    1/13/13 12:20:37.153 PM fseventsd[44]: disk logger: failed to open output file /Volumes/Big2TB/.fseventsd/0000000000048e11 (Invalid argument). mount point /Volumes/Big2TB/.fseventsd
    1/13/13 12:20:37.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:20:48.102 PM diskarbitrationd[49]: mds [34]:20995 not responding.
    1/13/13 12:21:04.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:21:04.451 PM com.apple.kextd[11]: Can't create kext: invalid CFBundleVersion in identifier cache entry entry 339.
    1/13/13 12:21:14.854 PM com.apple.security.pboxd[1518]: CGSGetWindowTags: Invalid window 0x7b5
    1/13/13 12:21:14.854 PM com.apple.security.pboxd[1518]: kCGErrorFailure: CGSSetHideOnDeact: error getting window tags
    1/13/13 12:21:15.372 PM com.apple.security.pboxd[1518]: CGSCopyWindowColorSpace: Invalid window 0x7b5
    1/13/13 12:21:22.606 PM WindowServer[114]: CGXDisableUpdate: UI updates were forcibly disabled by application "com.apple.security.pboxd" for over 1.00 seconds. Server has re-enabled them.
    1/13/13 12:21:23.060 PM com.apple.quicklook.satellite[1657]: bootstrap_look_up2 failed with 0x44c
    1/13/13 12:21:23.081 PM mds[34]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"
    1/13/13 12:21:23.090 PM WindowServer[114]: reenable_update_for_connection: UI updates were finally reenabled by application "com.apple.security.pboxd" after 1.48 seconds (server forcibly re-enabled them after 1.00 seconds)
    1/13/13 12:21:23.000 PM kernel[0]: Sandbox: sandboxd(1658) deny mach-lookup com.apple.coresymbolicationd
    1/13/13 12:21:26.021 PM com.apple.security.pboxd[1518]: CGSReleaseWindow: Invalid window 1973
    1/13/13 12:21:26.021 PM com.apple.security.pboxd[1518]: _NXTermWindow: error releasing window (1000)
    1/13/13 12:21:27.775 PM sandboxd[1658]: ([1657]) QuickLookSatelli(1657) deny mach-lookup com.apple.PowerManagement.control
    1/13/13 12:21:52.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:21:57.967 PM fseventsd[44]: disk logger: failed to open output file /Volumes/Big2TB/.fseventsd/0000000000048e11 (Invalid argument). mount point /Volumes/Big2TB/.fseventsd
    1/13/13 12:21:57.967 PM fseventsd[44]: disk logger: failed to open output file /Volumes/Big2TB/.fseventsd/0000000000048e11 (Invalid argument). mount point /Volumes/Big2TB/.fseventsd
    1/13/13 12:21:57.000 PM kernel[0]: disk1s2: I/O error.
    1/13/13 12:21:58.229 PM com.apple.kextd[11]: Can't create kext: invalid CFBundleVersion in identifier cache entry entry 339.
    1/13/13 12:21:58.000 PM kernel[0]: jnl: disk1s2: close: journal 0xffffff800908acc0, is invalid.  aborting outstanding transactions
    --- End Console ---
    ---- That's all folks! ----
    Any help would be great!

    The external drive is malfunctioning, or the data cable is bad, or you have another malfunctioning device on the bus, or there's an internal hardware fault.

  • Has anyone got Time Machine to work with Time Capsule?

    I've been trying for days to do an initial backup without success. Everything seems to be working fine and then it just stops and says the backup has "failed." The last one went 24 hours and backed up about 90 GB before it just stopped. Then it has to start over, from the beginning. (This thing is so slow you'd think somebody was writing the files out in longhand!) I even moved my iMac into the room with the Time Capsule, which is actually pretty annoying, in case it was a case of a dropped signal.

    Hi,
    I've spent hours and hours trying to get the harddisk to work properly. Set-up was easy-peasy and the Airport works great for the internet. However, when trying to use time-machine and the hard disk it was a nightmare !!! Each attempt at the back-up failed after about 4 gig with a 'unable to mount volume' error. If I re-tried, it failed. Following some of the tips on the forums, I deleted the back-up file created by time machine on the hard drive and the initial back-up started successfully but failed after about 4 gig again (I had 96 gig to back-up). There are various fixes flying around - ensure you have a name for your computer - should be short and no spaces or funny characters. Same goes for your name of the timecapsule. Some people are saying you should use an ethernet cable for your first back-up but that should not matter at all. I took mine back to the apple store in the end - a mac genius downloaded all the latest patches (only came out 19th march) for the time-capsule firmware, time machine software and airport express. Still didn't work, so conclusion was the time-capsule was knackered !!! SO MY RECOMMENDATION IS TO GET APPLE TO REPLACE IT BUT MAKE SURE YOU TRY THE ABOVE FIRST.
    New time-capsule was attached to my imac, started up great first time. My initial back-up ran through perfectly first time through wireless - it took 15 hours but I did have 96 gig to back-up. time machine sees this no problem so it looks like everything is fine.
    Good luck !!

  • How do I get Time Machine to "see" my NAS device?

    I recently set up a Drobo 5N for NAS.  It works fine with my iMac.  That is, Time Machine on the desktop immediately found the storage device and appears to be backing up to it.  However, Time Machine on my Macbook Pros on my home network do not see the device at all.  They do show the Airport Extreme (the Drobo is attached to Airport Extreme via Ethernet).  The Firewall on the Macbook Pro has been turned off.  All other networking functions seem to work fine.  All the computers in question are running Mountain Lion.  Anyone have any idea how to fix this?  Thanks. 

    Backing up to a third-party NAS with Time Machine, if it works at all, is risky, and unacceptably risky if it's your only backup. This is an example of what can happen.
    If you want network backup with Time Machine, use as the destination either an Apple Time Capsule or an external hard drive connected to another Mac or a mini-tower (802.11ac) AirPort base station. Only the 802.11ac base station supports Time Machine, not any previous model.

  • Why Time Machine stopped working with Time Capsule?

    I have my Time Capsule connected via Ethernet to my iMac and wirelessly to my MacBook. Several days ago I got a warning on the iMac saying "Time Machine couldn't complete the backup - an error occured while copying - may be temporary - if persists, use Disk Utility to repair your backup disc."
    Well, first Tim Capsule will not appear in Disk Utility, so that instruction is absurd. I went to Airport Utility but all that appears there is a graphic of T.C. with no buttons to do anything. My Mac consultant, who doesn't use Time Capsule or T.M, told me to hook it up using USB instead of Ethernet and it would appear in Disk Utility. Before I try that, does it make sense? He also suggested trying it wirelesslessly if that doesn't work.
    Incidently, during all this time the T.C. wireless backups of the MacBook have continued unabated.
    One forum participant urged me to take the T.C. to Apple to get it fixed. I don't think the drive is in that bad shape or why would the MacBook backups to its partition continue without problem?
    I cleaned the Ethernet cable, unplugged both ends and plugged back in. T.M. indicated it had backed up twice, but now it has displayed exactly the same warning again, and says the last backup was several days ago. What should I do? I've zapped the Pram, run permissions on the iMac HD, and deleted all the browers' cache files.

    My Mac consultant, who doesn't use Time Capsule or T.M, told me to hook it up using USB instead of Ethernet and it would appear in Disk Utility. Before I try that, does it make sense?
    Ah, no. The TC's USB port cannot be used for that purpose.
    I recommend another Mac consultant - Apple Support Communities contributor Pondini. Start with this: http://pondini.org/TM/C3.html
    There are a variety of possible causes for that message, so exhaust all the potential remedies.

  • Time Machine stopped working with new Mac address.

    Greetings,
    I have an IOMEGA 500, FireWire which I used to use for Time Machine. I now have a new Mac address and do not have access to the old Mac address. Is there any way that I can get the IOMEGA to start working with Time Machine? If so please give me step by steps instructions on how to make this external hard drive work again with Time Machine.
    Any help is most appreciated.
    Thank you for your attention to this matter.

    macuserr222 wrote:
    Greetings,
    I have an IOMEGA 500, FireWire which I used to use for Time Machine. I now have a new Mac address
    Do you have a new Mac, or a new logic board? Either will get you a new MAC (Media Access Control) address, which Time Machine interprets as a different Mac.
    Do you mean you haven't started doing backups of the new Mac, and want to view the old ones? If so, see #E2 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of the +Time Machine+ forum).
    If you want to use the old backups to set up a new Mac, see [Setting up a new Mac from an old one or its backups|http://web.me.com/pondini/AppleTips/Setup.html] (or use the link in *User Tips* at the top of this forum).
    When you do your first backup, OSX should ask how you want to handle the old backups. See #B5 in Troubleshooting for details.
    If that's not what you mean, please explain exactly what's going on, and what happens when you try to do whatever you're doing.
    Message was edited by: Pondini

  • Time Machine back up with hard drive connected to D-Link DIR-655

    Recently D-Link updated the share port utility with a mac version. I have heard that Time Machine does not easily recognize network shared hard drives but to my surprise this morning it did. With using the new software and hooking up my hard drive to my router Time machine recognized it! This is great since I dont have to buy a Time Capsule now.

    First, since this is *unsupported by Apple,* there's nowhere to go when there's trouble.
    Here's the official word: http://support.apple.com/kb/HT1733
    Second, you're risking a future update preventing it from working, and perhaps rendering your backups useless.
    It's your choice, of course, but I wouldn't trust my primary backups to it.

  • Does Time Machine only work with external HDD's and Networks?

    I have a Mac Mini that I just replaced the optical drive with a hard drive. This second HDD is formated into two partitions, with one of them being for my Time Machine backups, the other a media scratch drive.
    When I try to choose this volume in setting up Time Machine, I get an error message that says, +"Are you sure you want to back up to the same disk your original data is on?"+ The message goes on to explain that +"the volume you have chosen for storing backups is on the same disk as the volume containing your data... you should back up to a volume on a different disk."+
    The volume that I have selected IS on a different disk than my start-up system drive and the data to be backed up IS NOT on the same disk as the disk storing the backups. System Profiler defines my startup HDD as "BSD Name: disk0" and my second HDD as "disk1," with the two partitions "disk1s2" and "disk1s3." Mount Point for the start-up HDD is "/" and the two partitions on the second HDD are "/Volumes/Scratch Disk" and /Volumes/Time Machine." These two volumes show up as options when I "Choose Backup Disk" in Time Machine, but not the Mini's startup HDD.
    Does Time Machine allow the use of second internal HDD? I have an external HDD, but it has a clone of my start-up drive on it. Thanks for any help.

    Chris, excluding the other volume could certainly be the issue since the two options that I'm given for a backup volume are both on the same hard disk. The start-up system HDD is not listed. Maybe the message is referring to this, rather than to the start-up disk.
    Not until after I selected "use this volume anyway," did I get to the "Option" screen to exclude items from the backup. When I selected "+" I was surprised to find the other volume, Scratch Disk, listed along with the start-up HDD as being included in the backup routine. So I selected Scratch Disk as one of the items to exclude.
    As V.K. mentions, the cautionary message is rather vague as to what exactly it is referring to. Thanks.

  • Can't get Time Machine to see new hard drive

    since I now have three computers using time machine to back up to one hard drive via airport base station USB connection, I decided to upgrade to a 1 TB hard drive from a 300 gb. The new HD is showing up as a shared drive in Finder attached to my wireless base station. However it's not showing up as a drive in Time Machine's setup. What I am missing here. The 300 gb drive worked fine.
    Roger

    Is the drive properly prepared?
    Extended Hard Drive Preparation
    1. Open Disk Utility in your Utilities folder. If you need to reformat your startup volume, then you must boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger or Leopard.)
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
    3. Set the number of partitions from the drop down menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (only required for Intel Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
    4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
    5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
    6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
    This may be necessary for use with TM. Is the larger drive installed in an enclosure that supports drives larger than 500 GBs up to at least 1 TB?

Maybe you are looking for