MAJOR TM Bug found in 10.6.1! Time Machine corrupts HFS+ Filesystem! Raid 0

Hey there,
i guess i just found a major bug in 10.6.1 and Time Machine which will corrupt the whole Partion which was selected for the Time Machine Backup.
This is what i got here atm:
2x Western Digital MyBook Mirror Ed. (ext. 2TB Raid0 HDD (2x1TB))
1x Mac Pro running 10.6.1
1x Macbook Pro running 10.6.1
1x Mac Mini running 10.5.8
Ok here we go:
I just updated to Snow Leopard a few weeks ago and wondered why my always working WD MyBook was not working as a Time Machine Backup Partition anymore.
Everytime i started a backup it failed after 10 gig or so. After reading all over the troubleshooting and this forum i am a 100% sure that this is not a usually bug like not formatting the hard drive to GUID Mode or so.
Well... i tried the second MyBook.. same result on both Macs running 10.6.1
Now i got suspicious and opened the MyBook in order to put those 2 HDDs in my Mac Pro and built a 2TB Raid0 via OSX.
Guess what? Same result when running Time Machine! Running Time Machine on a single 1 TB HDD was working perfectly fine.
No i just remebered that there was a Mac Mini hooked up to my TV that was still running 10.5.8 just because of Plex... Hooked up BOTH MyBook Mirror Editions and both worked perfectly fine!
Now where can i report this error? I have no doubt that Time Machine on 10.6.1 is corrupting the HFS+ Filesystem when the partition is a RAID 0 Partition.
Please let me know what you think and where i can report this bug. Anyone knows if this one is already fixed in 10.6.2?
Thanks!
André

Yeah i did check the firmware updates for both mirror editions. Both are up to date. What botheres me is that they are not working aswell when they are out of their enclosure and directly built in to the mac pro. Can this really be a firmware issue then?
From what I've read on repair/recovery sites, WD does put some of their firmware on a special part of the drive's platter itself. So it's still possible to have instructions on the actual disk that can create a problem. I do not know if this is causing your issue, it's just something I became aware of when shooting trouble on some MyBook/Mac issues. There are some WD enhancements to power management that may be problematic for Time Machine. I don't really know the whole story, just relaying what I've read.
It's also possible that 10.6.2 (in beta) will help with an issue like yours. In our machines we've been using Hitachi and Seagate and the occasion Samsung drives for the last few years. Our external closures come from OWC and we haven't had any of the firmware issues that happened with the Leopard release and WD and now maybe the SL release.
The only way I would be able to point a finger right now would be to swap in a couple of other drives and see how they work. Right now it doesn't matter who's at fault, Apple or WD. The drives don't work. If it's a problem with your installation you may be able to determine that by doing the above tests. If it's a problem with Apple's drivers there may not be a repair possible or a future update will be required. The same goes for the WD drives.
Sidenote: For our own network, we have decided to do away with Leopard Server on an old Dual G4 1.42 tower and use our new ReadyNAS drive from Netgear. It's already working perfectly with Time Machine for several computers, file storage for PC/Mac/Linux, torrent download machine, basic web server, etc. We've put in 4 1TB drives and got 2.7TB of redundant hot swap raid. We'll replace the 1TB drives with 2TB drives, one at a time (although the available space won't increase until all 4 drives are swapped in), while the NAS is online, to increase our storage as required and the drives come down in price.
We decided that if the data is important then a striped 2 drive volume isn't safe enough. We would have needed to mirror the drives and loose half the space and still have to keep the old server online.
I'll watch this thread for information from others. I don't have the drives you are using to test with.

Similar Messages

After updating my MacBook Pro to yeosemite I want my old screen saver picture back. I did a full back up before the install. I found the "Settings" folder in Time machine but when I try to open it I get an error message saying "You can not open this

After updating my MacBook Pro to yeosemite I want my old desktop picture back. I did a full back up before the install. I found the "Settings" folder in Time machine but when I try to open it I get an error message saying "You can not open this folder. It is in TimeMachine".

Can you browse the Time Machine drive from Finder?
If you can and you know where the picture was stored ie on your desktop you can browse through the folder structure to the picture copy it and paste it somewhere on your new install before right clicking it and 'set as desktop background'

External hard drive no longer found after becoming full from time machine, External hard drive no longer found after becoming full from time machine

Hi, I have been using an external hard drive as a backup for my Mac using Time Machine. I was under the impression that once the backup drive became full, it would start to delete previous versions of the backup. However, instead of doing that, it has just stopped working and I now cannot access the hard drive via a Mac or a PC. On the PC, it does at least show up in that it will allow me to disconnect it safely but I cannot do anything else with it.
I am now looking to reformat it, and start again from scratch - but can't do this as it doesn't show up anywhere. Does anyone have any advice about how I can get this working again?
Thanks.

