[GUIDE] Haswell System - MacOS Monterey 12.0.1 OC 0.7.5

[zeph]

It's me, once again
With verbose mode I found where the boot seem stuck, something called Tx_flush on disk 6 (system disk)

2023-03-07 17:09:54.546348+0100 localhost kernel[0]: kern_open_file_for_direct_io(<private>, 0)
2023-03-07 17:09:54.546350+0100 localhost kernel[0]: kern_open_file_for_direct_io took 9053 ms
2023-03-07 17:09:54.553873+0100 localhost kernel[0]: kern_open_file_for_direct_io took 9053 ms
2023-03-07 17:09:54.553875+0100 localhost kernel[0]: Opened file /System/Volumes/VM/kernelcore, size 1048576, extents 1, maxio 2000000 ssd 1
2023-03-07 17:09:54.562079+0100 localhost kernel[0]: Opened file /System/Volumes/VM/kernelcore, size 1048576, extents 1, maxio 2000000 ssd 1
2023-03-07 17:09:54.562111+0100 localhost kernel[0]: polled file major 1, minor 18, blocksize 4096, pollers 5
2023-03-07 17:09:54.569553+0100 localhost kernel[0]: polled file major 1, minor 18, blocksize 4096, pollers 5
2023-03-07 17:09:54.569595+0100 localhost kernel[0]: Opened corefile of size 1 MB
2023-03-07 17:10:07.162278+0100 localhost kernel[0]: compressor_store_stop_compaction = FALSE
2023-03-07 17:10:17.129251+0100 localhost kernel[0]: (apfs) <apfs`log_warn> tx_flush:1043: disk6 tx xid 21073 took 1577268 us to flush
2023-03-07 17:10:20.247655+0100 localhost kernel[0]: (apfs) <apfs`log_warn> tx_flush:750: disk6 tx xid 21074 was closed for 2296771 us waiting to prepare to flush
2023-03-07 17:10:26.161245+0100 localhost kernel[0]: (apfs) <apfs`log_warn> tx_flush:750: disk6 tx xid 21075 was closed for 5039604 us waiting to prepare to flush
2023-03-07 17:10:26.168310+0100 localhost kernel[0]: (apfs) <apfs`log_warn> tx_enter_internal:2257: disk6 waited 4990973 us to open tx xid 21076 (nx_tx_wait_closed)
2023-03-07 17:10:27.207148+0100 localhost kernel[0]: (apfs) <apfs`log_warn> tx_flush:1043: disk6 tx xid 21075 took 1039171 us to flush
2023-03-07 17:10:37.793989+0100 localhost kernel[0]: (apfs) <apfs`log_warn> tx_flush:750: disk6 tx xid 21076 was closed for 8971178 us waiting to prepare to flush
2023-03-07 17:10:37.801546+0100 localhost kernel[0]: (apfs) <apfs`log_warn> tx_enter_internal:2257: disk6 waited 7228011 us to open tx xid 21077 (nx_tx_wait_closed)
2023-03-07 17:10:39.639206+0100 localhost kernel[0]: (apfs) <apfs`log_warn> tx_flush:1131: disk6 tx xid 21076 took 1038902 us to sync and write superblock
2023-03-07 17:10:47.257923+0100 localhost kernel[0]: (apfs) <apfs`log_warn> tx_flush:1131: disk6 tx xid 21077 took 1024436 us to sync and write superblock

 

[Edhawk]

Have you confirmed which APFS formatted drive is set as disk6? Is it your macOS system drive?

Have you tried running the system with this disk removed/disconnected?

Do you have a spare SSD/drive to use to install a clean macOS setup?

Is the system using the wrong APFS driver?

 

[zeph]

Disk6 is my system drive. It's in APFS format.

It was supposed to be a clean install
No spare disk for the moment (unless old HDD).
How can I check the APFS driver ?

The SSD is a low end one. I install Monterey on it to test if it could work.
I will migrate everything to a 560 EVO nvne as soon as possible but for the moment there is my Catalina install on it.

 

[zeph]

Edit from my last post
I did start from scratch. Seem to go faster. 1m10s between open core and login into the OS on Monterey.
36second on Catalina but it's on a MVME much faster.

 

[zeph]

Seems i've change something in bios, now oc won't start and there a big "halting on critical error" showing up...
I can't even boot on the USB stick. Same error!

 

[Edhawk]

Simple task to boot in to the bios, set the bios to Optimal Defaults (will undo any changes you made) and then reset the bios to match the requirements for running macOS. See bios settings below.

Change the following settings:

1. Virtualisation : Enabled
2. VT-d : Disabled
3. XHCI Hand-Off : Enabled
4. Legacy USB Support: Auto/Enabled
5. IO SerialPort : Disabled
6. Network Stack : Disabled
7. XMP Profile : Auto / Profile 1/Enabled
8. UEFI Booting set to Enabled and set Priority over Legacy
9. Secure Boot : Disabled
10. Fast Boot : Disabled
11. OS Type: Other OS
12. Wake on LAN : Disabled
13. Integrated Graphics : Enabled
14. Graphics: PEG/PCIe/Slot 1
15. Initial Display Output : PCIe/Slot1
16. DVMT Pre-Allocated : 128M or higher

Your Haswell system may not have all of these options, just make sure you set the ones present as shown above. Also make sure you look in each and every sub-folder, as bios creators tend to like to hide entries in unusual locations.

 

[zeph]

Did it in the bios.
I had to disable secure boot in OC too. I don't understand because i already did it...

Sadly, after all the system is unstable

Each time I start working with fine cut pro it crashes and the next boot is a bit longer

 

[Edhawk]

If you don't use Final Cut Pro (FCPX) does the system work OK? I don't use FCPX, so I have no idea what would cause the system to crash in this manner. Does it happen after you use a specific effect, extension, tool?

When the system crashes, you may need to use the CleanNvram or ResetNvramEntry tool/driver from the OC boot screen, to remove any data retained in the system following the crash.

 

[zeph]

I had one freeze if I remember well.
I went back to Catalina to work on Final Cut and now it also crash here

I'll test the clear nvram and deactivate the iGPU

I'll test tomorrow on Monterey ,on Catalina, no effect, even worse, the whole systeme freezer. I'll try to restore from Time Machine i need it to work quickly

 

[zeph]

Bluetooth just decided to work on his own
That's nice !

I still have those long boot tims with "tx_flush" things and Revolution Mx mouse is so slow when scrolling up or down