Apple Event: May 7th at 7 am PT
I have just noticed that TIme machine has not backed up to my external hard drive for nearly a year. I have checked and time machine is on, when I ask it to back up it gives a message to say it is preparing for a few seconds and then nothing! Please help
iMac (20-inch Mid 2007), Mac OS X (10.5.8)
TM as a lot do after a year...
Open TM preferences and re-associate the TM-disk.
Great... I think, at least teh solution is coming. COuld it be anything to do with the new memory installed last November?
I'll wait to hear from you, my closest Apple Store is not too far away in Bath so could get there no problem. Funny all this OS problem, I was just thinking I needed to upgrade to Sonow Leopard.
THanks again.
Pete1249 wrote:
Great... I think, at least teh solution is coming. COuld it be anything to do with the new memory installed last November?
About the time the problem started? Yes, that may not be a coincidence.
I'll wait to hear from you, my closest Apple Store is not too far away in Bath so could get there no problem.
Make an appointment. The visit and diagnosis is free while you're there (but they'll charge if they have to keep it), and you can cancel if not needed.
Funny all this OS problem, I was just thinking I needed to upgrade to Sonow Leopard.
Usually we advise against upgrading a malfunctioning system, but this might be an exception, even if it's a problem with the memory, since it may be difficult to reinstall Leopard. Snow Leopard is only $20, and can boot and repair your Mac. Let's see what advice we get.
EDIT: You may want to go ahead and order it: http://store.apple.com/us/product/MC573/mac-os-x-106-snow-leopard
Message was edited by: Pondini
Haven't heard anything much elsewhere yet. 😟
I'm wondering about the RAM. Have you had any other problems? Seems unlikely to affect TM only.
Still, you might want to remove it temporarily. Your Mac may run slower, but see if a backup will complete.
And/or, just re-seat it to be sure all those pins are making good contact.
You might want to try the free rember app via http://www.kelleycomputing.net:16080/rember/ (can't post as a link now??). It will test your RAM.
Hang in there . . .
Sorry not to get back to you sooner as I had gone to bed! About 12:30PM in the UK.
First thing I have tried the memory test, results below, the headline is all is OK!
I tried a backup after this and... for some strange reason it worked! I have not touched the memory modules and have a full back up, any idea why it has worked?
What should I do next do you think? I guess I will order and install Snow Leopard.
Rember Test Results
All tests passed!
Total built-in memory: 3 GB
This is the total amount of physical memory that the computer has installed. If this figure is not showing the correct amount of memory there may be a problem with one or more installed DIMMS.
Available memory: 1375 MB
Available memory is the amount of physical memory that is currently not in use by any other processes. All available memory will be used for testing when the "All" option is selected. To increase the amount of available memory, you can restart your computer before testing. If you are familiar with the command line (CLI), you can run memtest (the core of Rember) in single-user mode. See Rember help, or http://www.memtestosx.org for more information.
Requested amount: All MB
The total amount of memory requested for testing by the Rember application. Not all requested memory can be allocated for testing. See information on "Available memory" for more information.
Memory allocated for testing: 1375 MB
This is the total amount of memory that memtest was able to allocate for testing. See "Available memory" section for more information.
-------
Loops selected: 2
Total loops selected by user for testing. All loops should complete when testing is successful. Test failure when the "Continue on Error" preference is selected will cancel tests before this number of loops has been completed. Users can also cancel testing before this number is reached.
Loops completed: 2
Total loops completed by memtest. Note that the Rember is not always able to identify how many loops ran. If there are discrepancies between this and the loops selected, the log should be examined to determine exactly how many loops were performed.
-------
Total execution time: All tests passed! Execution time: 2894 seconds
This is the total amount of time that it took to execute the selected tests. Execution time may vary from system to system, and is provided as a guide for determining how long users can expect tests to run based on the amount of memory installed on the system.
Testing start time: 2013-08-29 07:15:18 +0100
Testing end time: 2013-08-29 08:03:34 +0100
Pete1249 wrote:
Sorry not to get back to you sooner as I had gone to bed! About 12:30PM in the UK.
Not a problem to me -- I'm here most of the time, and my iMac is always on, so I can respond to e-mails when convenient.
First thing I have tried the memory test, results below, the headline is all is OK!
Good! One thing mostly ruled out. 🙂
I tried a backup after this and... for some strange reason it worked! I have not touched the memory modules and have a full back up, any idea why it has worked?
None. 😟 Phase of the moon?
I didn't really think it was memory anyhow, by the nature of the crash reason, but anything's possible, and since this seems to have started about the time you installed it, certainly worth a look.
What should I do next do you think?
Keep an eye on your backups, of course. And anything else that seems odd.
Repeated crashes like that indicate some sort of problem, somewhere. I can't imagine a port or cable problem causing a crash with that sort of message, but you might want to have another cable handy, just in case.
I guess I will order and install Snow Leopard.
If you were thinking about it anyway, that's probably a good idea. At the very least, you'll have a disc that will boot your Mac, that you can use to repair your internal if you have to, reinstall OSX if necessary, not to mention do a full system restore from your backups.
There aren't a lot of major differences, but most of us like them, and it's smaller and usually a bit faster (no longer supports PPC processors) and generally less buggy.
And, you can get to the App Store, if that's of any interest. 😉
Keep us posted!
That's brilliant, I can't thank you enough for your brilliant support. Other problems I have been having with downloading music, iphoto, printing and scanning have all seemed to have cured themselves too.
I'll get that cable.
Cheers!
Pete1249 wrote:
That's brilliant, I can't thank you enough for your brilliant support.
Thanks, but not really. We still don't know what was going on, much less whether it will return.
Other problems I have been having with downloading music, iphoto, printing and scanning have all seemed to have cured themselves too.
Speculation, but the Safe Boot might have helped invisbly.
HI
I guess you knew I would probably be returning to this thread. 😟
Imac was shut down this afternoon and when restarted it would not backup again, message from Console below, any thoughts now the moon has changed phase? 🙂
Process: backupd [847]
Path: /System/Library/CoreServices/backupd
Identifier: backupd
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [1]
Date/Time: 2013-08-29 23:20:27.912 +0100
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: 15128AB5-DFA5-4C63-9635-4220B813411D
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 1
Thread 0:
0 libSystem.B.dylib 0x904bb166 mach_msg_trap + 10
1 libSystem.B.dylib 0x904c295c mach_msg + 72
2 com.apple.CoreFoundation 0x94589e7e CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x9458ab04 CFRunLoopRun + 84
4 backupd 0x00008651 0x1000 + 30289
5 backupd 0x0000257a 0x1000 + 5498
Thread 1 Crashed:
0 com.apple.LaunchServices 0x96b736a9 LSBindingState::LSBindingState(LSContext*, unsigned long, unsigned long, unsigned long, unsigned long) + 13
1 com.apple.LaunchServices 0x96b2c7fd _LSIsClaimedPackageExtension(LSContext*, XCFChars const*) + 71
2 com.apple.LaunchServices 0x96b1066c _LSIsPackageExtension(LSContext*, XCFChars const*) + 52
3 com.apple.LaunchServices 0x96b10602 _LSNodeIsPackage + 94
4 com.apple.LaunchServices 0x96b0fc29 _LSCopyInfoForNode + 645
5 com.apple.LaunchServices 0x96b2c60c _LSCopyItemInfoForRefInfo + 124
6 com.apple.DesktopServices 0x980c8ef6 TFSInfo::FetchData() + 82
7 com.apple.DesktopServices 0x980c8e95 TFSInfo::IsPackage() const + 29
8 com.apple.DesktopServices 0x980d5c46 TDeepFSIterator::PushIterator(TFSInfo const&) + 32
9 com.apple.DesktopServices 0x980c9687 TDeepFSIterator::NextInternal(TFSInfo&, long&, long&, bool&) + 303
10 com.apple.DesktopServices 0x980c9507 TDeepFSIterator::Next(TFSInfo&, long&, long&, bool&) + 47
11 com.apple.DesktopServices 0x980d7e5a TOperationSizer::Sizing(TFSInfo const&) + 166
12 com.apple.DesktopServices 0x980d7cef TOperationSizer::ComputeSize() + 345
13 com.apple.DesktopServices 0x980effb7 _NodeSizerWithSkipProc + 365
14 backupd 0x00011801 0x1000 + 67585
15 backupd 0x00016607 0x1000 + 87559
16 backupd 0x00016452 0x1000 + 87122
17 backupd 0x00015c8b 0x1000 + 85131
18 backupd 0x0000a2ed 0x1000 + 37613
19 backupd 0x00005924 0x1000 + 18724
20 backupd 0x00006835 0x1000 + 22581
21 com.apple.Foundation 0x93fa6dfd -[NSThread main] + 45
22 com.apple.Foundation 0x93fa69a4 __NSThread__main__ + 308
23 libSystem.B.dylib 0x904ec055 _pthread_start + 321
24 libSystem.B.dylib 0x904ebf12 thread_start + 34
Thread 1 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x96b10649 ecx: 0x00000000 edx: 0xb007eaa0
edi: 0xb007eaa0 esi: 0xb007e660 ebp: 0xb007e628 esp: 0xb007e610
ss: 0x0000001f efl: 0x00010282 eip: 0x96b736a9 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0x00000000
S
I'm shocked! 😉
Same as before.
Have you ordered Snow Leopard? All things considered, I think that's your best bet.
It may not cure the problem, but you'll at least have some tools to try to fix it.
Message was edited by: Pondini
Its ordered, should be with me on Wednesday the site advised. I'll install and advise of the outcome!
Great!
Fingers crossed here . . . again. 😉
Me too, just noticed is activity monitor that Finder is using between 60 and 70% of CPU, external backup drive going like crazy, this seems to happen quite a lot recently, any connection with teh problem do you think?
Try Relaunching the Finder.
Press Option-Cmd-Escape and choose Finder > Relaunch.
Hi
Back again, I have my copy of Snow Leopard.
I have tried to install it and after I get the install sceen and click on install nothing happens.
I looked online and saw non Apple memory may cause problems so have removed it and I am back to the original 1 GB only, still does not work!
Do you have at least 1 GB of Apple memory? And at least 5 GB of available disk space? If so, it should install.
Time machine not backing up
