My first Mac OS issue in Sonoma 14.3

[kagharaht]

I have the iMac M3, 24gb RAM, 8-10, 2TB, 4Port. So spotlight would not search anything. Everything else seems to be working fine, but Spotlight just would not search. Nothing comes up. So I select Restart on the Menu. It starts the process screen goes dark, but still on and it just sat there for minutes. Nothing. iMac still running despite blank screen. So I hold the power button down to force it to turn off. Turn it back on, but I did not get the alert when you force the Mac to shut down or unexpected shut down alert. It booted up normally without that alert. Spotlight works now. Hope it doesn't happen again in Sonoma. If it does, perhaps rebooting it daily will help clear up the cache or whatever reason that made spotlight fail.

Oh for Siri search this comes up in the console every time I do a search in Siri.
{"bug_type":"313",

Interesting:
{"bug_type":"151","timestamp":"2024-02-08 09:27:19.00 -0700","os_version":"macOS 14.3 (23D56)","roots_installed":0,"incident_id":"4CCBD8BC-324C-452C-8A81-BE49D86509A9"}
{
"build" : "macOS 14.3 (23D56)",
"product" : "Mac15,5",
"socId" : "8122",
"socRevision" : "20",
"incident" : "4CCBD8BC-324C-452C-8A81-BE49D86509A9",
"crashReporterKey" : "761C5C29-5BBD-078A-ABEB-86F07CA61331",
"kernel" : "Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:30 PST 2023; root:xnu-10002.81.5~7\/RELEASE_ARM64_T8122",
"date" : "2024-02-08 09:27:19.46 -0700",
"string" : "panic(cpu 5 caller 0xfffffe0026c13d1c): btn_rst\nDebugger message: panic\nMemory ID: 0xff\nOS release type: User\nOS version: 23D56\nKernel version: Darwin Kernel Version 23.3.0:

 

[bzgnyc2]

That's a real OS bug -- haven't seen one of those in macOS in a while.

In the meantime, perhaps try rebuilding your Spotlight indexes? I don't know if there is a GUI way but this should do it from Terminal if you are logged in as an "admin" user:

sudo mdutil -E -av

 

[kagharaht]

That's a real OS bug -- haven't seen one of those in macOS in a while.

In the meantime, perhaps try rebuilding your Spotlight indexes? I don't know if there is a GUI way but this should do it from Terminal if you are logged in as an "admin" user:

sudo mdutil -E -av

I'm good enough to look at stuff and copy and past it from Console. Thats my level of technology. LOL. I don't know how to use Terminal. So just copy this and paste it? Yes I'm admin.

 

[bzgnyc2]

I'm good enough to look at stuff and copy and past it from Console. Thats my level of technology. LOL. I don't know how to use Terminal. So just copy this and paste it? Yes I'm admin.

Yes -- you would just open the Terminal app and then paste that command after the prompt. It will then ask you for the password for that account before proceeding.

However, if Spotlight is working now and no more problems, the system may have rebuilt the Spotlight indexes after reboot on its own. You can check the index status with:

sudo mdutil -avs

Either way, I would check and save the results from that command before doing the earlier command just to see where the system is before overwriting it.

P.S.We are assuming corrupt Spotlight indexes. It is also possible that there was something else wrong somewhere in the OS (or an intermittent hardware problem) and the Spotlight failure was just the first visible symptom. I would have to see all the related logs leading up the freeze/crash to be more confident but not sure that is practical nor warranted in this case if the system is back to working well.

 

[kagharaht]

Yes -- you would just open the Terminal app and then paste that command after the prompt. It will then ask you for the password for that account before proceeding.

However, if Spotlight is working now and no more problems, the system may have rebuilt the Spotlight indexes after reboot on its own. You can check the index status with:

sudo mdutil -avs

Either way, I would check and save the results from that command before doing the earlier command just to see where the system is before overwriting it.

P.S.We are assuming corrupt Spotlight indexes. It is also possible that there was something else wrong somewhere in the OS (or an intermittent hardware problem) and the Spotlight failure was just the first visible symptom. I would have to see all the related logs leading up the freeze/crash to be more confident but not sure that is practical nor warranted in this case if the system is back to working well.

Got it. Yeah hopefully a one off thing. I'll do the "sudo mdutil -avs" thing. I'll just rename the drives in the post for privacy. Thanks for the tips and education.


Indexing enabled.
/System/Volumes/Data:
Indexing enabled.
/System/Volumes/Preboot:
Indexing enabled.
/Volumes/****:
Indexing enabled.
Scan base time: 2024-02-08 16:25:28 +0000 (12449 seconds ago), reasoning: '(null)'
/Volumes/****:
Indexing enabled.
Scan base time: 2024-02-08 16:25:28 +0000 (12449 seconds ago), reasoning: '(null)'
/Volumes/****:
Indexing enabled.
Scan base time: 2024-02-08 15:01:18 +0000 (17499 seconds ago), reasoning: '(null)'
/Volumes/Time Machine M3:
Indexing enabled.
Scan base time: 1970-01-01 00:00:01 +0000 (1707421976 seconds ago), reasoning: '(null)'
****@****-iMac ~ %

 

[bzgnyc2]

If I am reading all the above correctly, it looks like it rebuilt the 2nd to last volume (3rd one whose name you masked) at 8am MT, then rebuilt the first two masked volumes at 9:25am MT, then crashed at 9:27am MT. I am not 100% sure about the sequence of events as I am not sure the date in the kernel panic log is from when the system crashed versus when it was retrieved and entered into the log.

However, assuming the sequence of events is as I listed, I would make sure I had a full backup and then rebuild the indexes again. If it started rebuilding the indexes on its own and then froze and panic'd and then hasn't rebuilt them successfully since I would rebuild them all just to make sure. However, if it froze/panic'd while trying to rebuild the indexes, you could have a disk/filesystem issue which is why I would make sure I had a full backup just in case.

P.S.After I made sure I had a full backup handy somewhere but before I rebuilt the indexes, I would probably do a complete filesystem check using Disk Utility (i.e. run First Aid on each volume and expand Details to monitor the situation). While I don't like to get too crazy with all these resets and refreshes, I am pretty paranoid about my files/data/filesystem integrity.

 

[kagharaht]

If I am reading all the above correctly, it looks like it rebuilt the 2nd to last volume (3rd one whose name you masked) at 8am MT, then rebuilt the first two masked volumes at 9:25am MT, then crashed at 9:27am MT. I am not 100% sure about the sequence of events as I am not sure the date in the kernel panic log is from when the system crashed versus when it was retrieved and entered into the log.

However, assuming the sequence of events is as I listed, I would make sure I had a full backup and then rebuild the indexes again. If it started rebuilding the indexes on its own and then froze and panic'd and then hasn't rebuilt them successfully since I would rebuild them all just to make sure. However, if it froze/panic'd while trying to rebuild the indexes, you could have a disk/filesystem issue which is why I would make sure I had a full backup just in case.

P.S.After I made sure I had a full backup handy somewhere but before I rebuilt the indexes, I would probably do a complete filesystem check using Disk Utility (i.e. run First Aid on each volume and expand Details to monitor the situation). While I don't like to get too crazy with all these resets and refreshes, I am pretty paranoid about my files/data/filesystem integrity.

Thank you and I will do all this stuff and I have Time Machine backup every hour since getting the iMac in December.