Can you see the drive in Disk Utility? If so, try selecting it and using the Mount button in the top menu. You can also run repair disk and repair permissions.

User Not Found Using Migration Assistant and Time Machine

My iMac running Leopard kernel panicked which forced me to do a hard reset. After rebooting, the account I was logged in as disappeared. Fortunately, that wasn't the admin account. I logged into my admin account and thought I would use Migration Assistant to recreate the missing account (I did run Disk First Aid first to ensure the hard drive was in good working order). However, Migration Assistant does not list the missing user account when reading my Time Machine backup. I do see the user if I go directly into into Time Machine. I'm guessing that Migration Assistant may only be looking at the most recent backup which obviously doesn't contain the missing user.
Suggestions on how to restore the missing user or how to get Migration Assistant to read all of the users in my Time Machine backups?

BobParr wrote:
I'm guessing that Migration Assistant may only be looking at the most recent backup which obviously doesn't contain the missing user.
Correct.
Suggestions on how to restore the missing user or how to get Migration Assistant to read all of the users in my Time Machine backups?
How many backups were done after the problem occurred? One possibility would be to delete those backups (see #12 in the Frequently Asked Questions *User Tip,* also at the top of this forum), so the last one has the missing user's data, and Migration Assistant can find it. If you do that, once everything's properly restored, boot up from your Leopard Install disk, then reboot normally. That will trigger a "deep traversal" in the next backup, where TM will compare everything on your system to it's backups, thus assuring that nothing was lost via the earlier deletions.
Another would be to do a full restore from Time Machine, per #14 in the FAQ.

Found iCal events in Time Machine. Now Lion only allowing me to import one event at a time.

Upgrade my macbook pro over the weekend to Snow Leopard and then Lion.   I lost all my the majority of my iCal events.   Went to Apple store and they said that was rare and not sure how to restore my last back up from Time Machine on an external drive.   I've been spending hours trying to go through a bunch of threads on different MAC formums.
So I finally found my iCal events in Time Machine.   When I try to import these events, I am only allowed to highlight/import one event at a time.   This will take me forever to import years of missing data.   I basically have been using my iCal to journal for my 3 small daughters - first tooth, hair cut, etc.   So I am desperate to get these events back so I can get them printed and SAFE.
Does anyone have any suggestions on how to import my ics files?   The Apple Store Genius had me tryng to import the corestorage.ics files.   2 or 3 of those files showed they were trying to be imported for over 4 hours.   I finally Forced Quit iCal.   I've tried this several times and same result.
The corestorage files were under user/library/application support/ical/sources
I now located the calendar events user/library/calendars/ then a bunch of coded files leading to the events. These events appear to be the ones I am looking for as I can read some of the files.   I have several years I want to import back into my working iCal.
Please help if you know how!!!
Thank you,
Very Upset Mama of 3 little girls

Thomas - You are awesome - THANK YOU!
I did exactly what you said (CAN"T believe an Apple Genius did not know this) and I think all of my events got restored.
However, it duplicated all of the calendars - I have 6 (one for each family member plus an extra called home that we all have to do).   Not sure if I did something wrong, but do you have any ideas?
Also, the time setting must be wrong b/c I have events from 2008 showing up in 2012 - same day and time as the old sessoin - just out dated.    Do I need to manually change all of this?   Should I delete the Calendars folder again and try again?
Also, I read some where about deleting a iCal cache file.   Do I need to do this?
I TRULY appreciate you taking the time to help people in this forum.   I have spent hours the past two days trying to figure this out.   Plus, now I need to figure out about upgrading my Office for Mac b/c I didn't realize I lost Office 2004 when upgrading to Lion.
Thank you for your time and support!
Lori

Time Machine Bug after Restore

Hi all,
I've been learning Time Machine and will share two possible bugs if it is helpful. I am working on a 2011 MacBook Pro, upgraded to Mountain Lion some months back, with 50 GB data on SSD being backed up to and restored from a LaCie SSD 80 GB partition so the speed is very nice: 14 minutes for initial backup and 7 minutes for a Reboot + Command + R restore.
Bug #1. Both (initial) backup and restores begin with large 60 minute estimated times in Time Machine Prefs Progress Bar but, once it gets going, finishes in 14 and 7 minutes respectively. If symptom is due to some quadratic journal searching algorithm, it may explain why APL-CARE warned me about potential 16 hour restores and could be a bug. If it is due to Time Machine just counting what has been transferred so far, then maybe not a bug (but maybe a possible enhancement request).
Bug #2. It appears that the first time Time Machine runs after a Cmd+R restore, it tries to rebuild an entire journal or record of what it has and, if you interrupt this initial backup, you break Time Machine. The next time you try to backup, Time Machine thinks Everything needs to be backed up (even though your disk is identical to what it just restored), and it Fails in my case with message "Time Machine couldn't complete the back to [my LaCie drive because my 50 GB of data is already there and it thinks it needs a full 50 GB more]" in so many words. APL-CARE (and its expert advisor) tried to call this a feature and sent me to your article HT3275 but that seems like a different issue. Since I did not believe Time Machine was so stupid, I ran the sequence again and carefully avoided interrupting Time Machine during its initial backup following my Cmd+R restore and, indeed, it took about 8 minutes to backup 4.5 MB (and rebuild whatever it does that first time). So this feels like a straight-up bug, Time Machine should scare me with a popup if I interrupt it while it is rebuilding its critical list for the first time after a restore. If APL-CARE were correct, it would mean everyone loses all history after a restore, everyone needs to Erase their backup disk and start from scratch, and methinks that too would be a bug.
Hopefully this is helpful, Time Machine is otherwise very cool and I love the Star Trek GUI.
Regards,
Dave.

And this is an ERROR in time machine. I just did a test restore again, went quickly, then Time Machine is GONE, GONE, gone trying to restore 5MB, waiting over an hour when a fresh backup takes about 15 minutes.
So only solution is DESTROY all my backups, then start over. Really dumb, and this page has no option to change my post back to a question, also really dumb.
I am going to swear now: cr*p. OK. Fix your **** software please. I'll deal with workarounds till then.
-dave

BUG FOUND!! in Airport Disk programming

I'm betting this is having a bigger issue then most poeple realize as it effects reconnecting to the Airport disk.
Ok after lots of testing I've figured out a major bug in the Airport Disk Programming for Security.
This has only been verified with the following settings:
1. Airport Disk is configured with Accounts for access
2. Formatted with HFS+ USB drive.
Discription:
1. When connecting to the Airport Disk you get the error:
"Connection Failed
Unknown user, incorrect password, or login is disabled. Please retype the login information or contact the disk's administrator."
2. You retype the password and user name and it still says the same thing over and over and over.
The Cause of problem:
You connect to your Airport Disk the first time with no problem using your login and password. If you cause your connection to be interrupted for a small amount of time and you get that Warning about server disconnect and it shows your airport disk and personal disk with the disconnect button, and they disconnect!! Then you cannot reconnect to the Airport Disk till you reset the Airport Extreme.
To get this Disconnect dialog, it can be caused by a number of common uses, here are a few of the common ones:
1. you VPN into work (with Airport Disk shares mounted)
2. you change from wireless to Hardwired connection (with Airport Disk shares mounted)
3. You let your computer go to sleep when its on a wireless connection but are connected through another wireless access point hardwired to the network (with Airport Disk shares mounted)
When getting your Airport Disk volumes disconnected in this way, The Airport Extreme I'm guessing is deactivating the account and not properly disconnecting the connection. So at this point you have to Reboot the Airport Extreme to let you use your account again on the Airport Disk.
I hope some poeple from Apple actually read these. I've had to reset my Airport extreme about 24 times a day between my wife's 15" MBP and my 17" SR MBP getting this disconnect problem.
And for those poeple out there who keep having Airport Disk connection problems, Lets make sure your not having this problem. To test, simply reboot the airport extreme router & see if you can connect to your Airport Disk Volumes, then once your volumes are mounted turn off your Airport wireless (on your MAC) or unplug your Hardwire till you get the disconnect message. Then try to reconnect to your Airport Volumes after restoring your network connection.
This issue needs to be fixed ASAP!!!!
Please reply to this message with your nominations to try and get this issues raised to a P1 or lvl 1 priority so it's in the next firmware upgrade as it's not an issue with OS x programming side, as a rebot of the computer still doesn't restore the connectivity with the AirPort Disk.

HERES A SOLUTION I POSTED IN ANOTHER THREAD!
Hi,
I've been trying to work out the Hard Drive problems with the Airport Extreme for a few days and have had some success, so I'll share the info if its any use!
First of all, your printer and both hard drives all run off their own power supply, therefore, you don't need to have a powered usb hub, or just take the plug out and keep using the hub, save yourself a plug!
More importantly, I have had the same thing with the hard drive appearing in the Airport Utility yet whenever I try to connect, it comes up with an error and can't mount, although when I go to network and connect it appears but then goes wrong at the last part mounting, this is what I found...
the first time I plugged hard drive in all worked nicely, however, any time I have unplugged the power to the Aiport Extreme and connected again it'll show but never connect. When I went to make a few partitions I realised that if you unplug the router and repower, whatever HD name its seen before doesn't work until the HD name was changed again. For example....
I called my first HD to connect 'wifiHD', was working fine, next time i unplugged router was still showing in network but I couldn't mount it, I then plugged it to the mac and renamed it 'wifiDISK' for example and plugged it back into the router and it worked fine! Its very strange cos when I needed to unplug it last time I then had the same trouble and just renamed it back to 'wifiHD' it worked fine! Its a little flaw which is a right bugger to find so the bottom line is...
RENAME THE HARD DRIVE EVERY TIME YOU UNPLUG THE ROUTER AND YOU CAN MOUNT IT AGAIN
Another tip is format your HD in 'Mas OSX Extended' as it can be read by both mac and PC over the network. Then as windows isn't the best when you go to 'My Network Places' and 'Add Network Place' if you can't find the HD or even the router then enter
\\routername\\hardrivename\
in this format into the box, it'll take a mo but it'll then ask for the password! I personally have my hard drive guest access read + write so I entered
user: guest
password: base station password (or disk password as selected in airport utility)
and it all worked!
Sorry for the long explanation, hope this has helped!

Bug Found and Fix Found Creative ZEN XFI Style 32 Gig

9Bug Found and Fix Found> Creative ZEN XFI Style 32 Gig?Hello I was having problems getting my MP3 TAGS to show up on a number of my MP3's.
Whenever I loaded my files onto my ZEN it would show up as a Voice under Recordings.
And the file name would be "MIC and the date file created etc..."
I noticed that these files where all starting with the letters MIC at the front of the filename...
For instance: Michael_Jackson_Thriller.mp3?? or? Michael_W_Smith_Let_it_rain.mp3
and so on and so on... ANY file that started with the letters M I C? would be thrown in as a voice recorded file and the TAG would not operate.
I have the latest Firmware on my MP3 Player.
The fix was just to change the file name so it did not start with MIC... so i went and switched Michael Jackson to M.Jackson and also switched Michael W Smith to M W smith.
The tag showed up appropriately and I have had no problems since.
It would be nice if there was another Firmware update so that MP3's could start with the letters MIC also I was hoping to bring awareness to this situation for other users.

=Re: Bug Found and Fix Found> Creative ZEN XFI Style 32 Gig?I did three methods of?loading the files.
I used Windows Media Player to sync the files.
I used Creative Central to transfer the files.
These two methods produced results where the file starting with MIC turned into a voice recordings.
I also had problems just copying and pasting the files (using windows explorer).
I have not had any problems with any other file. I normally use MP3Tag to tag my files.
However i even tried using Windows Media to tag the file and I even tried using Creative Central to tag the files.
I tried as many work arounds as possible. But once i renamed the file it worked.

Bug Found: Illustrator CC *always* merges layers when opening a DXF file - CS6 works properly

Bug Found: Illustrator CC *always* merges layers when opening a DXF file - CS6 works properly. When opening a DXF, CC merges multiple layers into one, even if you have the "Merge Layers" unchecked. Can a forum admin employee get this submitted as a bug report? Thanks.

Thank you Larry. I just submitted this bug report pasted below at the link you provided.
******BUG******
Illustrator CC 17.0.0 *always* merges layers when opening a DXF file, even if you have the "Merge Layers" unchecked.
1. Open a DXF file that contain multiple layers in Illustrator CC 17.0.0
2. Uncheck the "Merge Layers" button.
3. Click OK.
Results: It has merge all the layers into one layer.
Expected results: It should open with multiple layers preserved. Illustrator CS6 works properly.

[svn] 4223: Some fixes for bugs found running the TC acceptance tests:

Revision: 4223
Author: [email protected]
Date: 2008-12-03 11:35:03 -0800 (Wed, 03 Dec 2008)
Log Message:
Some fixes for bugs found running the TC acceptance tests:
- Empty try {} throwing NPE while emitting code.
- OP_Callproperty and OP_Callproplex may have a known type but default value.
- Better diagnostic message for CONSTANT_TypeName and preliminary plumbing for CONSTANT_TypeName support.
Modified Paths:
flex/sdk/trunk/modules/asc/src/java/adobe/abc/GlobalOptimizer.java

Re: SB Audigy Series Support Pack 2.5 (08/09/2009)? Important Installation Notes
If any drivers are already installed, you must follow these steps to ensure a proper installation of the new Support Pack.
) Open a Command Prompt window with Admin privileges (right click and select Run as Administrator).
Type the following commands:
takeown /f C:\Windows\*.cdf
cacls C:\Windows\*.cdf /G [color="#ff0000"]Administrators:F
Where [color="#ff0000"]Administrators may?be different if you are running a localized version of Windows or?you can simply use your login name.
2) Unpack the previous Support Pack or Creative official release.
3) Run \Drivers\Setup.exe and choose Driver Uninstallation, select Delete all shared Creative audio driver files. and click OK. Reboot when asked to do so.
4) Make sure the following files were deleted, otherwise delete them manually:
- For Windows 7 / Vista 32-bit open?C:\Windows\System32 and delete UDAAPO32.DLL and?UDAPLD32.DLL.
- For Windows 7 / Vista 64-bit?open?[color="#ff0000"]C:\Windows\System32 and delete[color="#ff0000"] UDAAPO64.DLL and?[color="#ff0000"]UDAPLD64.DLL then? open?C:\Windows\SysWOW64 and delete UDAAPO32.DLL.

