That's interesting! Downloading now.
xCode requires updating with every OS release. It's one of the things that I hate the most.Xcode (command line) because I tried to check also for brew updates but this update has deleted xcode, don't know what's happened.
[Edit]Which command did you use to get that info?
But only for ARM Macs?!Since I have my m1 i had to reinstall xcode each time so annoying...
My DriveDx Trial has ended, but again... up to some point there was 100GB/night (unplugged, sleep). Then today morning ~900GB written by the kernel task. I just can't see the pattern ;/
More or less for me its:
- small writes
- small writes
- it goes all-in and makes almost 1TB writes in a day.
Plugged or unplugged. With or without an external monitor. That's just plain stupid and I think that Apple should step in and say:
"we know it, it's ok" or "we investigate" or "here is a fix".
After 11.2.3 update so far after few hours, it looks promising. It's too early to say it has been fixed so I will definitely will be watching at my disk usage. Still same workflow (no using TimeMachine - not even touched it).
First thoughts. I started seeing beachball in Affinity Designer. Like... a lot. Upon yesterday never happened.
If I want to monitor SMART data for USB drives how can I do that? It's not supported by smartmontools and I can't get it to work with DriveDX.
Yes, you can! The author of DriveDx released a native driver for M1 (Apple Silicon) in January. It will be included by default in the next version of DriveDx.On M1 you can't (AFAIK). On Intel machines you needed the SAT-Smart-Driver. This was supplied as signed kext by the author of DriveDx. Without a driver, you cannot get the smart data from the disks. And Apple apparently didn't implemented these commands in the OS or it's hidden somewhere in some private API.
Oh. Didn't saw that yet. Good to know.Yes, you can! The author of DriveDx released a native driver for M1 (Apple Silicon) in January. It will be included by default in the next version of DriveDx.
There must be something different with your PS install. I can't get mine to write anything with Launchd. I worked with the non-beta version this morning on very large files. After 4 hours Launchd wrote only 381MB (not related to PS).Updated to Big Sur 11.2.3 - Photoshop/Lightroom Classic still causing launchd to write tens of GB per hour.
Looks like choices are to:
SNAFU
- Hope Adobe/Apple fix this before disk wears out (falls to floor in fits of laughter)
- Revert to working on my old Mini
- Unsupported OS
- Unsupported Apps
- Lightroom on old Mini can't use catalog I have (one way conversion process was applied)
- For at least the Photoshop part, use a beta of an incomplete application
- For the Lightroom Classic part
- Wait for Adobe to release Apple Architecture version
- Checks life expectancy, doesn't look a promising option
Oh. Didn't saw that yet. Good to know.
Is it an NVMe based one? Like the T7? They will not work. DriveDx actually says this on the page you linked further down. My Adata SE800 also shows no SMART data on macOS, but perfectly fine on Windows.I have a Samsung 8TB SSD and it might work on other drives perhaps.
No, it's a Samsung 870 QVO 8TB SSDIs it an NVMe based one? Like the T7? They will not work. DriveDx actually says this on the page you linked further down. My Adata SE800 also shows no SMART data on macOS, but perfectly fine on Windows.
You most likely installed the driver version (0.10.2) that was included with the current version of DriveDx, and this is the Intel-only version. This is generally a very strange unexpected feature of macOS for M1, which allows you to install incompatible drivers for an incompatible architecture - for some reason (bug, indifference?) macOS does not check the type of driver architecture.Just a little heads up. I bought DriveDx the other day, and you have to do a bit of changes to the security in recover menu. "Less secure" I think i switched to, and allow external signing or what it's called.
Wa a bit more than just install the addon driver.
Even then I can't see SMART- on my external drive. Don't know why.
I have a Samsung 8TB SSD and it might work on other drives perhaps.
E: https://binaryfruit.com/drivedx/kb#external-drive-support-mac-t2-chip