Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
Updated to 11.2.3: first reboot kernel_task has written like 20GB in few minutes, rebooted again and things look better now, but I had to reinstall Xcode (command line) because I tried to check also for brew updates but this update has deleted xcode, don't know what's happened.

Screen Shot 2021-03-08 at 21.14.59.png


PS: this 2 seconds = almost 2 minutes! Anyway now all it's okay. I have to reboot and wait in the nex hours of usage what will happen with kernel_task process 👹
 
  • Like
Reactions: Quackers
Xcode (command line) because I tried to check also for brew updates but this update has deleted xcode, don't know what's happened.
xCode requires updating with every OS release. It's one of the things that I hate the most.
 
  • Like
Reactions: m-a
I don't remember I've updated xcode command line every minor releases (like 11.2.x) but could be my mistake :)
 
Which command did you use to get that info?
[Edit]

to get the power usage settings, run "sudo pmset -g"

To change one of the settings, just set it using a value (on/off use 1/0 values), e.g.

sudo pmset -a powernap 0

The "-a" mean "all power states", i.e. on battery or plugged in. You can set different configs for running on battery power with "-b".

Just "man pmset" for options!
 
Last edited:
  • Like
Reactions: eshroom
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".

Time Machine enabled? Maybe it is the way it handles, prunes and manages local copies.

Anyway, I hope that the latest patch solves the issue for those experiencing it.
 
I use Time Machine only in manual mode and not that often as SSDs are very reliable indeed.
Also backing up to a TB3 SSD is pretty fast.
That way no issues for me.
 
Saw this thread and thought I'd go look. My 2013 MacBook pro that's been running, well, since Late 2013 when I got it was around 20TB maybe? In 7 years. I'm at 2TB after 34 hours of power on time. It's only been used for a few days - that's it. Yikes.

1615267463051.png


For comparisons sake my work 2018 MacBook Pro that does all the heavy lifting 40hrs/week has 342 hours and 13 TB. It also has a 512GB SSD and 32GB of RAM, but also runs a Windows VM full time alongside macOS as well for what it's worth, but doesn't appear to swap much with the amount of memory it has.
 
I want to pressure the M1 a bit. Installed MS Edge, Citrix Workspace, A softphone client we use at work, MS Office 365 and currently working from home via Mac for the first time.
I'll check the disc writes via DriveDX later this evening to check.
 
  • Like
Reactions: osplo and gank41
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:
  • 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
SNAFU
 
  • Sad
Reactions: Ningj
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.

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.

What difference have you seen since updating?
 
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.

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.
 
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.
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.
 
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:
  • 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
SNAFU
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).
Do you use any plugins?
Did you do a fresh install?
How many files do you open at once?
 
Oh. Didn't saw that yet. Good to know.

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
 
Last edited:
I have a Samsung 8TB SSD and it might work on other drives perhaps.
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.
 
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.
No, it's a Samsung 870 QVO 8TB SSD
 
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
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.
So at the moment for M1 you need to separately download a special version (0.10.3) of the driver from the website. Then everything should work.
 
  • Like
Reactions: Dockland
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.