Wenn ich das richtig lese dann startet der TRIM beim Boot und braucht ca. 80s.
Da ich nach ca. 20s den Loginscreen erreiche ist das Problem wohl "gelöst" wenn ich das alles unten richtig interpretiere.
2022-05-27 10:10:33.097541+0200 0x3c2 Default 0x0 0 0 kernel: (apfs) spaceman_metazone_init:191: disk2 metazone for device 0 of size 2693771 blocks (encrypted: 0-1346885 unencrypted: 1346885-2693771)
2022-05-27 10:10:33.097544+0200 0x3c2 Default 0x0 0 0 kernel: (apfs) spaceman_datazone_init:625: disk2 allocation zone on dev 0 for allocations of 1 blocks starting at paddr 154927104
2022-05-27 10:10:33.097547+0200 0x3c2 Default 0x0 0 0 kernel: (apfs) spaceman_datazone_init:625: disk2 allocation zone on dev 0 for allocations of 2 blocks starting at paddr 150503424
2022-05-27 10:10:33.097550+0200 0x3c2 Default 0x0 0 0 kernel: (apfs) spaceman_datazone_init:625: disk2 allocation zone on dev 0 for allocations of 3 blocks starting at paddr 150142976
2022-05-27 10:10:33.097552+0200 0x3c2 Default 0x0 0 0 kernel: (apfs) spaceman_datazone_init:625: disk2 allocation zone on dev 0 for allocations of 4 blocks starting at paddr 150339584
2022-05-27 10:10:33.242663+0200 0x331 Default 0x0 0 0 kernel: (apfs) spaceman_scan_free_blocks:3172: disk2 scan took 0.145089 s (no trims)
2022-05-27 10:11:52.514226+0200 0x1ab Default 0x0 0 0 kernel: (apfs) spaceman_scan_free_blocks:3154: disk2 scan took 80.571627 s, trims took 80.412907 s
2022-05-27 10:11:52.514230+0200 0x1ab Default 0x0 0 0 kernel: (apfs) spaceman_scan_free_blocks:3156: disk2 99080733 blocks free in 204878 extents
2022-05-27 10:11:52.514232+0200 0x1ab Default 0x0 0 0 kernel: (apfs) spaceman_scan_free_blocks:3164: disk2 99080733 blocks trimmed in 204878 extents (392 us/trim, 2547 trims/s)
2022-05-27 10:11:52.514235+0200 0x1ab Default 0x0 0 0 kernel: (apfs) spaceman_scan_free_blocks:3167: disk2 trim distribution 1:64584 2+:32001 4+:55867 16+:23694 64+:10396 256+:18336
Gruss,
Joerg