Time Machine Different Mount Volumes

Have an external HD. Always did Time Machine Backups and the volume that would be initially mounted was the name of the external HD. Then I went out and purchased AirPort Extreme station. Set up the external HD through the USB port and started backing up through the router. The mount point is now called Time Machine Backup and I can't change it. New backups are happening but when I connect the HD through FireWire directly to my Mac now I can't see the latest backups. No matter what I do, change the disk in Time Machine, etc... still getting two different volumes pointed to the external HD. How do I reset time machine to its default settings without erasing data on my external HD?
If I do a df in Terminal I see now:
\Volumes\G-Disk
\Volumes\Time Machine Backup
Half of my backups are in the G-Disk and half in Time Machine Backup but I can't browse to the Time Machine Backup at all.
Message was edited by: cypisek77

cypisek77 wrote:
Hi, and welcome to the forums.
Then I went out and purchased AirPort Extreme station. Set up the external HD through the USB port and started backing up through the router.
I hate to have to tell you this, but backing-up that way is "iffy" and +*not supported by Apple.+* See [Using Time Machine with an Airport Extreme Air Disk|http://web.me.com/pondini/Time_Machine/Airport.html] (or use the link in *User Tips* at the top of this forum).
The mount point is now called Time Machine Backup and I can't change it.
Correct. Time Machine stores backups differently when they're made over a network. See the blue box in #E2 of Start with [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).

Similar Messages

  • How to prevent Time Machine from ejecting volume?

    I just set up a Buffalo Cloustor NAS (which is working very nicely, thank you) and one of its features is that it plays nice with Time Machine backups.  I also recently took advantage of a MacUpdate promo on Back-In-Time.  BIT works fine as long as the NAS backup volume is mounted but for some reason Time Machine ejects that volume when it's finished its backups.  I've seen similar problems in threads of non-Lion version of OSX but they seemed to be troubles with USB or FW drives rather than an Ethernet NAS.  I'd rather keep the NAS volume mounted so I can use this 3rd party app. 
    Here is a copy of the console messages filtered on "time machine" for the relevant time period:
    3/24/12 7:11:03.180 PM
    com.apple.backupd
    Disk image /Volumes/cloudshare/Mini2009’s Mac mini.sparsebundle mounted at: /Volumes/Time Machine Backups
    3/24/12 7:11:03.196 PM
    com.apple.backupd
    Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    3/24/12 7:12:37.276 PM
    com.apple.backupd
    Ejected Time Machine disk image.
    3/24/12 7:12:37.678 PM
    com.apple.backupd
    Ejected Time Machine network volume.
    Is there a way of telling Time Machine to not eject when finished?  I'm comfortable writing stuff using Terminal if that's what it takes.
    Thanks!
    -Tod

    BordeauxQuill wrote:
    If it is useful to anyone else, these are Western Digital My Passport Studio 640GB drives.
    Yup, you're the 3rd or 4th to report it with various models of WDs (one fellow had 3 of them!), and a few weeks ago someone had some Iomegas, I think, too.
    This confusion may well also explain some weird stats in Get Info I noticed last week (such as the drive apparently having used more bytes than its capacity, as I recall).
    Quite likely.
    Thank you for your support. I shall come back and mark the thread resolved when I have reformatted the drive.
    Cool. Also double-check the contents of the one you don't erase; you may find some extra stuff there.

  • I have not been able to back up for2 days.  Time machine error message: /Volumes/Data/David's MacBook Air.sparsebundle" is already in use.

    I have not been able to back up for2 days.  Time machine error message: /Volumes/Data/David’s MacBook Air.sparsebundle” is already in use.
    What now?
    Macbook Air.
    Was working fine for the past year until now.

    See more like this on the right.. this is the most common error reported here since mountain lion came out..
    Or read C12.. http://pondini.org/TM/Troubleshooting.html
    Or just restart the whole network.. in right order from off.. modem.. router / TC.. clients 2min gap.

  • Time machine cannot find volume, error-1.  Where can I fine solution for this error? Have latest updates for Airport and TM, running Lion.

    Time machine cannot find volume, error-1.  Where can I fine solution for this error? Have latest updates for Airport Utility and TM, running Lion.

    See #C17 in Time Machine - Troubleshooting.

  • Time Machine - "The backup volume could not be mounted" alert

    This is a heads-up for anybody suffering from this error when performing Time Machine backups:
    "The backup volume could not be mounted"
    I had been using this facility fine for months until a few days ago when backing up mysteriously failed. The Apple support KB articles didn't help (eg, reset time machine drive setup, etc).
    Apple Support didn't want to help me because they don't "support backups over networks" - sheesh! What happened to "Think Different!"??
    Drag and drop your SPARSEBUNDLE file from your backup drive to the Disk Utility.
    Perform a Verify Disk operation by clicking on the button.
    A normal backup should be able to perform this procedure, but a corrupted one won't.
    When trying to perform this on my backup, the Disk Utility would simply return to the original screen without performing anything a second after pressing the button.
    In this case, I found deleting the old backup file and starting from scratch restored my computers ability to perform automated Time Machine backups.
    I have concluded that the backup file became corrupted in some way - several previous posts have pointed to systems going into standby while backing up files as the cause of this.
    Hopefully someone finds this useful one day.

    There is a Time Machine preferences file at
    <your startup drive root>/Library/Preferences/com.apple.TimeMachine.plist
    Note: This is be main Library folder, not the one in your user folder.
    You might try moving that to the Desktop so that the system creates a new one.

  • Unable to prevent Time Machine backing up volume mounted from sparsebundle

    I have a password-protected sparsebundle that contains my financial files, private data, etc, which I mount as a volume at startup. It's about 8GB. If I'm going to be away from my computer for a bit, I'll unmount the volume as an extra security measure.
    I don't need or want Time Machine to back up the files INSIDE the volume, just the sparsebundle itself. If I needed to access a backup of a file inside the volume, I'd rather just pull up an earlier version of the sparsebundle, mount it, and find the file in there.
    However, I've recently discovered that I can't exclude the mounted volume from Time Machine backups in the usual way - the volume name is greyed out when I go through the System Preferences/Time Machine pane, and won't let me select it to be excluded from backup.
    So what's happening is that TM is backing up the contents of the volume, which is showing up as folders on the TM backup drive. Inside these folders is the complete listing (and actual data) of all the files in my secured volume!
    Even if I UNmount the volume from my system, it's still possible to access the data via Time Machine.app (and via Finder, on the TM backup disk).
    So, essentially, even though I've password protected the sparsebundle CONTAINING the data, all a person needs to get the data is to have access to my user account on my Mac, and they can get the data via the above methods.
    Is there any way to allow TM to back up the sparsebundle itself, but not the listing of the contents (and data) of the mounted image?
    It seems odd that I can exclude the volume contents from being indexed by Spotlight, but can't exclude them from being specifically backed up by Time Machine.
    Thanks in advance for any assistance!

    I have exactly the same issue. I cannot exclude the content of mounted disk images from my backup using the GUI (strangely on my other computer the content is not backuped).
    I have manually edited with a text editor the preference file (Library/Preferences/com.apple.TimeMachine.plist) today (I am using 10.6.3) and added in the SkipPaths section the mounting point of the disk image (typically /Volumes/NameofDisk ). So far so good. The corresponding folder appears in the backup but is empty.
    Use at your own risk

  • Time Machine and mounted sparse bundle disk image - file by file backup?

    I think I had this system working in Leopard, but upon upgrade to Snow Leopard it seems to have broken. Does anyone have any idea how I can get Time Machine to back up the contents of a mounted sparse bundle disk image in real time - file by file within the disk image? For example, I have a 2GB sparse bundle disk image that i keep all of my bank statements/files/records in. It auto-mounts on boot and stays mounted. I use the disk image to keep it password-protected, so if I unmount it it is fairly safe. In Leopard, I would exclude the .sparseimage file from backup, but it would still backup the mounted image itself on a file-by-file basis, so I could enter Time Machine and explore the image folder by folder, file by file (say I deleted an old bank statement by mistake, I could go into time machine and recover as if it were a normal file/folder).
    In Snow Leopard, after a clean install, and creating a new sparse bundle disk image and excluding the .sparsebundle file, I can't seem to get this to work even though the image is mounted. Is there any way to trick Time Machine into backing up the mounted image as it would any other folder? I know I can back up the .sparsebundle file incrementally but in order to recover a lost document I'd have to remount the old bundle and that seems rather roundabout.
    Thanks,

    I think you're trying to bypass the finder to mount the disk. Try this (I'll bold the key steps):
    - *Turn off Time Machine* in the System Preferences.
    - Option A: If you directly use a hard disk (not wireless) that has the sparsebundle you want to open, *connect the disk* but don't double click on the sparsebundle.
    - Option B: If you are using wireless, this means use shift-command-k (or shift-apple-k), and if it says "Connect As..." in the upper right instead of disconnect, then use that button to *connect to that wireless drive*.
    - Confirm the sparsebundle shows in that folder before proceeding...
    - *Open Terminal* (Applications>Utilities>Terminal.app)
    - Type: *hdiutil attach -noverify* (<-- notice a *space " "* must be included after typing this here but *DON'T hit return* yet.)
    - *Drag the sparsebundle to the cursor in terminal*, and it should fill in something like /Volumes/HardDrive/COMPUTERNAME.sparsebundle for you. Now you can hit return, and the disk will mount.
    - After you are done browsing sparsebundle's mounted image, *eject the mounted disk* like you would any other disk (not the sparsebundle image itself, just the disk icon that appeared if you successfully mounted it).
    - Turn *Time Machine back on* in the System Preferences.
    Hope this helps.

  • Time Machine says "Backup volume could not be found"

    Okay, I know what I did; now I need help in untangling an unintended consequence.
    I surmise from the error message (and from some info from Time Machine Buddy widget) that the problem is the cookie doesn't match.
    "Cookie file is not readable or does not exist at path: /Volumes/BigBackup/.000d9356b794
    Volume at path /Volumes/BigBackup does not appear to be the correct backup volume for
    this computer. (Cookies do not match)
    Backup failed with error: 18"
    I can guess why: I had some significant cosmetic damage to my G5 desktop a week or so back, and I moved all internal parts -- drives, RAM, even the added cards -- over from the "injured" G5 to an identical G5 that I had in reserve. Booted up and ran perfectly, no problems with identification from any outside sources and all software thinks it's still "home" and is running fine.
    However, if the cookie left by Time Machine on the backup uses a device identifier for the computer beyond just the basic computer network name (a safe guess!) then I see how I've created a problem -- yes???
    So, without destroying all of my previous backups or rendering them unreadable from this machine, HOW can I fool Time Machine, the G5, the cookie, and/or the backup volume into believing they've all been in love forever and ignoring the "oops, it's just a clone" problem? Can I doctor or hack the cookie or otherwise un-mess my mess? Thanks!

    Steve Jolly wrote:
    However, if the cookie left by Time Machine on the backup uses a device identifier for the computer beyond just the basic computer network name (a safe guess!) then I see how I've created a problem -- yes???
    Yes. Time Machine knows it's a different Mac, via the address that's embedded in the hardware of the replacement Mac's logic board.
    So, without destroying all of my previous backups or rendering them unreadable from this machine, HOW can I fool Time Machine, the G5, the cookie, and/or the backup volume into believing they've all been in love forever and ignoring the "oops, it's just a clone" problem? Can I doctor or hack the cookie or otherwise un-mess my mess? Thanks!
    You might be able to use the procedure in #C8 of Time Machine - Troubleshooting (or use the link in *User Tips* at the top of this forum).

  • Time Machine Error -- Backup Volume is Read Only

    I suddenly started getting this error today when Time Machine runs. I use a 1 TB WD My Book as my Time Machine drive. When I select get info on the backup folder on the WD drive and check sharing and Permissions tab, it states directly under this label that "you can only "read" even though I am the administrator and it shows me as having read and write access in the table below the "you can only read" message.
    Any thoughts?

    See the following:
    What to do if Time Machine reports you don't have permission
    This was posted in the Apple Discussions by V.K. I have only modified it slightly to be more generic.
    The problem seems to be that 10.5.6 changes permissions on a file so that even the root user doesn't have write peivileges. I have no idea why they did this. The workaround suggested in [an]other post will probably work, too, but i did something less drastic. Instead of deleting the file I changed permissions on it, and it worked just fine. An added benefit is that the permission change seems to stick, so you don't have to delete the file every time you change a drive.
    [Open the Terminal application in your Utilities folder. At the prompt [enter] the following command:
    sudo chmod 644 /volumes/"TM drive name"/.xxxxxxxxxxxx
    The name of the file .xxxxxxxxxxxx is based on the MAC address of your computer and will be different for every computer. Put the name of the TM drive in the above and keep the quotes.
    You'll have to enter your admin password (which you won't see) which is normal.
    This was edited by Kappy just for cleanup.
    Enable Finder to Show Invisible Files and Folders
    Open the Terminal application in your Utilities folder. At the prompt enter or paste the following command line then press RETURN.
    defaults write com.apple.finder AppleShowAllFiles TRUE
    To turn off the display of invisible files and folders enter or paste the following command line and press RETURN.
    defaults write com.apple.finder AppleShowAllFiles FALSE
    Alternatively you can use one of the numerous third-party utilities such as TinkerTool or ShowHideInvisibleFiles - VersionTracker or MacUpdate.

  • Time Machine wont mount backup, wants to create new one.

    I'm running OSX Lion 10.7 on an iMac 27 with an intel i5 2.7 GHz processor.
    I received a notification that Time Machine wasn't backing up.
    Somehow the external backup drive became disassociated with TM. So I re-selected it and TM began preparing for a backup. A few moments late a warning popped up stating there was not enough space on the disk to complete the backup.
    I entered Time Machine to free up space however, TM had created a new backup file and now it won't mount the original one. I've tried deleting the new backup file, hoping TM would mount the original, but it just keeps creating new ones.
    I noticed the new backup file name was different to the original. After looking in to it further, it appears as if this was due to some changes I'd made in my file sharing settings, a couple weeks back, while trying to download some photos from am Android phone. I changed the name back, however, TM still want's to create a new file and still won't mount the original.
    The last time it successfully backed up was Oct 30th and the good news is, I can manually open the original backup file in Finder, and see all the old files.
    I've read through a number of trouble shooting sites and I've already checked for and installed all updates with no luck.
    I really could use some help with this. Any and all input would be greatly appreciated.
    Thanks.

    No, I don't think playing around with the sparsebundle is very good idea ever.
    If you are now down to that level. Move the old sparsebundle off the TC. Either delete the whole thing and start over.. or save it beforehand.
    It is possible to archive off the old sparsebundle, although it is pointless if it is corrupted.
    You can copy it to a USB drive on the computer.
    See Q18 here. http://pondini.org/TM/FAQ.html
    That will take a long long time so be warned.. and do it with ethernet.. otherwise it will take forever.
    You can also do the archive directly to USB disk plugged into the TC. You need a hard disk at least as large as the data.
    And you will need to use v5.6 airport utility because Apple deleted it in the new version.
    If you run Mountain Lion (Lion is easy) you can download it and install by a trick.
    That will then give you access to archive and you can use that to save the present hard disk info.. then erase it and start over.
    How to load 5.6 into ML.
    1. Download 5.6 for Lion.
    http://support.apple.com/kb/DL1482
    Click to open the dmg but do not attempt to install the pkg.. it won't work anyway.
    2. Download and install unpkg.
    http://www.timdoug.com/unpkg/
    Run unpkg on the desktop.. it is very simple.. drag the AirPortUtility56.pkg file over to unpkg.. and it will create a new directory of the same name on the desktop.. drill down.. applications utilities .. there lo and behold is Airport utility 5.6 .. drag it to your main utilities directory or just run it from current location.
    You cannot uninstall 6.1 (now 6.2 if you updated) so don't try.. and you cannot or should not run them both at the same time.. so just ignore the toyland version.. the plastic hammer.. and start using 5.6.. a real tool.
    For screen shots see this post.
    https://discussions.apple.com/thread/4668746?tstart=0

  • Time Machine Excluding External Volumes?

    The following threads discuss backing up external volumes using Time Machine.
    https://discussions.apple.com/thread/5316613?start=30&tstart=0
    https://discussions.apple.com/message/16591548#16591548
    https://discussions.apple.com/message/6785149?searchText=Time%20Machine%20Exclud ing%20External%20Volumes#6785149
    So apparently TM can backup external volumes but I have not been able to do so. 
    I've been experimenting with TM to backup external drives.  It will not backup my external drive, even when I remove it from the exclusion list.  It automatically re-added it to the exclusion list even though I explicitly removed it from that list.
    My test:
    - I plugged in a 1 GB thumb drive and formatted it as Mac OS Extended (journaled). 
    - I put some new files on it with unique filenames for a test. 
    - I told TM to run backups (several ones in sequence). 
    - I opened the thumb-drive volume then entered TM.  TM showed only the current state with no backups.
    I opened Preferences > Time Machine > Options…  It listed the thumb drive as excluded.  So I removed the exclusion.
    I unmounted the thumb drive, mounted it again and repeated the experiment.  Same result.  It appeared in the exclusion list again.
    What gives?  How do I tell TM to backup external volumes (or not to exclude doing so)?

    Yep.  Read that before posting.
    Also found https://discussions.apple.com/message/20711519#20711519
    where Linc Davis says
    External drives are automatically added to the Time Machine exclusion list. To back them up, remove them from the list. Volumes on the backup drive itself are automatically excluded, and you can't change that.
    There is no reason why you shouldn't back up multiple volumes in Time Machine.
    I did remove it from the exclusions list but TM added it back.  What now?

  • Time Machine cannot mount remote backup disk (ReadyNAS NV+)

    Hello,
    I own a ReadyNAS NV+ which I use as an external backup. It has a "Time Machine" backup daemon, so the iMac see's it over network. I used it for a couple of months without issues.
    A couple of days ago I had to change the physical location of ReadyNAS. Now there are 2 switches between my iMac and the readyNAS.
    Since I changed the physical position of the ReadyNAS I try to backup using time machine but it's not possible. Time machine hangs up when trying to up at "Making Backup Disk Available". Using the terminal I can clearly see that AFP has issues mounting the disk:
    afp_4pcsta0oyhi62C4wJd3Bx6yh-1.2e00000b on /Volumes/ReadyNAS (afpfs, nobrowse)
    angel:log root# dmesg
    6a800!
    jnl: disk3s2: journal_open: Error replaying the journal!
    hfs: early jnl init: failed to open/create the journal (retval 0).
    disk3s2: 0x5 (UNDEFINED).
    0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 5] [IOType Read] [PBlkNum 2] [LBlkNum 2] [FSLogMsgID 1814855696] [FSLogMsgOrder First]
    0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [DevNode devfs] [MountPt /dev] [Path /dev/disk3s2] [FSLogMsgID 1814855696] [FSLogMsgOrder Last]
    AFP_VFS afpfs_unmount: /Volumes/ReadyNAS, flags 524288, pid 285
    AFP_VFS afpfs_mount: /Volumes/ReadyNAS, pid 872
    jnl: disk4s2: replay_journal: from: 8247296 to: 4564992 (joffset 0x962000)
    ASP_TCP dothreadread: no reqInfo found for reqID 5
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa258660
    AFP_VFS afpfs_DoReconnect started /Volumes/ReadyNAS prevTrigger 0 currTrigger 1
    ASP_TCP CancelOneRequest: cancelling slot 22 error 89 reqID 3256 flags 0x29 afpCmd 0x3D so 0xa258660
    ASP_TCP CancelOneRequest: cancelling slot 23 error 89 reqID 3257 flags 0x29 afpCmd 0x22 so 0xa258660
    ASP_TCP CancelOneRequest: cancelling slot 24 error 89 reqID 3258 flags 0x29 afpCmd 0x22 so 0xa258660
    ASP_TCP CancelOneRequest: cancelling slot 25 error 89 reqID 3259 flags 0x29 afpCmd 0x22 so 0xa258660
    ASP_TCP CancelOneRequest: cancelling slot 26 error 89 reqID 3260 flags 0x29 afpCmd 0x22 so 0xa258660
    ASP_TCP CancelOneRequest: cancelling slot 27 error 89 reqID 3261 flags 0x29 afpCmd 0xB so 0xa258660
    ASP_TCP CancelOneRequest: cancelling slot 28 error 89 reqID 3262 flags 0x29 afpCmd 0x22 so 0xa258660
    ASP_TCP CancelOneRequest: cancelling slot 29 error 89 reqID 3263 flags 0x29 afpCmd 0x22 so 0xa258660
    0 [Level 5] [com.apple.message.domain com.apple.afpfs.reconnect] [com.apple.message.signature Reconnect failed - socket failed to start reconnect] [com.apple.message.value 1297443679] [Message afpfs_DoReconnect: socket failed to start reconnect 61 /Volumes/ReadyNAS
    AFP_VFS afpfs_DoReconnect: posting to KEA to unmount /Volumes/ReadyNAS
    0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 6] [IOType Write] [PBlkNum 8] [LBlkNum 8] [FSLogMsgID 1662666978] [FSLogMsgOrder First]
    0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [DevNode afp_4pcsta0oyhi62C4wJd3Bx6yh-1.2e00000a] [MountPt /Volumes/ReadyNAS] [Path /Volumes/ReadyNAS/angel.sparsebundle/bands/0] [FSLogMsgID 1662666978] [FSLogMsgOrder Last]
    disk4s2: 0x5 (UNDEFINED).
    0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 5] [IOType Read] [PBlkNum 11744] [LBlkNum 11744] [FSLogMsgID 1726805554] [FSLogMsgOrder First]
    0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [DevNode devfs] [MountPt /dev] [Path /dev/disk4s2] [FSLogMsgID 1726805554] [FSLogMsgOrder Last]
    jnl: disk4s2: updatefsblock: error reading fs block # 11744! (ret 5)
    disk4s2: 0x5 (UNDEFINED).
    0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 5] [IOType Read] [PBlkNum 27379] [LBlkNum 27379] [FSLogMsgID 1933006271] [FSLogMsgOrder First]
    0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [DevNode devfs] [MountPt /dev] [Path /dev/disk4s2] [FSLogMsgID 1933006271] [FSLogMsgOrder Last]
    jnl: disk4s2: dojnlio: strategy err 0x5
    jnl: disk4s2: replay_journal: Could not read journal entry data @ offset 0x46a800!
    jnl: disk4s2: journal_open: Error replaying the journal!
    hfs: early jnl init: failed to open/create the journal (retval 0).
    disk4s2: 0x5 (UNDEFINED).
    0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [ErrType IO] [ErrNo 5] [IOType Read] [PBlkNum 2] [LBlkNum 2] [FSLogMsgID 800265459] [FSLogMsgOrder First]
    0 [Level 3] [ReadUID 0] [Facility com.apple.system.fs] [DevNode devfs] [MountPt /dev] [Path /dev/disk4s2] [FSLogMsgID 800265459] [FSLogMsgOrder Last]
    AFP_VFS afpfs_unmount: /Volumes/ReadyNAS, flags 524288, pid 285
    AFP_VFS afpfs_mount: /Volumes/ReadyNAS, pid 933
    jnl: disk5s2: replay_journal: from: 8247296 to: 4564992 (joffset 0x962000)
    angel:log root#
    Finally Time Machine exists with error "Backup disk cannot be accessed. error 109".
    Can someone give me a hint or two on how to solve this issue?
    regards

    Not a NAS-specific issue.  The OS is trying to read a block of the sparse disk image, and the read is failing.  Basically, the sparse bundle is damaged.  You'll need to rename it and then try backing up again to a clean sparse bundle.
    That said, make sure you're running a version of the ReadyNAS firmware that actually supports Time Machine.  There are several AFP commands that were added for Time Machine that *must* be supported for correct operation, and older AFP implementations did not implement them.  The reconnect errors suggest to me that maybe the firmware you are running doesn't support the Reconnect UAM, in which case it probably also doesn't support the replay cache, etc.  If that's the case, then things probably won't work correctly without a firmware update even after you fix the corrupted sparse bundle.
    Edit: actually, on further searching, it might be a NAS-specific issue.  Certain buggy network switches do not properly support jumbo frames in mixed networks, which can cause read errors similar to what you are seeing when working with AFP.  (This might have been your post on the other board.)  In the Network prefs pane, choose Ethernet, click "Advanced", click the Ethernet tab, change Configure to Manually, and set the MTU to Standard (1500).

  • Time Machine Wont Mount

    Hi,
    Hopefully someone can help here, I have a mid-late 2007 Al 2.0 Ghz iMac, and I had the weirdest thing just happen. I was watching a video on quicktime and decided to plug in a jumpdrive, it didnt mount so I unplugged it.
    The OS then told me that it was unplugged without ejecting and it unmounted all of my disks (one labeled videos, my TM and the jumpdrive i guess). I got an error about the Videos disk when it auto remounted saying it needed repairing, but Mac Os could not (Fat32 format). I rebooted to see if that would correct the mounting error, and then neither of my two disks would mount.
    I rebooted with the leopard dvd to check the os drive to make sure it was not corrupt, and the TM hd was mounted there as a generic drive, HSF+ formated, but would not verify or get any details. It also would not eject at all.
    I rebooted again back to the regular os (start up disk returned no errors when checked) and the Videos disk mounted without a problem, but the TM disk wont. It wont show up in Disk Utilities either. It does however show up in about my mac as an external drive.
    The output of my /dev
    /dev/disk0s2 on / (hfs, local, journaled)
    devfs on /dev (devfs, local)
    fdesc on /dev (fdesc, union)
    map -hosts on /net (autofs, automounted)
    map auto_home on /home (autofs, automounted)
    /dev/disk2s1 on /Volumes/VIDEOS (msdos, local, nodev, nosuid, noowners)
    and the info on system profiler of the TM drive
    External HDD:
    Product ID: 0x0910
    Vendor ID: 0x1058 (Western Digital Technologies, Inc.)
    Version: 1.06
    Serial Number: 574341505A30363236353239
    Speed: Up to 480 Mb/sec
    Manufacturer: Western Digital
    Location ID: 0xfa430000
    Current Available (mA): 500
    Current Required (mA): 2
    now if i list my /dev I do get a retun of the following disks
    disk0
    disk0s1
    disk0s2
    disk2
    disk2s1
    disk3
    disk3s1
    disk3s2
    if i try to force mount the drive in terminal I return
    Nobodys-imac:~ admin$ mount /dev/disk3
    mount: /dev/disk3: unknown special file or file system.
    So im thinking I hosed the drive, but it wasnt reading/writing when it was force unmounted earlier.
    Its spinning and it sounds like the drive is seeking or reading/writing.
    Any thoughts are appreciated.
    Thanks for reading,
    Brian
    Message was edited by: brian.parker

    It figured itself out I guess, I rebooted for the third time and time machine kicked in and started back up, no problems for several days now.

  • Time machine only mounts the drive to Finder. The Program doesn't open. What is missing here?

    Selecting <Time Machine> <enter time machine> on my Mac Air brings up a dialogue <connecting to backup disk>.  The disk  appears <mounted> on the desktop as a icon and shows as a connected drive in Finder.  It doesnt  open into the Time Machine interface that I expect and which used to work.  Is there a simple fix here?

    Sorry, you have lost me.
    If you open AirPort Utility and click the Disks tab, what do you see there?
    Next to Partitions, you should see "Data" which is the default name of the Time Capsule drive.....or.....if you have renamed "Data", you will see the name that you have assigned to the drive.  In the example below, I have renamed "Data" to read "Backups".
    Are you saying that you made previous backups at one time to the drive, then changed the name of the drive?

  • Time Machine to AFP volume is extremely slow after 10.5.2 update

    I remember the time, after I have just installed the very first version of Leopard, when Time Machine was working with close to physical speed of my wireless network. Incremental backups would take less than a minute.
    Comes 10.5.1. Time Machine became slower, but still tolerable: it might take up to 10 minutes to do an hourly backup.
    Comes 10.5.2. Now Time Machine might take a couple of hours to do its "hourly" backup! 99% of the time it spends backing stuff up - when it shows the progress of the backup. So right now it says it's backing up 34.1 megabytes, and then it stopped at 1.4 megabytes, spent there about 15 minutes. Then it continued to about 9.5 megabytes, spend another 20 minutes there, without any progress, no CPU usage, very little network usage. Then it progressed to about 10.5 megabytes, and stuck again. Now it's at 15.2 megabytes, and been there for about 10 minutes already.
    I use Airport Extreme base station with 802.11n at 5GHz, and the backup volume is on my Mac Mini, connected to AEBS via an ethernet cable, and during the phases when Time Machine gets stuck, I tested how the network works from my MacBook Pro, which I'm trying to backup to Mac Mini - constantly getting about 8-9 megabytes per second transfer rate, so clearly it's not that my wireless network is experiencing issues. Besides, the same problem persists even if I plug Ethernet cable directly into my MacBook Pro.
    I've cleaned all caches, repaired permissions, repaired all volumes, rebuilt Spotlight indices on both my MacBook Pro and in the backup sparse bundle. The only thing it solved is insanely long "Preparing for backup" issue, but it DIDN'T solve the slow backup I have just described.
    For comparison: rsync takes about a minute to do a full sync of my entire hard drive to the same AFP volume. Apple Backup 3.1.2 takes about as much. Time Machine - hours. I fail to even begin to imagine what in a world might they be doing there, spending this much time copying 34.1 megabytes of data over the network.
    P.S. As I finish writing this, the backup progress is still at 15.2 magebytes. About 15 minutes now. A little over an hour now and not even half of the 34 megabytes is completed.
    Message was edited by: Farlander
    Message was edited by: Farlander

    Is it slow wireless LAN behavior affecting Time Machine? Check out the third page of this thread, specificallly the post by John Albergo about "delay_ack."
    http://discussions.apple.com/thread.jspa?threadID=1394485&start=30&tstart=0
    It helped me a lot.

Maybe you are looking for