Jump to content
180 posts in this topic

Recommended Posts

7 hours ago, Wayang-NT said:

but this is the BIG DRAMA ...

 

This isn't a drama... Even if this isn't a beta bug and Apple really does remove full support for HFS+ starting with version 26.4, you can simply convert the file system directly from a running macOS:

diskutil apfs convert /Volumes/Name

You can also do this through the graphical interface of the macOS Disk Utility.

Although this operation is routine and considered safe, a backup copy of your data will not be superfluous.

Edited by verdazil
  • Like 5
11 hours ago, Shikumo said:

Same issue here with a simple HFS+ partition.

Manually unmounting and remounting the volume as writable (sudo mount -w -t hfs /dev/diskXsY /Volumes/HFSDISK) seems to make it work again (until the next boot(? not tested yet)).

For the RAID, you may need to perform a complex conversion via terminal to APFS.

 

However, if you have this problem on single disks, it is easy to solve.

You need to start from a recovery (for me, different from 26.4, which gives me an error for this procedure).

I used the one from 26.3.

Then recovery.

Disk Utility.

Right-click on the disk. Convert to APFS.

Done.

  • Like 4

Already known issues by Apple developer: "HFS external media might fail to mount automatically".  So they recommends to "use CLI tool diskutil mount to attach the relevant disk device". 😎 Wait and see.

  • Like 4
13 hours ago, Dragster27 said:

It installed successfully here but I get errors on my FAT formatted USB Sticks... plus, I can't apply root patches with OCLP-MOD:

 

image.png.503fd45e9257ee35c07d6ccff47ddf76.png

The same, as is. OCLP-MOD and OCLP 3.0.0 Nightly from Izhoang2801 give this error.

 2026-02-17 в 16.15.44.png

  • Like 6

Smooth update from Tahoe 26.3 -> 26.4 (25E5207k) Beta.  VoodooHDA.kext 3.0.3 (audio) and itlwm 2.3.0 (Intel Wi-Fi) continue to work flawlessly.  Still not installing any root patches on this hack.  SIP remains untouched with csr-active-config = <01000000>. 

 

Prior to update, temporarily disabled BluetoolFixup.kext for incremental update.

Spoiler

Screenshot2026-02-17at8_58_28AM.png.8beeb17c3301ffb59a0f898a526b8792.png

 

Screenshot2026-02-17at9_33_08AM.png.ba7751bc99e52f3778cf824a359289cc.png

 

 

EDIT: I haven't performed any concrete benchmarks, but Tahoe 26.4 feels more responsive than previous versions of Tahoe on this HackBookPro16,2.  I continue to run Tahoe with the following System Settings:

  • Accessibility > Display > Reduce Transparency: Enabled
  • Accessibility > Motion > Reduce Motion: Enabled
  • Terminal: defaults write -g com.apple.SwiftUI.DisableSolarium -bool YES

 

EDIT2: Power management in Tahoe continues to be OUTSTANDING.  My laptop is silent - fans hardly run with very good responsiveness.

Edited by deeveedee
  • Like 7
37 minutes ago, deeveedee said:

Smooth update from Tahoe 26.3 -> 26.4 (25E5207k) Beta.  VoodooHDA.kext 3.0.3 (audio) and itlwm 2.3.0 (Intel Wi-Fi) continue to work flawlessly.  Still not installing any root patches on this hack.  SIP remains untouched with csr-active-config = <01000000>. 

 

Prior to update, temporarily disabled BluetoolFixup.kext for incremental update.

  Reveal hidden contents

 

Screenshot2026-02-17at9_33_08AM.png.ba7751bc99e52f3778cf824a359289cc.png

 

 

EDIT: I haven't performed any concrete benchmarks, but Tahoe 26.4 feels more responsive than previous versions of Tahoe on this HackBookPro16,2.  I continue to run Tahoe with the following System Settings:

  • Accessibility > Display > Reduce Transparency: Enabled
  • Accessibility > Motion > Reduce Motion: Enabled
  • Terminal: defaults write -g com.apple.SwiftUI.DisableSolarium -bool YES

O-u! Tell me what is com.apple.SwiftUI.DisableSolarium?

  • Like 3

Ok.  So after reading the above I decided to install.  Things went fine and I was able to get to the desktop.  As others have said OCLP 3.1.5 which is new could not update.  I get a permissions error and it died.  Also true about USB install stick for Tahoe.  I tried to convert to APFS via Disk Utility and this failed with an error.

 

I will hold off reverting to previous version for now.

 

Cheers, Howard

  • Like 3
Guest
This topic is now closed to further replies.
×
×
  • Create New...