Finder search results are broken aliases

This is a huge issue for Mac users adnit is amazing that it has taken this long and still no answer from MAC - the productivity loss and time cost to work aroudn this issue is huge and is hitting critical. MAC are you listenting and are you solving this?

You shoudl eb able to save to it. just liek normal, or drag and drop it on the drive. Are you having problems seeing the drive or opening it and viewing the content? I don;t think that is what this is about, just searching files. They come back as broken aliases. That would be a differnt issue if you can't see your drives or content.

For me is different, I can't access the external drive when accessing from the Finder and it shows the exact same error. I have encounter the same error in different cases and anyone has a way to fix it. It seems is the error Apple shows whenever they don't want to fix something.

I have a Mac that is having the same issue with seeing search results from a brand new Windows server. The OS. on the iMac is. 10.13.1.

Not updating to 10.13.2 because another client is having issues moving folders on the server via SMB with 10.13.2. Finder crashes and has to be hard restarted to get the computer to work again.

Let me know if anyone finds a solution.

Added this issue to the comments section on MacRumors about the 10.13.3 update to ask if anyone trying it saw the issue gets fixed. Seem to not be fixed in the 10.13.3 beta.

https://forums.macrumors.com/threads/apple-seeds-second-beta-of-macos-high-sierr a-10-13-3-to-developers.2095775/

I'm having issues too - whole office of imacs not able to automatically connect to the share (tried using script and dragging to login items) and broken aliases when searching - everything works great from my 2017 MBP, which ironically enough also has high sierra on it!

Ugh :-( Just discovered I have the same problem after moving all my documents and files to a Synology NAS, connected via SMB. Will try if the suggested tool works. Don't know why Apple doesn't repair this, it's asked around all over the internet. Also I notice that SMB is way slower then AFP; both are slower then using SMB from Windows or Linux machines. Oh well, I guess I have to learn to live with it... :-/

I had the exact same problem and I could fix it by erasing and rebuilding the spotlight index for all network shares affected.

What I did was:

1 - Rebooted my mac.

2 - After a clean boot, I connected to one of my network shares.

3 - Launched Terminal and checked the spotlight indexing status for the share using "mdutil -s /Volumes/networksharename".

If it's on, proceed to step 4.

If it's off, you have to enable it using "mdutil -i on /Volumes/networksharename". Once you do so, it'll start indexing, but I recommend performing the next step anyway.

4 - Still in Terminal, executed "mdutil -E /Volumes/networksharename" to erase and rebuild the spotlight index for that share.

5 - Launched Activity Monitor to check the indexing processes (mds, mdworker, etc). Once they were done, the problem was solved.

Hope it helps 😉

Hi,

I have High Sierra and a Synology connected via iSCSI using globalSAN. The LUN is formatted NTFS using Paragon NTFS for Mac. When I search even for a file that is displaying in finder (I'm in that folder) the resulting search is just a broken alias. The error message is as everyone else. Trying to repair the alias fails with an error -8060 code.

I think it is an error with searching in an NTFS file system and not an SMB issue. I'm using an iSCSI drive so it is not presented as SMB. I think iSCSI has it's own networking connection, right?

Please help the community and fix this bug.

Hi,

I have High Sierra and a Synology connected via iSCSI using globalSAN. The LUN is formatted NTFS using Paragon NTFS for Mac. When I search even for a file that is displaying in finder (I'm in that folder) the resulting search is just a broken alias. The error message is as everyone else. Trying to repair the alias fails with an error -8060 code.

I think it is an error with searching in an NTFS file system and not an SMB issue. I'm using an iSCSI drive so it is not presented as SMB. I think iSCSI has it's own networking connectionPlease help the community and fix this bug.

This is working for me. I had to use:

"sudo mdutil -E /Volumes/sharedvolumename", instead of "mdutil -E /Volumes/sharedvolumename", but this has now indexed the shared drive.

Also, the index is updating itself for files created since I performed the original indexing command files - the Search Results are including these new files. This indicates to me that indexing is now ongoing.

Hope this helps anyone else experiencing this issue.

All the best.

I am not a IT guy just a user, I have this issue myself: when you say run this: "sudo mdutil -E /Volumes/sharedvolumename" is that the thing to run in terminal or is there a name that I replace "sharedvolumename" with, because I get "

Michaels-MBP:~ EwingWorks$ "sudo mdutil -E /Volumes/sharedvolumename"

-bash: sudo mdutil -E /Volumes/sharedvolumename: No such file or directory

Michaels-MBP:~ EwingWorks$

so I ahve not idea waht this means or if I am doing it right.

Sorry I am going to ask one more question of you if it is okay: did it and this is result:

/Volumes/BIGDADDY:

2018-02-09 07:05:43.519 mdutil[37936:1089482] mdutil disabling Spotlight: /Volumes/BIGDADDY -> kMDConfigSearchLevelFSSearchOnly

Indexing disabled.

Michaels-MBP:~ EwingWorks$

Is says indexing disabled, will it dtart itself or do i need to do something to make it index again?

I followed these steps (but added in "sudo" before mdutil) - from further up the discussion thread:

1 - Rebooted my mac.

2 - After a clean boot, I connected to one of my network shares.

3 - Launched Terminal and checked the spotlight indexing status for the share using "mdutil -s /Volumes/networksharename".

If it's on, proceed to step 4.

If it's off, you have to enable it using "mdutil -i on /Volumes/networksharename". Once you do so, it'll start indexing, but I recommend performing the next step anyway.

4 - Still in Terminal, executed "mdutil -E /Volumes/networksharename" to erase and rebuild the spotlight index for that share.

5 - Launched Activity Monitor to check the indexing processes (mds, mdworker, etc). Once they were done, the problem was solved.

I'm no expert, so if this doesn't work for you, I don't know what else to suggest.

Cheers.

No, if you look at the full instructions as given by felpzrj, the member that originally found this solution, you will realize there are a few variations on the mdutil command given. The one with the -E is to erase the index and is recommend to have a "clean slate" and avoid some possible corruption. It is harmless as you are going to create a new, fresh index executing the following step

"mdutil -i on /Volumes/networksharename" without the quotation marks and replacing networksharename with the actual name of your share.

This command turns indexing on and if no index exist, it creates and starts a new one.

The original member that found the solution is felpzrj and he recommended (not necessary, just in case you are a bit OCD) that as a final step #5, and I quote, "

5 - Launched Activity Monitor to check the indexing processes (mds, mdworker, etc). Once they were done, the problem was solved."