1

My SSD has bad blocks, so I get overwhelmed by those messages:

2018-07-07 21:24:03.950826+0000 0xd0       Default     0x0                  0      kernel: (IOStorageFamily) disk1s1: device error.
2018-07-07 21:24:03.950827+0000 0xd0       Default     0x0                  0      kernel: (IOStorageFamily) disk1s1: IO failed, error = 83.

They take too much of the log so log process begins to take more than 90% cpu.

Question: how do I block those messages in the new mac logging system or disable the system completely?

Tried to sudo log config --mode "level: off", but when I do the sudo log config I see no change (when I use levels default or info the change works).

By the way, clearing the log with log erase --all makes the log process hush for a while, but I definitely ain't gonna put this in cron due to religious considerations.

  • 1
    Why not fix the issue by replacing the SSD? – Allan Jul 7 '18 at 22:22
  • 1
    @Allan bash commands are way cheaper, you know :D – Alagunto Jul 7 '18 at 22:23
  • 1
    Until you lose data...then it becomes priceless. – Allan Jul 7 '18 at 22:49
  • 1
    Why not mark the bad blocks as bad? Disk Drill has this ability – Allan Jul 7 '18 at 23:17
  • 1
    It was supposed to work like you and I both hoped it would... It seems, however, that log messages at error- and fault-level are always streamed and saved to disk, and so, I think, is information logged by the kernel. Apparently this behavior cannot be altered from the default despite your success at obtaining OFF PERSIST_OFF. (P.S.: You'd be better served by using Console.app or log show rather than log stream when possible; much less juggling of electrons in the CPU.) Sorry to be of no help. – Doc G. Jul 8 '18 at 18:00

You must log in to answer this question.

Browse other questions tagged .