Why did iStat Menus disable S.M.A.R.T.? Nothing can disable S.M.A.R.T. It is a technology built into the firmware of your HDD or SDD that reports on the health of your drive. It's not something that can be disabled. After I installed iStat Menus my launchd job immediately threw me a popup saying me to backup all my files. I checked with Disk Utility and I saw S.M.A.R.T. Status as Unsupported.
This is because there is a system service residing at the hardware layer that's intercepting responses from the drive's S.M.A.R.T. Disk Utility is attempting to send a request to the drive to report back on it's status and iStat Menu is (for a lack of a better word) grabbing the result; no result comes back - thus it's 'Unsupported.' Regarding your script. While your script in and of itself is good, Disk Util's 'S.M.A.R.T.
Maclife On Twitter We Call Istat Menus 5 For Mac Free Download
Status = Verified' is nothing more than the 'check engine light' on a car's dashboard. It tells you something is wrong, but not what and only after something has failed. This is about as useful as closing the barn door after the horse escaped. Has a number of that Disk Util doesn't monitor nor report on. To get comprehensive reporting and more granular data as well as thresholds that will warn you of impending failures, look to tools specifically made for this type of task. (Free, CLI based).
(Free for monitoring, paid for data recovery). (Free trial, paid for continued use) I have personally used the built-in Disk Util to get the S.M.A.R.T.
Dec 31, 2014 - They can't cause distractions in meetings and don't require Wi-Fi. While I try to. 'Why I Drilled Holes in My MacBook Pro and Put It in the Oven' ». He maintains a weblog called dot info and calls Twitter his second home. IStat Menus 5, by Bjango: an advanced system monitor for your Mac's menubar. When anything's wrong with your Mac, or you think that the machine is too hot, iStat Menus is how you can track down what that is with more sensors and data than you thought possible. Five Essential Apps for Your Mac. Bartender 3 is a super popular Mac app that lets you rearrange and hide icons on the menu bar of your Mac. With Bartender, you can put the menu bar items you.
Status in a pinch. However, I prefer the 'pro' tools designed specifically for this type of task. Smartmontools is sufficient for me, but for clients who aren't comfortable with a CLI, I recommend either Disk Drill or Drive Dx.
See my post here: What we're seeing in these crash logs is a kernel panic where PID #0 (kerneltask) is the panicked 'task'. But a lot of different things run under the kerneltask process-all your drivers, etc.
So when we dig into it a bit more and look for which thread panicked, it is consistently coming up as AppleSMC. I'm not 100% sure about how to read these logs that start with mentions of BridgeOS, but they really all look like macOS kernel panics. The link these have to Bridge OS is still unclear to me.
Is Bridge OS crashing and taking down AppleSMC driver with it? Is AppleSMC a/the connection point between macOS (running on the main CPU) and Bridge OS (running on the T2), now that T1/T2 chips are doing what the SMC used to do? Is Bridge OS just sending a bad message to macOS that the AppleSMC driver can't handle?
Or is Bridge OS just doing some higher level crash reporting? It doesn't feel like Bridge OS is just simply 'crashing', particularly since I would think that any sane engineers would have had enough isolation between Bridge OS and macOS so that even if BridgeOS on the T2 crashed hard, it would still fail gracefully and not take down macOS with it.
Seems much more likely that there's some sort of 'miscommunication'. One test I want to run in the next week is whether we'd see Windows crash in the same sleep scenarios-Windows would have a completely different driver stack (albeit one that could share some idiosyncrasies with macOS since apple presumably wrote both drivers).
It'd be a great data point. I just scanned StudioSanctum's most recent crash log again, and he had a much more specific message in his panicString. Code: Stackshot Reason: Wake transition timed out after 180 seconds while calling power state change callbacks.
Suspected bundle: com.uaudio.driver.UAD2System.That's interesting, as it is actually calling out that uaudio driver (even though it was AppleSMC that panicked), whereas in most of the other crashlogs I've taken a look at, the panicString has had a bit more. Generic description, such as 'Sleep /Wake hang detected' or 'x86 global reset detected' Update: reading this panicString again, it reads as if various drivers such as the uaudio driver are registered with the OS to be told when the power state changes (the 'power state change callbacks'). Maybe AppleSMC is managing those callbacks. In the case here, it reads as if the system was trying to tell drivers that the power state changed, but something caused it to hang which has prevented the entire power state transition, and perhaps AppleSMC gets grumpy when that happens? Anyway, it all seems very software-ish to me. I know it means little to nothing, but I’m sorry you’re going through this. I know you have to be about to throw that thing out of the window right now.
It would be one thing if it crashed during sleep, but once it starts to crash while you’re actively using it. You are experiencing what I went through with the 2016 MacBook Pro.
The only difference is I went through about 4 machines before I happened to get one that didn’t have issues right out of the box. Are you able to replicate the crash essentially on command at this point? While I wasn’t sure that the new beta fixed it (how can I / any of us be), I was hopeful. I think what one of the members above said is very interesting, in that he was asking if BridgeOS is just the task that is reporting the actual crash, and perhaps not necessarily the cause of the crash itself. That just goes to show how little we really know about how the T2 is tied into the machine as a whole.
You’re still in touch with Apple, yeah? Have they offered you anything at all? Send in for repair, data capture, etc? With my 2016 they had me install the capture utility which logged nearly everything and sent it to them as a.dmg. Edit: meanwhile: Makes you wonder if macOS is still a high priority, doesn’t it?
Click to expand.Over two years now professionally on W10 with zero issues on multiple systems. It's nonsense like this why I dumped Apple for anything remotely serious, and that one squarely sits with Apple. If Apple ever get's it act together I'll reconsider, however current management is just focused on churning out nice looking underperforming computers for pretentious students, while it's dwindling professional audience look elsewhere, as they too need to deliver.
Over two decades with the Mac. Click to expand.One of the major points of the Mac was 'it just works' having to jump through hoops, second guess and suffer crashes is a far cry from my expectations. Apple needs to put more focus on the Mac, stop churning out half baked software and hardware. We the customers need to send a clear message that the current behaviour is not acceptable. Apple literally has all the money in the world, yet it's seemingly incapable of designing robust software & hardware solutions, being more focused on nickel & diming, cutting cost and boosting margins.