Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. Thanks, I can confirm that the problem can be solved by buying a Western Digital Black SN750 SSD (as you suggested): https://www.amazon.com/Western-Digital-Black-SN750-500GB/dp/B07NDF52G2 and cloning the existing drive using Carbon Copy Cloner and swapping out the existing Samsung (or other SSD like my ADATA SX8200 Pro) SSD. I also had to mount the EFI partition and copy over the folder into the new WD SSD. This worked like a charm for me and now allows my system running Catalina 10.15.6 to boot in 10.7 seconds (down from 32.5 seconds). Amazing SSD from Western Digital! Thank you.
  2. I see. That's impressive (11 sec. boot time). Are you using a WD Black SN750 NVMe SSD for OS X and what board and cpu are you using? Also, opencore or clover? Thanks.
  3. I tried both, but no success. I read that enabling trim is not possible on nvme drives. I've tried everything I can think of, but no luck. I am using opencore 0.6.0, but recently tried 0.6.1 and a new iMac20,1, but also no luck. I even purchased the ADATA SX8200 Pro because they use the same controller (Silicon Motion) as OWC Mac Sales. The issue has always been: 2020-09-09 14:31:28.797446-0400 localhost kernel[0]: (ALF) <ALF`sockwall_cntl_updaterules> ALF, old data swfs_pid_entry <private>, updaterules_msg <private>, updaterules_state <private> Any help would be appreciated. Thanks.
  4. Hello, would appreciate any advice on a slow boot issue I'm having. I am currently running Catalina 10.15.6 (build 19G2021 August 12, 2020) using OpenCore 0.60 with an i7-10700K on an MSI MPG Z490M GAMING EDGE WIFI board. The system is stable, but the boot time is running about 15 seconds slower than it should. Running the command: log show --last boot --style syslog Update: Kernel log from HackinTool: I believe I've identified the issue (about a 15 second delay) as an incompatible wifi module (Intel AX201) on this motherboard. In my config.plist, my smbios is set to iMac19,1 to allow it to work with Intel Comet Lake CPU's. Partial log file displaying the issue I believe is the problem. New kernel log below: 2020-09-09 14:31:05.743794-0400 localhost kernel[0]: BSD root: disk4s52020-09-09 14:31:05.743795-0400 localhost kernel[0]: , major 1, minor 142020-09-09 14:31:05.743872-0400 localhost kernel[0]: (IOStorageFamily) <IOStorageFamily`dkreadwritecompletion(void*, void*, int, unsigned long long)> disk4s5: device is not readable.2020-09-09 14:31:05.743875-0400 localhost kernel[0]: (HFS) <HFS`hfs_mountfs> hfs_mountfs: buf_meta_bread failed with 132020-09-09 14:31:05.743878-0400 localhost kernel[0]: (HFS) <HFS`hfs_mount> hfs_mount: hfs_mountfs returned error=13 for device unknown-dev2020-09-09 14:31:05.743880-0400 localhost kernel[0]: hfs_mountroot failed: 132020-09-09 14:31:05.743882-0400 localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_mountroot:1502: apfs: mountroot called!2020-09-09 14:31:05.743980-0400 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:294: /dev/disk4: device accelerated crypto: 0 (compiled @ Jul 6 2020 11:46:26)2020-09-09 14:31:05.743983-0400 localhost kernel[0]: (apfs) <apfs`log_debug> dev_init:297: /dev/disk4: device_handle block size 4096 block count 249999948 features 16 internal solidstate2020-09-09 14:31:05.744050-0400 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1121: /dev/disk4: initializing cache w/hash_size 16384 and cache size 409602020-09-09 14:31:05.753043-0400 localhost kernel[0]: (apfs) <apfs`log_debug> nx_kernel_mount:1385: /dev/disk4: checkpoint search: largest xid 36575, best xid 36575 @ 1142020-09-09 14:31:05.753428-0400 localhost kernel[0]: (apfs) <apfs`log_debug> sanity_check_alloced_blocks:270: fs_alloc_count mismatch: fs root nodes 40957 extent 1 omap 550 snap_meta 1 er: 0 udata: 2665387 fs_alloc_count 27103212020-09-09 14:31:05.753430-0400 localhost kernel[0]: (apfs) <apfs`log_debug> er_state_obj_get_for_recovery:4639: No ER state object for volume hack1nt0sh - rolling is not happening, nothing to recover.2020-09-09 14:31:05.753432-0400 localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_mount:1318: Promoter has been locked for /dev/disk42020-09-09 14:31:05.753470-0400 localhost kernel[0]: (apfs) <apfs`log_info> handle_mount:329: vol-uuid: B6C8D021-9BB7-4A78-87BF-3EC54A7EA42A block size: 4096 block count: 249999948 (unencrypted; flags: 0x1; features: 1.0.12)2020-09-09 14:31:05.754127-0400 localhost kernel[0]: (apfs) <apfs`log_debug> handle_mount:342: setting dev block size to 4096 from 5122020-09-09 14:31:05.754130-0400 localhost kernel[0]: (apfs) <apfs`log_debug> handle_mount:383: ROSV: apfs mounted RO and is the system volume of a volume group and mounted as the root fs: creating the shadow fs_root2020-09-09 14:31:05.754134-0400 localhost kernel[0]: (apfs) <apfs`log_debug> fs_setup_shadow_fs_root_tree:1452: Created the shadow_fs_root tree <private>2020-09-09 14:31:05.754156-0400 localhost kernel[0]: (apfs) <apfs`log_debug> nx_volume_group_update:6431: Set volume (role 0x1) to 41d xid 02020-09-09 14:31:05.754181-0400 localhost kernel[0]: (apfs) <apfs`log_debug> apfs_vfsop_mount:1489: mounted volume: hack1nt0sh2020-09-09 14:31:05.754250-0400 localhost kernel[0]: ioqueue_depth = 256, ioscale = 82020-09-09 14:31:05.754849-0400 localhost kernel[0]: NOTE: Attempting ROSV mount2020-09-09 14:31:05.754850-0400 localhost kernel[0]: NOTE: DETECTED ROSV CONFIG2020-09-09 14:31:05.754851-0400 localhost kernel[0]: attempting kernel mount for data volume...2020-09-09 14:31:05.756079-0400 localhost kernel[0]: (apfs) <apfs`log_debug> sanity_check_alloced_blocks:270: fs_alloc_count mismatch: fs root nodes 89881 extent 1509 omap 1944 snap_meta 1 er: 0 udata: 7946200 fs_alloc_count 80884762020-09-09 14:31:28.797446-0400 localhost kernel[0]: (ALF) <ALF`sockwall_cntl_updaterules> ALF, old data swfs_pid_entry <private>, updaterules_msg <private>, updaterules_state <private>2020-09-09 14:31:28.799850-0400 localhost kernel[0]: PMRD: power event 4 args 0x3b773984eebb8303 0x02020-09-09 14:31:28.804643-0400 localhost kernel[0]: PMRD: power event 6 args 0x3b773984f0ed7403 0x02020-09-09 14:31:28.804644-0400 localhost kernel[0]: PMRD: power event 6 args 0x3b773984f0ed7403 0x02020-09-09 14:31:28.804651-0400 localhost kernel[0]: PMRD: destroyed capability client set 0x3b773984f0f908332020-09-09 14:31:28.804658-0400 localhost kernel[0]: PMRD: PowerChangeDone: ON_STATE->ON_STATE2020-09-09 14:31:28.804858-0400 localhost kernel[0]: PMRD: power event 12 args 0x3b773984f0f924e3 0x02020-09-09 14:31:28.804860-0400 localhost kernel[0]: PMRD: SleepWake UUID queued: B3ED6BB3-1B07-4D88-8C04-DB703B6CA9172020-09-09 14:31:28.805129-0400 localhost kernel[0]: Waiting for DSMOS...2020-09-09 14:31:28.815566-0400 localhost kernel[0]: ifnet_attach: All kernel threads created for interface en0 have been scheduled at least once. Proceeding.2020-09-09 14:31:28.857175-0400 localhost kernel[0]: (HFS) <HFS`hfs_mountfs> hfs: mounted samsung1Tb on device disk2s12020-09-09 14:31:29.045311-0400 localhost kernel[0]: PMRD: power event 5 args 0x3b773984eebb8303 0x02020-09-09 14:31:29.046825-0400 localhost kernel[0]: PMRD: setAggressiveness(0) kPMMinutesToSleep = 602020-09-09 14:31:29.046830-0400 localhost kernel[0]: PMRD: setAggressiveness(0) kPMMinutesToDim = 602020-09-09 14:31:29.047114-0400 localhost kernel[0]: PMRD: aggressiveness changed: system 0->60, display 602020-09-09 14:31:29.047115-0400 localhost kernel[0]: PMRD: idle time -> 0 secs (ena 1)2020-09-09 14:31:29.047115-0400 localhost kernel[0]: PMRD: idle sleep timer enabled My question is, can you please tell me how I can prevent Catalina from trying to load/enable Wifi (I tried disabling Wifi and Bluetooth in the BIOS without success)? Can I disable it in the devices section in my config.plist or by editing a .kext? Thank you for any help you can provide. I have 2 NVME SSD's (1 Samsung 970 and 1 ADATA SX8200 Pro). Trim support has been enabled. Any ideas on how to resolve the boot delay? Appreciated! voyager99
  • Create New...