Imovie not seeing partitioned time machine drive. I partitioned my TM 2GB and formatted Mac OS Extended (Journalled). These drives in iMovie have a Yellow exclamation mark and I cant access events. Can access in Finder?

Any assistance would be greatly appreciated

Thank you for your response. I was able to successfully format the drives Extended journaled when they were out of the raid configuration. I was not able to format as Extended (not journaled) in the Raid configuration.

Similar Messages

HT4589 How can I get my Mac laptop FCPX Events Library to see my external drives? Yes it is formatted Mac-OS-Extended (Journaled)

How can I get my Mac laptop FCPX Events Library to see my external drives? Yes it is formatted Mac-OS-Extended (Journaled).

I do not seem to have that as an option. Attached is a screen shot with the gear popup open. I simply copied the event and projct folders from my desktop so I could contiue working while on a trip with my laptop.

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.

HT201250 Will Time Machine wipe my external hard drive if its formatted Mac OS Extended (Journaled)?

I want to use Time Machine to back up my mac. I have heard that it will wipe the HDD if its not formatted correctly. Disk utility says its
Mac OS Extended (Journaled). Is this alright? or will it wipe it?

Yes, if you use Disk Utility to reformat the drive or assign that drive to TimeMachine it will wipe all existing data off the drive/partition.
Like was mentioned, only use one drive for TimeMachine and preferably another one for a bootable clone.
Most commonly used backup methods

I've bought Mountain Lion but my iMac's HD isn't the correct format (Mac OS Extended(Journaled) instead of GUID partition what do I do?

Can I just back up to Time machine, then reformat disk then re down load?

As mende1 stated, the two are different and must be both.
If you open Disk Utility and select the hard drive (the type, size, and serial number), not the volume (Macintosh HD), it will tell you at the bottom of the screen what the Partition Table is. It should be GUID. If not, then you will need to back it up, then repartition the drive. Also, copy the Mountain Lion installer onto another drive so you don't have to download again. It is in the Applications folder.
There are a few methods to get back where you are, including wipe, install old OS, restore from TM, install ML.
You might search the web for a tutorial on creating a boot/install disk using the Mountain Lion installer.
Another easy way is to use something like Carbon Copy Cloner or SuperDuper to clone your current OS onto another drive. Then, boot using the external you cloned. Use Disk Utility to re-partition the internal drive as noted below, then Clone your current OS back to the internal. Then, use the installer you tucked away to reinstall.
If running Snow Leopard, you need to boot using your install disk, then open Disk Utility.
If running Lion, you need to boot into the Recovery HD by holding down cmd-r on restart.
From there, open Disk Utility, select the hard drive, then the Partition tab.
Select 1 partition from the partition layout dropdown (or however you'd like, just don't use current).
Set the Name of the disk. Macintosh HD is the norm, but you can name it anything you want.
Set the Format to Mac OS Extended (Journaled)
Click the Options Button.
Set the Partition Table to GUID Partition Table.
Back on the partition tab, click Apply.

Finder cannot see AirPort Time Machine drives

I'm running OS X 10.9.4 on a MacBook Air (2 GB memory, 64 GB SSD storage).
I'm using an AirPort Time Capsule (with Time Machine) as my router and backup. I have an additional hard drive connected to the USB port on my AirPort Time Capsule.
For over a year the entire configuration has worked well: Backups are done, and I can access both the AirPort Time Capsule internal hard drive and the external hard drive from my MacBook Air, and from any other device on the network.
For the past few weeks, Finder (on my MacBook Air) sometimes cannot see either drive (internal or external) on the AirPort Time Capsule. Backups are still okay, and PCs are still able to access and use both drives on the AirPort Time Capsule. Also, software on my MacBook Air CAN see and use the drives. For example, if I have a photo on one of those drives that I want to post on Facebook, the "finder" window that appears when I click "Upload Photos/Video" (on Facebook) sees the drives, and can upload the photo from the drives. The ONLY time I cannot see the drives is when I try to access them with Finder. (See photos.)
At first, Finder occasionally could not see the drives, or sometimes it took a minute or two to see the drives. Now, Finder generally cannot see the drives, no matter how long I wait. My PCs, and ALL SOFTWARE on the MacBook Air CAN ALWAYS see the drives. Also, Finder can ALWAYS see ALL THE OTHER shared drives on the network (on the PCs, for example), even when it cannot see the drives on the AirPort Time Capsule.
Can anyone tell me what is going on?
Using Finder:
Using Facebook:

With the shared folder open, select
View ▹ Show View Options
from the Finder menu bar. In the dialog that opens, select
Arrange by: None