Time Machine Bug

I believe there is a major bug with time machine being unable to restore a case sensitive file system. If i do a clean install with a case sensitive file system then do a full time machine backup. I am then unable to restore that backup onto an new system with either the disk formatted as case sensitive or case insensitive.
I do have a log of the restore crash but it's a bit big to paste it all here.
Can anyone confirm this bug and if so can it please be fixed as I'm now relying on 3rd party backup software as time machine is unable to perform it's job.
K

It's a full restore from a clean install onto a same spec mbp using the osx install cd to boot from and do the restore. this has been tested on 3 different laptops all suffering from the same issue. restoring a clean non case sensitive install onto the same mbp works fine.
Dec 31 16:28:54 localhost LCA[79]: Folder Manager is being asked to create a folder (cach) while running as uid 0
Dec 31 16:28:57 localhost configd[65]: subnetroute_ifindex: can't get interface name
Dec 31 16:28:59 localhost LCA[79]: Using keyboard layout 2
Dec 31 16:29:00 localhost LCA[79]: Found primary language hint "en"
Dec 31 16:29:45 localhost LCA[79]: Launching the Installer using language code "English"
Dec 31 16:29:45 localhost OSInstaller[145]: Mac OS X Installer application started
Dec 31 16:29:45 localhost OSInstaller[145]: 1 display(s) found.
Dec 31 16:29:45 localhost OSInstaller[145]: Display[1] is using OpenGL acceleration.
Dec 31 16:29:45 localhost OSInstaller[145]: @(#)PROGRAM:Install PROJECT:Install-580
Dec 31 16:29:45 localhost OSInstaller[145]: @(#)PROGRAM:Mac OS X Installer PROJECT:OSInstaller-262
Dec 31 16:29:45 localhost OSInstaller[145]: Hardware: MacBookPro6,2 @ 2.66 GHz (x 4), 4096 MB RAM
Dec 31 16:29:45 localhost OSInstaller[145]: Running OS Build: Mac OS X 10.6.3 (10D2084)
Dec 31 16:29:45 localhost OSInstaller[145]: Env: DYLDNO_FIXPREBINDING=1
Dec 31 16:29:45 localhost OSInstaller[145]: Env: PATH=/usr/bin:/bin:/usr/sbin:/sbin
Dec 31 16:29:45 localhost OSInstaller[145]: Env: PWD=/
Dec 31 16:29:45 localhost OSInstaller[145]: Env: SHLVL=1
Dec 31 16:29:45 localhost OSInstaller[145]: Env: OS_INSTALL=1
Dec 31 16:29:45 localhost OSInstaller[145]: Env: _=/System/Installation/CDIS/LCA.app/Contents/MacOS/LCA
Dec 31 16:29:45 localhost OSInstaller[145]: Using install media product at /System/Installation/Packages
Dec 31 16:29:45 localhost OSInstaller[145]: Opening OSInstall package '/System/Installation/Packages/OSInstall.mpkg'.
Dec 31 16:29:50 localhost OSInstaller[145]: Memory statistics for 'Install Mac OS X' pane:
Dec 31 16:29:50 localhost OSInstaller[145]: Physical Memory Allocation: 818 MB wired, 130 MB trapped, 76 MB active, 31 MB inactive, 3041 MB free, 3148 MB usable, 4096 MB total
Dec 31 16:30:25 localhost Unknown[80]: 2000-12-31 16:30:25.631 Disk Utility[153:903] ********
Dec 31 16:30:25 localhost Unknown[80]: 2000-12-31 16:30:25.692 Disk Utility[153:903] Disk Utility started.
Dec 31 16:30:25 localhost Unknown[80]:
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.556 Disk Utility[153:903] Preparing to remove partition from disk: ‚ÄúTOSHIBA MK5055GSXF Media‚Äù
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.580 Disk Utility[153:903] Partition Scheme: GUID Partition Table
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.581 Disk Utility[153:903] 1 partition will be removed
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.582 Disk Utility[153:903]
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.582 Disk Utility[153:903] Partition 1
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.583 Disk Utility[153:903] Size : 499.76 GB
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.583 Disk Utility[153:903] Filesystem : Free Space
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.584 Disk Utility[153:903]
Dec 31 16:30:56 localhost Unknown[80]: 2000-12-31 16:30:56.638 Disk Utility[153:903] Unmounting disk
Dec 31 16:31:11 localhost Unknown[80]: 2000-12-31 16:31:11.797 Disk Utility[153:903] Creating partition map
Dec 31 16:31:12 localhost Unknown[80]: 2000-12-31 16:31:12.225 Disk Utility[153:903] Waiting for disks to reappear
Dec 31 16:31:12 localhost Unknown[80]: 2000-12-31 16:31:12.262 Disk Utility[153:903] Partition complete.
Dec 31 16:31:12 localhost Unknown[80]: 2000-12-31 16:31:12.263 Disk Utility[153:903]
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.077 Disk Utility[153:903] Preparing to partition disk: ‚ÄúTOSHIBA MK5055GSXF Media‚Äù
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.086 Disk Utility[153:903] Partition Scheme: GUID Partition Table
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.087 Disk Utility[153:903] 1 partition will be created
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.087 Disk Utility[153:903]
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.088 Disk Utility[153:903] Partition 1
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.089 Disk Utility[153:903] Name : ‚ÄúUntitled 1‚Äù
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.089 Disk Utility[153:903] Size : 500.11 GB
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.090 Disk Utility[153:903] Filesystem : Mac OS Extended (Case-sensitive, Journaled)
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.090 Disk Utility[153:903]
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.803 Disk Utility[153:903] Unmounting disk
Dec 31 16:31:26 localhost Unknown[80]: 2000-12-31 16:31:26.828 Disk Utility[153:903] Creating partition map
Dec 31 16:31:27 localhost Unknown[80]: 2000-12-31 16:31:27.019 Disk Utility[153:903] Waiting for disks to reappear
Dec 31 16:31:27 localhost Unknown[80]: 2000-12-31 16:31:27.656 Disk Utility[153:903] Formatting disk0s2 as Mac OS Extended (Case-sensitive, Journaled) with name Untitled 1
Dec 31 16:31:32 localhost Unknown[80]: 2000-12-31 16:31:32.822 Disk Utility[153:903] Partition complete.
Dec 31 16:31:32 localhost Unknown[80]: 2000-12-31 16:31:32.823 Disk Utility[153:903]
Dec 31 16:31:49 localhost Unknown[80]: 2000-12-31 16:31:49.062 Disk Utility[153:903] NSDocumentController's invocation of -[NSFileManager URLForDirectory:inDomain:appropriateForURL:create:error:] returned nil for NSAutosavedInformationDirectory. Here's the error:
Dec 31 16:31:49 localhost Unknown[80]: Error Domain=NSCocoaErrorDomain Code=642 UserInfo=0x106db1290 "You can‚Äôt save the file ‚ÄúAutosave Information‚Äù because the volume ‚ÄúMac OS X Install DVD‚Äù is read only." Underlying Error=(Error Domain=NSPOSIXErrorDomain Code=30 "The operation couldn‚Äôt be completed. Read-only file system")
Dec 31 16:31:49 localhost Unknown[80]:
c 31 16:36:41 localhost OSInstaller[145]: [RESTORE] 5: restoring Developer
Dec 31 16:36:41 localhost OSInstaller[145]: from source path: /Volumes/test/Backups.backupdb/berry/2010-08-06-162655/plum/Developer
Dec 31 16:36:41 localhost OSInstaller[145]: to destination path: /Volumes/plum
Dec 31 16:39:31 localhost LCA[79]: Child exited with status 11
Dec 31 16:39:36 localhost Unknown[204]: Launching the Installer Crash Log Viewer
Dec 31 16:40:11 localhost ReportCrash[203]: Process: Mac OS X Installer [145]
Dec 31 16:40:11 localhost ReportCrash[203]: Path: /System/Installation/CDIS/Mac OS X Installer.app/Contents/MacOS/Mac OS X Installer
Dec 31 16:40:11 localhost ReportCrash[203]: Identifier: Mac OS X Installer
Dec 31 16:40:11 localhost ReportCrash[203]: Version: ??? (???)
Dec 31 16:40:11 localhost ReportCrash[203]: Code Type: X86-64 (Native)
Dec 31 16:40:11 localhost ReportCrash[203]: Parent Process: LCA [79]
Dec 31 16:40:11 localhost ReportCrash[203]:
Dec 31 16:40:11 localhost ReportCrash[203]: Date/Time: 2000-12-31 16:38:59.284 -0800
Dec 31 16:40:11 localhost ReportCrash[203]: OS Version: Mac OS X 10.6.3 (10D2084)
Dec 31 16:40:11 localhost ReportCrash[203]: Report Version: 6
Dec 31 16:40:11 localhost ReportCrash[203]:
Dec 31 16:40:11 localhost ReportCrash[203]: Exception Type: EXCBADACCESS (SIGSEGV)
Dec 31 16:40:11 localhost ReportCrash[203]: Exception Codes: KERNINVALIDADDRESS at 0x000000000745c40c
Dec 31 16:40:11 localhost ReportCrash[203]: Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Dec 31 16:40:11 localhost ReportCrash[203]:
Dec 31 16:40:11 localhost ReportCrash[203]: Application Specific Information:
Dec 31 16:40:11 localhost ReportCrash[203]: objc_msgSend() selector name: release
Dec 31 16:40:11 localhost ReportCrash[203]:

Bit by Mountain Lion's Time Machine bug - how to proceed best in the simpler cases?

My MacBook Air mid-2012 had never been updated to Mavericks. I had backed it up just a week before a big coffee spill that killed it (June 2014).
I finally got a replacement never-before-used 2012 Macbook Air running Mountain Lion (great to make the Time Machine restore seamless).
That's when I tried "Restore from Time Machine" and it showed the "last full backup" as being from June 2013!!! Then in Migration Assistant, couldn't locate my disk. I've been bitten by the "Exclusion" bug and my Library/ Applications / System folders have not been backed up since a year ago. I'm one of the ones that "found out after it was too late."
So I'll try the workaround. Thanks to Pondini for his great website:
http://pondini.org/TM/D10.html
http://pondini.org/TM/D10r.html
My plan is to restore from Time Machine to my 2013 full system.
Then swap out the Users folder to bring it up to date to the June 2014 version that I have backed up.
Luckily I have only one user account so this can't get TOO complicated.
After that, I'll reset Time Machine and check it periodically via the Command-R trick to make sure it's backing everything up fully.
Still, I'm left with a few questions/concerns that I'm hoping Pondini or others can help to allay before I proceed....
-What will I have lost in a year from those folders that did not back up? I know I may have lost non-Mac applications that I downloaded and also any software updates to said applications. What problems might I encounter in the way of error messages, etc.? I feel like i don't understand the contents of these folders well enough to realize how in trouble I'm in (or not) regarding these folders being out-of-date by a whole year.
-Is it really as simple as swapping out the Users folder on the new system with my most recent backup from June 2014? Any hiccups I should expect from this process? Will all of my photos go back into iPhoto? Will all of my mail files go back into the Mail app? Or in these cases, is there something I need to initiate to smooth out this process? Photos and Mails are the two big concerns; as for the other stuff, I have yet to find out if it's relevant until a problem occurs.
-Once I have restored Apps/Systems/Library to the 2013 backup and Users to the 2014 backup, then what? I'll reset Time Machine but then should I assign it to the new computer? Should I tell it to inherit the new computer? Should I wipe it clean and start fresh? How to proceed after so that I don't have more and more problems down the line, and hopefully don't lose any of the data that I at least have managed to save/restore up to now...
Thanks in advance for any help and sorry if I'm not more clear; I'm not so technologically literate so I'm not sure how best to phrase these things to get my point across.
And special shout out to Pondini who made the discovery of this bug a lot easier to stomach thanks to your helpful website.

A clone is an option.
Clone - Carbon Copy Cloner (Often recommended as it has more features than some others)
Clone – Data Backup
Clone – Deja Vu
Clone - SuperDuper
Clone - Synk
Clone Software – 6 Applications Tested
Commonly Used Backup Methods

Time Capsule / Leopard 10.5.8 / Time Machine / Disk can't be opened because the original item can't be found / OSStatus error -6602

Hi,
I'm facing a big issue with Time Machine on my Mac Book running Leopard 10.5.8 (build 9L31a) and my Time Capsule (firmware 7.6.1 (76100.4)).
I have searched a lot (during 3 days !!) to find a solution but no luck !
I have the same syntoms as described by LUNY in this thread: https://discussions.apple.com/message/9364556#9364556
To quickly summarize:
My MacBook was configured to use my Time Capsule as backup disk. Everything went fine during 2 years and then one day I suddently got problems with time machine !
Time Machine was unable to access my Time Capsule. Moreover it was drastically slowing down my MacBook !
So:
1. I stopped Time Machine and tried to change the backup disk: every time I chose my Time Capsule Disk, I got a OSStatus error -6602
2. Then, I tried to access my Time Capsule from the Finder -> slow and then got this message 'Disk can't be opened because the original item can't be found'
3. I searched in the logs for the specific reason and I found:
   - system.log (/var/log) :
      myMacBook kernel[0]: disk0s2: I/O error.
      myMacBook /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[198]: NetworkNode::handleMountCallBack returned -6602 (the same error)
      myMacBook ReportCrash[358]: Saved crashreport to /Library/Logs/CrashReporter/kextload_2012-12-30-112946_myMacBook.crash using uid: 0 gid: 0, euid: 0 egid: 0
   - In CrashReporter (/Library/Logs/CrashReporter/): i see the problem coming from kextload with this exception:
       Exception Type: EXC_BAD_ACCESS (SIGBUS)
       Exception Codes: 0x000000000000000a, 0x000000000122d000
4. I tried to mount the time capsule disk with Terminal (AFP protocol):
   > mount -t afp afp://admin:[email protected]/Data /Volumes/termAFPData/
   result -> mount_afp: AFPMountURL returned error 19, errno is 19
These errors (6602 and 19) are neither documented anywhere nor associated to a clear description of the problem. The only thing I have found is that errno 19 is an IO error -> http://www.opensource.apple.com/source/CarbonHeaders/CarbonHeaders-18.1/MacError s.h
On the other hand, and this is the really weird part of the issue, my time capsule disk works well when I mount it with SMB protocol !!! (Or when I access it with a Windows XP machine).
So, the workaround is: mount -t smbfs //admin:[email protected]/Data /Volumes/termSMBData/
Or, in Finder -> Connect to server and there use the URL: smb://xxx.xxx.xxx.xxx/Data
Not sure what is going on ... but I pretty sure that's a bug and not a hardware problem.
Is there someone who has already found a solution for this kind of behaviour ?
It would avoid me a lot of headaches and improve the support for this kind of problem.
Thanks !!!
Greetz
A Belgian boy

JoBidun wrote:
Thanks a lot for this really quick reply.
When you say: "I would though go back to 7.5.2 firmware." Do you mean a reset to factory default ?
Greetz
NO, your time capsule is running 7.6.1 but it is built with AFP following increased security for LION.. that is not required or available in Leopard.. so there is no point.. it is also not as stable on the older hardware.. at least in my experience.. I have repaired about 200 of the suckers so I do see a few.
When you select firmware update in the airport utility.. hold the option key.. all valid firmware versions for your TC then show up.. not only upgrades.. select 7.5.2 and upgrade to that.
Do a factory reset when you do it is a good idea though.. start off again.
And do reset of TM.. A4 in pondini.
See if it helps.
Oh, the TC will continually complain about needing a firmware update.. turn off automatic checking of updates.. it will still annoy you for fun every few weeks but that is better than daily.

Funny bugs with Time Machine connecting to MacBook when reboot

Found a bug for Time Machine.
Reboot with TM disk connect to the MacBook. Most of the time, there will be no show of TM Disk on the desktop and connect thumb drives will not detect too. And do a normal shutdown, I can still feel the warm air venting out from the MacBook.
Have to remove the battery for a few seconds, replace it back and power up. Then everything will back to normal. If reboot with thumb drive connect, such symptoms will not appear.

dilagan wrote:
i attempted to backup the imac with time machine to an external hard drive, it began backing up, stopped and I got the same error message: "time machine error unable to complete backup an error occurred while copying files." Little help!
Yes, that message is not some of Apple's best work.
Most likely, there's a damaged/corrupted file that Time Machine is choking on. See #C3 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're getting a different message from the Pro, see #C2.

Time Capsule disk cannot be mounted nor found by Time Machine

Suddenly Time Machine can't find my Time Capsule disk to back up to.
I've tried setting up my Time Capsule in various ways, even resetting to default factory settings.
My network seems to work fine and Time Capsule is shining brightly green, but clicking on Time Machine Preferences, it asks me to Choose Backup Disk. Clicking on that I just get an empty list. No disks. My only choice is to Set Up Time Capsule, which I've now done a couple of times without change. The Apple Support suggest a change to a shorter name... Needless to say, this is not the problem. Tried that too.
When I click on Manual Setup and check the Disks tab, there are no disks available there either.
Patience running on empty... Anyone found a solution to this or is my only option to shut off this expensive machine forever (seeing as it doesn't back up and that it's started to hum annoyingly loudly)?
Any help at all would be greatly appreciated! Thanks!

My last resort was to connect my laptop and the time capsule with an usb cable.
The bad thing is that nothing happened. So for me this means heading back again to apple care so they tell me whats wrong with it (i just received it today from apple care because it stopped turning on 2 weeks ago and they didn't knew what was wrong with it).

MAJOR TM Bug found in 10.6.1! Time Machine corrupts HFS+ Filesystem! Raid 0

Similar Messages

Maybe you are looking for