Get Spotlight to index a NAS disk?
Is it possible to get Spotlight to index a NAS disk? (Or should it do this normally but it's not working properly?).
I have a NAS disk permanently connected to my Mac (LaCie Ethernet Disk Mini) & every time I do a search on there it will churn away searching but not return any results.
Actually it seems like it might be a bug because as well as not returning any results once I've closed the Finder window it will still continue churning away searching (I can hear the disk activity).
It will continue until I reboot the computer.
OK, the Terminal is a the way that you access UNIX shell commands (the Mac command line interface). Instead of clicking on things you have to type the actual command into the "prompt" hit return, and then the shell executes the command. So you go to the Utilities folder and double click Terminal to launch it. Exactly what you see when it finishes launching will depend on how you have configured it, so it won't be exactly what I see, but there will be some words of encouragement and then the prompt, where you will type things:
Last login: Tue Mar 20 14:06:01 on ttyp1
Welcome to Darwin!
-bash:~francine$
The "$" is where you start typing, or you can copy and paste things in also. You would then type:
sudo mdutil -i on /Volumes/YOURDRIVENAME/
You must make sure everything you type is exactly as given, thus you may want to simply copy and paste this:
sudo mdutil -i on /Volumes/
and, making sure there is no space after that final "/" character, type the name of your drive exactly as it appears in Finder. If the name has any spaces in it be sure to surround it with quotes:
sudo mdutil -i on /Volumes/"MY FAT DRIVE"/
Then hit the Return key. You will be asked for your admin password, and given a little lecture (this is only delivered the first time you use a sudo command). The password you type is not echoed to the screen in anyway whatsoever, so type very carefully and when you finish hit the Return key again. You'll then get the notice that indexing is enabled. Type the word exit, hit Return, and then quit Terminal.
Francine
Francine
Schwieder
Similar Messages
-
Spotlight and indexing of other disk partitions
Hi,
I have the internal drive of my 12" PowerBook formatted into two partitions, a small maintenance partition that's running 10.4.8, and a main partition, that's running 10.5.2. While I don't have a problem with upgrading the maintenance partition to Leopard, after seeing this report, I'm wondering if it's not a good idea to have Tiger and Leopard installed on separate partitions of the same internal drive. This leads to my questions:
Question 1:
Is it true that booting into a Tiger installation will cause Spotlight to overwrite the index files that Leopard created on either (or both) partitions? If this is true, then it would seem that I should really upgrade the maintenance partition to Leopard to prevent complete reindexing whenever I switch startup drives from one partition to the other.
Question 2:
Is there any way that I can tell Spotlight on the maintenance partition to not index the main partition? I only boot into the maintenance partition to run tools to maintain the main partition, so I have no need for Spotlight when booted into the maintenance partition.
Question 3:
Even if I upgrade the maintenance partition to Leopard, is there any way that I can prevent each partition's installation from indexing the other?
Thanks,
KenI want to make sure that I have each partition's installation set up so Spotlight won't corrupt or redo what the other partition's Spotlight has already done.
You can't do that, which is why I ended up with the less than satisfactory solution I have. When you boot up Spotlight begins to run as part of the system activities. It then looks at every mounted drive. Each and every drive has an invisible Spotlight folder. In that folder are the instructions to Spotlight about whether the drive or any directories on the drive have been excluded from Spotlight, and also, if the drive is supposed to be indexed, then the indexes themselves are in that folder. Thus the command line instruction to turn Spotlight status on or off specifies the path to the particular drive. There is no way to "quarantine" the Tiger or Leopard Spotlight. Whichever version is running looks to see if any given drive is supposed to be indexed, and, if it is, indexes it. The two versions can read each others general instruction about whether or not something is supposed to BE indexed, but can't read each others actual indexes. So if the instruction is for indexing to be on, then the version of Spotlight running looks at the index, can't read the index from the other version, and so proceeds to create a new index.
You can either have Spotlight on or off for a particular drive, that information will be read by both versions of Spotlight and acted on accordingly. Thus I booted in Leopard, ran the command line to turn the status off on my Tiger drive, preventing the drive from being indexed in Leopard, and edited the /etc/hostconfig file for Tiger to disable the Tiger Spotlight. When I booted in Tiger Spotlight didn't run AT ALL, so it didn't re-do the indexing for either the Tiger or Leopard drive. As far as I've been able to figure out this is the best solution, since I am generally booted in Leopard.
If all I had done was to add the Tiger drive to the Leopard Privacy pane, when I booted in Tiger its Spotlight would run, consult the preference for its drive, see it wasn't supposed to index its own startup drive, look at the information on the Leopard drive, see that that drive was supposed to be indexed, be unable to read the index and create a new one. When I next booted into Leopard it would have to re-index its own drive because its index would have been over-written.
Hope that makes a nasty situation clearer. I pondered the conundrum for some time before coming up with a solution. When I am booted in Tiger (which is rarely) I have to remember to use EasyFind when I want to find something, and when I am in Leopard a search of the Tiger drive is "brute force" only, but it can be searched.
Francine
Francine
Schwieder -
Indexing of encrypted disk images permanently disabled in 10.8?
In the past, I've had no trouble forcing Spotlight to index my encrypted disk image, using the command in Terminal:
sudo mdutil -i on /Volumes/Encrypted_Data
After entering that command, my encrypted disk image was indexed and searchable using Spotlight.
A couple weeks ago I updated from Lion to Mountain Lion. Today I noticed Spotlight wasn't showing any results from my encrypted disk image. So went back to Terminal and entered the above command. Instead of successfully activating indexing, Terminal gives me this message:
/Volumes/Encrypted_Data:
Indexing disabled.
Is this procedure now impossible in Mountain Lion?
Is there any way to enable indexing of this encrypted disk image? I can't get it to work.
Thanks.I appear to have solved the problem to get Spotlight to index a disk image. My image was an encrypted disk image. I was able to get spotlight to work when it was new, but now Spotlight won't index it. Here is the solution that I found:
After double clicking and mounting disk the image, open Disk Utility, select the disk image file, then click unmount in the Toolbar. Wait until it is unmounted, then click mount again. Then go to terminal and try mdutil -sa . If it is still not enabled, try to sudo mdutil -i on option. The unmounting and remounting must be done everytime the image is opened. -
Can anyone indicate how I can get spotlight to index properly? I've tried suggestions such as:
Placing HD in Privacy and then removing.
Using mdutil to stop and restart indexing.
Cursing.
Here is an example of the system log:
Sep 6 08:10:25 birds-imac.home mds[35]: (/)(Warning) IndexQuery in bool preIterate_FSI(SISearchCtx_FSI *):Throttling inefficient file system query
Sep 6 08:10:27 birds-imac.home mds[35]: (/)(Warning) IndexQuery in virtual bool SISearchCtx_FSI::performSearch(struct PartialQueryResults *):Retried searchfs 4 times
Sep 6 08:42:20 birds-imac.home mds[35]: (/)(Warning) IndexQuery in bool preIterate_FSI(SISearchCtx_FSI *):Throttling inefficient file system query
Sep 6 08:42:28 birds-imac.home mds[35]: (/)(Warning) IndexQuery in bool preIterate_FSI(SISearchCtx_FSI *):Throttling inefficient file system query
Sep 6 08:42:33 birds-imac.home mds[35]: (/)(Warning) IndexQuery in virtual bool SISearchCtx_FSI::performSearch(struct PartialQueryResults *):Retried searchfs 4 times
I don't know what else to try.
Thanks,
TrajBirds-iMac:~ traj$ sudo opensnoop -n mdworker
Password:
UID PID COMM FD PATH
89 2110 mdworker 3 /dev/dtracehelper
501 2111 mdworker 3 /dev/dtracehelper
89 2110 mdworker 3 /dev/autofs_nowait
89 2110 mdworker -1 /var/empty/.CFUserTextEncoding
89 2110 mdworker 3 /dev/autofs_nowait
89 2110 mdworker -1 /var/empty/.CFUserTextEncoding
89 2110 mdworker 4 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support
89 2110 mdworker 4 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
89 2110 mdworker 4 /.vol/16777219/29166387/mdworker/..namedfork/rsrc
89 2110 mdworker 4 /.vol/16777219/29166387/mdworker/..namedfork/rsrc
89 2110 mdworker 4 /.vol/16777219/29166387/mdworker/..namedfork/rsrc
89 2110 mdworker -1 /Library/Sandbox/Profiles/mdworker-bundle.sb
89 2110 mdworker -1 /System/Library/Sandbox/Profiles/mdworker-bundle.sb
89 2110 mdworker 4 /usr/share/sandbox/mdworker-bundle.sb
89 2110 mdworker 5 /var/folders/zz/zyxvpxvq6csfxvn_n00000b400002s/C//sandbox-cache.db
89 2110 mdworker 4 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework
501 2111 mdworker 3 /dev/autofs_nowait
501 2111 mdworker 4 /Users/traj/.CFUserTextEncoding
501 2111 mdworker 4 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support
501 2111 mdworker 4 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Versions/A/Support/mdworker
501 2111 mdworker 3 /dev/autofs_nowait
501 2111 mdworker 4 /Users/traj/.CFUserTextEncoding
501 2111 mdworker 4 /.vol/16777219/29166387/mdworker/..namedfork/rsrc
501 2111 mdworker 4 /.vol/16777219/29166387/mdworker/..namedfork/rsrc
501 2111 mdworker 4 /.vol/16777219/29166387/mdworker/..namedfork/rsrc
501 2111 mdworker -1 /Library/Sandbox/Profiles/mdworker-bundle.sb
501 2111 mdworker -1 /System/Library/Sandbox/Profiles/mdworker-bundle.sb
501 2111 mdworker 4 /usr/share/sandbox/mdworker-bundle.sb
501 2111 mdworker 5 /var/folders/z2/mf6zt6m16cb_ztb6pmxmtn7m0000gn/C//sandbox-cache.db
501 2111 mdworker 4 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework
89 2110 mdworker 4 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Resources
89 2110 mdworker 4 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Resources/English.lproj
89 2110 mdworker -1 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Resources/Base.lproj
89 2110 mdworker 4 /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Resources/schema.plist
89 2110 mdworker 4 /usr/share/icu/icudt49l.dat
89 2110 mdworker 4 /Library/Spotlight
89 2110 mdworker 4 /Library/Spotlight
89 2110 mdworker -1 /Library/Spotlight/en.lproj
89 2110 mdworker -1 /Library/Spotlight/Base.lproj
89 2110 mdworker 4 /Library/Spotlight/GBSpotlightImporter.mdimporter
89 2110 mdworker 4 /Library/Spotlight/GBSpotlightImporter.mdimporter/Contents
89 2110 mdworker 4 /Library/Spotlight/GBSpotlightImporter.mdimporter/Contents/Info.plist
89 2110 mdworker 4 /Library/Spotlight/GBSpotlightImporter.mdimporter/Contents/MacOS/GBSpotlightImp orter
89 2110 mdworker 4 /Library/Spotlight/GBSpotlightImporter.mdimporter/Contents/Resources
89 2110 mdworker 4 /Library/Spotlight/GBSpotlightImporter.mdimporter/Contents/Resources
89 2110 mdworker 4 /Library/Spotlight/GBSpotlightImporter.mdimporter/Contents/Resources/English.lp roj
89 2110 mdworker -1 /Library/Spotlight/GBSpotlightImporter.mdimporter/Contents/Resources/Base.lproj
89 2110 mdworker 4 /Library/Spotlight/GBSpotlightImporter.mdimporter/Contents/Resources/schema.xml
89 2110 mdworker 4 /Library/Spotlight/GBSpotlightImporter.mdimporter/Contents/Resources/English.lp roj/schema.strings
89 2110 mdworker 4 /Library/Spotlight/GBSpotlightImporter.mdimporter/Contents/MacOS/GBSpotlightImp orter
89 2110 mdworker 5 /Library/Spotlight/GBSpotlightImporter.mdimporter/Contents/MacOS/GBSpotlightImp orter
89 2110 mdworker 4 /var/folders/zz/zyxvpxvq6csfxvn_n00000b400002s/C//mds/mds.lock
89 2110 mdworker 6 /var/folders/zz/zyxvpxvq6csfxvn_n00000b400002s/C//mds/mdsObject.db_
89 2110 mdworker 7 /private/var/db/mds/system/mdsObject.db
89 2110 mdworker 6 /var/folders/zz/zyxvpxvq6csfxvn_n00000b400002s/C//mds/mdsDirectory.db_
89 2110 mdworker 7 /private/var/db/mds/system/mdsDirectory.db
89 2110 mdworker 6 /var/folders/zz/zyxvpxvq6csfxvn_n00000b400002s/C//mds/mdsObject.db
89 2110 mdworker 6 /System/Library/Security
89 2110 mdworker -1 /var/empty/Library/Security
89 2110 mdworker 4 /var/folders/zz/zyxvpxvq6csfxvn_n00000b400002s/C//mds/mdsDirectory.db
89 2110 mdworker 4 /System/Library/Keychains/EVRoots.plist
89 2110 mdworker 4 /etc/localtime
89 2110 mdworker 4 /Library/Spotlight/GBSpotlightImporter.mdimporter/Contents/Info.plist
89 2110 mdworker 4 /Library/Spotlight/GBSpotlightImporter.mdimporter/Contents/MacOS/GBSpotlightImp orter
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Application.mdimporter/Contents/version.plist
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Application.mdimporter/Contents/_CodeSignature/Co deEntitlements
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Application.mdimporter/Contents/Resources/English .lproj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Application.mdimporter/Contents/Resources/English .lproj/English.lproj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Application.mdimporter/Contents/Resources/Base.lp roj/English.lproj
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Info.plist
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/MacOS/Archives
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/English.lp roj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/Base.lproj
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/MacOS/Archives
501 2111 mdworker 5 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/MacOS/Archives
501 2111 mdworker 4 /Users/traj/Library/Preferences/com.apple.security.revocation.plist
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/tr.lproj
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/uk.lproj
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/zh_CN.lpro j
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/zh_TW.lpro j
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/version.plist
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/_CodeSignature/CodeE ntitlements
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/Dutch.lpro j
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/English.lp roj/Dutch.lproj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/Base.lproj /Dutch.lproj
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/English.lp roj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/English.lp roj/English.lproj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/Base.lproj /English.lproj
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/French.lpr oj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/English.lp roj/French.lproj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/Base.lproj /French.lproj
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/German.lpr oj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/English.lp roj/German.lproj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/Base.lproj /German.lproj
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/Italian.lp roj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/English.lp roj/Italian.lproj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/Base.lproj /Italian.lproj
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/Japanese.l proj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/English.lp roj/Japanese.lproj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/Base.lproj /Japanese.lproj
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/Spanish.lp roj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/English.lp roj/Spanish.lproj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/Base.lproj /Spanish.lproj
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/ar.lproj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/English.lp roj/ar.lproj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/Base.lproj /ar.lproj
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/ca.lproj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/English.lp roj/ca.lproj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/Base.lproj /ca.lproj
501 2111 mdworker 4 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/cs.lproj
501 2111 mdworker -1 /Users/traj/Library/Spotlight/Archives.mdimporter/Contents/Resources/English.lp roj/cs.lproj
501 2111 mdworker -1 -
How to get Outlook email indexed by Spotlight after reinstalling Office 2011?
I reinstalled Office 2011 and my Outlook email index stopped updating. I forced a reindex of the entire drive, but the email still wasn't indexing. Stopped by the Genius Bar and they suggested reindexing the drive and repairing permissions (didn't work).
Hi
As per the information and details provided by you, to get Outlook email indexed by spotlight after reinstalling Office 2011, please follow these steps: -
Outlook provides a custom importer to Spotlight to index email. It is typically found in:
"/Applications/Microsoft Office 2011/Microsoft Outlook.app/Contents/Library/Spotlight/Microsoft Outlook.mdimporter",
You can use the command
/usr/bin/mdimport –L to list all installed importers. When I did that I saw that the importer from the old installation of Outlook was still installed because it was still in the trash can. When I tried to manually import an email using the
command usr/bin/mdimport –d2 /[ path ]/x00_138.olk14Message I saw that it was failing to load the importer from the trash.
Emptying the trash fixed the issue. Wish there was a way to selectively empty the trash without deleting everything.
Once I emptied the trash, had to force Spotlight to reindex the email folder by adding the /Users/jim/Documents/Microsoft User Data folder to Privacy
tab of Spotlight System Settings, and then removing it again. After spotlight reported the indexing was complete (via the Spotlight dropdown in the upper right) the email was all indexed again.
I hope this information will be helpful for you.
Thanks and regards
Shweta@G -
HT204014 How can I get spotlight search to work over a network running OS X Server?
I have installed OS X Server on an iMac to share its files over a network.
I can access the files fine, but if I try and search the shared folders from another Mac on the network it yields no results.
How can I get search to work as well as it does on the files on local disks.Spotlight searching of shared volumes works for me using OS X 10.10.3 Server and OS X 10.10.3 client, as follows:
If I use Spotlight to search for some content "Aaron Aardvark" the file that contains this text does not seem to show up in the immediate results, but if I select "Show All in Finder" and switch from "This Mac" to "Shared" the file "untitled text.txt" that contains it is listed.
In the past Spotlight was responsible for bringing servers to their knees, so I suspect that the above two-step process is a way of limiting server searches to cases where it is actually required.
Server 4.1 (OS X 10.10.3) seems to add the extended attributes needed to allow Spotlight to index sharepoints:
test_server3:~ admin$ ls -el /Volumes/Server\ 3\ Users/
total 0
drwxr-xr-x+ 4 admin staff 136 30 Apr 17:02 Server 3 Users
0: user:_spotlight inherited allow list,search,file_inherit,directory_inherit
test_server3:~ admin$
but in the past, e.g. Snow Leopard server, you could choose whether or not these attributes were set or not. IIRC Snow Leopard clients would always include server volumes in Spotlight searches, causing significant slow-downs on the client, so a lot of sysadmins, myself included, chose not to enable it.
C. -
Spotlight NOT Indexing or SHOWING files? Nothing shows IN PRIVATE
Being stupid and doing something without knowing what would happen, I read a tip on battery life to add the HD or folders to PRIVACY to TURN OFF INDEXING.
Well now, nothing happens when I search. Of course, as it was, when I went to PRIVACY, nothing shows up as listed (OMIT) and I have tried adding to privacy, of course, nothing shows up, so I can't add it then delete it - nothing happens when I add something to privacy.
I can not get spotlight to work, I have tried OYNX the mac utility that had a RESET INDEXING and nothing happens.
Please, there must be a way to turn INDEXING back on and or seeing the FILES that are being omitted, (ARE THEY HIDDEN?) - please help, have tried booting to safe and running disc utility but after 10 minutes of watching the DISC UTILITY NEVER FIND THE HARD DRIVE, I got fed up.
Please tell me there is another way (besides disc utility, waited 10+ minutes).
Thankshave tried booting to safe and running disc utility but after 10 minutes of watching the DISC UTILITY NEVER FIND THE HARD DRIVE, I got fed up.
Uhm, was this a spinning radian you're talking about? That is trying to repair your HDD.
I booted to external (Target mode, Leopard) ran disk util on macbook pro TIGER HARD DRIVE, it said it was going to take 2 hours to repair.
Opps, you may have real problems now. Forget that, use your Tiger Install Disk to repair your Tiger Mac.
1. Insert the Mac OS X TIGER Install disc that came with your computer, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, *you must select your language first.)*
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume.
6. Click Repair. Disk Utility checks and repairs the disk.
Then Safe Boot off the HD & use Disk Utility from there to Repair Permissions, reboot once more.
Wondering if the reason the PRIVATE never showed up was due to it not having enough time to display?
Nope, your HDD/OS is messed up.
Man I am so upset about that TIP, they should warn you that its going to do something like that.
That tip is a simple operation & should not cause any problems, you had serious problems before trying that tip, you just hadn't noticed anything other than the not searching apparently.
Will repairing disk permissions work? (albeit 2 hours, from my Leopard Target Mode).
Repair the HDD before Repairing Permissions, and +DO NOT+ do either from a Leopard Disk. -
Spotlight trouble indexing mail in Lion
Having a terrible time with Spotlight perpetually indexing mail.
system log shows
Jul 11 17:01:26 xxxxx com.apple.mdworker.lsb.0[2660]: [Assigning new unique identifiers to all messages]
Jul 11 17:01:26: --- last message repeated 249 times ---
and of course All messages shows every one of those.
also plenty of messages like
Jul 11 17:03:02 xxxxx com.apple.mdworker.lsb.0[2660]: %Unterminated mailbox: [email protected].
Jul 11 17:03:02 xxxxx com.apple.mdworker.lsb.0[2660]: %Unexpected characters at end of address: :;>
Jul 11 17:03:02 xxxxx com.apple.mdworker.lsb.0[2660]: %Unterminated mailbox: [email protected].
Jul 11 17:03:02 xxxxx com.apple.mdworker.lsb.0[2660]: %Unexpected characters at end of address: :;>
Jul 11 17:03:04 xxxxx com.apple.mdworker.lsb.0[2660]: %Missing parameter value: NAME
Jul 11 17:03:04 xxxxx com.apple.mdworker.lsb.0[2660]: %Missing parameter value: FILENAME
-- those seem to be ridiculous errors for Spotlight -- if it can't figure out how to parse some of the info, it should ignore that info.
This continues until the disk cache gets totally overloaded, and the machine slows down.
Only help is to reboot.
I have tried turning off spotlight indexing to delete the spotlight cache (and used Cocktail to delete the Spotlight index)
That was no help.
Also rebuilt all of the mailboxes within the Mail program.
Then turned indexing off and back on.
Still no help.
Just tried deleting a couple of old mailbox entries in ~/Library/Mail
There was an old Unix mailbox there from an early version of OS X, and another one that I could not identify, and should have been deleted long ago.
I know I can turn off the indexing for mail, but that is one area where I would like to keep it.
I haven't tried a reboot since the latest deletes, but seeing the same messages flowing in the logs does not give me much hope.
It may be possible that 1 or 2 bad emails are causing all the trouble, but I am at a loss to find them.
Have 18 different accounts that are active ( I do web work so have webmaster, and other accounts on a number of servers).
Those are a mix of IMAP and POP.
INBOX total is usually kept around 100 emails - almost never goes above 200 unless I am away for an extended time.
Most mail ends up in folders ON MY MAC.
Largest of those has about 1500 messages.
Do not have extra folders on the servers with any of the IMAP accounts.
It is about time I archive some of the older messages, and that may help, but it will take me a while to get to that, and then flush the messages.
Problem occurred after update to Lion.
Did not seem to have the problem with Snow Leopard
Anyone have any other ideas?I thought I had posted a follow up to this posting, but I guess not.
Soooo, here it is.
The problem was not with Apple Mail.app as it seemed, but actually with Mailsmith.app.
I use it for a number of mail accounts that I want to handle separately from my other mail accounts.
Within that application there is a Spotlight helper/worker
-- /Applications/Mailsmith.app/Contents/Library/Spotlight/MailsmithImporter.mdimporter/ --
That is what was causing the problem for me.
Some users remove that section from the application, or do as I did -
Set the folders for Mailsmith mail for privacy in Spotlight.
Note: also set any backups of the Mailsmith mail for privacy also.
I filed a bug report with Mailsmith, but it is still open.
There appear to be a lot of issues with their Spotlight helper through the various versions of OS and Mailsmith.
see their discussion groups -
https://groups.google.com/forum/?fromgroups=#!searchin/mailsmith-talk/spotlight$ 20indexing
The problem may be with certain emails, attachments, or addresses, don't know.
I am happy excluding that mail from Spotlight, and now my logs don't overflow and crash, the machine goes into deep sleep, and runs much cooler. -
Repeated Corruption of Spotlight Database on Time Machine disk?
I'm going to try this here since I don't seem to get much traction with this question in the Time Machine forum, and there is no forum here specific to Spotlight issues in Leopard:
I've been seeing repeated corruption of the Spotlight database on my external, Fireware 800, LaCie drive which is used exclusively for Time Machine. The symptom is that searches done in the Finder window after entering Time Machine produce no results or partial results.
There is no problem with Spotlight on the main hard drive for my laptop.
I received instructions from AppleCare for how to find and delete the hidden folder which makes up the Spotlight database on that drive -- an action which causes Spotlight to immediately rebuild the database on that drive from scratch -- but within days after doing that the database is corrupt again.
An additional symptom is that errors appear in the Console during a reboot -- but only if the Time Machine drive happens to be attached during the reboot. If the drive is attached AFTER booting and logging in, no such errors appear. The errors are from the "mds" process, and indicate either that a portion of the Spotlight database's "Stores" folder is having problems "storing dirty pages", and/or that a portion of the Spotlight database needs to be "recovered". Once those error messages start to appear, they will appear (identically) on every reboot where the drive is attached. No "recovery" happens. And searches after entering Time Machine fail to produce full results as described above.
There are no other Console complaints that appear relevant. No corrupt files during Time Machine backups, no errors when having entered Time Machine to view or restore files, no errors during searches themselves while in Time Machine.
Attempting to rebuild the Spotlight datbase on that drive by dragging it into the System Preferences > Spotlight > Privacy list and then removing it are fruitless. Spotlight indexing fires up for only a couple seconds after removing the disk from Privacy and there is no change in the search failures. And no new error message are entered in the Console. The same thing happens when attempting to use the "mdutil" command from Terminal to force a rebuild (as instructed by AppleCare). Only completely trashing the hidden Spotlight database folder on that drive suffices to get Spotlight to rebuild the database from scratch and start over in a fresh, uncorrupted state. But that doesn't last!
Meanwhile, Time Machine backups themselves are working just fine. No errors -- everything seems to be getting over to the drive -- and viewing within or restoring from Time Machine continues to work without problem. That is, the problem is entirely and ONLY within Spotlight for the Time Machine drive. (Again, that drive is used only for Time Machine.)
And as stated above, Spotlight continues to work without issue on the main hard drive.
Disk Utility > Verify Disk also has no complaints about that Time Machine drive (or the main hard drive)
And the usual panacea cures (booting once in Safe Mode, reset PRAM, reset PCU, Repair Permissions) also have no effect on this problem.
The computer in question was an "upgrade" install from 10.4.10 and has two accounts on it -- a non administrative account for normal work and an Administrator account that is almost never used. Only the one drive, the main hard drive, is being captured by the Time Machine backups. Nothing has been excluded from the Time Machine backups. I've even done a successful "full restore" of the system from that Time Machine. I.e., this is all very plain vanilla stuff. I can't fathom why I'm having this problem.
My Time Machine dates back to after installing 10.5.1. I've tried the process of deleting, and thus recreating, the Spotlight database several times without any luck.
Yesterday, after applying the "Time Machine and Airport Drivers" update to my 10.5.2 system, I decided it was time for a fresh start just in case there was something about the data put onto the drive by the older, 10.5.1, Time Machine that was causing Spotlight such grief.
So I erased the Time Machine drive and did an entirely new initial backup.
That completed without errors.
I then did a few incremental backups on top of that. After which I did a reboot to see if there were any Console error messages from mds. There were none, and my tests of searches while viewing in Time Machine all produced correct and complete results.
So far so good.
However, this morning, after I booted up with the Time Machine drive attached, I went immediately into Console and found the dreaded error messages from the mds process. And sure enough my searches inside of Time Machine now only produce partial results again. Here are the two messages I'm getting at the moment (with personal information "xxx"d out):
3/20/08 1:48:48 PM mds[26] (/Volumes/xxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/4CE0F19E-8757-43F1-A5DD-06B1DCAD0E50)(E rror) IndexStore in SIStoreDirytySDBChunks:Error storing dirty sdb pages: 30
3/20/08 1:48:48 PM mds[26] (/Volumes/xxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/ABE285E8-4E3D-45BD-A3EF-D9A5B4A149DA)(E rror) IndexStore in SIStoreDirytySDBChunks:Error storing dirty sdb pages: 30
So far I have NOT yet seen the messages saying that the Spotlight database "needs recovery".
I'm at a loss on this one. Again, the Time Machine backups themselves seem to be fully complete and fully functional. And Spotlight was perfectly happy after the new, initial backup, and a few incremental backups.
But I just can't get Spotlight to STAY happy with this Time Machine drive.
Any suggestions?
--BobOK I've completed the repartitioning test and the results are unexpected! Here's what I did and what I've spotted so far:
First, the only differences between what I'm going to list here and what I've done before is the repartitioning of the drive and the fact that I decided to do things this time entirely while logged in to my Administrator account. In the past, I did this stuff logged into my "standard" account and supplying Admin passwords when requested:
@ Rebooted with the drive attached and logged in to Admin
@ In System Preferences > Time Machine, did a Change Disk to No Disk to turn off Time Machine backups.
Note: In what follows, each of the several times Time Machine asked me if I wanted to use the external drive as the new Time Machine drive I selected "Cancel".
@ Used Disk Utility to re-partition the Time Machine drive into 2 untitled partitions (Apple Partition Map since this is a Powerbook Mac, Mac OS X Extended (Journalled) formatting, Mac OS 9 drivers turned off). I then partitioned it AGAIN back to 1 partition titled as my Time Machine drive (same settings). I did this two step process to make SURE the partitioning data was actually being re-written.
@ Used Disk Utility to Erase the single partition just created -- using the option to Write 0's to the drive to make sure all of the drive was exercised.
@ Checked and found the Time Machine volume was now identified as disk1s3.
@ Used Disk Utility to Verify Disk on my main hard drive.
@ Checked in Console after all of this and there were no I/O or other errors logged.
The next few steps were done to maximize the chances that my new "initial backup" would be as clean as possible.
@ Shut Down the computer and rebooted once into Safe Mode to let the Safe Mode boot delete caches and do its other background maintenance tasks. Shut Down immediately from the Safe Mode login window instead of logging in.
@ Rebooted while resetting PRAM. Just because.
@ Logged in as Admin, and used Disk Utility to Repair Permissions on the main hard drive. No messages were generated by this.
@ Rebooted once again and logged back in as Admin to get things into a fresh state.
At this point I was now ready to start the new, Time Machine "initial backup". However before I did that I decided to check the Console one more time.
Imagine my surprise when I found one each of the two Spotlight related error messages I reported above! There was one "needs recovery" error and one error trying to "store dirty pages"! (Note that normally I see TWO of each of these.)
Keep in mind that the drive had just been freshly partitioned and then erased again. Time Machine had never been given access to the drive. And no other user applications had been run. And yet the Spotlight database was ALREADY generating errors on that drive!
Upon checking further, I discovered that the first pair of these error messages was generated during the Safe Mode boot above. They were generated again during the boot where I reset PRAM.
BUT, there were NO ERROR MESSAGES in the most recent reboot I had just completed!
At this point I decided to do a 2 more reboots and there were NO ERROR MESSAGES in either of those.
Curious indeed! Well perhaps some sort of recovery had happened.
In any event, at this point I decide to do the "initial backup".
@ In System Preferences > Time Machine, I selected the drive for Time Machine use and let the initial backup complete. I also had Console running during this. The backup completed without any significant messages. In fact one additional incremental backup also completed without errors before I noticed it was done.
At this point, I entered Time Machine and tried my usual test searches which have demonstrated the Spotlight corruption in the past, and there were no problems. Spotlight was apparently good.
I then rebooted and checked the Console and son of a gun but the Spotlight error messages were back -- this time 2 of each.
However, when I checked searches in Time Machine -- THEY WORKED! This is the first time I've ever seen a case where the presence of those error messages during reboot wasn't accompanied by search failures inside of Time Machine.
I immediately did another reboot -- AND NO ERROR MESSAGES!
I've since done several additional incremental backups and several reboots, and I can't find a pattern anymore. The error messages OFTEN appear on reboot (if the Time Machine drive is attached), but not ALWAYS as was the case in the past. And up to now searches inside of Time Machine are working without problems.
I can see several possible explanations:
1) The error messages are spurious (or there is some sort of automatic recovery that is working now when it didn't work before) and the repartitioning above actually fixed the problem.
2) The database is indeed corrupted, but the corruption has moved to a portion of the database that my test searches aren't exercising.
3) I need to do more incremental backups before the database corruption will actually become visible in my test searches. I.e., the problem just hasn't had time to develop yet.
Meanwhile I heard back from LaCie support that they have not heard of a problem like this for Time Machine or Spotlight on this particular drive. I've also pointed them at this thread for details.
So I'll just continue to use this Mac normally over the next few days, while periodically checking to see if the Spotlight search failures reappear and to see if I can spot any pattern as to why those Console error messages sometimes appear on reboot and sometimes not.
I'll report back when I have more info.
Again, if anyone has any insight into what those 2 Console error messages actually mean, or if anyone else is seeing those error messages, or is having Spotlight search failures when inside Time Machine whether or not you see those error messages, please chime in.
--Bob -
I am getting a message that states "startup disk is full". What does this mean and how do I fix it?
For information about the Other category in the Storage display, see this support article. If the Storage display seems to be inaccurate, try rebuilding the Spotlight index.
Empty the Trash if you haven't already done so. If you use iPhoto, empty its internal Trash first:
iPhoto ▹ Empty Trash
Do the same in other applications, such as Aperture, that have an internal Trash feature. Then restart the computer. That will temporarily free up some space.
According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation—not the mythical 10%, 15%, or any other percentage. You also need enough space left over to allow for growth of the data. There is little or no performance advantage to having more available space than the minimum Apple recommends. Available storage space that you'll never use is wasted space.
When Time Machine backs up a portable Mac, some of the free space will be used to make local snapshots, which are backup copies of recently deleted files. The space occupied by local snapshots is reported as available by the Finder, and should be considered as such. In the Storage display of System Information, local snapshots are shown as Backups. The snapshots are automatically deleted when they expire or when free space falls below a certain level. You ordinarily don't need to, and should not, delete local snapshots yourself. If you followed bad advice to disable local snapshots by running a shell command, you may have ended up with a lot of data in the Other category. Ask for instructions in that case.
See this support article for some simple ways to free up storage space.
You can more effectively use a tool such as OmniDiskSweeper (ODS) or GrandPerspective (GP) to explore the volume and find out what's taking up the space. You can also delete files with it, but don't do that unless you're sure that you know what you're deleting and that all data is safely backed up. That means you have multiple backups, not just one. Note that ODS only works with OS X 10.8 or later. If you're running an older OS version, use GP.
Deleting files inside an iPhoto or Aperture library will corrupt the library. Any changes to a photo library must be made from within the application that created it. The same goes for Mail files.
Proceed further only if the problem isn't solved by the above steps.
ODS or GP can't see the whole filesystem when you run it just by double-clicking; it only sees files that you have permission to read. To see everything, you have to run it as root.
Back up all data now.
If you have more than one user account, make sure you're logged in as an administrator. The administrator account is the one that was created automatically when you first set up the computer.
Install the app you downloaded in the Applications folder as usual. Quit it if it's running.
Triple-click anywhere in the corresponding line of text below on this page to select it, then copy the selected text to the Clipboard by pressing the key combination command-C:
sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper
sudo /Applications/GrandPerspective.app/Contents/MacOS/GrandPerspective
Launch the built-in 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 by pressing command-V. You'll be prompted for your login password, which won't be displayed when you type it. Type carefully and then press return. You may get a one-time warning to be careful. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator. Ignore any other messages that appear in the Terminal window.
The application window will open, eventually showing all files in all folders, sorted by size. It may take a few minutes for the app to finish scanning.
I don't recommend that you make a habit of doing this. Don't delete anything as root. If something needs to be deleted, make sure you know what it is and how it got there, and then delete it by other, safer, means. When in doubt, leave it alone or ask for guidance.
When you're done with the app, quit it and also quit Terminal. -
Yesterday I was erasing an external 40 gb hard drive through disk utility and the program seemed to have froze since it never updated the time remaining (53 minutes). That drive may have some bad sectors. So I just forced my computer to shutdown and unplugged my hard drive (via usb). Today morning when I started the computer, Spotlight was indexing my computer. Did i mess something up because I pulled the hard drive out? Or is this due to me copying 4 gb worth of files from the drive before erasing it? Ive heard that this done if a drive is failing, is that true?
Hard to tell, but in Spotlight's Pref Pane>Privacy tab, add all your drives to that to stop Spotlight from doing it's thing until you get it figured out.
Try Erasing the drive again with the Security option of Zero Data once. -
Time Machine never gets out of Indexing backup...
I had a problem with my iMac earlier today. My first instinct was to create a complete backup. But since then I've not been able to create a backup. Time Machine never gets out of Indexing backup...
Each time I try to backup the message log contains:
Starting standard backup
Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Backup content size: 253.8 GB excluded items size: 613.1 MB for volume Macintosh HD
303.83 GB required (including padding), 1.82 TB available
Waiting for index to be ready (101)
Waiting for index to be ready (101)
The tiny numbers in Activity Monitor suggest that Time Machine isn't really doing anything.
So far I have:
1. Verified my main hard disk and my original backup disk.
2. Bought a new external hard disk and set it up as a new backup disk.
3. Deleted the Spotlight files on my main hard disk and both the backup disks.
4. Reset Time Machine by deleting its .plist file and choosing the new backup disc again.
Given the failure earlier today I am really keen to get a full back up done.
Any ideas?
JohnJWaterworth wrote:
I had a problem with my iMac earlier today. My first instinct was to create a complete backup. But since then I've not been able to create a backup. Time Machine never gets out of Indexing backup...
Indexing the backup and actually performing the backup are two different things. Sometimes Lion Time Machine has trouble maintaining the index when used over a wireless network. That doesn't affect the creation of new backups. You can always enter Time Machine and see just how many backups you have.
The tiny numbers in Activity Monitor suggest that Time Machine isn't really doing anything.
After the initial backup, Time Machine doesn't take much CPU time.
So far I have:
3. Deleted the Spotlight files on my main hard disk and both the backup disks.
4. Reset Time Machine by deleting its .plist file and choosing the new backup disc again.
Please don't do things like this. What you need to do now is:
1) Boot from your recovery volume.
2) Repair your disk and permissions
3) Wait for Spotlight to finish reindexing your hard drive.
4) Erase your Time Machine drive and start Time Machine over again.
Come back if you are still having trouble. If you muck around with low-level files that shouldn't be mucked with, all bets are off. -
How I solved my Spotlight+ Mail indexing problem
OK, so I thought I would post my solution to a stubborn indexing problem, for people who may have the same issue (and it does seem many people do).
Problem: Spotlight index was unreliable. In particular, Spotlight was terrible at indexing mail. It could not find the messages by content that it would find by searching the "from" field, nor could it find those reliably. Unusable.
What DID NOT work:
-- adding and removing any folder whatsoever in the Privacy preferences of Spotlight. The index would rebuild, but with the same problems.
-- doing this via terminal (e.g, using sudo mdutil -E /Volumes/MyHardDisk)
-- using Onyx
-- using Spotless
-- simply reinstalling the system
-- manually modifying the plist files inside the .spotlight folder to add and remove the folders that would not get indexed.
What DID work:
-- first, I reinstalled the system. That's not such a big deal. Upgrade up to 10.4.6
-- then, I authorized the root user (that's probably not necessary) (this, you do by using Netinfo manager)
-- Then, I deactivated the index (via terminal:
sudo mdutil -i off /Volumes/MyHardDisk
-- now the tricky part. This concerns Mail, in particular.
I have a very complex mail folder (tens of thousands of messages). I noticed that inside each mail folder, I had two things that were not supposed to be there
1. a copy of each folder.mbox which was empty, but with the same name without the extension .mbox. This is probably something that was created while importing mail from Panther to Tiger, for what I can tell.
2. Most importantly, a file named ".index.ready". This also, apparently, was an old legacy coming from Panther. I suspect this was the main problem for the lack of indexing in Mail.
Ok, so... I deleted these folders and files. If you have a complex structure of subfolders, you can delete the files with an Unix command by first cd to your mail folder, and then use
find . -name \.index.r* -ok rm {} \;
which will ask you confirmation before deleting each file.
It was faster to remove the empty subfolders by hand, as they all had different names.
-- Ok, at this point, I erased entirely the .Spotlight-V100 directory which stays at the root of your computer. You can do it with a rmdir command from the terminal or, as I did, you can login as root (remember, we activated root), use a utility that allows you to see hidden files (e.g., Tinkertool), and move it manually to the trash folder.
Then I emptied the trash. For superstition, I restarted, and let the index be built again (that took about 5 hours in my computer, for an HD with about 60 gb occupied on it).
Now everything seems to work perfectly fine. I don't know whether this procedure can be shortened, but I do know that nothing else worked for me. I thought I would post it here as I spent sooo much time to solve this problem, and furthermore, I found that none of the suggested solutions would work.
OK, your responsibility to do it, if you want to do it. Hope nobody needs to!
Best to you all,
l.
Mac OS X (10.4.6)Thank you, thank you, thank you, Lucabo! Using ideas from your post, I also (at least for now) solved my Mail indexing problem. One day (not even after an upgrade) Mail just quit finding messages by content, even when I had open a message with that content!
What I did:
-- In System Preferences, told Spotlight to index only Mail (I just use grep from a Terminal window for everything else!)
-- Ensured Mail app wasn't running
-- Backed up my Library/Mail folder to an external disk
-- Turned off indexing via Terminal (after sudo sh), with
mdutil -i off /Volumes/MyHardDisk
-- Deleted old files in my mailboxes (inside the whatever.mbox folders):
.index.ready
mbox
tableofcontents
content_index
It was clear that mbox, tableofcontents, and content_index were left over from a previous version of mail - they hadn't been accessed since I upgraded.
Note that I didn't delete the whatever.mbox folders (just the plain mbox file inside)!
-- Deleted (in Terminal) the .Spotlight-V100 in the root directory
-- Restarted my Mac. The indexing started itself. Since I had it set up to index only Mail, it took about 3-ish hours to finish (I have 100s of 1000s of emails in thousands of folders).
After the indexing finished, all the test searches that I tried worked. From now on I will always be suspicious if search doesn't find anything!
Also, I just checked - using the Spotlight field on the menu bar now works better too. When the Mail search problem showed up, I tried using the Spotlight field and the Spotlight window, but they would just flash up a few items, remove the list, over and over, sometimes with the beachball, then finally settle to an empty list. Now the Spotlight field seems to work.
I infer that the Spotlight index gets corrupted, and that the Spotlight code doesn't notice that it's reading junk from the index...
BTW, about the same time that search quit working, some emails in my Inboxes got highlighted with a dark brown background color. Have no idea why. They aren't marked as Junk (the junk messages have the text in the usual lighter brown). But, when I select a message with the dark brown highlight, mark it as junk, then mark it as not junk, the dark brown highlight goes away. On some occasions, just quitting Mail and restarting makes the dark brown highlights go away - but not always. Sigh... at least it's not a show stopper, even if it is ugly!
Thanks again, Lucabo, for your post!
Mac OS X (10.4.6) -
I plug in my printer and I get a message that says, "the disk you inserted is not readable." It didn't do this before but after I installed a segate hardrive software. I have removed the segate hardrive software but the message still appears. What can I do to remove this error.
Please read this whole message before doing anything.
This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac.
These steps are to be taken while booted in “normal” mode, not in safe mode. If you’re now running in safe mode, reboot as usual before continuing.
Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects.
Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then copy it. The headings “Step 1” and so on are not part of the commands.
Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply.
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.
When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign.
Step 1
Triple-click the line of text below on this page to select it:
kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}' | open -f -a TextEdit
Copy the selected text to the Clipboard by pressing the key combination command-C. Then click anywhere in the Terminal window and paste (command-V). A TextEdit window will open with the output of the command. If the command produced no output, the window will be empty. Post the contents of the TextEdit window (not the Terminal window), if any — the text, please, not a screenshot. You can then close the TextEdit window. The title of the window doesn't matter, and you don't need to post that. No typing is involved in this step.
Step 2
Repeat with this line:
{ sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix)|org\.(amav|apac|cups|isc|ntp|postf|x)/{print $3}'; sudo defaults read com.apple.loginwindow LoginHook; sudo crontab -l; } 2> /dev/null | open -f -a TextEdit
This time you'll be prompted for your login password, which you do have to type. Nothing will be displayed when you type it. Type it carefully and then press return. You may get a one-time warning to be careful. Heed that warning, but don't post it. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step.
Step 3
{ launchctl list | sed 1d | awk '!/0x|com\.apple|org\.(x|openbsd)/{print $3}'; crontab -l 2> /dev/null; } | open -f -a TextEdit
Step 4
ls -1A /e*/{la,mach}* {,/}L*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts .la* 2> /dev/null | open -f -a TextEdit
Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting.
Step 5
osascript -e 'tell application "System Events" to get name of every login item' | open -f -a TextEdit
Remember, steps 1-5 are all copy-and-paste — no typing, except your password. Also remember to post the output.
You can then quit Terminal. -
Use of NAS disk for project material
I intend to buy a new computer. I have used and vill continue use a 2 TB NAS disk in the system to store photos, documents and videolips. It is a Synology DS111 with Gigabit Ethernet connection.
I will use this computer for videoediting. I have used Premiere Pro 1.5 before and DV material and even if the system was not very fast it worked until now. I will purchase Adobe Premiere CS6
I intend to include a 256GB SSD as system disk(Samsung 840 or similar) and a 128 GB SSD as scratch disk.
The rest of the computer will probably be
Intel Core i7 3770K 3,5Ghz (Ivy Bridge)
2x Corsair 8GB (1x8192MB) CL10 1600MHz VENGEANCE
Asus P8Z77-V
KFA2 GeForce GTX 660Ti 2048MB OC
I do not know how Premiere Pro CS6 handles files in runtime so my question is how much the NAS disk will be involved in video editing if I have Premiere Pro installed on the system disk (SSD) and use the second SSD for scratch disk. Video clips will be on the NAS.
Can the videoediting still be fast when rendering and exporting contents except that final storage to NAS will not be lightspeed fast. Any comments on this usage are highly appreciated.
/StefanStefan,
I'm not sure from your post whether your plans are to continue working solely with DV video or whether you have some plans in the future for HD formats.
In any case, I think that you would be much better served by making changes to both your hardware plans and workflow more along the lines of the following:
Single 128GB Samsung 840 Pro (don't get the std. 840, its writes are much slower) - OS/Programs; if you turn off the hibernate feature 128GB should provide plenty of space
Two 1TB 7200 rpm drives and either spread the load (projects and media on one and scratch / cache / outputs on the other) or RAID 0 them and put all files on the RAID array
Do nightly backups of media and project files to your DS111 (orgainze your directory structure so scratch, cache, and output files can be easily ignored from the backup)
This plan with give you way more speed and improved redundancy as well (as the DS111 is only a single drive unit).
With your new faster system you would probably enjoy using the local drives for photo editing work as well, especially if you go with the 2x RAID 0 array option.
Finally, you should probably increase the RAM of your new build to 32GB; what Windows 7/8 does not use for programs is does use for disk caching and that tends to speed things up for photo and video editing workflows.
Regards,
Jim
Maybe you are looking for
-
Powerbook to HDTV. Need cable help.
I'm looking to hook up my early model Powerbook 12 (the one with the the 867mhz processor) to my Sony Bravia hdtv. Half an hour of googling has yielded this: my powerbook outputs video using some archaic **** called mini vga and there is no easy way
-
Understanding velocity control on 9505 FPGA VI
I was able to quickly use the 9505 Servo Drive example to do closed loop position control on the FPGA but I'm having trouble with figuring out how to modify the code to support velocity control (which I need for a different axis). I'm trying to make
-
Hi all, I am using a database link from between oracle 10g enterprise & oracle 10g express edition on window based system. We are getting below given error at one client system and others clients system is working fine.. ORA-02068: following server e
-
My iphone 4s keeps on crashing/restarting on iOS 7. How can i fix this?
After i've updated my Iphone 4s to iOS7, it keeps on restrting. the screen suddenly turns dim and turns to black and restarts. is there any possible way to fix this?
-
Mods, please, do visit and comment
All Mods, I don't know how many and how mods operate here, but if you see number of useful replies by Moderators in 3000 notebook forum during last week, customers tend to feel estranged. There are many issues which only Mods can understand, answer o