Finder Lags Until Time Machine Drive RPM Increase
Example.
In a FInder window I click on Today and the list of files modified today will not appear until the time machine drive gets up to speed. I can hear the drive start to spin when I click on Today, and when the drive gets up to a certiain speed, the list of files appear and the spinnig wheel is gone.
Is this normal?
Mtn Lion 10.8.3
WD 2TB Drive using Firewire
It's normal if you have been using files from the external drive. Note that external drives may take some seconds to load data. The same happens when you are using Time Machine on an external drive and you want to restore a file: the Time Machine window is frozen until the external drive loads all backups saved in it
Similar Messages
-
Lion can't find my external Time Machine Drive
Anyone having a problem with Lion identifying the external Time Machine drive? When I go to Time Machine set up all I get is "Set Up other Time Capsule". Connections seem OK and drive is on and worked fine previous to the upgrade.
Any ideas?Is the drive a USB or FireWire external HD, or a network drive (NAS)?
If it's a NAS, it needs an update. See #C16 in Time Machine - Troubleshooting.
If it's an external HD, try repairing it, per #A5 in that same link. -
My Retina Macbook Pro died due to a hardware error. During the diagnosis I was asked by Apple support personnel to format and reinstall OSX, which I did but did not fix the issue. The mainboard has since been replaced and I am trying to restore the TimeMachine backup I have.
The USB disk containing the TimeMachine backup contains TimeMachine backups for two different computers, my last Mac and the one I owned before that, which died earlier this year.
When I plug the drive in, I am able to browse the backups from both machines, as shown in the screenshot below.
The problem comes in when I attempt to run the migration assistant. I select the first option (restore from USB drive, etc). The migration assistant finds the USB volume and in the list underneath shows backups from a single computer - which it calls Unknown. The date of the last back is shown as 10 December 2012, the same date as the last backup from my old Mac (doolittle). There is no trace of the backups from my new mac.
Any ideas of how to get around this?
Thanks
Andrewhttp://pondini.org/OSX/MigrationProblems.html
-
Lost the ability to Spotlight Index my Time Machine drive
I have an external, Firewire Time Machine drive which has been working without problems up to now. This evening I had a backup which hung up in the "preparing" stage (no file transfers begun yet). When I went to look in the console, there was a device error apparently related to trying to detect the powered-on state of my Time Machine drive. Apparently Time Machine did not handle this gracefully. In the course of trying to clear that I got into a state where I had to force shutdown of the system (holding the power button). (I accidentally clicked on the Time Machine icon which got hung up trying to display the histories, and left me with no access to the Desktop....)
Things appeared to check out fine when I brought the machine back up (including Verify Disk of both the main and Time Machine drives and Repair Permissions of the main drive), and I finally did a Back Up Now in Time Machine. Due to the forced shut down, this became a "Deep Traversal" "preparing"stage. We'll I've seen those before, so no worries. However it lasted quite a bit longer than it should, at which point I noticed that Spotlight was indexing the Time Machine drive.
So at this point I dragged the Time Machine into the Spotlight Privacy list. Rather than going away completely as I expected, the indexing of the Time Machine drive apparently went into some sort of clean-up phase that said it was still indexing for another 5 minutes (where it had, just prior, said it was going to be indexing for another 2 hours). The progress bar advanced normally as if it really did do 5 minutes more of indexing of the Time Machine drive. I've not seen this before
When that finished, the backup which had been "preparing" during all of this also finished "preparing", transferred the several MB of files I expected, and finished normally. There were no errors in the console related to any of this.
I rebooted, and once again did a pair of Disk Verifies and a Repair Permissions without problems. Opened up the console to track things, and poked around in the Time Machine. All was normal as far as I can tell. I also explored the Time Machine drive via the Finder. No problems.
So I now went into Spotlight Privacy and removed the Time Machine drive from the privacy list expecting it to do the re-indexing I had stopped above. Spotlight started indexing the drive and a couple seconds later it stopped. I tried again -- into and out of privacy -- same result, a couple seconds of indexing and then it stopped.
At this point I noticed the console was saying I had some bus errors in the I/O system, and that's what was terminating the md worker process and stopping the indexing.
So I shut down, unplugged the Time Machine drive, and went through my maintenance ritual.
I reset the PMU (this is a powerbook), reset PRAM, booted once in Safe Mode, booted normally, and ran Disk Utility again to Verify and Repair Permissions on the main hard drive. All of that went without a hitch. No failures, faults or funnies.
I ran through the list of Applications I use, keeping an eye on the console. Again no problems.
So I shut down, plugged the Time Machine drive back in and booted back up. I put the drive into Spotlight Privacy and turned off Time Machine backups. I then did a Verify Disk on that drive. No problems. I went into the Time Machine history display. No problems. And no problems looking at it in the Finder either. In particular, no bus errors or anything else funny in the console.
I rebooted and did a new Back Up Now. It completed without problems. It was another Deep Traversal backup due to the Safe Mode Boot, but it went without a hitch. I rebooted and did another Back Up Now and got a normal speed incremental backup again without a hitch. The bottom line is that as far as I can see that Time Machine drive is working just fine.
So I went into Spotlight Privacy and removed it from the list. Once again it started to index and stopped in a couple seconds. But this time there were NO Console error messages.
I moved my main hard drive into Spotlight Privacy and removed it and it re-indexed from scratch just fine. Tried again with the Time Machine drive -- indexing stopped in a couple of seconds with no message in the Console. Spotlight searches find all the right stuff in the main drive. Spotlight and finder searches find only the top level Time Machine folders in the Time Machine drive.
I also tried removing the Spotlight plist from my account's Library / Preferences. Spotlight created a new plist as expected but it still won't index that darned Time Machine drive.
Apparently there is something left over from when I originally aborted the Spotlight indexing of that drive which is causing Spotlight to think it has no work to do. I'm not seeing any I/O errors of any sort any more (I think my maintenance pass took care of that) and Time Machine backups and history access continue to work just fine. And again, the Time Machine disk Verifies just fine.
So I've run out of things to try.
Is there a hidden file that I need to remove from that drive so that Spotlight no longer thinks it already has it indexed?
--BobWell unfortunately the command
sudo mdutil -E /Volumes/MyDiskName
didn't help.
The command itself echoed the name of the volume and then said "Indexing Enabled", which looked good. But the Spotlight indexing stopped after a couple seconds. The Console reported the Terminal sudo command and nothing else.
I tried moving the Time Machine drive in and out of Spotlight privacy and once again the indexing started and stopped a couple seconds later with no Console messages.
I then tried another trick I've learned to make Spotlight indexing happen which is to do a Finder search for, say, all folders (limited to the one drive) via Command-f and while Including both System Files and files both Visible and Invisible. And indeed Spotlight indexing started but again stopped a few seconds later.
However, this time there were console messages and a crash report.
The Console shows (with personal information x'ed out):
12/31/07 1:30:38 PM mds[28] (/)(Error) IndexCI in openindex_filelazy:open file error: 2, 0.indexGroups
12/31/07 1:30:41 PM ReportCrash[146] Formulating crash report for process mds[28]
12/31/07 1:30:42 PM com.apple.launchd[1] (com.apple.metadata.mds[28]) Exited abnormally: Bus error
12/31/07 1:30:42 PM com.apple.launchd[1] (0x10ba40.mdworker[96]) Exited: Terminated
12/31/07 1:30:42 PM com.apple.launchd[1] (0x1004a0.mdworker[108]) Exited: Terminated
12/31/07 1:30:42 PM mds[147] (/Volumes/Xxxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/80F3EC85-D77A-49FE-8BDC-BB7C3B3EC1CF)(E rror) IndexCI in ContentIndexOpenBulk:Unclean shutdown of /Volumes/Xxxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/80F3EC85-D77A-49FE-8BDC-BB7C3B3EC1CF/0. ; needs recovery
12/31/07 1:30:43 PM ReportCrash[146] Saved crashreport to /Library/Logs/CrashReporter/mds2007-12-31-133038Xxxxxx-Xxxxxx-Computer.crash using uid: 0 gid: 0, euid: 0 egid: 0
The Crash Report reads as follows (again with personal information x'ed out):
Process: mds [28]
Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
Identifier: mds
Version: ??? (???)
Code Type: PPC (Native)
Parent Process: launchd [1]
Date/Time: 2007-12-31 13:30:38.746 -0500
OS Version: Mac OS X 10.5.1 (9B18)
Report Version: 6
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000030
Crashed Thread: 15
Thread 0:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0000cfa0 0x1000 + 49056
5 mds 0x00005580 0x1000 + 17792
Thread 1:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 2:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 3:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 4:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 5:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 6:
0 libSystem.B.dylib 0x92eda3ec _semwaitsignal + 12
1 libSystem.B.dylib 0x92f16fa0 pthread_condwait + 1580
2 mds 0x00009648 0x1000 + 34376
3 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 7:
0 libSystem.B.dylib 0x92ee0ea0 read$UNIX2003 + 12
1 mds 0x000091b4 0x1000 + 33204
Thread 8:
0 libSystem.B.dylib 0x92f15438 kevent + 12
1 mds 0x0007e584 0x1000 + 513412
Thread 9:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 10:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 11:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 12:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 13:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.spotlight.index 0x00207f0c _handleExceptions + 208
3 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 14:
0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
3 mds 0x00059ab8 0x1000 + 363192
4 mds 0x0005987c 0x1000 + 362620
5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 15 Crashed:
0 com.apple.spotlight.index 0x002046cc ContentIndexContainsContentByDocId + 204
1 com.apple.spotlight.index 0x00164358 QueryFunctionCallbackContext::findContent(db_obj*, __CFString const*, char*, int) + 244
2 com.apple.spotlight.index 0x001634d0 qpContentIndexMatch(datastoreinfo*, dblazyobj*, query_piece*, void*, int) + 328
3 com.apple.spotlight.index 0x0015587c comparefile_againsttree + 828
4 com.apple.spotlight.index 0x00155d30 comparefile_againsttree + 2032
5 com.apple.spotlight.index 0x00155d5c comparefile_againsttree + 2076
6 com.apple.spotlight.index 0x001e307c -[SISearchCtx isObjectInQuery:withQuery:shortcut:] + 144
7 com.apple.spotlight.index 0x001fa268 -[SISearchCtx_FSWalk performSearch:] + 996
8 com.apple.spotlight.index 0x001e2cbc -[SISearchCtx executeSearchContextCracked_2:jobNum:] + 136
9 com.apple.spotlight.index 0x00177e80 siwork_queueprocess + 752
10 com.apple.spotlight.index 0x0017811c sischeduleronce + 356
11 com.apple.spotlight.index 0x0017816c sischeduleronce + 436
12 com.apple.spotlight.index 0x001784f8 sischeduler_run_waitingtimeout + 640
13 com.apple.spotlight.index 0x0016529c runLoop + 72
14 com.apple.spotlight.index 0x00165308 query_runLoop + 32
15 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
Thread 15 crashed with PPC Thread State 32:
srr0: 0x002046cc srr1: 0x0200f030 dar: 0x00000030 dsisr: 0x40000000
r0: 0x002046a4 r1: 0xf09a4380 r2: 0x00000000 r3: 0x00000000
r4: 0xf09a43c0 r5: 0x00000000 r6: 0x000074d1 r7: 0x00000000
r8: 0x003fc080 r9: 0x00000000 r10: 0x00000000 r11: 0x44000444
r12: 0x92ede094 r13: 0x00000000 r14: 0x00000000 r15: 0x00373410
r16: 0x00000000 r17: 0x00239e98 r18: 0x00000001 r19: 0x00227b9c
r20: 0x00000000 r21: 0x00245554 r22: 0x00000001 r23: 0x00000001
r24: 0x00000000 r25: 0x00000005 r26: 0x00000000 r27: 0x00000000
r28: 0x00000000 r29: 0x00000005 r30: 0xf09a43c0 r31: 0x00204610
cr: 0x24000444 xer: 0x20000004 lr: 0x002046a4 ctr: 0x92ede094
vrsave: 0x00000000
Binary Images:
0x1000 - 0xc1ffb mds ??? (???) <af9cc958b4b030835101ff024186c7d3> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
0xde000 - 0xe0ffd com.apple.MDSChannel 1.0 (1.0) /System/Library/PrivateFrameworks/MDSChannel.framework/Versions/A/MDSChannel
0x139000 - 0x23fffb com.apple.spotlight.index 10.5.0 (398.1) <5843125c709dd85f22f9bd42744beea5> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/Spotlight Index
0x1ca9000 - 0x1caaffc liblangid.dylib ??? (???) <5f078ac1f623f5ce432ea53fc29338c0> /usr/lib/liblangid.dylib
0x2198000 - 0x22bdffb libmecab.1.0.0.dylib ??? (???) <cd875e74974e4ec3a0b13eeeb236fa53> /usr/lib/libmecab.1.0.0.dylib
0x8fe00000 - 0x8fe309d3 dyld 95.3 (???) <a7be977c203ec5c76b2f25a7aef66554> /usr/lib/dyld
0x90123000 - 0x9016effb com.apple.Metadata 10.5.0 (398) <b6bb1fd5a7a9135f546b2d8cbd65eafc> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x901ab000 - 0x902d0ff3 com.apple.CoreFoundation 6.5 (476) <9073c2bfdf6842562c8b7f0308109c02> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x9060a000 - 0x90612fff libbsm.dylib ??? (???) <c1fca3cbe3b1c21e9b31bc89b920f34c> /usr/lib/libbsm.dylib
0x90683000 - 0x90688ff6 libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x90757000 - 0x907d2fff com.apple.SearchKit 1.2.0 (1.2.0) <1b448fbae02460eae76ee1c6883f45d6> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x9088a000 - 0x9090ffff libsqlite3.0.dylib ??? (???) <7b379cb4220346e99c32c427d4539496> /usr/lib/libsqlite3.0.dylib
0x90aa7000 - 0x90ab5fff libz.1.dylib ??? (???) <1a70dd3594a8c5ad39d785af5da23237> /usr/lib/libz.1.dylib
0x90b50000 - 0x90be2fff com.apple.framework.IOKit 1.5.1 (???) <591b8b0cc4261db98a6e72e38eef5f9a> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x91105000 - 0x9116cffb libstdc++.6.dylib ??? (???) <a4e9b10268b3ffac26d0296499b24e8e> /usr/lib/libstdc++.6.dylib
0x9116d000 - 0x912b5ff3 libicucore.A.dylib ??? (???) <250daed2fb2e6bf114480e2e4da0728b> /usr/lib/libicucore.A.dylib
0x91c3c000 - 0x91d32ffc libiconv.2.dylib ??? (???) <05ae1fcc97404173b2f9caef8f8be797> /usr/lib/libiconv.2.dylib
0x91d3a000 - 0x91db4ffd com.apple.CFNetwork 220 (221) <00b882d3d3325526b78ded74880759fe> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x9236a000 - 0x92382ffb com.apple.DictionaryServices 1.0.0 (1.0.0) <fe37191e732eeb66189185cd000a210b> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
0x92383000 - 0x9238effb libgcc_s.1.dylib ??? (???) <ea47fd375407f162c76d14d64ba246cd> /usr/lib/libgcc_s.1.dylib
0x92742000 - 0x92769fff libxslt.1.dylib ??? (???) <3700d04090629deddb436aa2d516c56d> /usr/lib/libxslt.1.dylib
0x92777000 - 0x92860fff libxml2.2.dylib ??? (???) <6f383df1e1e775be0158ba947784ae13> /usr/lib/libxml2.2.dylib
0x928aa000 - 0x928b9fff com.apple.DSObjCWrappers.Framework 1.2 (1.2) <2411674c821a8907449ac741ce6a40c3> /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWra ppers
0x92a17000 - 0x92afafeb libobjc.A.dylib ??? (???) <4a90e315bd1718c3f5ae09ee6c23e36c> /usr/lib/libobjc.A.dylib
0x92afb000 - 0x92bc9ff7 com.apple.CoreServices.OSServices 210.2 (210.2) <bad4943629f870d305f2bc7c6dfffe2d> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x92bde000 - 0x92dbfffb com.apple.security 5.0.1 (32736) <15632bf9bbdb223194b3d79a2e48e02d> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x92e9a000 - 0x92ec5ff7 libauto.dylib ??? (???) <c1f2bd227817ad7c7bf29ec74729ac7c> /usr/lib/libauto.dylib
0x92ed2000 - 0x9306bfe3 libSystem.B.dylib ??? (???) <8a6cd873dfa7ada786efac188f95ed1b> /usr/lib/libSystem.B.dylib
0x931a7000 - 0x934a7ff3 com.apple.CoreServices.CarbonCore 783 (783) <fd2acaf23e95472f78b8a077fa039986> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x946f2000 - 0x9472afff com.apple.SystemConfiguration 1.9.0 (1.9.0) <d925dde7699e6231c88a41b0254a7591> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x94933000 - 0x9494eff3 com.apple.DirectoryService.Framework 3.5 (3.5) <3246a5d1c6a3d678798a90e8c5cd3677> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
0x9494f000 - 0x9494fffa com.apple.CoreServices 32 (32) <42b6dda539f7411606187335d9eae0c5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x94c68000 - 0x94c9dfff com.apple.AE 402 (402) <a4b92c8ac89cc774b85fb44c48b9d882> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x96831000 - 0x9683afff com.apple.DiskArbitration 2.2 (2.2) <9c8f8ade43fa25b32109ef9dcc0cb5d5> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x9683b000 - 0x968d1ff7 com.apple.LaunchServices 286 (286) <a3a0b2af862e9a8945072f8cb523678f> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
0x969bc000 - 0x96c00ffb com.apple.Foundation 6.5.1 (677.1) <4152239382fb0f48abbcbf35bd04afa6> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0xfffec000 - 0xfffeffff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff8000 - 0xffff9703 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
Apparently the mdutil command didn't actually delete the Spotlight index file which is causing the problem, or at least didn't leave the indexing files in a consistent, empty state to start indexing over again. I may have to Erase this Time Machine disk and start over.
I should point out that except for Spotlight indexing this disk is otherwise working just fine. It passes Verify Disk with no errors and both new Time Machine backups and viewing and restoring via Time Machine and Finder work without problem.
Any suggestions before I just Erase the disk and start over with a new backup?
--Bob -
I have an iMac that had drive problems last winter. Took the iMac to the Apple Store and they reinstalled everything and now it works again. Only thing is that my external Time Machine drive is screwed up now. Its 1.5 TB.
I had the Time Machine drive partioned into two parts. One partion was for an emergency bootup using carbon copy cloner. That partion I can open and mounts on my desktop. The other partion was Time Machine. It once upon a time opened and mounted without a password.
It requests a password to unlock even though I never had it password protected before the iMac drive problems. And so now it won't mount the drive.
I can go to Disk Utilities and I can see Time Machine with both partions. The Carbon Copy partion is mounted. The Time Machine partion is not mounted. For this reason I can't select it and erase it.
What the heck am I supposed ot do now to erase it and start over. Any help would be appreciated. I really don't want to go and buy another drive.
KevinTriple-click anywhere in the line below to select it:
{ diskutil list; echo; diskutil cs list; } | open -f -a TextEdit
Copy the selected text to the Clipboard (command-C).
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V).
A TextEdit window will open with the output of the command. Post the contents of that window, if any — the text, please, not a screenshot. The title of the window doesn't matter, and you don't need to post that.
If any personal information appears in the output, anonymize before posting, but don’t remove the context. -
External time machine drive no longer being automatically recognized
Recently my RMBP has stopped recognizing my external time machine drive. When ever I connect my 1 TB WD drive to my mac, it shows up on my desktop as usually but will not get recognized by time machine. I used to be able to connect the drive, have it show up on my desk with the orange USB logo, and then it would be auto recognized and the time machine logo would appear on it and it would start backing up. Now, I connect it and it just stays at the orange USB logo. I have to go to the time machine menu bar icon and open time machine's preferences and manually select the drive to get it to back up. This happens both on battery power and while I'm charging. I have already verified the disk in disk utility and have repaired as well. I don't recall when this started happening. I was running the 10.9.4 beta before its public release, but it hadn't been working before I upgraded to that either.
This simple procedure will clear your Time Machine settings, including exclusions. The backups won't be affected. If you have a long exclusion list that can't be recreated easily, you may prefer a more complicated procedure that preserves the exclusion list. In that case, ask for instructions. Otherwise, do as follows.
Triple-click anywhere in the line below on this page to select it:
/Library/Preferences/com.apple.TimeMachine.plist
Right-click or control-click the highlighted line and select
Services ▹ Reveal in Finder (or just Reveal)
from the contextual menu.* A Finder window should open with a file selected. Copy the file to the Desktop. Then move it (the original, not the copy) to the Trash. You'll be prompted for your administrator password. Restart the computer and recreate your settings in the Time Machine preference pane. It will show that you have no backups. Don't worry; your backups haven't been touched. Run a backup to test. The backup may take much longer than usual. If TM now performs as expected, delete the file you copied to the Desktop.
*If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combinationcommand-C. In the Finder, select
Go ▹ Go to Folder...
from the menu bar and paste into the box that opens by pressing command-V. You won't see what you pasted because a line break is included. Press return. -
Encrypted Time Machine Drive not visible
Hi,
I have a Mac Mini (2.53 GHz Intel Core 2 Duo with 4GB 1067 MHz DDR3 Ram) running OS 10.8.4 and all other OS/application updates have been run. I have a Drobo (2nd Generation, the one with four drive bays & Firewire) with 3.69TB used and 1.72TB free. The Drobo has the most up-to-date firmware 1.4.2 as well as the latest Drobo Dashboard software (2.5.2).
I was using a different NAS to backup my data from the Mini but the housing failed and I'm waiting for Other World Computing to send a new one. In the mean time, I decided to backup the Mini to the Drobo and Encrypt it. I believe it went through one complete backup of the Mini (440GBs) overnight. I also use the Drobo as my main drive for my photos and iTunes library. I have about 2TBs of music/movies and about 1TBs of photos already stored on the Drobo. During the day yesterday, during a regularly scheduled Time Machine backup (I believe it backs up every hour), I was in the process of deleting photos off the Drobo and got the dreaded spinning beach ball. I waited for 1/2 hour but still after no changes, I turned off the Mini and after rebooting the Time Machine drive will not show on the desktop.
The Drobo is visable in the Drobo Dashboard app and of course it says there are no issues.
The Drobo shows up in Disk Utility as a Virtual Whole Disk (in red type) and when running Verify or Repair Disk, it states that "Error: This disk needs to be repaired. Click Repair Disk." I can do this till the cows come home but nothing changes. The only other info that shows up in red is "Invalid Disk Label @ 17591825289216: invalid field value. It repeats it four times, I'm assuming once for each drive. The last piece of info is "disk3s2 is not a CoreStorage volume.
I saw on another thread to run a Terminal command "diskutil cs list" and it came up with the below listed info.
Last login: Thu Jul 18 12:51:04 on console
skurkis:~ administrator$ diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 6E1361BB-CAF7-468D-9CD5-5A77ED37C763
=========================================================
Name: -none-
Status: Initializing
Size: 0 B (0 B)
Free Space: -none-
|
+-< Physical Volume 161162B5-ABCE-4540-BA90-A3EA9E2E956B
Index: 18446744073709551615
Disk: disk3s2
Status: Failed
Size: -none-
skurkis:~ administrator$
Any help to get my nearly 4TBs of music, movies, photos back would be awesome!
Thanks,
JeffAre there any utilities that can help "uncorrupt" the volume so I can rescue my data?
The only thing you can do is destroy the Core Storage logical volume, which will remove all data. If there is anything other than backup data on it, you're in a recovery situation, which is a job for professionals.
You should immediately start a new backup on another storage device. Don't do anything else with the computer until that's done. -
Ejecting an encrypted Time Machine drive always prompts "Eject All"
Whenever I eject my encrypted Time Machine drive, Finder reports that the drive has more than one partition and asks if I want to eject just the Time Machine partition or all. So I have to hit "Eject All" in this dialog every time I want to disconnect my MacBook from my Time Machine drive.
Thing is, there is only one partition. I've even gone so far as reformatting the drive to one partition and restarting my Time Machine backups fresh twice, but I still get the Eject All prompt every time.
Anybody else have this issue and/or know of a solution?I wouldn't use RAID for TM, but...
http://pondini.org/TM/2.html
https://discussions.apple.com/thread/4062015?start=0&tstart=0 -
Time Machine Drive Starts Up Every Time I Try And Open A Word File
I had this problem when I first got Leopard and now that I've upgraded to 10.6 I'm having it again. Whenever I open word and then look for a file the Time Machine drive starts to whir and I have to wait an eternity to start looking for files on my Mac, not the Time Machine drive. I can't find a setting in Word to shut off the search feature and I have Time Machine shut off from Spotlight so I can't figure out the problem. And it's not exclusive to Word. It's all programs where I have to search for a particular file, iMovie, iWeb, Final Draft, etc. Help!
try rebuilding launch services database. run the following command in terminal
/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user
see if that helps. -
Genius Bar lost a business file. Can't seem to find it in Time Machine...Got Ideas?
Genius Bar lost a business financial file. Can't seem to find it in Time Machine. Gone back several days...Got Ideas?
You need to give me more info..
What did you take the Mac to the genius for??
What did they do to it?
Did you have TM setup at defaults doing backups hourly?
Are you using a Time Capsule? Did you ever backup the time capsule??
Please do a backup of your Time Machine backup right now.. in TC plug in a suitable sized USB drive and do an archive.. you can do nothing else while this is happening but it is crucial for you to have another copy of whatever you have.
Archive is a bit slow.. and the backup is slightly less useful.
The fastest method is plug the USB into your computer and copy and paste the backups.backupdb directly to the USB drive. It should copy at around 60GB/hr so calculate how long that will take. See instructions here. http://pondini.org/TM/18.html Assuming you are using a TC then you use method 4.. copying from a Network backup to local drive.
Never work directly from the original backup .. work just from this copy so anything you do can be reversed or recovered.
Read very carefully the methods of restoring files from TM.. it is a bit out of date but Pondini has the best details.
So Q14-17 here. http://pondini.org/TM/FAQ.html
You can do a full recovery of the backup to a USB drive.. and then search for your file in more normal way.
Get professional help.. and this is where you need data recovery people who are familiar with apple TM backup format. Check local apple store or perhaps better local Apple independent repair business that are used to handling this kind of event.
Also talk to the company that makes the software as they must have to deal with people who manage to lose, corrupt or in some other way ruin their data and need to recover.. see what hints they can give you.
Surely at some point you pass your info to your accountant in the form of a computer backup file from your accounting package.
I have to admit I am surprised if you never backed up your business data file to a USB stick and put it in a filing cabinet at home or a hard disk at a friends place.. Cloud storage for your business files.. Did you depend totally on TM for backups? You never planned for a fire or theft of your computer and TC?? Or what has happened.. loss of computer files and failure of the backup? No greater teacher than the burnt hand that touching hot stuff isn't a good idea. Sorry .. it is a very hard lesson.. but electronic data storage on magnetic media is ever one byte away from being gone forever.. !! -
What happens when the Time Machine drive is full?
I'm on my second iMac. My first one (G5, 1984) died, and I replaced it early 2010 with an Intel mac. The transition when exceedingly well largely due to Time Machine. I just hooked the Time Machine drive to the new system, and I was soon back up running!
My home folder has 70GB of data. The Macintosh drive has 105GB of data and 395GB free. The Time Machine drive has 220GB used and 30GB free.
1. What happens when the Time Machine drive is full?
2. Do I have control over what backups get deleted?
3. If lightning strikes twice, will I still be able to restore my Intel mac like my G5 mac, even if backups get deleted?
4. Is there anyway to control what backups/backup files get deleted?
5. Any other thoughts?
Thanks.maxseven wrote:
i have deleted the time machine folders and they are now in my trash. when i try to secure empty my trash it will delete everything but the t/m folders. how do i delete them?
Do you mean all of them? The entire Backups.backupdb folder?
That's a large mess. First, even a normal delete will take a very long time, as there are probably hundreds of thousands, or even millions, of files. Your best bet by far is to simply erase them with Disk Utility -- that will only take a few moments. If your TM drive has a single partition, see #1 in [Formatting, Partitioning, Verifying, and Repairing Disks|http://web.me.com/pondini/AppleTips/DU.html]. If there are other partition(s) on the drive, see #2 there.
If not, and you only deleted some of the folders, you have a different, worse problem. Unfortunately, Apple doesn't do a very good job of warning folks: +*Never move, change, or delete anything in your backups via the Finder or Terminal.+*
You shouldn't have to delete backups at all, since Time Machine will do that automatically when the disk/partition gets full. But you can do it without harm via Time Machine. See #12 in [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum).
A normal delete will take a very long time, as there are probably tens or hundreds of thousands of items, each of which must be individually deleted. A secure delete will take much, much longer, as each deleted file must be overwritten with zeros. -
Cloned Time Machine Drive Invalid Node Structure
My Hitachi 2TB HD I use for Time Machine started sending out S.M.A.R.T. errors earlier this month, so I sent it in to Hitachi under warranty. Before I sent it out, I was able to clone the drive to another 2TB drive using the Restore feature in Disk Utility. This worked great, I have since been using the clone as a Time Machine drive and doing regular automatic backups - smooth so far!
When I got the new drive back from Hitachi, I tried to send the data back to the new drive using the same Restore function, and it looked like it was a complete success. After the restore process finished, both drives suddenly reporting "Invalid Node Structure" in Disk Utility.
I've since tried Disk Warrior, and it tells me I'm out of RAM (I have 8GB of RAM on a 2 x 2.26 Quad-Core MacPro) and the Disk Utility Repair Disk function is failing. I've since done a complete wipe of the new drive again (I used the Certify function in SoftRAID 4.0), and voila, no errors on the new drive. I then tried simply dragging over the Backups folder from the clone, and Finder tells me "Operation Not Supported." Strangely enough, Time Machine backups still work!?
Any idea how this happened and how I can fix it? I really can't buy Drive Genius only to find out it's not going to work too...do you think it would work? I would really hate to completely lose all this valuable backup data, it's been quite valuable to have around in the past.
Thanks everyone for your help, I'm at a total loss as to what happened.John Nightingale1 wrote:
I then tried simply dragging over the Backups folder from the clone, and Finder tells me "Operation Not Supported."
Yes, prior to Lion, you can't copy Time Machine backups with the Finder.
Are both drives formatted exactly the same, and with the GUID Partition Map scheme?
I'd be inclined to just let Time Machine start fresh on the new drive. You can always view and restore from the old one via the Browse ... option, per #17 in Time Machine - Frequently Asked Questions. -
Time Machine Drive Ejecting Itself--Spotlight culprit?
Hi,
I have to backup my MBP ASAP so that I can take it to Apple for repairs. When I first got the computer, I thought both my external drives were ejecting randomly so I never thought that Time Machine was the issue. The other hard drive proved to have a faulty wire and solved that problem, but I still can't seem to determine why my Time Machine drive keeps randomly ejecting. I searched this and various other forums for an answer and narrowed down my problems to my antivirus and spotlight indexing. At first, the harddrive would last anywhere from 0mins-45mins before being ejected. I began checking the console logs and notices some instances where my antivirus was running at the same moment. I disabled scanning of the TM backup and saw the biggest improvement in how long the drive was able to stay connected and make backups before ejecting. It stayed on for close to 6-7 hours.
Then, it ejected randomly again and I checked the console messages and saw spotlight returned some indexing errors. This time the ejection made the drive unreadable and I had to reformat. I backed up again and it kept ejecting itself early on in the backup process with the same spotlight errors. I added the entire drive to Spotlight's privacy list, and it managed to complete the entire backup. The drive then stayed connected without ejecting for another 7-9 hours the next day without any random ejects before the spotlight errors struck again. The drive is still listed in the privacy and it is still excluded from antivirus scanning. I have repaired the disk several times and gotten the "Appears to be OK" message. I even reformatted the drive and did another complete backup hoping that would take care of any corrupt Spotlight indexing. I have also rebuilt the entire index for both Spotlight on the internal and external drive. At this point, I need to run the backup as I am getting my hard drive swapped. What I am most concerned about is, even if I get another backup successfully on the drive, will I run into any problem using Setup/Migration assistant (random ejects, freezes, corrupt data) when its time to transfer my info back to the new install of OS X and be left without my data altogether? I also just need to this work... as what is the point of a backup solution, if you can't rely on it to make it through a day without crashing..
Below is the latest log file from Console. Any help will be greatly appreciated as I have went through the same steps that proved successful for others who had the same issue before me.
Console Log:
Oct 25 19:35:58 CSKMBP1086 com.apple.backupd[12396]: Starting standard backup
Oct 25 19:35:58 CSKMBP1086 com.apple.backupd[12396]: Backing up to: /Volumes/Time Machine /Backups.backupdb
Oct 25 19:36:04 CSKMBP1086 com.apple.backupd[12396]: No pre-backup thinning needed: 202.8 MB requested (including padding), 35.59 GB available
Oct 25 19:37:15 CSKMBP1086 kernel[0]:
Oct 25 19:37:15 CSKMBP1086 com.apple.backupd[12396]: Error: (-36) SrcErr:NO Copying /Library/Logs to /Volumes/Time Machine /Backups.backupdb/CSKMBP1086/2010-10-25-193558.inProgress/69A3D5EC-1F5B-495A-AE B6-CFE539F99764/Macintosh HD/Library
Oct 25 19:37:15 CSKMBP1086 kernel[0]:
Oct 25 19:37:15: --- last message repeated 4 times ---
Oct 25 19:37:15 CSKMBP1086 mds[41]: (/Volumes/Time Machine/.Spotlight-V100/Store-V1/Stores/3ACBCEAD-A6E0-485B-9EC8-6ABCAB507777)(E rror) IndexStore in SIStoreDirytySDBChunks:Error storing dirty sdb pages: 22
Oct 25 19:37:15 CSKMBP1086 kernel[0]:
Oct 25 19:37:15: --- last message repeated 1 time ---
Oct 25 19:37:15 CSKMBP1086 mds[41]: (/Volumes/Time Machine /.Spotlight-V100/Store-V1/Stores/3ACBCEAD-A6E0-485B-9EC8-6ABCAB507777)(Error) IndexCI in _ContentIndexSyncIndexBulk:preSync error:22 22
Oct 25 19:37:16 CSKMBP1086 com.apple.launchd[1] (com.apple.backupd[12396]): Job appears to have crashed: Segmentation fault
Oct 25 19:37:16 CSKMBP1086 Finder[7405]: * CFMessagePort: dropping corrupt reply Mach message (0b100101)
Oct 25 19:37:16 CSKMBP1086 com.apple.Finder[7405]: Failed to send message to backup server: error = -5
Oct 25 19:37:16 CSKMBP1086 SystemUIServer[7404]: * CFMessagePort: dropping corrupt reply Mach message (0b100101)
Oct 25 19:37:16 CSKMBP1086 com.apple.SystemUIServer.agent[7404]: Failed to send message to backup server: error = -5
Oct 25 19:37:16 CSKMBP1086 com.apple.ReportCrash.Root[12410]: 2010-10-25 19:37:16.532 ReportCrash[12410:1407] Saved crash report for backupd[12396] version ??? (???) to /Library/Logs/DiagnosticReports/backupd2010-10-25-193716localhost.crashBrinXx wrote:
narrowed down my problems to my antivirus
Unless you're running Windoze on your Mac, you may not need any anti-virus software at all. See Thomas Reed's [Mac Virus Guide|http://www.reedcorner.net/thomas/guides/macvirus]. But yes, keep your TM drive excluded.
The drive then stayed connected without ejecting for another 7-9 hours the next day without any random ejects before the spotlight errors struck again.
Excluding your TM drive from Spotlight doesn't stop all indexing of it: http://docs.info.apple.com/article.html?path=Mac/10.6/en/8991.html
What I am most concerned about is, even if I get another backup successfully on the drive, will I run into any problem using Setup/Migration assistant (random ejects, freezes, corrupt data) when its time to transfer my info back to the new install of OS X and be left without my data altogether?
The backups will probably be ok, but if your internal HD is corrupted, as it seems to be, that corruption may be transferred to them.
Oct 25 19:37:15 CSKMBP1086 com.apple.backupd[12396]: Error: (-36) SrcErr:NO Copying /Library/Logs to /Volumes/Time Machine /Backups.backupdb/CSKMBP1086/2010-10-25-193558.inProgress/69A3D5EC-1F5B-495A-AE B6-CFE539F99764/Macintosh HD/Library
Now that's quite odd, indeed: the /Library/Logs folder is supposed to be +*excluded automatically+* from backups! That's controlled by a special plist deep inside OSX, so it's been altered, corrupted, or ignored, which is not a good sign.
Ordinarily, I'd suggest downloading and installing the 10.6.4 "combo" update, but that may not be enough -- you may need to reinstall OSX, too, and depending on what's wrong with your system, you may not have time, and if your system is misbehaving, it may not work anyway. If you want to, the info and download are available at: http://support.apple.com/kb/DL1048 Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards.
Oct 25 19:37:15 CSKMBP1086 mds[41]: (/Volumes/Time Machine/.Spotlight-V100/Store-V1/Stores/3ACBCEAD-A6E0-485B-9EC8-6ABCAB507777)(E rror) IndexStore in SIStoreDirytySDBChunks:Error storing dirty sdb pages: 22
That's from the mds process, used by both Spotlight and Time Machine.
Oct 25 19:37:16 CSKMBP1086 com.apple.launchd[1] (com.apple.backupd[12396]): Job appears to have crashed: Segmentation fault
Another indication of possible corruption in your installation of OSX.
|
It's always a good idea to keep secondary backups, since all hardware fails, sooner or later, and no backup app is perfect. Given the apparent corruption of your installation of OSX, I'd recommend that even more strongly. See #27 in [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum) for some suggestions.
Sorry not to have better news or more concrete suggestions.
Let us know what Apple finds, and/or if you need help restoring. -
Recovering Mail messages from Time Machine drive
I recently deleted some important Mail messages do to my iPhone and iMac Mail sync via the Cloud. The messages are likely (for sure) on my Time Machine drive, but I don't know a simple way to find them. Right now enter Time Machine and can go User> Me> Library> Mail and the into the inbox of the related Mail account and then I am arbitrarily looking in subfolders with # labels, and seeing lists of xml (or whatever they are) files. The are in no order, and when I open them I find messages willy nilly from past dates.
Is there an easy way to actually find these messages, to search or read the messages in the Time Machine drive to recover specific ones. The method I describe above is simply not workable.
Thanks.Note that you have to open the Time Machine app while you are using the Mail window. If not, a Finder window will pop up and it will not work. After opening the Time Machine app, you should see a screen like this one:
Then, use the arrows to navigate through your backups, and when you have found the mails you want to restore, select them with the Command key and press "Restore". Note that OS X is in Spanish in my computer, but you should see the text in English. -
Migration Assistant doesn't see USB Time Machine drive
My dad recently got a new MacBook Pro and wants to restore from his Time Machine backup, stored on a USB drive. He didn't use the Setup Assistant at the start - I'm really not sure why, but anyway...
Now we're looking at Migration Assistant, and it can't find the Time Machine drive. On the 'Select your disk' screen, the wheel just spins and spins. The backup drive is plugged in and mounted. We've checked the drive for errors using Disk Util, and it's fine. Moreover, I tested this with my own MBP and it's backup drive and the same problem occurs.
He also tried booting from the install DVD and using the 'restore' option from the Utilities menu, without success.
Is this because he has started to set up the machine using a user (as admin) with the same account name as the Time Machine backups? This website suggested that maybe that's what happening: http://web.me.com/pondini/AppleTips/Setup.html. Before I take him through a reinstall, etc, I'm hoping to confirm that this is really the problem!Just create a new user account with a different name. Logout of the current account and log into the new one. Be sure the new account has admin status. You can then try migrating and see if it now works. Also see OS X 10.5- Migration Assistant keeps "looking for other computers".
See User Tips for Time Machine for help with TM problems. Also you can select Mac Help from the Finder's Help menu and search for "time machine" to locate articles on how to use TM. See also Mac 101- Time Machine.
Maybe you are looking for
-
Unable to modify a XML node which is a SimpleType using a Typed XML field.
Hello, I have an XSD schema that uses SimpleTypes. When I attempt to modify a node in an Schema typed XML field, which has a schema using simpletypes, I receive the error: XQuery [modify()]: The value is of type "xs:string", which is not a subtype
-
MacBook Pro loses wifi connection upon wake since I bought a new AirPort Express
Hi. I've been using Apple devices and computers since february 2008 and had no problems until now. I currently own an early 2011 13" MacBook Pro and a PC running Windows 7 and Ubuntu 12.10. Until early February, I used a 2nd gen AirPort Extreme to co
-
Vertical slider position not updated while displaying .pdfs with Adobe Reader X
When a .pdf file is opened inside Firefox 4 (beta/RC1), the vertical slider position does not update while scrolling through the document until the mouse cursor is moved to the slider bar (then the slider immediately jumps to the right place). I am u
-
Create a 2-dim array dynamically
Hello! I have had this problem here before but try one moore time :-) This is the thing: We have a text-file from which we read. This textfile can be different from time to time. From this textfile we can catch numbers of columns and numbers of rows
-
When I try to use the file I added to my library in illustrator, it gives me an error: Could not place the document '8d63df86-9954-4c5c-b49e-0c0255fd7d11.ai' because of a program error. Any idea what's wrong or how to resolve this?