Time machine causing inaccurate disc space readout
Hi,
there's clearly a bug with relation to time machine as my hard drive disc space readout is continuously giving ridiculous readouts (and this changes as time machine is doing its thing)
Currently it says i have 2 petabytes free! on my 500gb SSD (I wish!). Turning time machine off and on again gives me back the correct reading. But it doesn't last for long (well until the next time machine backup).
Is there any way to fix this? or is there any was we can notify Apple of this bug, as its quite annoying not knowing how much free space I have left
thanks guys!
N
don't think ill be switching OS in a hurry!
I meant rather using a reliable version of OS X.. eg your profile version.. Mountain Lion.. works pretty well for me!!
Not as good as Snow Leopard but OK..
I would do a CC to the time capsule, but I've read somewhere thats its not totally recommended to copy any other files to the TC data disc if you're running a time machine as well. Do you have any thoughts on this?
You can do CCC to a sparsebundle.. that is identical to the way Time Machine works..
In fact using sparsebundle on a network disk is the recommended method for CCC.. and it can co-exist very happily with TM..
The reference to not mixing data and TM backups is more to do with placing files directly on the data partition of the TC.. And is still good advice.. although there are workarounds.
I would however do at least one CCC backup to a USB drive plugged into your computer.. called a bootable clone. You do not need to do this on a regular basis.. but even just having one proper bootable clone.. alongside the network backups will allow you to restore your computer to operational status in about 2 min.. the time it takes to boot the bootable clone.
Macs are difficult to get to boot over network.. that is why it needs to be a local disk.
Similar Messages
-
Does backing up my hard drive to time machine gain me more space/speed on my iMac?
I have an iMac. here are the specs:
Hardware Overview:
Model Name: iMac
Model Identifier: iMac8,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.8 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 6 MB
Memory: 4 GB
Bus Speed: 1.07 GHz
Boot ROM Version: IM81.00C1.B00
SMC Version (system): 1.30f1
Serial Number (system): QP921090ZE4
Hardware UUID: 20AE2D9A-DB71-54DF-95F7-DAEFEE167723
I have a TON of art/photos on this computer. I'm wondering if backing my hard drive up with time machine gains me more space and processing speed-or if it only slows my computer down? is it better to house my files on a seperate drive from the drive i am using for backing up with time machine?Just to add a little, Time Machine is not a storage drive. Backups on there are not in a form you can use as you would from your normal internal. If you delete your pics etc. after backup, they won't be backed up on subsequent runs, and will eventually be lost when the TM drive gets near full and starts deleting the oldest backups. Have a read of Pondini's TM articles; http://pondini.org/TM/Home.html
To do what you want, you need another drive to which you can simply copy your pics etc and open from there while booted to your internal. (this is a basic storage drive)
The storage drive can then also be backed up to TM (provided the TM disc is big enough). -
How to restore from Time Machine WITHOUT install discs using a second Mac
It's a question that is asked repeatedly all over the web by Mac users like me that bought in to Time Machine (TM) on the assumption that if their computer died one day it would be a piece of cake to restore from it, only for that day to come and then to be told "ahh, okay the first thing is to get your computers install discs..." (loud crashing sound of world falling around ears).
I've never been able to afford a new Mac and both of my machines were bought second-hand. Neither came with Leopard (both have Tiger and have been upgraded to Leopard via the net). This was never supposed to be a problem as I've been backing up with TM. However it appears that Tiger discs are as much use as an inflatable dart board when it comes to using TM. So I've been faced with the possibility of having to spend £130 (about two hundred Pres Sheets, Yankees) on the Leopard install discs just so that I can have the option of restoring from TM. Bonkers.
However after much nashing of teeth, a very long weekend learning all sorts of things about 'Target Mode', 'Single User Mode', 'Verbose Mode', 'Open Source 9' etc the following solution has worked without the need to go out and buy those over-priced discs...
What you will need:
1 broken Mac requiring restoration
1 second donor Mac running Leopard (or Snow Leopard so long as the broken Mac can run it)
1 firewire cable with the correct fitting at either end to attach both Macs together
1 Time Machine backup
Note: The following is for when you have given up trying to boot from your hard drive. In my case I couldn't boot in to Safe Mode etc. so was forced to format my drive and re-import everything. If you've read this far I'm assuming your at the same point as well and have tried everything else that's out there first.
Also - both my Macs are Power PC's so can't run Snow Leopard, so I can't say 100% this will work with SL (Intel) machines. From what I've read Snow Leopard will work with this procedure too, but if you've found differently please feel free to add your experiences below...
STEP ONE: Format the corrupt Hard Drive or replace with a fresh HDD
*Link the two computers with a firewire.
*If you're replacing your HDD, remove your corrupted hard drive from the 'broken' machine and insert a new one.
*Power up the broken Mac whilst holding down the 'T' key. This will start it up in Target Mode and you'll get a nice firewire symbol floating around that machine's screen.
*Power up the second 'healthy' Mac. This will be our 'donor' machine. When it starts up after a few seconds you will see the hard drive of the broken Mac appear on the donor Mac's desktop.
*Using your donor Mac's 'Disc Utility', format the broken Mac's hard drive (now's the time to partition it etc. if you want to).
STEP TWO: Clone your donor Mac
Your broken Mac is no longer broken and now needs a new OS. But you don't have the discs, right? Well get this... you can clone your donor mac on to your machine, even if they are totally different i.e. a laptop on to a tower.
*Again using Disc Utility, click on your donor Mac's hard drive. The restore tab appears as an option.
*Click on restore and drag the donor Mac's hard drive that contains the operating system in to the Source box.
*Drag the newly formatted hard drive on the broken Mac in to the Destination box.
*Click restore. Your donor Mac's hard drive will now be 'cloned' on to your no-longer-broken Mac. Once this is done, eject the first Mac's hard drive from your donor Mac's desktop. You no longer need the donor Mac.
Ta daa! Your machine now starts up happy and smily again. Time to restore all that stuff that's been sat on your Time Machine drive...
STEP 3: Restore from Time Machine using Migration Assistant
This is the really clever part that prompted me to write this piece in the first place. Time Machine IS accessible without those Leopard install discs you don't have. You need to use something called 'Migration Assistant'.
*Start up your machine as normal and you'll see it is an exact clone of the donor machine. Weird huh?
*Attach your Time Machine hard drive. It will show up as an icon on the desktop and because of it's size, you'll be asked if you want to use it as a Time Machine backup. Err, NO YOU DON'T! Click 'cancel'.
*Open Migration Assistant (if you can't find it just type it in to Finder and click). There are three options, the middle one being to restore from TM or another disc. Yup, you want that one.
*Migration Assistant will now ask you what you want to restore in stages, firstly User Accounts, then folders, Apps etc. It will even import internet settings
And that's you done. Let Migration Assistant do it's thang... altogether I had about 140gb to restore, so it wasn't exactly speedy. This wasn't helped by the fact that my TM hard drive is connected via USB (yes, I know). Just leave it alone and it'll whirr happily away...
Before I go - you don't have an option of when to restore from, and will restore from the last Time Machine save. At least then you should be able to access TM and go 'backwards' if you need to.
Also - for a Mac expert, the above will be up there with 'Spot Goes To The Farm' in terms of complexity. However, for the rest of us the above is only available in fragments all over the net. By far the most common response to 'how do I restore from Time Machine without install discs' is 'you can't'. If I'd found the above information in one place I could have saved a lot of hair pulling and swearing over the last couple of days, so forgive me for sharing this workaround with the rest of the world. Meanwhile your expertise will come in very handy for the inevitable questions that will get posted below, so please feel free to help those people that won't be sure if this solution is the right one for them. I'm no expert, I just want to help people that were stuck in the same situation (and looking at the web, there's a LOT of them).
Hope this is of use to someone, thanks and *good luck*!Most maintenance and repair, restore and install procedures require the use
of the correct OS X install DVD; be it an original machine-specific restore/install
disc set or a later retail non-specific general install disc set.
By having an unsupported system, perhaps installed via an illegal download or
other file-sharing scheme, where no retail official discs are involved and the
initial upgrade was done by other means outside of the License Agreements,
you are asking us to discuss a matter of illegal installation and use of a product.
There are no legal complete OS X system download upgrades online; only bits
that are update segments to a retail or as-shipped machine's original OS X install.
+{Or an installation where a previous owner had correct retail upgrade discs, &+
+chose to not include them with the re-sale of the computer it was installed in.}+
However, to answer the initial question. To get and use an externally enclosed
hard drive in suitable boot-capable housing, and get a free-running Clone
Utility (download online; often a donation-ware product, runs free) you can
make a bootable backup of everything in your computer to an external HDD.
This is the way to make a complete backup to restore all functions to the computer.
The Time Machine has some limits, in that it can restore only that which it saves.
It does not make a bootable clone of your entire computer system with apps and
your files, to an external drive device. A clone can. And some of the clone utility's
settings can also backup changes to an external drive's system; if that other drive
is attached to the computer correctly.
Carbon Copy Cloner, from Bombich Software; and also SuperDuper, another of
the most known software names you can download and use to clone boot-capable
system backups of your computer's hard disk drive contents, are often cited.
However you resolve the matter of the running OS X system in your computer,
derived from what appears to be questionable means, is part of the initial issue.
Since you do need to be able to fix an existing installation by unmounting the
computer's hard disk drive and run the computer from the other (install disc or
system clone) while it is Unmounted; and use the correct Disk Utility version to
help diagnose and perhaps be able to fix it. You can't use a Tiger version Disk
Utility to fix a Leopard installation, and so on.
So, the situation and replies as far as they can go (since the matter does
constitute an illegal system, if it was arrived at without correct discs) is a
limited one. And file sharing of copied Mac OS X (and other) software is
also considered illegal.
And, one way to get odd malware and unusual stuff, is to get an unauthorized
system upgrade from an illegal source online. You never know what's inside it.
The other reply was not a personal attack; the matter is of legal status and as
you have a product with a questionable system, the answer is to correct it.
And if you want to save everything in your computer, make a clone to a suitable
externally enclosed self-powered boot capable hard disk drive. With older PPC
Macs, that would best be to one with FireWire and the Oxford-type control chips.
However that works out...
Good luck & happy computing! -
Time Machine causes screen to go blank when starting backup
Time machine causes screen to go blank when it starts backup. I have cable wireless modem with ethernet to time machine; then ethernet to computer. Cable company just increased speed to 30. What may be happening? I am afraid of losing all my data. Screen recovers within one second, but it goes completely blank when time machine starts backup
Time machine causes screen to go blank when it starts backup. I have cable wireless modem with ethernet to time machine; then ethernet to computer. Cable company just increased speed to 30. What may be happening? I am afraid of losing all my data. Screen recovers within one second, but it goes completely blank when time machine starts backup
-
Due to NAS issues, when I started a new time machine backup it did not have the old backups available. My question is do I need to delete them or will time machine automatically reclaim the space? There is only one sparse bundle but when I enter time machine I don't see my historic backups. I use a synology DS212 for my time machine. Started a new backup which is 218gb but it says 618 gb is occupied therefore it looks like 2 or 3 backups are still on the disk. Before my NAS issues the last backup was in 2014. As you can see there is a second sparse bundle from 2012. Not sure what that is.
This is an old message now, but what happened to me similarly was:
I had a major computer crash and through complicated pathways ended up reinstalling (Mavericks) as a new user (long story).
At least I had good Time Machine backups on an NAS drive (Synology DS212j), or so I thought - when I started Time Machine up again, the old backup file was gone, replaced by a new one using my "new computer" name. The old file was gone both by directly mounting the NAS drive and by clicking "Enter Time Machine".
It's like I had {OldShareName}.sparsebundle and then it was replaced by {NewShareName}.sparsebundle, all of the old info vanished.
(I have spent a week finding old files elsewhere and have completed a satisfactory self-restore. It pays to "archive" [my own variation of] as well as "back-up".)
My belief is that if this were a wired-netword-drive, e.g. plugged right into my iMac with a USB cable, then the old file would have remained.
But this is an NAS drive, connected directly to my Airport wireless router, and I don't know the significance of the fact that it stores its Time Machine backups as "sparsebundle" files rather than simply as plain(er) files.
As usual when things get complicated with computers (not just Apple computers) there was never a warning message. Something like "YOU'RE ABOUT TO DELETE A TIME MACHINE BACK-UP FILE!!!" would have made my life a lot simpler.
BTW, I did try a "restore from Time Machine" option the first thing I had my "new computer" (old hardware, 2009 iMac) up and running, using Migration Assistant, and it ran for many hours and then failed in the wee hours - what that has to do with anything I'm not sure.
I'm not sure that I have a question about this other than "why do these things happen to me?", but it's a warning. Apart from that I've been very happy with the stability and reliability (but not the cost or set-up complexity) of NAS vs. directly-cabled external drives.
Charles -
Time machine causes error message " Disk not properly ejected" with USB backup drive
I am using iMac OS X Lion and Time Machine causes the error message with a WD 1.5 TB drive in aThermaltake dock, USB. every time I wake up the computer.... Ejection of Time Machine and shut it down and turn opp power to drive causes the error message problem to disappear. What is the solutin?
If it were mine I would replace the drive with another brand. WD drives EHD's tend to have more issues than any other EHD. If you want to continue using it you can try resetting the SMC (may take 2-3 tries) and/or restarting in Safe Mode to reset some caches, it's possible one or more has become corrupt.
SMC RESET
Shut down the computer.
Unplug the computer's power cord and all peripherals.
Press and hold the power button for 5 seconds.
Release the power button.
Attach the computers power cable.
Press the power button to turn on the computer.
PRAM RESET
Shut down the computer.
Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
Turn on the computer.
Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the second time.
Release the keys. -
how do i reset my mac completely? I have parental controls and cant seem to get to time machine cause i bought the computer with parental controls on it and they did not have the password. How do i completely reset my macbook pro?
If you have a rescue email address (which is not the same thing as an alternate email address) on your account then the steps on this page will give you a reset link on your account : http://support.apple.com/kb/HT6170
If you don't have a rescue email address (you won't be able to add one until you can answer your questions) then you will need to contact Support in your country to get the questions reset.
Contacting Apple about account security : http://support.apple.com/kb/HT5699
When they've been reset (and if you don't already have a rescue email address) you can then use the steps on this page to add a rescue email address for potential future use : http://support.apple.com/kb/HT5620
Or, if it's available in your country, you could change to 2-step verification : http://support.apple.com/kb/HT5570 -
What items do you delete from backup on time machine to make more space available
What items do you delete from back up on time machine to make more space?
There's no need to do that unless Time Machine has reported a Disk Full alert. In this case you can:
1. Delete older entries using the Time Machine application to free up sufficient space.
2. Get a new and larger Time Machine backup drive to replace the old one.
3. Erase the backup drive and start over. -
I am having problems with Time Machine and having enough space to finish my last back up.
I am having problems with Time Machine and having enough space to finish my last back up.
Take a look at this link, http://support.apple.com/kb/HT1427
-
Thought I'd do a TM backup before installing Mavericks. It messed up big time!
I backup manually depending on how much stuff has accumulated. It varies between a few Mb to 3 or 4 Gb sometimes more. Today Time Machine decided that it wanted to reorganise the backup in some way. I watched as the available space on the TM disk went up as TM set about the task. After a couple or three hours TM actually started to do the backup. The size of the backup being 500Gb or something like that. Several hours later of listening to my fans working flat out I cancelled the back up with TM reporting that there was 200 odd Gb to go. No warning from TM to say this was a bad idea. It had been chuntering away for something like 5 hours.
After halting the backup I thought I'd start the backup again just to see how much more needed to be done. This is when I got the report that the backup disk needed to be in the order of Tb. And the oldest backup is now Nov 2013. The oldest backup before this was way back in June 2012 (MacBookPro Rertina mid 2012) when I first bought the computer.
Entering TM I find that even that is not complete. All but a couple of applications have dissapeared as have many other files.
Trouble is I use it as an archive and happily delete files on my hard drive knowing that there is a copy in a backup that pre dates the deletion.
There is also an earlier backup from my previous machine - again as a rarely accessed archive. So that's another reason not to reformat.
I'm pretty sure all is lost and I think I just have to bite the bullet and risk not needing anything from the archive. After all I have CD and DVD backups/archives that go back to the late '90s and I have rarely needed to access them over the years. The biggest loss will be photos. ****!
Anyway. What happened? Why has TM gone off the rails? I have done nothing different to what I have done in 5 years or so. Is this normal behaviour? If I hadn't have cancelled the back up would TM have slowly rebuilt all my backups as was?
AndyTrouble is I use it as an archive and happily delete files on my hard drive knowing that there is a copy in a backup that pre dates the deletion.
Before going any further please understand that's a very bad idea. It's beyond Time Machine's scope to do that. It is not an archival system and cannot be made to become one. Time Machine guarantees nothing other than one complete copy of the source volume's contents. Anything erased from the source becomes fair game for Time Machine to delete from the backup, the moment it requires the space it occupies.
Next: I have no idea why the problem occurred, but a first and harmless troubleshooting step is to reset Time Machine by doing the following:
Turn off Time Machine first, and make sure a backup is not in progress.
Triple click to select the entire line, then control-click and select Services > Reveal in Finder. Drag the selected file to the Desktop, or directly to the Trash:
/Library/Preferences/com.apple.TimeMachine.plist
This will not delete your existing backups.
Turn on Time Machine and reselect your backup volume. The effect of deleting that file will cause erroneous values to be shown in the "backing up xxx of yyy" messages until the subsequent backup.
If it's any consolation, terminating Time Machine as you did is not an abnormal user action and did not cause the problem. It may have resulted in inaccurate information being written to the property list, which you will fix by deleting it. It's quite possible that your backups have remained intact. Just remember that anything you delete from the source may no longer exist following the subsequent backup, and that is to be expected. -
Time Machine has no more space
I just received a notice that the hard drive I am using for my Time Machine backup has no more room. I am wondering how I go about making more room on the hard disc. I don't really want to go out an get a new one. If this isn't an option, how do I go about replacing the one I have?
As your backup drive begins to fill up to its capacity, Time Machine intelligently deletes the oldest backups to make room for newer ones (and will alert you if the "Notify after old backups are deleted" option is selected in Time Machine preferences).
If your backup disk is filling up often causing your oldest available backups to be erased sooner than you might want, consider the following options:
Use an additional drives for your backups or transfer your backups to a new, larger drive as detailed above. When you connect a new drive for the first time, use Time Machine preferences to select the drive. Tip: You can also browse the original backup drive for past backups by using "Browse other Time Machine Disks"--to see this choice, hold the Option key then click the Time Machine menu in the Finder (to see the menu, "Show Time Machine status in the menu bar" must be selected in Time Machine preferences.
Reduce the amount of information being backed up by adding to the "Exclude these items from backups" list in Time Machine preferences, as mentioned above. Your backup drive will fill up less often.
Delete file(s) that are no longer needed (such as from your desktop, Documents folder, or other Home folder locations), so they will no longer be backed up. You can also enter the Time Machine restore interface and find files that can be removed from the backup drive itself to conserve space. To do this, select the file(s) and from the Action pop-up menu (gear icon) in the Time Machine Finder window choose "Delete All Backups of...". Be sure to only delete files you are sure you won't need or want to restore later. -
Time Machine Eats All Available Space
I have a new iMac 20 inch, using a WD "My Book" 1 TB drive. Setting up time machine, it uses all the drive space until error for "out of space". I have 300G of space used on the iMac hard drive, and it seems to do the math correctly on how much to back up and how long that will take. But, after the little bar fills up for the back up it keeps going, counting up the space on the external drive while saying 5 seconds left, and eventually it fills up the drive backing up 300G and writing it out as 980 G.
Any ideas on what causes this behavior? I've removed all the files from the WD external, and used disk utility to make sure there's no structure problems on the external drive. Support pages have no information on this - I've gone through the troubleshooting pages already.
(By the way, the new support community seems to encourage cryptic new discussion titles, since the new discussion box seems to be the search box).This does not seem to be going as expected. I was expecting some diagnostic information, but only the start messages are found:
7/31/12 10:59:31.946 AM com.apple.backupd: Starting standard backup
7/31/12 12:05:02.241 PM com.apple.backupd: Starting standard backup
8/1/12 11:53:09.078 PM com.apple.backupd: Starting standard backup
8/3/12 8:23:39.145 PM com.apple.backupd: Starting standard backup
8/3/12 9:12:28.782 PM com.apple.backupd: Starting standard backup
8/3/12 9:21:40.058 PM com.apple.backupd: Starting standard backup
8/3/12 9:53:31.635 PM com.apple.backupd: Starting standard backup
8/3/12 10:21:39.904 PM com.apple.backupd: Starting standard backup
8/3/12 11:21:39.757 PM com.apple.backupd: Starting standard backup
8/4/12 12:21:39.784 AM com.apple.backupd: Starting standard backup
8/4/12 12:28:34.961 AM com.apple.backupd: Starting standard backup
8/4/12 10:45:41.842 AM com.apple.backupd: Starting standard backup
8/4/12 10:49:19.440 AM com.apple.backupd: Starting standard backup
8/4/12 11:49:20.858 AM com.apple.backupd: Starting standard backup
8/4/12 1:49:21.543 PM com.apple.backupd: Starting standard backup
8/4/12 6:36:37.970 PM com.apple.backupd: Starting standard backup
8/4/12 7:07:36.653 PM com.apple.backupd: Starting standard backup
8/4/12 7:30:44.526 PM com.apple.backupd: Starting standard backup
8/5/12 12:29:00.781 AM com.apple.backupd: Starting standard backup
8/5/12 3:29:15.922 PM com.apple.backupd: Starting standard backup
8/5/12 4:05:54.646 PM com.apple.backupd: Starting standard backup
8/6/12 12:19:10.956 AM com.apple.backupd: Starting standard backup
I think the problem might be related to how migration assistant copied over programs from my older computer (an iMac G5), which contained a Western Digital utility of some kind that seems to be crashing, if I'm interpreting this right. Maybe there was some software upgrade I should have done? But, the drive mounts and I've been able to read and write to it:
Process: WDDriveManagerStatusMenu [474]
Path: /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/MacOS/WDDriveManage rStatusMenu
Identifier: com.wdc.drivemgrstatusmenu
Version: 1.0.5 (1.0.5)
Code Type: X86 (Native)
Parent Process: launchd [374]
Date/Time: 2012-08-06 00:29:07.855 -0400
OS Version: Mac OS X 10.7.4 (11E53)
Report Version: 9
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000010
VM Regions Near 0x10:
--> __PAGEZERO 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/MacOS/WDDriveManage rStatusMenu
__TEXT 0000000000001000-000000000012f000 [ 1208K] r-x/rwx SM=COW /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/MacOS/WDDriveManage rStatusMenu
Application Specific Information:
objc[474]: garbage collection is OFF
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x995dcc22 (anonymous namespace)::AutoreleasePoolPage::pop(void*) + 350
1 com.apple.CoreFoundation 0x965dde05 _CFAutoreleasePoolPop + 53
2 com.apple.Foundation 0x906f2a2f -[NSAutoreleasePool release] + 131
3 Framework76b.rbx_10.dylib 0x01e7e872 0x1e7a000 + 18546
4 com.apple.HIToolbox 0x9a786ee1 TimerVector + 22
5 com.apple.CoreFoundation 0x966072a6 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 22
6 com.apple.CoreFoundation 0x96606c37 __CFRunLoopDoTimer + 743
7 com.apple.CoreFoundation 0x965e5cd0 __CFRunLoopRun + 1888
8 com.apple.CoreFoundation 0x965e51dc CFRunLoopRunSpecific + 332
9 com.apple.CoreFoundation 0x965e5088 CFRunLoopRunInMode + 120
10 com.apple.HIToolbox 0x9a76b723 RunCurrentEventLoopInMode + 318
11 com.apple.HIToolbox 0x9a772a8b ReceiveNextEventCommon + 381
12 com.apple.HIToolbox 0x9a908af0 ReceiveNextEventInMode + 67
13 com.apple.HIToolbox 0x9a908b88 ReceiveNextEvent + 72
14 rbframework.dylib 0x0026db82 SetFocusPane(SubPane*) + 458
15 rbframework.dylib 0x0026de89 EventPump(unsigned char) + 435
16 rbframework.dylib 0x0026ed55 UpdateMouseCursor() + 555
17 rbframework.dylib 0x0026e265 IsAppShuttingDown() + 53
18 rbframework.dylib 0x0026e2ea CallFunctionWithExceptionHandling(void (*)()) + 14
19 rbframework.dylib 0x0026e90a mainloop() + 118
20 rbframework.dylib 0x0021d203 RuntimeRun + 47
21 com.wdc.drivemgrstatusmenu 0x000024ea REALbasic._RuntimeRun + 34
22 com.wdc.drivemgrstatusmenu 0x000017f4 _Main + 73
23 com.wdc.drivemgrstatusmenu 0x000014c8 % main + 36
24 com.wdc.drivemgrstatusmenu 0x0010fdfc _start + 116
25 com.wdc.drivemgrstatusmenu 0x0010fd52 start + 43
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x95d9f90a kevent + 10
1 libdispatch.dylib 0x92780e10 _dispatch_mgr_invoke + 969
2 libdispatch.dylib 0x9277f85f _dispatch_mgr_thread + 53
Thread 2:
0 libsystem_kernel.dylib 0x95d9f02e __workq_kernreturn + 10
1 libsystem_c.dylib 0x93418ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x9341a6fe start_wqthread + 30
Thread 3:
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x028a2028 ebx: 0x01e7e856 ecx: 0x028a2028 edx: 0x00000000
edi: 0x028a2000 esi: 0x00000000 ebp: 0xbfffe9a8 esp: 0xbfffe770
ss: 0x00000023 efl: 0x00010246 eip: 0x995dcc22 cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0x00000010
Logical CPU: 1
Binary Images:
0x1000 - 0x12e259 +com.wdc.drivemgrstatusmenu (1.0.5 - 1.0.5) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/MacOS/WDDriveManage rStatusMenu
0x1a8000 - 0x37affa +rbframework.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/MacOS/rbframework.d ylib
0x7f4000 - 0x7f5ff1 com.apple.textencoding.unicode (2.4 - 2.4) <4E55D4B9-4E67-3FC9-9407-3E99D1D50F15> /System/Library/TextEncodings/Unicode Encodings.bundle/Contents/MacOS/Unicode Encodings
0x1e6f000 - 0x1e74fff +Framework76b.rbx_10.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76b.rbx_10.dylib
0x1e7a000 - 0x1e7ffff +Framework76b.rbx_10.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76b.rbx_10.dylib
0x1e85000 - 0x1e88fff +Framework76b.rbx_5.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76b.rbx_5.dylib
0x1e8d000 - 0x1e90fff +Framework76b.rbx_5.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76b.rbx_5.dylib
0x1e95000 - 0x1e9dfff +Framework76b.rbx_6.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76b.rbx_6.dylib
0x1ea3000 - 0x1eabfff +Framework76b.rbx_6.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76b.rbx_6.dylib
0x1eb1000 - 0x1ebdff3 +Framework76n.rbx_19.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76n.rbx_19.dylib
0x1ec7000 - 0x1ed3ff3 +Framework76n.rbx_19.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76n.rbx_19.dylib
0x1edd000 - 0x1ee3ff3 +Framework76n.rbx_31.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76n.rbx_31.dylib
0x1ee9000 - 0x1eefff3 +Framework76n.rbx_31.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76n.rbx_31.dylib
0x1ef5000 - 0x1ef6ff7 +Framework76o.rbx_1.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76o.rbx_1.dylib
0x1efa000 - 0x1efbff7 +Framework76o.rbx_1.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76o.rbx_1.dylib
0x2000000 - 0x2003fe3 +Framework76o.rbx_23.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76o.rbx_23.dylib
0x2007000 - 0x200afe3 +Framework76o.rbx_23.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76o.rbx_23.dylib
0x200e000 - 0x2013ff7 +Framework76o.rbx_41.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76o.rbx_41.dylib
0x2017000 - 0x201cff7 +Framework76o.rbx_41.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76o.rbx_41.dylib
0x2053000 - 0x2058fff +Framework76t.rbx_4.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76t.rbx_4.dylib
0x205c000 - 0x2061fff +Framework76t.rbx_4.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76t.rbx_4.dylib
0x2065000 - 0x2067ff3 +Framework76t.rbx_6.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76t.rbx_6.dylib
0x206b000 - 0x206dff3 +Framework76t.rbx_6.dylib (??? - ???) /Users/USER/Desktop/*/WDDriveManagerStatusMenu.app/Contents/Frameworks/Framewor k76t.rbx_6.dylib
0x8fe6e000 - 0x8fea0aa7 dyld (195.6 - ???) <3A866A34-4CDD-35A4-B26E-F145B05F3644> /usr/lib/dyld
0x900a6000 - 0x900aeff3 libunwind.dylib (30.0.0 - compatibility 1.0.0) <E8DA8CEC-12D6-3C8D-B2E2-5D567C8F3CB5> /usr/lib/system/libunwind.dylib
0x900af000 - 0x904b1ff6 libLAPACK.dylib (??? - ???) <00BE0221-8564-3F87-9F6B-8A910CF2F141> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
0x904b2000 - 0x904c6fff com.apple.CFOpenDirectory (10.7 - 146) <9149C1FE-865E-3A8D-B9D9-547384F553C8> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpen Directory.framework/Versions/A/CFOpenDirectory
0x904c7000 - 0x905d6fff com.apple.DesktopServices (1.6.3 - 1.6.3) <18CAAA9E-7065-3FF7-ACFE-CDB60E5426A2> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x905d7000 - 0x905ecfff com.apple.speech.synthesis.framework (4.0.74 - 4.0.74) <92AADDB0-BADF-3B00-8941-B8390EDC931B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x905ed000 - 0x90603ffe libxpc.dylib (77.19.0 - compatibility 1.0.0) <0585AA94-F4FD-32C1-B586-22E7184B781A> /usr/lib/system/libxpc.dylib
0x906e9000 - 0x909f3ff3 com.apple.Foundation (6.7.2 - 833.25) <4C52ED74-A1FD-3087-A2E1-035AB3CF9610> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x90a63000 - 0x90a74fff libbsm.0.dylib (??? - ???) <54ACF696-87C6-3652-808A-17BE7275C230> /usr/lib/libbsm.0.dylib
0x91107000 - 0x9110bff3 libsystem_network.dylib (??? - ???) <62EBADDA-FC72-3275-AAB3-5EDD949FEFAF> /usr/lib/system/libsystem_network.dylib
0x9110c000 - 0x9112ffff com.apple.CoreVideo (1.7 - 70.3) <4234C11C-E8E9-309A-9465-27D6D7458895> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
0x91190000 - 0x91190fff libdnsinfo.dylib (395.11.0 - compatibility 1.0.0) <7EFAD88C-AFBC-3D48-BE14-60B8EACC68D7> /usr/lib/system/libdnsinfo.dylib
0x91191000 - 0x911abfff com.apple.Kerberos (1.0 - 1) <D7920A1C-FEC4-3460-8DD0-D02491578CBB> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
0x911ac000 - 0x911b5ff3 com.apple.CommonAuth (2.2 - 2.0) <C3FD6EC2-8EB3-38FB-BBB7-05009CA49024> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
0x911c1000 - 0x911efff7 com.apple.DictionaryServices (1.2.1 - 158.2) <DA16A8B2-F359-345A-BAF7-8E6A5A0741A1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x911f0000 - 0x91215ff9 libJPEG.dylib (??? - ???) <743578F6-8C0C-39CC-9F15-3A01E1616EAE> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x9134e000 - 0x913a7fff com.apple.HIServices (1.21 - ???) <5F4D3797-32E2-3709-85F4-4B56515A17D7> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
0x913a8000 - 0x9150affb com.apple.QuartzCore (1.7 - 270.4) <6BC84C60-1003-3008-ABE4-779EF7B4F524> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x9150b000 - 0x9150bff2 com.apple.CoreServices (53 - 53) <7CB7AA95-D5A7-366A-BB8A-035AA9E582F8> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x9150c000 - 0x916c0ff3 libicucore.A.dylib (46.1.0 - compatibility 1.0.0) <6AD14A51-AEA8-3732-B07B-DEA37577E13A> /usr/lib/libicucore.A.dylib
0x916c7000 - 0x917bfff7 libFontParser.dylib (??? - ???) <1A0DA421-62B2-3AA7-9F62-0E01C1887D09> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontParser.dylib
0x917c0000 - 0x91912fff com.apple.audio.toolbox.AudioToolbox (1.7.2 - 1.7.2) <E369AC9E-F548-3DF6-B320-9D09E486070E> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x91a2b000 - 0x91a30ffd libGFXShared.dylib (??? - ???) <1CA9B41B-2C61-38F8-ABAC-1D5511478F5C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.d ylib
0x91ad4000 - 0x91ad5ff4 libremovefile.dylib (21.1.0 - compatibility 1.0.0) <6DE3FDC7-0BE0-3791-B6F5-C15422A8AFB8> /usr/lib/system/libremovefile.dylib
0x91b43000 - 0x91b63ff7 com.apple.RemoteViewServices (1.4 - 44.1) <1F831750-1E77-3013-B1A6-0DF528623790> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/Remot eViewServices
0x91bc1000 - 0x91bc2fff libsystem_blocks.dylib (53.0.0 - compatibility 1.0.0) <B04592B1-0924-3422-82FF-976B339DF567> /usr/lib/system/libsystem_blocks.dylib
0x91bc5000 - 0x91c61fef com.apple.ink.framework (1.4 - 110) <1A3E2916-60C1-3AC1-86BF-202F6567B228> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
0x91c62000 - 0x91cabff7 libGLU.dylib (??? - ???) <5EE0B644-FAD6-3E3C-A380-9B0CDA0B6432> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x91cac000 - 0x91cd6ff1 com.apple.CoreServicesInternal (113.17 - 113.17) <41979516-2F26-3707-A6CA-7A95A1B0D963> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/Cor eServicesInternal
0x91cd7000 - 0x91d0efef com.apple.DebugSymbols (2.1 - 87) <EB951B78-31A5-379F-AFA1-B5C9A7BB3D23> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbol s
0x91d15000 - 0x91e26ff7 libJP2.dylib (??? - ???) <845C74F4-1074-3983-945F-EB669538CAA9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x91e27000 - 0x91e88ffb com.apple.audio.CoreAudio (4.0.2 - 4.0.2) <E617857C-D870-3E2D-BA13-3732DD1BC15E> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x91e89000 - 0x91e8dfff libGIF.dylib (??? - ???) <A6F1ACAE-7B9B-3B3F-A54A-ED4004EA1D85> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x91e8e000 - 0x91e8eff0 com.apple.ApplicationServices (41 - 41) <C48EF6B2-ABF9-35BD-A07A-A38EC0008294> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x92091000 - 0x92100fff com.apple.Heimdal (2.2 - 2.0) <2E1B8779-36D4-3C62-A67E-0034D77D7707> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
0x9277d000 - 0x9277dfff com.apple.Cocoa (6.6 - ???) <5FAFE73E-6AF5-3D09-9191-0BDC8C6875CB> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x9277e000 - 0x9278cfff libdispatch.dylib (187.9.0 - compatibility 1.0.0) <2F918480-12C8-3F22-9B1A-9B2D76F6F4F5> /usr/lib/system/libdispatch.dylib
0x9278d000 - 0x92814fff com.apple.print.framework.PrintCore (7.1 - 366.3) <EEC03CAB-7F79-3931-87FE-4DF0B767BF47> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
0x92815000 - 0x92820ffb com.apple.speech.recognition.framework (4.0.21 - 4.0.21) <A1764D2F-EB84-33DC-9ED5-CDA3B468FF3E> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x9282c000 - 0x928b9ff7 com.apple.CoreText (220.20.0 - ???) <0C3EDD4F-6112-353A-8A3A-8D630182C22A> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
0x928c5000 - 0x92940ffb com.apple.ApplicationServices.ATS (317.11.0 - ???) <42238C8B-C93F-3369-A500-EC0F10EB2C80> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
0x92941000 - 0x92956ff7 com.apple.ImageCapture (7.0.1 - 7.0.1) <1C8933A9-C7C6-36E9-9D8B-0EF08ACA3315> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
0x92957000 - 0x92993ffa libGLImage.dylib (??? - ???) <504E7865-571E-38B4-A84A-D7B513AC84F5> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
0x92ac8000 - 0x92b5eff7 com.apple.LaunchServices (480.33 - 480.33) <5A4BF529-391E-3987-940E-287ACE56078A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x92b88000 - 0x92d80ff7 com.apple.CoreData (104.1 - 358.14) <C1730963-F75D-3338-B65F-D50235538B28> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x92d81000 - 0x92e44fff com.apple.CoreServices.OSServices (478.46 - 478.46) <F2063FC8-2BE1-3B97-98AF-8796B0D4BE58> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x92f53000 - 0x92faeff3 com.apple.Symbolication (1.3 - 91) <4D12D2EC-5010-3958-A205-9A67E972C76A> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolicat ion
0x92fb3000 - 0x93040fe7 libvMisc.dylib (325.4.0 - compatibility 1.0.0) <F2A8BBA3-6431-3CED-8CD3-0953410B6F96> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
0x93041000 - 0x93045ffd IOSurface (??? - ???) <EDDBEE65-1EB8-33A7-9972-E361A3508234> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
0x933af000 - 0x933b9ff2 com.apple.audio.SoundManager (3.9.4.1 - 3.9.4.1) <2A089CE8-9760-3F0F-B77D-29A78940EA17> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
0x933ba000 - 0x93485fff libsystem_c.dylib (763.13.0 - compatibility 1.0.0) <52421B00-79C8-3727-94DE-62F6820B9C31> /usr/lib/system/libsystem_c.dylib
0x93486000 - 0x9348dff9 libsystem_dnssd.dylib (??? - ???) <D3A766FC-C409-3A57-ADE4-94B7688E1C7E> /usr/lib/system/libsystem_dnssd.dylib
0x935b6000 - 0x935b6ffe libkeymgr.dylib (23.0.0 - compatibility 1.0.0) <7F0E8EE2-9E8F-366F-9988-E2F119DB9A82> /usr/lib/system/libkeymgr.dylib
0x935b7000 - 0x93608ff9 com.apple.ScalableUserInterface (1.0 - 1) <3C39DF4D-5CAE-373A-BE08-8CD16E514337> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/ScalableU serInterface.framework/Versions/A/ScalableUserInterface
0x93609000 - 0x93649ff7 com.apple.NavigationServices (3.7 - 193) <16A8BCC8-7343-3A90-88B3-AAA334DF615F> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
0x9364a000 - 0x93673ffe com.apple.opencl (1.50.69 - 1.50.69) <2601993F-F3B3-3737-91AE-4A5795C52CD5> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
0x93983000 - 0x93987fff com.apple.CommonPanels (1.2.5 - 94) <EA47550D-7DAF-30D9-91DB-1FB594CC8522> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
0x93988000 - 0x939eaff3 libstdc++.6.dylib (52.0.0 - compatibility 7.0.0) <266CE9B3-526A-3C41-BA58-7AE66A3B15FD> /usr/lib/libstdc++.6.dylib
0x93a38000 - 0x93a88ff8 libTIFF.dylib (??? - ???) <4DC2025D-15E7-35CA-B7C5-9F73B26C8B53> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x944bb000 - 0x9455ffff com.apple.QD (3.40 - ???) <3881BEC6-0908-3073-BA44-346356E1CDF9> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
0x94560000 - 0x945eaffb com.apple.SearchKit (1.4.0 - 1.4.0) <CF074082-64AB-3A1F-831E-582DF1667827> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x945eb000 - 0x945ecff0 libunc.dylib (24.0.0 - compatibility 1.0.0) <2F4B35B2-706C-3383-AA86-DABA409FAE45> /usr/lib/system/libunc.dylib
0x94ce8000 - 0x94cebffb com.apple.help (1.3.2 - 42) <B1E6701C-7473-30B2-AB5A-AFC9A4823694> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
0x94f16000 - 0x9519bfe3 com.apple.QuickTime (7.7.1 - 2330) <060B6A47-FC15-3D38-8EFB-FCF38680510B> /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
0x9519c000 - 0x9519cfff com.apple.Accelerate.vecLib (3.7 - vecLib 3.7) <22997C20-BEB7-301D-86C5-5BFB3B06D212> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
0x9519d000 - 0x95201fff com.apple.framework.IOKit (2.0 - ???) <88D60E59-430D-35B8-B1E9-F5138301AEF9> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x95202000 - 0x9520afff com.apple.DiskArbitration (2.4.1 - 2.4.1) <28D5D8B5-14E8-3DA1-9085-B9BC96835ACF> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x9520b000 - 0x952eeff7 libcrypto.0.9.8.dylib (44.0.0 - compatibility 0.9.8) <BD913D3B-388D-33AE-AA5E-4810C743C28F> /usr/lib/libcrypto.0.9.8.dylib
0x95698000 - 0x956a8fff com.apple.LangAnalysis (1.7.0 - 1.7.0) <6D6F0C9D-2EEA-3578-AF3D-E2A09BCECAF3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
0x956a9000 - 0x956b9ff7 libCRFSuite.dylib (??? - ???) <94E040D2-2769-359A-A21B-DB85FCB73BDC> /usr/lib/libCRFSuite.dylib
0x956dc000 - 0x956dcfff com.apple.audio.units.AudioUnit (1.7.2 - 1.7.2) <2E71E880-25D1-3210-8D26-21EC47ED810C> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x95754000 - 0x9577cff7 libxslt.1.dylib (3.24.0 - compatibility 3.0.0) <AB530FB2-8BD1-3328-95E8-CF449F0429CA> /usr/lib/libxslt.1.dylib
0x95795000 - 0x95796fff com.apple.TrustEvaluationAgent (2.0 - 1) <4BB39578-2F5E-3A50-AD59-9C0AB99472EB> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/Tru stEvaluationAgent
0x95797000 - 0x957dfff7 com.apple.SystemConfiguration (1.11.3 - 1.11) <68B92FEA-F754-3E7E-B5E6-D512E26144E7> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x957e0000 - 0x957eefff com.apple.opengl (1.7.7 - 1.7.7) <2D362F15-5EA6-37B6-9BCB-58F2C599ACDA> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x95858000 - 0x9588eff7 com.apple.AE (527.7 - 527.7) <7BAFBF18-3997-3656-9823-FD3B455056A4> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x9588f000 - 0x95977fff libxml2.2.dylib (10.3.0 - compatibility 10.0.0) <1841196F-68B5-309F-8ED1-6714B1DFEC83> /usr/lib/libxml2.2.dylib
0x95bdc000 - 0x95c50fff com.apple.CoreSymbolication (2.2 - 73.2) <FA9305CA-FB9B-3646-8C41-FF8DF15AB2C1> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSy mbolication
0x95c5f000 - 0x95c66ffd com.apple.NetFS (4.0 - 4.0) <AE731CFE-1B2E-3E46-8759-843F5FB8C24F> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
0x95c73000 - 0x95c79ffb com.apple.print.framework.Print (7.4 - 247.3) <CB075EEE-FA1F-345C-A1B5-1AB266FC73A1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
0x95c7a000 - 0x95cbdffd libcommonCrypto.dylib (55010.0.0 - compatibility 1.0.0) <6B35F203-5D72-335A-A4BC-CC89FEC0E14F> /usr/lib/system/libcommonCrypto.dylib
0x95d86000 - 0x95da4ff7 libsystem_kernel.dylib (1699.26.8 - compatibility 1.0.0) <3705DE40-E00F-3E37-ADB0-D4AE5F9950F5> /usr/lib/system/libsystem_kernel.dylib
0x961b6000 - 0x961b7ff7 libquarantine.dylib (36.6.0 - compatibility 1.0.0) <600909D9-BD75-386E-8D3E-7CBD29079DF3> /usr/lib/system/libquarantine.dylib
0x961b8000 - 0x961bdff7 libmacho.dylib (800.0.0 - compatibility 1.0.0) <943213F3-CC9B-328E-8A6F-16D85C4274C7> /usr/lib/system/libmacho.dylib
0x96533000 - 0x965a9fff com.apple.Metadata (10.7.0 - 627.32) <650EE880-1488-3DC6-963B-F3D6E043FFDC> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x965aa000 - 0x96781fe7 com.apple.CoreFoundation (6.7.2 - 635.21) <4D1D2BAF-1332-32DF-A81B-7E79D4F0A6CB> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x96782000 - 0x96872ff1 libiconv.2.dylib (7.0.0 - compatibility 7.0.0) <9E5F86A3-8405-3774-9E0C-3A074273C96D> /usr/lib/libiconv.2.dylib
0x96873000 - 0x96876ff7 libmathCommon.A.dylib (2026.0.0 - compatibility 1.0.0) <69357047-7BE0-3360-A36D-000F55E39336> /usr/lib/system/libmathCommon.A.dylib
0x96911000 - 0x969e1ffb com.apple.ImageIO.framework (3.1.2 - 3.1.2) <94798A2B-4C7A-30EA-9920-283451BDB9FA> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
0x969e2000 - 0x96a47ff7 libvDSP.dylib (325.4.0 - compatibility 1.0.0) <4B4B32D2-4F66-3B0D-BD61-FA8429FF8507> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
0x96a4b000 - 0x96a54fff libc++abi.dylib (14.0.0 - compatibility 1.0.0) <FEB5330E-AD5D-37A0-8AB2-0820F311A2C8> /usr/lib/libc++abi.dylib
0x96a55000 - 0x96a55fff com.apple.Carbon (153 - 153) <63603A0C-723B-3968-B302-EBEEE6A14E97> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x96f09000 - 0x96f0fffd com.apple.CommerceCore (1.0 - 17) <E59CD307-58E2-35FD-9131-B38978799910> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/C ommerceCore.framework/Versions/A/CommerceCore
0x96f63000 - 0x96f7fff5 com.apple.GenerationalStorage (1.0 - 126.1) <E622F823-7D98-3D13-9C3D-7EA482567394> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/Gene rationalStorage
0x96f80000 - 0x97a15ff6 com.apple.AppKit (6.7.3 - 1138.47) <D8CD06D7-F18C-39BE-BC68-B343F87F0469> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x97a16000 - 0x97b42ff9 com.apple.CFNetwork (520.4.3 - 520.4.3) <E9E315D4-CE22-3715-BED2-BB95AD5E10E8> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x97bf6000 - 0x97bf8ff9 com.apple.securityhi (4.0 - 1) <ACEEED5F-8D58-377D-B2B8-E4A7F4E5E286> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
0x97bf9000 - 0x980d5ff6 libBLAS.dylib (??? - ???) <134ABFC6-F29E-3DC5-8E57-E13CB6EF7B41> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
0x980d6000 - 0x980e1fff libkxld.dylib (??? - ???) <D8ED88D0-7153-3514-9927-AF15A12261A5> /usr/lib/system/libkxld.dylib
0x98252000 - 0x98253ffd libCVMSPluginSupport.dylib (??? - ???) <22B85645-AA98-372B-BB55-55DCCF0EC716> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginS upport.dylib
0x98254000 - 0x986c9ff7 FaceCoreLight (1.4.7 - compatibility 1.0.0) <3E2BF587-5168-3FC5-9D8D-183A9C7C1DED> /System/Library/PrivateFrameworks/FaceCoreLight.framework/Versions/A/FaceCoreLi ght
0x9871b000 - 0x9871cfff libDiagnosticMessagesClient.dylib (??? - ???) <DB3889C2-2FC2-3087-A2A2-4C319455E35C> /usr/lib/libDiagnosticMessagesClient.dylib
0x9871e000 - 0x9883cfec com.apple.vImage (5.1 - 5.1) <7757F253-B281-3612-89D4-F2B04061CBE1> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
0x98841000 - 0x98845ffa libcache.dylib (47.0.0 - compatibility 1.0.0) <56256537-6538-3522-BCB6-2C79DA6AC8CD> /usr/lib/system/libcache.dylib
0x98846000 - 0x98862ffc libPng.dylib (??? - ???) <75F41C08-E187-354C-8115-79387F57FC2C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
0x9887c000 - 0x9888aff7 libxar-nossl.dylib (??? - ???) <5BF4DA8E-C319-354A-967E-A0C725DC8BA3> /usr/lib/libxar-nossl.dylib
0x988ab000 - 0x98942ff3 com.apple.securityfoundation (5.0 - 55116) <EB53CEF7-4836-39FD-B012-6BC122ED4CE9> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoun dation
0x98943000 - 0x98947ff7 com.apple.OpenDirectory (10.7 - 146) <4986A382-8FEF-3392-8CE9-CF6A5EE4E365> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
0x98a90000 - 0x98d03ffb com.apple.CoreImage (7.98 - 1.0.1) <EDC91BA1-673D-3B47-BFD5-BBF11C36EE6A> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage .framework/Versions/A/CoreImage
0x98f23000 - 0x991e6fff com.apple.security (7.0 - 55148.1) <77754898-4FCD-3CA3-9339-F1058C852806> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x991e7000 - 0x991eaff7 libcompiler_rt.dylib (6.0.0 - compatibility 1.0.0) <7F6C14CC-0169-3F1B-B89C-372F67F1F3B5> /usr/lib/system/libcompiler_rt.dylib
0x991eb000 - 0x991f3ff5 libcopyfile.dylib (85.1.0 - compatibility 1.0.0) <BB0C7B49-600F-3551-A460-B7E36CA4C4A4> /usr/lib/system/libcopyfile.dylib
0x994af000 - 0x994c2ff8 com.apple.MultitouchSupport.framework (231.4 - 231.4) <083F7787-4C3B-31DA-B5BB-1993D9A9723D> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/Multit ouchSupport
0x99501000 - 0x9950ffff libz.1.dylib (1.2.5 - compatibility 1.0.0) <E73A4025-835C-3F73-9853-B08606E892DB> /usr/lib/libz.1.dylib
0x99512000 - 0x995d2ffb com.apple.ColorSync (4.7.4 - 4.7.4) <0A68AF35-15DF-3A0A-9B17-70CE2A106A6C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
0x995d3000 - 0x996a9aab libobjc.A.dylib (228.0.0 - compatibility 1.0.0) <2E272DCA-38A0-3530-BBF4-47AE678D20D4> /usr/lib/libobjc.A.dylib
0x99704000 - 0x99a06fff com.apple.CoreServices.CarbonCore (960.24 - 960.24) <9692D838-85A5-32C1-B7FB-7C141FFC2557> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x99a07000 - 0x99a35fe7 libSystem.B.dylib (159.1.0 - compatibility 1.0.0) <30189C33-6ADD-3142-83F3-6114B1FC152E> /usr/lib/libSystem.B.dylib
0x99a36000 - 0x99a37fff liblangid.dylib (??? - ???) <C8C204E9-1785-3785-BBD7-22D59493B98B> /usr/lib/liblangid.dylib
0x99b22000 - 0x99b2dff3 libCSync.A.dylib (600.0.0 - compatibility 64.0.0) <EDA0F56F-CB2C-30BB-940D-C6A25B73C717> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x99b2e000 - 0x99b30ff7 libdyld.dylib (195.6.0 - compatibility 1.0.0) <1F865C73-5803-3B08-988C-65B8D86CB7BE> /usr/lib/system/libdyld.dylib
0x99b31000 - 0x99b34ffd libCoreVMClient.dylib (??? - ???) <361CCFAF-8565-383F-915F-0B059C793E42> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClien t.dylib
0x99b35000 - 0x99b37ffb libRadiance.dylib (??? - ???) <4721057E-5A1F-3083-911B-200ED1CE7678> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x99b38000 - 0x99b67ff7 libsystem_info.dylib (??? - ???) <37640811-445B-3BB7-9934-A7C99848250D> /usr/lib/system/libsystem_info.dylib
0x99d7e000 - 0x99ddbffb com.apple.htmlrendering (76 - 1.1.4) <409EF0CB-2997-369A-9326-BE12436B9EE1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
0x99ddc000 - 0x99e1cff7 libauto.dylib (??? - ???) <984C81BE-FA1C-3228-8F7E-2965E7E5EB85> /usr/lib/libauto.dylib
0x99f60000 - 0x99f8bfff com.apple.GSS (2.2 - 2.0) <2C468B23-FA87-30B5-B9A6-8C5D1373AA30> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
0x99f8c000 - 0x99f99fff libGL.dylib (??? - ???) <30E6DED6-0213-3A3B-B2B3-310E33301CCB> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x99f9a000 - 0x99fb7ff3 com.apple.openscripting (1.3.3 - ???) <33713C0B-B7D5-37AA-87DB-2727FDCC8007> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
0x99fb8000 - 0x9a4cafeb com.apple.RawCamera.bundle (3.14.0 - 646) <27962422-EA30-43CF-2B3E-E662BB4C46C7> /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
0x9a769000 - 0x9aaafff3 com.apple.HIToolbox (1.9 - ???) <409E6397-0DCB-3431-9CCC-368317C62545> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x9aab0000 - 0x9aab0fff com.apple.Accelerate (1.7 - Accelerate 1.7) <4192CE7A-BCE0-3D3C-AAF7-6F1B3C607386> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x9aabb000 - 0x9aac6ffe libbz2.1.0.dylib (1.0.5 - compatibility 1.0.0) <B63F5D07-93B3-3F02-BFB7-472B4ED3521F> /usr/lib/libbz2.1.0.dylib
0x9ab1a000 - 0x9ab3cffe com.apple.framework.familycontrols (3.0 - 300) <5BCCDDC2-AFAC-3290-AEEF-23B2664CA11F> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyCon trols
0x9af34000 - 0x9af3fffe com.apple.NetAuth (3.2 - 3.2) <4377FB18-A550-35C6-BCD2-71C42134EEA6> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
0x9bec4000 - 0x9bec4fff com.apple.vecLib (3.7 - vecLib 3.7) <8CCF99BF-A4B7-3C01-9219-B83D2AE5F82A> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x9bec5000 - 0x9bf02ff7 libcups.2.dylib (2.9.0 - compatibility 2.0.0) <1C757924-4E54-3522-A885-99795EA10228> /usr/lib/libcups.2.dylib
0x9bf84000 - 0x9bfe2fff com.apple.coreui (1.2.2 - 165.10) <C6B099D6-7F02-3971-99B9-E415308959CF> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x9bfe3000 - 0x9c04bff7 libc++.1.dylib (28.1.0 - compatibility 1.0.0) <FE3304C5-C000-3DA0-9E53-0E4CA074B73B> /usr/lib/libc++.1.dylib
0x9c079000 - 0x9c189fe7 libsqlite3.dylib (9.6.0 - compatibility 9.0.0) <34E1E3CC-7B6A-3B37-8D07-1258D11E16CB> /usr/lib/libsqlite3.dylib
0x9c18a000 - 0x9c1dcff7 libFontRegistry.dylib (??? - ???) <96E9602C-DFD3-3021-8090-60228CC80D26> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontRegistry.dylib
0x9c1dd000 - 0x9c1fafff libresolv.9.dylib (46.1.0 - compatibility 1.0.0) <2870320A-28DA-3B44-9D82-D56E0036F6BB> /usr/lib/libresolv.9.dylib
0x9c1fb000 - 0x9cb2559b com.apple.CoreGraphics (1.600.0 - ???) <62026E0C-E30F-3FF0-B0F6-6A2D270B20BF> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x9cb75000 - 0x9cb76ff7 libsystem_sandbox.dylib (??? - ???) <EBC6ED6B-7D94-32A9-A718-BB9EDA1732C9> /usr/lib/system/libsystem_sandbox.dylib
0x9cb77000 - 0x9cb99ff8 com.apple.PerformanceAnalysis (1.11 - 11) <453463FF-7C42-3526-8C96-A9971EE07154> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/Perf ormanceAnalysis
0x9cc58000 - 0x9cc96fff libRIP.A.dylib (600.0.0 - compatibility 64.0.0) <19174EC0-DE0F-38EA-B5F3-7580E84677DD> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x9cd36000 - 0x9cd98ffb com.apple.datadetectorscore (3.0 - 179.4) <3A418498-C189-37A1-9B86-F0ECB33AD91C> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
0x9cdc6000 - 0x9cdceff3 liblaunch.dylib (392.38.0 - compatibility 1.0.0) <D7F6E875-263A-37B5-B403-53F76710538C> /usr/lib/system/liblaunch.dylib
0x9cf3f000 - 0x9cf42ffc libpam.2.dylib (3.0.0 - compatibility 3.0.0) <6FFDBD60-5EC6-3EFA-996B-EE030443C16C> /usr/lib/libpam.2.dylib
0x9cf43000 - 0x9cf4aff7 libsystem_notify.dylib (80.1.0 - compatibility 1.0.0) <47DB9E1B-A7D1-3818-A747-382B2C5D9E1B> /usr/lib/system/libsystem_notify.dylib
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 7
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 835
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=141.8M resident=81.4M(57%) swapped_out_or_unallocated=60.5M(43%)
Writable regions: Total=100.2M written=2612K(3%) resident=5380K(5%) swapped_out=0K(0%) unallocated=95.0M(95%)
REGION TYPE VIRTUAL
=========== =======
ATS (font support) 31.8M
ATS (font support) (reserved) 4K reserved VM address space (unallocated)
CG backing stores 212K
CG shared images 128K
CoreGraphics 12K
CoreServices 4408K
MALLOC 41.6M
MALLOC guard page 48K
Memory tag=240 4K
Memory tag=242 12K
Memory tag=249 156K
Stack 65.0M
Stack (reserved) 516K reserved VM address space (unallocated)
VM_ALLOCATE 16.1M
__CI_BITMAP 80K
__DATA 8220K
__DATA/__OBJC 92K
__IMAGE 528K
__IMPORT 92K
__LINKEDIT 43.2M
__OBJC 1424K
__PAGEZERO 4K
__RC_CAMERAS 248K
__TEXT 98.6M
__UNICODE 544K
mapped file 129.1M
shared memory 312K
shared pmap 9.9M
=========== =======
TOTAL 452.0M
TOTAL, minus reserved VM space 451.5M -
Time Machine Very Large Backup Space Requirements
I'm having a bit of trouble with Time Machine. I recently recreated a User Account. The old User account's home library permissions had become corrupt. Rather than try to sort through the permissions, I opted to just move all the personal data to another account (the primary admin), delete the old user account, recreate it, and move all the personal data to the new account. This worked splendidly. However, now Time Machine claims it needs about 2.1 TB to do it's next backup. I find this odd because a full backup is estimated as only 384 GB, and the computer's hard drive is only 1 TB to begin with. So, it needs a factor of 2 more space than is available on the computer. So, there is something amiss. I imagine Time Machine tracked the data being moved to the admin account and to the new account, and it wants to back all of this up. I don't want it to do that. Is there someway to cause Time Machine to forget the most recent changes?
Clearly, I don't want Time Machine to not backup the new account's information. However, I'm would like not to loose the previous backups. Any solutions?Hello again:
Erasing and then formatting the Time Machine volume and having Time Machine make a new backup would be the way I would do it.
As an aside, I use two external hard drives. I have Time Machine set to make alternating backups on the externals, and I also make a bootable clone (SuperDuper!) on one of the externals. Short of a meltdown, I am reasonably well protected.
Barry -
Trying to access time machine causes the macbook to freeze up
I have a significant problem with iphoto. Now I would like to access my pictures using the time machine. This is what I do and what happens.
1) go to the dock and click on time machine icon
2) a bar with blue traveling stripe appears says connecting to time machine
3) after less than 1 or 2 minutes the bar turns grey and stops moving
4)now nothing works. there is nothing I can do but shut off the macbook with the little on and off button at the top right hand corner of the computer.
5) i turn the computer off. Wait a minute or two
6) turn computer on
7) repeat steps 1-6
8)now that I have gone thru this process i get the color wheel all the time.
I have tried to find answers in all sorts of mac books, discussions, you tube and google.
When I see something I think might work it's to complicated for me to follow mostly because I don't know where to begin, which of the many ways that there are to enter a program. Which honestly is what started this problem a couple months ago. New to the mac. Started working with my photos with no knowledge of the ins and outs at all and in doing so I began to loose group after group of photos to the grey/black ! monster.
My happy thought was knowing they were all backed up by the time machine. I could recover them from there, SMILE. Not now I cant even access that now. Things keep getting worse.
Please save a Mac by helping meWhy not start by reading the three User tips at the top of this forum's topic listing, especially the one on troubleshooting.
My guess is you have something faulty with your system from what you describe. I would start by:
Repairing the Hard Drive and Permissions
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 and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
Next try booting into safe mode to see if the problem ceases.
Download and install AppleJack - VersionTracker or MacUpdate. Read the documentation then boot into single-user mode and run the software per its instructions.
If none of the above help then you will likely need to reinstall OS X. You may be able to do the following:
How to Perform an Archive and Install
An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
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.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update. -
Defrag an old Time Machine backup to save space for archiving?
I'm aware of all the reasons not to defragment an OSX volume, as well as Time Machine volumes, but hear me out on this one...
I bought a new iMac and will be starting a brand new Time Machine backup. I would like to keep the old Time Machine backup around just in case I need access to some old files. I will not be adding anything further to this old backup, and I will not be using this old backup to restore any system. I will only be browsing and restoring files from this backup, but only rarely. I have removed (via the Time Machine interface's "Delete all backups of...") a number of large files and unecessary directories to reduce the backup size. I then ran the hdiutil compact command to reclaim free space from the sparsebundle.
I read, however, that the hdiutil compact command will only delete unused bands of the sparsebundle, and that defragmenting the contents of a sparsebundle will likely produce more "empty" bands that can be removed with another run of compact to further free up space.
Will it be okay to defragment the sparsebundle under these circumstances?I've looked over Pondini's site and it's an awesome resource. I've learned a lot from it over the years. But my specific question isn't answered there.
The Time Machine software is complex and I understand that there's a lot of things to know to keep it running smoothly. However, my particular situation isn't commonly discussed. In scenarios not involving Time Machine, defragging a sparsebundle before running hdiutil compact is known to help free up more disk space by creating more unused bands within the sparsebundle that can be removed by compact. Makes sense. Why would this affect Time Machine's process? And could it be that it won't cause a problem for a sparsebundle that will only be used to browse and restore files? ... As opposed to a sparsebundle that one intends to continue backing up to? Are there defregmenting options that I should avoid, or be sure to use?
Maybe you are looking for
-
Apple TV (atv) no sound via optical or analog BUT sound through HDMI
Hi all, This is my first post into the forums. I spent some time searching for problems with Apple TV audio and as a result I think I already know the answer to my question, but would appreciate a second opinion. My Apple TV is about 1.5 years old (n
-
Mail app wont automaticaly fetch mail
Hi everyone I have configured my business mail account which is based on a Microsoft Exchange 365 Server. Inbox including subfolders got synchronized without any issues. My problem is that if i dont click on the subfolders the new emails on each sub
-
Automatic payment settlement - F110
Hi, While making payment settlement for a particular document in F110 transaction it prompts to select partner type during reallocation, where as it never picks the partner type which was set during document posting. Pls help me out from this so that
-
How to integrate price list on a Purchase Order?
Hi, Version : R12.1.3 I wanted to know how to use price list on a purchase order. I have created one price list but I am not able to use that, how could I use this. How to link Price list to the particular supplier. Thanks in advance. AmolA
-
i am trying to import pdf images into keynote or aperture. these are single page pdf's that i dragged out of a multi-page pdf in Preview. the original pdf was created in AutoCad. these are coming up as either washed out or as having black backgrounds