IIRC it was something with processing disk image, just wanted to repeat the glitch but could not replay it. Tho I am at Mojave atm.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
High Sierra booting possibly corrupts newer Systems. Fix, description and a boot picker renamer
- Thread starter Macschrauber
- Start date
- Sort by reaction score
IIRC it was something with processing disk image, just wanted to repeat the glitch but could not replay it. Tho I am at Mojave atm.
Yes, my 3.1 just "ignores" .disk_label icons for ESPs, too and I made some icons to distinguish ESPs.
The Mac Pro 5.1's firmware renders the .disk_label file.
Edit: tried the original
makemultilinedisklabel in Monterey and it worked, too for ESPs.Mac Pro 5,1 firmware 144.0.0.0.0 with multiline
.disk_label for those ESPs.
Last edited:
thanks, will add this to reference.
A HFS+ disk has no separate Preboot Volume so it can copy nothing from it to nowhere :]
back on topic:
Do you have an idea, why changing the dates like
Code:
sudo touch -t 203009110327 /System/Library/CoreServices/SystemVersion.plist
sudo touch -t 203009042358 /System/Library/CoreServices/PlatformSupport.plistSince I did it no more hits on other Preboots.
btw:
The Dumper package is also on Github btw, with a document about this topic also:
Macschrauber-s-Rom-Dump/Rename_and_repair_preboot.md at main · Macschrauber/Macschrauber-s-Rom-Dump
A tool for dumping and analysing Mac firmwares. Plus flashing for Mac Pro 4.1 / 5.1 - Macschrauber/Macschrauber-s-Rom-Dump
github.com
I am even later to this party but I hope somebody can help me. I am not to tech savvy, which means I could use some help.
I have a iMac 12,1 (Mid 2011) running High Sierra which I upgraded a few years ago with an SSD and more Ram-Sticks (now 12 GB total). I use it mainly for photo editing and some internet browsing. Two weeks ago I saw that Firefox drops its support in March 2025 for High Sierra and I found a lot of YT-Video about Open Core Legacy Patcher.
Last week I installed macOS Sonoma on an external SSD and so far it worked. Then I installed Sonoma on a seperate Partition on my SSD which i named "iMac SSD 2" (the Partition with High Sierra is called "iMac SSD").
I need dual boot with both OS because I have some Software on High Sierra which I cant get in Sonoma.
So far both OS work ok. Yesterday I came across a a very in depth german guide for Open Core Legacy Patcher. In this guide is a warning about dual booting with High Sierra and a never macOS. In the guide is a link to a GitHub-Post from Macschrauber and from there I found this post here.
I did read this post twice but I dont really understand If I should be worried about my iMac running dual boot with High Sierra and Sonoma or not. If I can boot into both OS now am I ok or is this like a ticking time bomb?
Like I wrote, I can boot into both OS at the moment and as far all is working fine. But I did notice some wierd behaviour that is also described here. My Sonoma Partition is not called "iMac SSD 2" but "iMac SSD 2 - Daten". An on the boot picker both OS have the High Sierra Logo.
When booted into High Sierra there is a new Harddrive called "Update" for some reason which is not showing up when I am in Sonoma.
What should I do?
I have a iMac 12,1 (Mid 2011) running High Sierra which I upgraded a few years ago with an SSD and more Ram-Sticks (now 12 GB total). I use it mainly for photo editing and some internet browsing. Two weeks ago I saw that Firefox drops its support in March 2025 for High Sierra and I found a lot of YT-Video about Open Core Legacy Patcher.
Last week I installed macOS Sonoma on an external SSD and so far it worked. Then I installed Sonoma on a seperate Partition on my SSD which i named "iMac SSD 2" (the Partition with High Sierra is called "iMac SSD").
I need dual boot with both OS because I have some Software on High Sierra which I cant get in Sonoma.
So far both OS work ok. Yesterday I came across a a very in depth german guide for Open Core Legacy Patcher. In this guide is a warning about dual booting with High Sierra and a never macOS. In the guide is a link to a GitHub-Post from Macschrauber and from there I found this post here.
I did read this post twice but I dont really understand If I should be worried about my iMac running dual boot with High Sierra and Sonoma or not. If I can boot into both OS now am I ok or is this like a ticking time bomb?
Like I wrote, I can boot into both OS at the moment and as far all is working fine. But I did notice some wierd behaviour that is also described here. My Sonoma Partition is not called "iMac SSD 2" but "iMac SSD 2 - Daten". An on the boot picker both OS have the High Sierra Logo.
When booted into High Sierra there is a new Harddrive called "Update" for some reason which is not showing up when I am in Sonoma.
What should I do?
I think the first post mostly explains what to do.
Since you can boot both partitions still, you do not need to add
-no_compat_check to boot-args.Click the
Spoiler: Screenshots of the cure button in the post to see all the steps for running the Preboot fixer and renamer tool. I think you can run it in Sonoma.After running the tool, check the dates of High Sierra's
SystemVersion.plist and PlatformSupport.plist files. Maybe try using the sudo touch -t commands to update the dates of those files if you have to reapply the tool again in the future.Thank you joevt for your fast response. I will try running the "Preboot fixer and renamer" in Sonoma.
I forgot to write something before, maybe it matters.
My OS High Sierra was on the SSD which was formated in Mac OS Extended (journaled). When I installed OS Sonoma I first tried to create a APFS partition which would have deleted the hole SSD, which was no option for me. So I made another Mac OS Extended (journaled) Partition and then changed that Partition to APFS.
Ausdauersportler did write:
"Late to this party, but this bug and a fix is known since 2021 when Big Sur hit the road using a new APFS implementation unknown to High Sierra.
IMHO you can avoid this problem completely when running High Sierra on an HFS+ disk."
Does this make a difference or do I still have to worry about my OS Sonoma install?
I forgot to write something before, maybe it matters.
My OS High Sierra was on the SSD which was formated in Mac OS Extended (journaled). When I installed OS Sonoma I first tried to create a APFS partition which would have deleted the hole SSD, which was no option for me. So I made another Mac OS Extended (journaled) Partition and then changed that Partition to APFS.
Ausdauersportler did write:
"Late to this party, but this bug and a fix is known since 2021 when Big Sur hit the road using a new APFS implementation unknown to High Sierra.
IMHO you can avoid this problem completely when running High Sierra on an HFS+ disk."
Does this make a difference or do I still have to worry about my OS Sonoma install?
As you see the High Sierra icon and -Data name, High Sierra has already overwritten files on your new OS.
Just run the tool, let it replace the files and rename the boot volume.
If it happens again, run it again.
Take care, sip is activated when running High Sierra, OpenCore adjusts sip as needed.
To do this run the High Sierra recovery, start Terminal, enter
csrutil enable
Last edited:
Thanks Guys for your help! It worked with your Tool! The boot picker is looking good now and the SSD-Name is also now without the "Data" in the name.
I did boot twice back into High Sierra to double check but so far it still looks good.
I also changed the Dates in Terminal in High Sierra, just to be on the save side.
Another Question:
My sister has the same iMac and I will install Sonoma on her iMac too. If I change the dates in the Terminal directly, is that enough or do I still need to use your Tool?
If Sonoma runs on her iMac she won`t boot into High Sierra anymore, I just want the keep the original OS on there as a "fail safe".
I did boot twice back into High Sierra to double check but so far it still looks good.
I also changed the Dates in Terminal in High Sierra, just to be on the save side.
Another Question:
My sister has the same iMac and I will install Sonoma on her iMac too. If I change the dates in the Terminal directly, is that enough or do I still need to use your Tool?
If Sonoma runs on her iMac she won`t boot into High Sierra anymore, I just want the keep the original OS on there as a "fail safe".
The tool to fix the problem will not be needed unless the problem happens.
You don't need to worry about the problem since there's a tool to fix the problem.
Hi - just found this thread and hoping that this is the right place to ask about my OCLP dual-boot High Sierra/Ventura 12,2 imac.
I havent experienced any problems with booting either volume (I guess maybe because my High Sierra disk is formatted HFS and the second drive where Ventura is installed is APFS).
I have also noticed the odd phenomenon mentioned previously of the Ventura volume having ' - data' appended to when in High Sierra (the 'Mac HD - data' volume created by Ventura is displayed as 'Mac HD - data - data' in High Sierra!
However, what I am finding is that there are system crashes leading to reboot when High Sierra spotlight tries to index something - presumably on the Ventura APFS2 volumes). I have added all the Ventura volumes that High Sierra can see to the spotlight exclusion list but it looks like there are still problems with spotlight crashing the system...
Any suggestions?
Many thanks
I havent experienced any problems with booting either volume (I guess maybe because my High Sierra disk is formatted HFS and the second drive where Ventura is installed is APFS).
I have also noticed the odd phenomenon mentioned previously of the Ventura volume having ' - data' appended to when in High Sierra (the 'Mac HD - data' volume created by Ventura is displayed as 'Mac HD - data - data' in High Sierra!
However, what I am finding is that there are system crashes leading to reboot when High Sierra spotlight tries to index something - presumably on the Ventura APFS2 volumes). I have added all the Ventura volumes that High Sierra can see to the spotlight exclusion list but it looks like there are still problems with spotlight crashing the system...
Any suggestions?
Many thanks
Last edited:
Have you checked with the <Preboot Fixer>, if there are mismatches in the config files?
If there are no mismatches, this is not related to the topic of this thread.
The disk image password is
romInside the "Readme & other tools" folder is a "Preboot fixer and renamer" folder which has "Preboot fixer and renamer.app". Look at the screenshots.
Hi thank-you. I have run the fixer a couple of times, it finds the discrepancy between the two volume names - comes up with:
[/Volumes/Preboot/8646313A-7B93-4DE1-A0B4-B567170DCAF5/System/Library/CoreServices/.disk_label_2x]
with the files:
.disk_label.contentDetails:
[Mac HD New - Data]
.contentDetails:
[Mac HD New - Data - Data]
in: [Samsung SSD 870 QVO 2TB @ Internal (SATA)]
System Version: [13.7.2]
'Mac HD New - Data' is displayed in the name field and i click 'change if text entered' but this doesn't change the volume name - the 2nd '- Data' is still there...
it then says:
Mac HD New - Data - Data's Preboot is: [13.7.2]
Can not compare (System volume not mounted)
Mac HD New - Data - Data's Preboot .im4m files matches
PS as indicated above, I have unmounted the Ventura volumes in High Sierra as I have been getting all sorts of crashes caused by mds - spotlight indexing - I'm sure it is being caused by spotlight trying to index something it can't!
Hi! well I think i`m the last guy to this party and the dumbest because I have a mac pro 5,1 with monterey and high sierra and everytime I go to sierra I can`t get back to monterey. I Reinstall monterey with OC and I run the tool preboot fixer, and it`s all ok, but then when I go to sierra, monterey gets the forbiden sign. When I run the tool in High sierra I get this message.
Found
/Volumes/Preboot/D98A27DE-0416-4EA1-8016-FC169DC4DCDF/System/Library/CoreServices/SystemVersion.plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ProductBuildVersion</key>
<string>17G66</string>
<key>ProductCopyright</key>
<string>1983-2018 Apple Inc.</string>
<key>ProductName</key>
<string>Mac OS X</string>
<key>ProductUserVisibleVersion</key>
<string>10.13.6</string>
<key>ProductVersion</key>
<string>10.13.6</string>
</dict>
</plist>
of High Sierra with the bound System volume of
[SSD500 - Datos] this OS can not mount
to copy back the files.
This is most likely corrupted and needs to
be repaired booting a System from Big Sur up
re-using the fixer.
and this
SSD500 - Datos SystemVersion.plist possibly corrupted
[10.13.6]!
SSD500 - Datos's Preboot .im4m files matches
High Sierra [10.13.6] SystemVersion.plist ok
High Sierra [10.13.6] PlatformSupport.plist ok
but I can`t get back to monterey to run the tool again... I`m sure I am the problem, but how do I proceed? thanks for the patience.
Found
/Volumes/Preboot/D98A27DE-0416-4EA1-8016-FC169DC4DCDF/System/Library/CoreServices/SystemVersion.plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>ProductBuildVersion</key>
<string>17G66</string>
<key>ProductCopyright</key>
<string>1983-2018 Apple Inc.</string>
<key>ProductName</key>
<string>Mac OS X</string>
<key>ProductUserVisibleVersion</key>
<string>10.13.6</string>
<key>ProductVersion</key>
<string>10.13.6</string>
</dict>
</plist>
of High Sierra with the bound System volume of
[SSD500 - Datos] this OS can not mount
to copy back the files.
This is most likely corrupted and needs to
be repaired booting a System from Big Sur up
re-using the fixer.
and this
SSD500 - Datos SystemVersion.plist possibly corrupted
[10.13.6]!
SSD500 - Datos's Preboot .im4m files matches
High Sierra [10.13.6] SystemVersion.plist ok
High Sierra [10.13.6] PlatformSupport.plist ok
but I can`t get back to monterey to run the tool again... I`m sure I am the problem, but how do I proceed? thanks for the patience.