Slow boot APFS trim issue

[rchen29]

I been having this problem since upgraded to macos 12. Currently have oc 0.7.5. The problem is that my system took about 3 minutes to boot up. The boot log show that APFS trim took like 156.6s.

Any help would be appreciated.

2021-10-25 13:23:11.511381-0500 localhost kernel[0]: IOUSBHostInterface(0x1000003ff): matching deferred by IOUSBHostHIDDevice
2021-10-25 13:23:21.594884-0500 localhost kernel[0]: compressor_store_stop_compaction = FALSE
2021-10-25 13:25:47.879615-0500 localhost kernel[0]: (apfs) <apfs`log_debug> spaceman_scan_free_blocks:3153: disk2 scan took 156.789766 s, trims took 156.606247 s
2021-10-25 13:25:47.879630-0500 localhost kernel[0]: (apfs) <apfs`log_debug> spaceman_scan_free_blocks:3155: disk2 49248201 blocks free in 432721 extents
2021-10-25 13:25:47.879644-0500 localhost kernel[0]: (apfs) <apfs`log_debug> spaceman_scan_free_blocks:3163: disk2 49248201 blocks trimmed in 432721 extents (361 us/trim, 2763 trims/s)
2021-10-25 13:25:47.879665-0500 localhost kernel[0]: (apfs) <apfs`log_debug> spaceman_scan_free_blocks:3166: disk2 trim distribution 1:124941 2+:84210 4+:106524 16+:55821 64+:29839 256+:31386
2021-10-25 13:25:47.926755-0500 localhost kernel[0]: (ALF) <ALF`sockwall_cntl_updaterules> ALF, old data swfs_pid_entry <private>, updaterules_msg <private>, updaterules_state <private>
2021-10-25 13:25:47.926766-0500 localhost kernel[0]: (ALF) <ALF`sockwall_cntl_updaterules> ALF, old data swfs_pid_entry <private>, updaterules_msg <private>, updaterules_state <private>
2021-10-25 13:25:47.927814-0500 localhost kernel[0]: (ALF) <ALF`sockwall_cntl_updaterules> ALF, old data swfs_pid_entry <private>, updaterules_msg <private>, updaterules_state <private>
2021-10-25 13:25:47.927945-0500 localhost kernel[0]: (ALF) <ALF`sockwall_cntl_updaterules> ALF, old data swfs_pid_entry <private>, updaterules_msg <private>, updaterules_state <private>
2021-10-25 13:25:47.667302-0500 localhost kernel[0]: (ALF) <ALF`sockwall_cntl_updaterules> ALF, old data swfs_pid_entry <private>, updaterules_msg <private>, updaterules_state <private>

 

[theruck]

its a known problem of Samsung NVMe drives. no solution yet. best is to change the drive manufacturer. WD 750S are proven to be working well