Migration Assistant Does not see my Time Machine Backup disk

I have a TM backup disk connected via Firewire that I have several months of backup on. I did a clean install of SL. When I went to restore using Migration Assistant, the MI does not show the TM backup disk. The disk is mounted and visible through the finder. Time Machine itself sees the disk just fine. But when I run MI, the only drive it shows me is the one where the new SL is installed.
I found another post describing the same situation and the solution there said to make sure that the TM disk is formatted the same way, ie GUID. I check with Disk Utility and both the SL volume and the TM volume are formatted GUID.
HELP!

sorry, i don't know what else it could be then. if you have another external drive you can try doing a full system restore from the TM backups onto that drive and see if MA will recognize that drive and migrate from it. other than this there is always manual migration. slow and tedious but it can be done. see this link for help with that
http://discussions.apple.com/message.jspa?messageID=6185507

Airport Extreme connected drive does not appear in Time Machines drive list

I have two Macbook Pros. Both have 500GB hard drives. I have an airport Extreme with a WD terabyte hard drive and a HP printer attached via USB cable. Both Macbooks can access the WD HD & internet.
One MacbookPro has time machine set up to use the Terabyte HD as backup.
I want the other MacbookPro to also use this terabyte drive for backup.
But when I try to set up Time Machine to use the drive, the drive does not appear in the backup drive list.
What can I do to fix this? I had a HD crash on the non-backed up Macbook recently. I desperately need it to be backed up!
Any ideas?

Does the drive show in Disk Utility? Try a restart.

Migration assistant does not see my time machine disk

I had an issue with my hard disk on my imac in which I had to re-format and reinstall the OS. Since 10.7 is not available as a "rescue reinstall disk", I had to reinstall 10.6. When that finished, the install asked if I would like to transfer my stuff from Time Machine. I said "yes". Unfortunately, my time machine disk does not show up! Migration Assistant thinks my "macintosh HD" system disk is the only disk available as the time machine backup. So I skipped migration. I went ahead and did all of the OS upgrades to get back to 10.7.3. I re-connected all external disks (I have 4-the time machine disk included) and tried migration assistant again. The only disk migration assistant still thinks is available as the time machine backup is the macintosh HD system disk, not the one called "Time Machine Backup". Time machine backup is a western digital 2TB usb 2.0 disk.
So....
I decided this morning to re-do everything again (since I still could not get my data back). Guess what?!?! the same thing is happening! Migration Assistant thinks that the macintosh HD is the time machine disk and does not see any others - even though the disk is there and mounted!
Please help! I would like my data back, but I am not able to pay Apple at the Apple store or a phone call to them for help!
Thanks!
Diana

Diana Stephens wrote:
Migration Assistant thinks my "macintosh HD" system disk is the only disk available as the time machine backup.
Those are your backups. Migration Assistant shows the name of the disk and system that were backed-up, not the disk they're on. It will not show the disk you're running from.
See the tan box in Using Migration Assistant on Lion.

Exclamation marks next to songs, but I can no longer find them on my harddrive

I have a Win 7 laptop and an old 30GB ipod. Both iTunes and iPod software are up to date. I download songs from CDs that I own and they appear in the proper iTunes folder. However, after I sync my ipod, many of these songs suddenly get an exclamation mark next to them in iTunes and I can no longer find these songs on my hard drive anywhere. In some cases, only a couple songs from a CD get the exclamation mark and disappear and in other cases it is the entire CD. Why is this happening and where are the songs that I downloaded? These is happening over and over. What is the fix?

This means iTunes can't find the location of the files. Try these articles:
http://support.apple.com/kb/TS1967?viewlocale=en_US
http://support.apple.com/kb/TS1408?viewlocale=en_US
Hope these helps my friend.

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?
--Bob

Well 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

How do I access photos stored using Time Machine on a back up disk from an old Mac without importing the whole library to my new mac?

I just bought a MacBook Air and don't want to store all my photos on it. I'd like to be able to store and access them on a separate back up disk but iPhoto won't allow me to access these saying:
"The iPhoto library is a Time Machine backup, and so cannot be used as the main library. Reopen iPhoto with the Option key held down to choose another library."
Can I use my back up disk to store my photos? If not, how do I get my photos from iPhoto onto my back up disk?
Would love any help!
Thanks in advance :-)

