Jump to content

schmu

Member
  • Posts

    11
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

schmu's Achievements

Helping Hand

Helping Hand (3/5)

0

Reputation

  1. okay, feel free, thanks - I wasn't sure if I should have made a new thread from the beginning. I also prefer fewer threads that then have a clear solution when searching. Best wishes 🙂
  2. ok. the crash yesterday killed the index, other than that I had not touched it since the 14.1 update. thanks for the info! if it crashes once more I'll just clean install.
  3. Hi, I had issues of Alfred not finding files and thought I had solved them. They appeared after a move from a Ventura Carbon Copy Cloner (CCC) backup to a Sonoma new install form the Apple Store after a boot failure and firmware reload. in this thread with lots of help from Andrew and Stephen_C (thanks!) I thought I had solved the issue of Alfed not finding files and reporting an unknown indexing state error after 1. trashing the .Spotlight-V100 folder and 2. immediately updating to Sonoma 14.1 because this command gave Indexing enabled: mdutil -s / resulted in /: Indexing enabled. However, my mac just shut itself off and restarted (). Afterwards, I did the following: 1. booted into Safe Mode and back 2. checked the indexing status mdutil -s / is still fine, but mdutil -s /Unsers/homefolder/ resulted in /System/Volumes/Data/Users/homefolder: Error: unknown indexing state. so my home folder is not indexed. Spotlight search has an Indexing... blue bar. Alfred finds more files, probably because of the cache. Can this be due to a Migration Assistant error as the "Nov 5 post" from Vero here? (Just to say again, I have done all the steps in the post twice: Once: symptom 1 : Alfred finds no files, folders or apps symptom 2: indexing status via "mdutil -s /" gave "error: unknown indexing state". trashed the .Spotlight-V100 folder from Alfred rebooted waited for indexing to complete (which took a day, not an hour) checked for indexing status via "mdutil -s /" the index was lost again, unknown indexing state in terminal. result 1 : Alfred finds no files, folders or apps result 2: indexing status via "mdutil -s /" gave "error: unknown indexing state". Second time: trashed the .Spotlight-V100 folder from Alfred did not reboot installed Sonoma 14.1 update rebotted with the update waited for indexing to complete (which again took more than a day, not an hour) checked for indexing status via "mdutil -s /" result 1 : Alfred finds everything result 2: indexing status via "mdutil -s /" gave "indexing enabled" Now, the computer restarted itself  (sent a crash report to Apple but do not see a crash repoirt in Console) and the index via "mdutil -s /" gives "indexing enabled" but "mdutil -s /Users/homefolder/" gives "unknown indexing state". as here: Or are there any other suspects apart from Migration Assistant? Thank you
  4. Yesterday before installing Sonoma 14.1 update I deleted the .Spotlicht-V100 folder once more via Alfred and used the reboot from the update. The progress bar in the Spotlight search window took more than 12 hours to finish but now it seems stable. I checked the indexing status from time to time via Terminal mdutil -s / and always got /: Indexing enabled. no more unknown indexing status error. Maybe I'll install from scratch without migrating nevertheless, but for now Alfred and Spotlight work again. thanks much!
  5. I tried the double reset of search scope in the post above, thank you. Typing f now finds the Finder.app and Force quit some things, but typing z does not find Zotero 6.app, for example. Searching for "migrate" on the forum reveals some posts that definitely make me not use the migration assistant any more for anything, especially not migrating stuff to a new system. I'm more concerned about these more fundamental problems. I think it is smart to wipe the drive by booting into Disk Utility and reinstalling Sonoma, then put everything back by hand from the CCC backup or from Dropbox/ Onedrive/ iCloud/App store without the Migration Assistant. But will that be enough? Or does this unknown indexing status hint at a different problem, maybe hardware after all? I was told at the store that the mac not booting was either a software issue or a broken SSD, and if reloading the firmware didn't help I would have to wait for a new logic board. Then they told me reloading the firmware was enough and said that any program could corrupt the firmware. If I don't force shut down my mac (which I don't, I'm nice to it), this usually doesn't happen, and there is nothing else I could do to avoid firmware corruption. I'm not so sure. I appreciate your advice.
  6. yes, I have done all suggestions from all posts, including yours from the troubleshooting page that you linked to before my first post. I got the same issue and error messages. That's why I continued here instead of making a new thread. Here is a list of what I did: - checked that Alfred has Full Disk Access - added the internal ssd to Privacy and removed it and waited for indexing to finish (twice) - booted into Safe Mode and back - pressed Delete .Spotlight-V100 Folder in Alfred Prefs > Advanced > Rebuild macOS Metadata, rebooted and waited for two days (Andrew said it can take an hour) after finishing the new index, Spotlight and Alfred worked initially, but then on and off, not finding anything (except websites for Spotlight) in the morning and finding everything including files later in the day, right now it finds only apps. - checked mdutil -s / in terminal several times which gives the "Error: unknown indexing state" googling "unknown indexing state", I have found problem reports but not solutions that refer to Sonoma. I have found terminal commands for older systems that repaired people's indexing function. I don't want to run terminal commands that were recommended from an older system, though. (I have not received a response at discussions.apple.com.) All of this happened since my Apple certified store had to reload the firmware two weeks ago because the mac would not boot any more. They wiped my drive and gave it back to me on Sonoma. I migrated everything back from a Carbon Copy Cloner backup from the last version of Ventura, everything was fine, and then Alfred did not find my files any more. I could wipe the drive myself once more and not migrate but copy/download/install everything new. I had not done this initially because I have a paper due next week. unsmart. I also don't know what caused the firmware issue in the first place. There is one thread saying that the Ventura 13.6 update did so for many, but my mac didn't fail right after the update. https://discussions.apple.com/thread/255162457 . EtreCheck has minor issues and complains about the usual suspects, Cisco Secure Client from my university, Proton VPN, Adobe and Microsoft apps and my logitech presenter, and reports high CPU usage on (backwards chronologically) knowledgeconstructiond, Zotero 6.app, , spotlightknowledged, suggestd, an AuthenticationServicesAgent crash, mdwrite, revisiond, backupd, EtreCheckPro682.app, ZoteroSafariExtension, PDF Expert 2.app , CloneKitService, Scrivener, Excel and installd right after getting my mac back. I hope this is useful info. Thanks a lot
  7. failure report from this morning of a screen shot that has been sitting in Downloads for two days: Starting Diagnostics... File: 'Screenshot 2023-10-23 at 12.31.14 CEST.png' Path: '/Users/pi/Downloads' ----------------------------------------------------------- Check file cache database... ✅ File cache integrity is ok ----------------------------------------------------------- Check if file is readable... ✅ Alfred has permissions to read this file. Unix Permissions: 420 Underlying Type: NSFileTypeRegular Extended Attributes: ( "com.apple.lastuseddate#PS", "com.apple.macl", "com.apple.metadata:kMDItemIsScreenCapture", "com.apple.metadata:kMDItemScreenCaptureGlobalRect", "com.apple.metadata:kMDItemScreenCaptureType" ) ----------------------------------------------------------- Check if volume '/' is indexed by macOS... ⚠️ Indexing may not be enabled on this drive /: Error: unknown indexing state. ----------------------------------------------------------- Check direct file metadata... ⚠️ Direct metadata is missing, this file is likely not indexed by macOS ----------------------------------------------------------- Check mdls file metadata... ❌ macOS metadata missing essential items /Users/pi/Downloads/Screenshot 2023-10-23 at 12.31.14 CEST.png: could not find /Users/pi/Downloads/Screenshot 2023-10-23 at 12.31.14 CEST.png. ----------------------------------------------------------- ❌ Troubleshooting failed Alfred and Spotlight find only apps, no progress bar in spotlight:
  8. Hi Andrew, yes, Alfred has full disk access: I figured this was the exact issue I have and I have since deleted the index via Alfred about 3 days ago while using the mac almost constantly. At first it worked, spotlight was indexing and files were found once it was done, but now eery morning I find nothing. The mac is open over night and the backup drives attached (2x2TB external SSDs, one CCC, one Time Machine, overnight should be plenty to index these as well if that were the issue). After half an hour or so of progress bar, I get apps, and later also files in Alfred and Spotlight. I think Sonoma has a spotlight issue but I posted in the apple forum and got no response. Not sure why. https://discussions.apple.com/thread/255221664 Thanks for responding!
  9. Hi Stephen, thank you, here is one report. I was referring to Dropbox moving all user data to a Library folder in order to conform with Apple File Provider API: https://help.dropbox.com/installs/dropbox-for-macos-support#:~:text=Dropbox for macOS on File,changes required by the API. that one has not hit me yet. Thus my files are still in /Users/username/Dropbox/ . What will happen once they are in Library, I have no idea. I might give up Dropbox before it can do this. Yes, I have everything "Make available offline". Starting Diagnostics... File: 'xxx.pdf' Path: '/Users/username/Dropbox/a/b/c/d/e/f' ----------------------------------------------------------- Check file cache database... ✅ File cache integrity is ok ----------------------------------------------------------- Check if file is readable... ✅ Alfred has permissions to read this file. Unix Permissions: 420 Underlying Type: NSFileTypeRegular Extended Attributes: ( "com.apple.lastuseddate#PS", "com.apple.metadata:_kMDItemUserTags", "com.apple.metadata:kMDItemFinderComment", "com.apple.provenance", "com.dropbox.attrs", "com.readdle.LastPosition", "com.readdle.pdfexpert.handoff.overriddenFileModificationDate" ) ----------------------------------------------------------- Check if volume '/' is indexed by macOS... ⚠️ Indexing may not be enabled on this drive /: Error: unknown indexing state. ----------------------------------------------------------- Check direct file metadata... ⚠️ Direct metadata is missing, this file is likely not indexed by macOS ----------------------------------------------------------- Check mdls file metadata... ❌ macOS metadata missing essential items /Users/username/Dropbox/a/b/c/d/e/f/xxx.pdf: could not find /Users/username/Dropbox/a/b/c/d/e/f/xxx.pdf. ----------------------------------------------------------- ❌ Troubleshooting failed
  10. I installed Sonoma a week ago and have since reindexed 3 times, twice reindexed by adding my internal ssd to privacy and removing, and once via the "Delete .Spotlight-V100 Folder" button. The last time is 3 days ago, so spotlight should have finished. But each morning it takes a restart and half an hour before it works, with the same result "likely not indexed" when checking a file in Alfred. Spotlight initially finds only websites and does not show an indexing bar for half an hour, then it does and takes 30 minutes to finish an index. Then it works and troubleshooting is passed. This seems odd. I do have 1.6 TB and mostly on Dropbox (still in home folder) but the mac was open with backup drives attached as it does every night. I Would appreciate more information about a possible Sonoma bug or a permission s issue with Dropbox or something. Thank you
×
×
  • Create New...