You need to first restore the Time Machine back up. This excuse a TM back up is condensed and fragmented and so it needs to be expanded and reassembled before iPhoto can understand it.
After that, moving the Library is simple:
Make sure the drive is formatted Mac OS Extended (Journaled)
1. Quit iPhoto
2. Copy the iPhoto Library from your Pictures Folder to the External Disk.
3. Hold down the option (or alt) key while launching iPhoto. From the resulting menu select 'Choose Library' and navigate to the new location. From that point on this will be the default location of your library.
4. Test the library and when you're sure all is well, trash the one on your internal HD to free up space.
Regards
TD

Lion Install thinks that the system disk "Macintosh HD" is not Mac OS Extended (journaled); it is. Exactly what do I do in Disk Utility to "reformat" the disk, I don't see that listed on the menus.

Error Message, during installation of Lion; “This disk is not formatted as Mac OS Extended (journaled). Use Disk Utility to enable journaling or reformat the disk.” The disk I selected to install OS X on, was the only one listed, “Macintosh HD”. The results of a Disk Utility check are; Format: Mac OS Extended (journaled), Name: Macintosh HD. There is a fresh Time Machine backup. The computer was Restarted and installation attempted again - same result. I have downloaded Lion a second time, and tired install again, same results. The computer is a December 2007, iMac 24” with 2.4 GHz Intel Core 2 Duo, 4 GB Memory, s/w version 10.7.5; Disk Capacity 319 GB, Available 117 GB. Macintosh HD has alway been the system disk, does it now have an identity crisis? Would reformatting the disk mean Erasing it? Exactly what do I do in Disk Utility to “reformat” the disk, I don’t see that listed on the menus. This computer is getting cranky, I no longer Shut Down at night, only Sleep. If it’s Shut Down, the next morning I am treated to a white screen, for a long time, before it finally shows me the Log On Screen. Suggestions would be appreciated.

RRFS - This took me a long time to finally get to a fix. Your reply led me to investigate the Repair Disk Partition - as it turned out there wasn't one; the HardDrive was going bad slowly. The 10 to 40 minutes it took to startup in the morning, was the HD trying to find it's way. I had the 320GB HD replaced with a 2TB HD. All is OK now. Thank You very much!! Also, the Apple store geeks couldn't make it better but the locally owned Apple retailer did just great with it. from San Luis Obispo County - Peace.

Mac OS extended journaled drive cannot be written to

I have two WD MyBook external drives that are formatted Mac OS extended journaled. Permissions are set for owner to write to the drive. I am the owner. Carbon Copy Cloner and Time Machine write to the drives regularly. When I attempt to copy a file to the drive a small window opens telling me "The item is not writeable. You do not have sufficient permissions to write to the item."
Any help in understand what's going on here would be greatly appreciated.

Try trash the com.apple.iPhoto.plist file from the HD/Users/ Your Name / library / preferences folder.
(On 10.7 or later: Hold the option (or alt) key while clicking on the Go menu in Finder to access the User Library)
(Remember you'll need to reset your User options afterwards. These include minor settings like the window colour and so on. Note: If you've moved your library you'll need to point iPhoto at it again.)
What's the plist file?
For new users: Every application on your Mac has an accompanying plist file. It records certain User choices. For instance, in your favourite Word Processor it remembers your choice of Default Font, on your Web Browser is remembers things like your choice of Home Page. It even recalls what windows you had open last if your app allows you to pick up from where you left off last. The iPhoto plist file remembers things like the location of the Library, your choice of background colour, whether you are running a Referenced or Managed Library, what preferences you have for autosplitting events and so on. Trashing the plist file forces the app to generate a new one on the next launch, and this restores things to the Factory Defaults. Hence, if you've changed any of these things you'll need to reset them. If you haven't, then no bother. Trashing the plist file is Mac troubleshooting 101.
Then try select it again.

Can not see the Time Capsule disc in Time Machine what can I do??????

I just set up my new TC with my MacBook Air. The Wireless network is working fine but I can not find (see) the TC hard drive on my MacBook air so I can not set up Time Machine to back up my stuff. :=(
Can someone help me with this... ?

As it was in the beginning, is now and ever shall be, world without end.. amen!!
Welcome to ML excellent standard networking.. I am awarding it the golden vista OS of the year.
Did you turn it off and on again??
Will no longer be the first phrase of all windows servicing.. it now extends to Macs as well.
Maybe an auto electrical clock where you setup a timed daily reboot.. !!
A mechanical one of course.. cannot trust those electronical versions.. they might use OS as reliable as Vista!!

Imovie not seeing partitioned time machine drive. I partitioned my TM 2GB and formatted Mac OS Extended (Journalled). These drives in iMovie have a Yellow exclamation mark and I cant access events. Can access in Finder?

Similar Messages

Maybe you are looking for