An error occurred while restoring the basesystem image to the target volume

Как быстро решить проблему, если поврежден экземпляр программы Mac OS

При попытках загрузки хакинтош Mac OS на экране компьютера может появляться уведомление о том, что экземпляр программы установка Mac OS поврежден.

Данное предупреждение характерно для нескольких версий, включая High Sierra, El Capitan, Catalina и MoJave. Рассмотрим, как следует поступать в таких случаях, чтобы решить проблему грамотно и оперативно.

Что означает предупреждение о поврежденных экземплярах

Впервые увидев предупреждение Экземпляр программы macos поврежден, можно ошибочно подумать, что это связано с дефектами некоторых файлов установщика.

В действительности, речь идет о том, что устанавливаемая версия системы нуждается в обновлении по причине устаревания.

Устранить этот сбой можно двумя способами:

• заменить устаревшую версию установщика на актуальную;
• изменить системную дату на более раннюю для того, чтобы установленная на компьютере совпадала с релизом.

Второй способ является более простым и позволяет сэкономить время.

Устранение оповещений о повреждениях при установке Mac OS

Существует два способа, позволяющих устранить предупреждение экземпляр программы установка mac os mojave поврежден — через настройку BIOS или с помощью терминала, встроенного в системную панель Mac OS.

Использование терминала

Встроенный терминал панели Мак ОС представляет собой аналог командной строки, характерной для всех версий операционной системы Виндоус. Используя его, устранить оповещение о поврежденном экземпляре проще всего.

Для этого необходимо последовательно выполнить такие действия:

1. Ознакомиться со списком версий операционной системы Mac OS, доступном в Википедии по ссылке https://ru.wikipedia.org/wiki/MacOS.
2. В пункте «Хронология версий» узнать точную дату релиза и номера сборки, которую планируется установить.
3. В окошке с предупреждением нажать на кнопку «ОК», а в верхней панели меню выбрать пункт «Утилиты».
4. В этом пункте перейти на вкладку «Терминал».
5. Задать требуемые параметры в формате — месяц / число / время / год. На практике это будет выглядеть так. Предположим, пользователь собирается установить операционную систему macOS 10.14 Mojave 10.14.5, выпуск которой состоялся 13 мая 2019 года. Нужно от официальной даты релиза отсчитать вперед один месяц. В результате получится 13 июня 2019 года. Именно эту дату и следует указывать в параметрах. Также нужно указать точное время — например, 09:00. Следовательно, в терминале нужно ввести такую команду: 051309002019.
6. Подтвердить ввод команды, для того чтобы установились произведенные изменения.
7. Для дальнейшей установки выйти из терминала панели.

Рассмотренный способ прост и удобен, однако не исключены сбои. Вероятно, что будет автоматически происходить сброс установленной даты к текущим параметрам. Поэтому следует обратиться к настройкам БИОС.

Настройки BIOS

Чтобы избежать оповещения о том, что экземпляр программы установка high sierra поврежден, нужно войти в BIOS.

Инструменты для изменения находятся во вкладках «Main», «Standart CMOS Features» или «Sysinfo». После этого произвести соответствующие изменения в опциях «System Time» и «System Date».

При чистой установке Мак ОС может появляться уведомление о том, что «не удалось проверить экземпляр программы, так как он мог быть поврежден или подвергнуться изменениям в процессе загрузке».

Для решения проблемы иногда достаточно перезагрузить компьютер и повторить процесс. При слишком частом возникновении оповещения — единственным верным решением станет изменение даты на устройстве Mac.

Сообщение о поврежденных экземплярах программы установки Мак — не сложная проблема. Устранить ее можно путем изменения даты под конкретный релиз. Если этот метод не сработает, нужно сменить версию установщика. Рекомендуется выбирать сборки с поздними датами выхода.

Источник

Макинтошим

Новичку

Похожие посты

22 апреля 2013, 19:07

24 марта 2013, 17:53

19 апреля 2013, 14:15

7 апреля 2013, 17:01

15 апреля 2013, 19:23

20 апреля 2015, 16:45

12 апреля 2013, 14:37

19 декабря 2012, 18:17

9 октября 2013, 15:27

20 апреля 2013, 13:16

Прямой эфир

Решение проблемы «an error occurred while adding a recovery system to the destination disk»

Что-то давно не проверял свой диск на наличие ошибок дисковой утилитой и таки проверил на свою голову :). Нет нет, с дисковой утилитой все в порядке, а вот с моими нервами…

Дисковая утилита нашла ряд ошибок на загрузочном диске. Попытка починить ошибки привела к надписи — откатай бекап при помощи тайм машины, отформатируй диск и верни все на место.

Создал новый бекап. Перезагрузил компьютер в Recovery Mode (Cmd+R) и отформатировал диск.
Затем захожу в бекап, выбираю последнюю свежую версию бекапа и вижу вот такие неприятные новости для меня: «an error occurred while adding a recovery system to the destination disk». Ну все думаю, приехали!

Как оказалось решение проблемы очень простое:
1. Необходимо установить на отформатированный диск чистую операционную систему. Создать загрузочный USB можно при помощи DiskMakerX либо в Recovery Mode выкачать и установить.
2. После установки зайти опять в Recovery Mode и процесс восстановления начнется без проблем.

Источник

macOS 10.14 Mojave on Unsupported Macs Thread

Kevbasscat

macrumors 6502

I updated supplemental 2 on my 8,2 via QTA and I got the partial loading screen then a quick black screen and then the white screen, as shown below. I tried rebooting three times, same story. I booted verbose and got almost 3 pages of info, but the last page ended at the very top with the flashing bar, and I was not able to record the output. How can I record the output?

Also, @dosdude1 this is the 8,2 that you performed your firmware fix to disable the GPU from being recognized, but I’m not so sure it worked.. My wife, being even less computer wise than me was watching Netflix on it, when she gave it back, she said, «oh btw, it shut down 5 times while I was watching my movie and it got very hot.» I started it up this morning and all seemed good, then this with the update. Could any of these behaviors be related in any way? You loaded 10.14.4 on it, and I’ll need to make a USB patcher from my 18,3 iMac if I need to reinstall. I read somewhere that 10.14.4 was the last version that had hardware support, is that true and can I re download it from a version of your patcher to keep it, or am I mistaken?
Dang! The things I don’t know, fill libraries . I’ll also need to remove that ssd and replace it if it needs to be erased as I juust put some photos on it 10 mins before this issue and obviously didn’t back it up, and no longer have access to those photos, or can I install and kepp my data?

Edit:
After reading some more, should I just make a patcher and run post install on it with rebuild?

View media item»> View media item»>

Источник

macOS High Sierra (10.13) Unsupported Macs Thread

BartmanEH

macrumors member

macrumors G5

I Am now thinking the updates are just fscked.

My 2017 MacBook automatically downloaded the latest Mojave update and auto-initiated the install and now it won’t boot properly.

jbarley

macrumors 601

Hi, i’m writing from a 5,1 Macbook with HS. I have just modified and installed the 002 patch (ending with an error), and after reboot, i have reinstalled the nightshift patch from patch updater. I got 17G3025 in about this mac. Everything seemed to be ok until I realised that Bettertouchtool won’t start (it says «bettertouchtool cant be open»).

I tried to start the app using terminal, but it says:

dyld: Symbol not found: _OBJC_CLASS_$_CBTrueToneClient

Referenced from: /System/Library/PrivateFrameworks/UniversalAccess.framework/Versions/A/UniversalAccess

Expected in: /System/Library/PrivateFrameworks/CoreBrightness.framework/Versions/A/CoreBrightness

What can I do? Will a complete reinstall using a installation disk using dosdude1 app fix the problem? Or should I recover the corebrightness framework from my time machine?

Snowscape

macrumors newbie

Was wondering if anyone can help me out here as I’m not sure what else I can do.

I’m on a Mac Pro Early 2008 (3,1) and recently upgraded to High Sierra 10.13.6 via the dosdude1 method. The main install and post install seemed to go okay and I also installed the latest Nvidia Web Driver.

So when I restarted it with my GTX 960 installed (for the upgrade I went back to the ATI 5770) I’m seeing a lot of flickering and slow refreshing like this (from another user):

I swapped the 960 for a 1050 TI to see if this solved the issue — it didn’t. Tried connecting over HDMI instead of DisplayPort — same problem. Uninstalled and reinstalled the Nvidia Web Driver — no change.

In another thread by that other user (GTX 1050 & Mac Pro 3,1 GFX really bad) they mentioned removing an AMD patch that the dosdude1 patcher includes(?). I tried the shell script he attached but again there was no difference.

So yeah, I’m not really sure what else do here If anyone can help me out that would be much appreciated.

Thanks in advance.

juliusmaximus

macrumors newbie

For anyone trying to get the bcm4321 working in High Sierra, I finally got it to work (MacBook Pro 4,1) and it was relatively simple.

I did the following:

1. Download Kext Utility
2. Download OSX combo update 10.10.5
3. Download Pacifist
4. Extract the IO80211family.kext from the 10.10.5 package using Pacifist
5. Load the Kext using Kext Utility

All the other solutions I tried either didn’t work at all or the card showed as active but couldn’t detect any wireless networks.

macrumors 6502

Amazing. Working as advertised.

As support for El Capitan ended with the release of Mojave, I was eager to update my MacBook Air 2,1 to High Sierra. A laptop without WLAN is basically useless, so this was crucial.

Thank you so much for figuring this out and sharing it.

PS: I installed 10.13.6, applied your patch and everything was fine, but SU 2018-002 messed things up a lot, unrelated to your patch most probably. Time Machine for the rescue and trying again.

juliusmaximus

macrumors newbie

Amazing. Working as advertised.

As support for El Capitan ended with the release of Mojave, I was eager to update my MacBook Air 2,1 to High Sierra. A laptop without WLAN is basically useless, so this was crucial.

Thank you so much for figuring this out and sharing it.

PS: I installed 10.13.6, applied your patch and everything was fine, but SU 2018-002 messed things up a lot, unrelated to your patch most probably. Time Machine for the rescue and trying again.

s.berlin

macrumors member

Hy folks,
i had the following issue ,
i want to creat a macos high sierra install stick (wih dosduesds patch)
i had several times formatted the stck but every time
i had creat thee patch it failed wit he fololwing

An error occurred while restoring the BaseSystem image to the target volume.

I had installed macos mojave with dosdudes patch.
What caan i do to create the sick?

macrumors 6502

Something weird happened today. After restoring my Time Machine backup and only updating iWork and Safari, I’ve forgotten to disable automatic OS and security updates.

When I woke my MacBook Air 2,1 this evening, it took a very long time to log me in. System Version is now 17G3025, albeit it doesn’t show an installed SU 2018-002 in App Store or System Profiler. But it does show ‘macOS Installer Notification’ and ‘MRTConfigData’ installs one day after the Safari update. I didn’t issue those and they were never shown in App Store. SU 2018-002 is no longer available for me in App Store.

WiFi was broken again, but I just had to reinstall IO80211.kext from 10.10.5. Everything else seems fine for now, had issues with Finder sidebar only showing one item on the last attempt. And kernel panics every other minute.

I’m not 100% sure, but it looks like my firmware was updated, too! I’m pretty positive it read along the lines of ‘1.34f8’ just like the SMC version — not sure about the exact numbers, but the formatting was the same — now it is MBA21.0075.B03. I don’t trust my memory here, maybe it was like this all the time. Should have taken a screenshot.

Since 1989, this is by far the strangest update I’ve ever experienced, even on supported machines (Mac Pro 5,1).
[doublepost=1542562094][/doublepost]

s.berlin

macrumors member

Something weird happened today. After restoring my Time Machine backup and only updating iWork and Safari, I’ve forgotten to disable automatic OS and security updates.

When I woke my MacBook Air 2,1 this evening, it took a very long time to log me in. System Version is now 17G3025, albeit it doesn’t show an installed SU 2018-002 in App Store or System Profiler. But it does show ‘macOS Installer Notification’ and ‘MRTConfigData’ installs one day after the Safari update. I didn’t issue those and they were never shown in App Store. SU 2018-002 is no longer available for me in App Store.

WiFi was broken again, but I just had to reinstall IO80211.kext from 10.10.5. Everything else seems fine for now, had issues with Finder sidebar only showing one item on the last attempt. And kernel panics every other minute.

I’m not 100% sure, but it looks like my firmware was updated, too! I’m pretty positive it read along the lines of ‘1.34f8’ just like the SMC version — not sure about the exact numbers, but the formatting was the same — now it is MBA21.0075.B03. I don’t trust my memory here, maybe it was like this all the time. Should have taken a screenshot.

Since 1989, this is by far the strangest update I’ve ever experienced, even on supported machines (Mac Pro 5,1).
[doublepost=1542562094][/doublepost]Try a different USB stick.

Something weird happened today. After restoring my Time Machine backup and only updating iWork and Safari, I’ve forgotten to disable automatic OS and security updates.

When I woke my MacBook Air 2,1 this evening, it took a very long time to log me in. System Version is now 17G3025, albeit it doesn’t show an installed SU 2018-002 in App Store or System Profiler. But it does show ‘macOS Installer Notification’ and ‘MRTConfigData’ installs one day after the Safari update. I didn’t issue those and they were never shown in App Store. SU 2018-002 is no longer available for me in App Store.

WiFi was broken again, but I just had to reinstall IO80211.kext from 10.10.5. Everything else seems fine for now, had issues with Finder sidebar only showing one item on the last attempt. And kernel panics every other minute.

I’m not 100% sure, but it looks like my firmware was updated, too! I’m pretty positive it read along the lines of ‘1.34f8’ just like the SMC version — not sure about the exact numbers, but the formatting was the same — now it is MBA21.0075.B03. I don’t trust my memory here, maybe it was like this all the time. Should have taken a screenshot.

Since 1989, this is by far the strangest update I’ve ever experienced, even on supported machines (Mac Pro 5,1).
[doublepost=1542562094][/doublepost]Try a different USB stick.

Something weird happened today. After restoring my Time Machine backup and only updating iWork and Safari, I’ve forgotten to disable automatic OS and security updates.

When I woke my MacBook Air 2,1 this evening, it took a very long time to log me in. System Version is now 17G3025, albeit it doesn’t show an installed SU 2018-002 in App Store or System Profiler. But it does show ‘macOS Installer Notification’ and ‘MRTConfigData’ installs one day after the Safari update. I didn’t issue those and they were never shown in App Store. SU 2018-002 is no longer available for me in App Store.

WiFi was broken again, but I just had to reinstall IO80211.kext from 10.10.5. Everything else seems fine for now, had issues with Finder sidebar only showing one item on the last attempt. And kernel panics every other minute.

I’m not d100% sure, but it looks like my firmware was updated, too! I’m pretty positive it read along the lines of ‘1.34f8’ just like the SMC version — not sure about the exact numbers, but the formatting was the same — now it is MBA21.0075.B03. I don’t trust my memory here, maybe it was like this all the time. Should have taken a screenshot.

Since 1989, this is by far the strangest update I’ve ever experienced, even on supported machines (Mac Pro 5,1).
[doublepost=1542562094][/doublepost]Try a different USB stick.

Something weird happened today. After restoring my Time Machine backup and only updating iWork and Safari, I’ve forgotten to disable automatic OS and security updates.

When I woke my MacBook Air 2,1 this evening, it took a very long time to log me in. System Version is now 17G3025, albeit it doesn’t show an installed SU 2018-002 in App Store or System Profiler. But it does show ‘macOS Installer Notification’ and ‘MRTConfigData’ installs one day after the Safari update. I didn’t issue those and they were never shown in App Store. SU 2018-002 is no longer available for me in App Store.

WiFi was broken again, but I just had to reinstall IO80211.kext from 10.10.5. Everything else seems fine for now, had issues with Finder sidebar only showing one item on the last attempt. And kernel panics every other minute.

I’m not 100% sure, but it looks like my firmware was updated, too! I’m pretty positive it read along the lines of ‘1.34f8’ just like the SMC version — not sure about the exact numbers, but the formatting was the same — now it is MBA21.0075.B03. I don’t trust my memory here, maybe it was like this all the time. Should have taken a screenshot.

Since 1989, this is by far the strangest update I’ve ever experienced, even on supported machines (Mac Pro 5,1).
[doublepost=1542562094][/doublepost]Try a different USB stick.

taranee

macrumors member

View media item»> View media item»> View media item»>

ok for some reason i cant get in to the mouse track pad or keyboard preference panes. when i click on them i get this. it was working fine tell now. only thing i did was install mojave on a 2nd partitions. this is under 10,13,6

and this is for any one doing a search as the only result i came up with was in Mojave unsupported thread.
You can’t open Trackpad preferences pane because it doesn’t work on an Intel-based Mac.
You can’t open Keyboard preferences pane because it doesn’t work on an Intel-based Mac.
You can’t open Mouse preferences pane because it doesn’t work on an Intel-based Mac.

jbarley

macrumors 601

ok for some reason i cant get in to the mouse track pad or keyboard preference panes. when i click on them i get this. it was working fine tell now. only thing i did was install mojave on a 2nd partitions. this is under 10,13,6

and this is for any one doing a search as the only result i came up with was in Mojave unsupported thread.
You can’t open Trackpad preferences pane because it doesn’t work on an Intel-based Mac.
You can’t open Keyboard preferences pane because it doesn’t work on an Intel-based Mac.
You can’t open Mouse preferences pane because it doesn’t work on an Intel-based Mac.

BartmanEH

macrumors member

BigMacX

macrumors newbie

aaronNW

macrumors newbie

I searched the thread and didn’t find an answer to this question:

Will a flashed NVIDIA GTX 960 work in a Mac Pro 3,1 running High Sierra using dosdude1’s patcher?

I’ve read some instances of cards that don’t play nice even when flashed (slow, blocky refreshing, flicker, etc.)

taranee

macrumors member

one of the main problem is it all worked fine till now. i even reinstalled 10,13 on another partition to confirm and that one works fine as will. with night shift. i looked at the post but they pretty much just settled on night shift not working. me i liked night shift and i want it all working like it used to. not shure why im suddenly having this problem out of no where.
[doublepost=1542669907][/doublepost]um am i doing this wrong ? or is this just not right ? i was trying to show the hiddon system files

View media item»> View media item»>

BigMacX

macrumors newbie

BartmanEH

macrumors member

BigMacX

macrumors newbie

taranee

macrumors member

ok for some reason i cant get in to the mouse track pad or keyboard preference panes. when i click on them i get this. it was working fine tell now. only thing i did was install mojave on a 2nd partitions. this is under 10,13,6

and this is for any one doing a search as the only result i came up with was in Mojave unsupported thread.
You can’t open Trackpad preferences pane because it doesn’t work on an Intel-based Mac.
You can’t open Keyboard preferences pane because it doesn’t work on an Intel-based Mac.
You can’t open Mouse preferences pane because it doesn’t work on an Intel-based Mac.

and solved with a real fix. not no work around.

now hears how to really fix it the right way not a work around. make a time machine backup just in case. download and make a more updated flash installer. and without erasing the drive. just reinstall the os. once done apply patches and boot to 10,13. then apply the night shift patch. and reboot if it says there is no keyboard or mouse then just hard reboot and done. night shift and all preference pane fully working again.

View media item»> View media item»> View media item»> View media item»> View media item»>

juliusmaximus

macrumors newbie

Something weird happened today. After restoring my Time Machine backup and only updating iWork and Safari, I’ve forgotten to disable automatic OS and security updates.

When I woke my MacBook Air 2,1 this evening, it took a very long time to log me in. System Version is now 17G3025, albeit it doesn’t show an installed SU 2018-002 in App Store or System Profiler. But it does show ‘macOS Installer Notification’ and ‘MRTConfigData’ installs one day after the Safari update. I didn’t issue those and they were never shown in App Store. SU 2018-002 is no longer available for me in App Store.

WiFi was broken again, but I just had to reinstall IO80211.kext from 10.10.5. Everything else seems fine for now, had issues with Finder sidebar only showing one item on the last attempt. And kernel panics every other minute.

I’m not 100% sure, but it looks like my firmware was updated, too! I’m pretty positive it read along the lines of ‘1.34f8’ just like the SMC version — not sure about the exact numbers, but the formatting was the same — now it is MBA21.0075.B03. I don’t trust my memory here, maybe it was like this all the time. Should have taken a screenshot.

Since 1989, this is by far the strangest update I’ve ever experienced, even on supported machines (Mac Pro 5,1).
[doublepost=1542562094][/doublepost]Try a different USB stick.

I had an almost identical experience as you. The update doesn’t show as installed however it clearly is. I’ll grab some more details tomorrow evening and update this thread.

Источник

MOJAVE SUCCESS — Thank you!

Well after a few weeks of trial and error, I finally have Mojave installed on this Early 2011 MacBookPro8,1.

View attachment 803750

Many thanks @jackluke and @dosdude1 for persevering with me to get this installed…

My installation went like this;

1. Installed Mojave (Unsupported) 10.14.1 onto a new SSD, formatted as APFS using the Mojave Patcher 1.2.3 with all the relevant MacBookPro8,1 patches applied.
2. Upon reboot, flashing question mark
3. Reinstalled original HDD (HFS+) and installed High Sierra 10.13.6 with all the latest security updates to get the latest Firmware update for this model.
4. Reinstalled SSD, formatted as APFS and attempted reinstall of Mojave with the patcher.
5. Upon reboot, I was getting a circle with a line through it — no boot.
6. Enabled verbose boot mode and witnessed boot.efi related errors — it seems the Mac couldn’t find the APFS Preboot volume.
7. I tried many, many things to resolve this and couldn’t get anywhere. I decided to give up on Mojave and tried installing High Sierra onto the SSD as a supported installation — I had not yet witnessed this SSD running ANY OS.
8. High Sierra (Supported) installer began OK, it copied the install system onto the SSD, but failed to startup on the first mid-install reboot (circle with line through it) — enabling verbose showed missing boot.efi related errors.
9. Thinking it must be an APFS issue with this Mac, I reformatted the SSD as HFS+ and witnessed the same issue — I tried several times, but there was no way the High Sierra installer would work with this SSD.
10. I assumed the SSD was faulty, but to test this theory, I installed it into a MacBook5,1 and installed El Capitan (Supported) onto it.
11. The SSD ran El Cap perfectly in the MB5,1, so I was back at square one…
12. I then tried installing Mojave (Unsupported) onto the MBP8,1 using the original 320GB HDD and it actually worked — all signs started to point to an incompatibility between this specific SSD and the MBP8,1
13. After further research I found many answers to bizarre SSD behaviour in the MBP8,1 (and others) pointing to a suspect SATA connector.
14. Fortunately I had another (non-working) MBP8,1 (Late 2011) on hand, so I pulled the SATA connector (with IR sensor and status indicator light) and installed it into the working MBP8,1.
15. To check the box for «Yes, I have a working High Sierra system on this SSD» before trying Mojave again, I successfully installed 10.13.6 on the SSD
15. I then re-created the Mojave USB using the patcher, booted up the MBP8,1, added a new APFS volume using Disk Utility on the SSD and ran the installer for what seemed like the 50th time. The installation appeared to go without a hitch, it auto-rebooted and showed the circle with a line through it. I rebooted from USB and applied the Post install patches, rebooted again and was greeted by the Mojave setup screen!!

LONG story short.. It was a faulty SATA connector in the MacBook Pro which was causing all the trouble. Although there were no problems when using the original spinner — go figure?

View attachment 803749

To confirm the SATA connector and SSD are all running their best, I checked System Profiler to see a reported full SATA III (6Gb) negotiated link speed to the SSD. I then installed Blackmagic Disk Speed Test to benchmark the drive and witnessed write speeds as LOW as 20MB/sec… After further research I tried enabling TRIM using ‘sudo trimforce enable’, then a quick reboot and we’re back up over 400MB/sec write speeds as expected!

A few issues though…

ICLOUD PHOTOS

I enabled the iCloud Photo syncing and the system became instantly bogged down — lagging mouse cursor, major delays in typing and launching apps. I could put this down to not enough RAM (only 4GB installed), but I have also witnessed this behaviour from iCloud Photo syncing on my iMac (Late 2009) C2D 3.33Ghz with 10GB of RAM, under High Sierra.

ALSO, the result of the photo sync is this…

View attachment 803740

Only a handful of my photos actually came through OK, 99% appear to be corrupted. So, the Photo syncing is now turned OFF and system responsiveness is back to normal.

TRACKPAD

I like to use tap-to-click on my Macs.. but System Preferences doesn’t show me any options for the built in trackpad. It endlessly searches for a Bluetooth trackpad. Is there a workaround for this?

View attachment 803741

CONCLUSION

In all, Mojave’s system responsiveness is much the same as High Sierra after disabling the Photo syncing and enabling TRIM support — I’ll need to go back and see if TRIM was enabled under HiSi as I do recall 400MB/sec + write speeds reported by Blackmagic Disk Speed Test under 10.13.6.

Finally, I have installed the HybridMode 1.3 patch to correct the light mode look (and many dark mode quibbles) on the non-Metal GPU. Mojave looks much better now!

————

I’ll get some more RAM next (probably 2x4GB) and an aftermarket battery and this $20 salvaged Mac will be destined for a long life ahead — I have already earmarked this one as an upgrade for my wife to finally move up from her 2009 MacBook (4GB, HDD, El Cap) — which will then go to my 6y/o son.

Not bad for a Mac which was ready to become landfill!

-AphoticD

При попытках загрузки хакинтош Mac OS на экране компьютера может появляться уведомление о том, что экземпляр программы установка Mac OS поврежден.

Данное предупреждение характерно для нескольких версий, включая High Sierra, El Capitan, Catalina и MoJave. Рассмотрим, как следует поступать в таких случаях, чтобы решить проблему грамотно и оперативно.

Что означает
предупреждение о поврежденных экземплярах

Впервые увидев предупреждение Экземпляр программы macos поврежден, можно ошибочно подумать, что это связано с дефектами некоторых файлов установщика.

В действительности, речь идет о том, что устанавливаемая версия системы нуждается в обновлении по причине устаревания.

Устранить этот сбой
можно двумя способами:

• заменить устаревшую версию установщика на
  актуальную;
• изменить системную дату на более раннюю для
  того, чтобы установленная на компьютере совпадала с релизом.

Второй способ является более простым и позволяет сэкономить время.

Устранение
оповещений о повреждениях при установке Mac OS

Существует два способа,
позволяющих устранить предупреждение экземпляр
программы установка mac os mojave поврежден — через настройку BIOS или с
помощью терминала, встроенного в системную панель Mac OS.

Использование
терминала

Встроенный терминал панели Мак ОС представляет собой аналог командной строки, характерной для всех версий операционной системы Виндоус. Используя его, устранить оповещение о поврежденном экземпляре проще всего.

Для этого необходимо последовательно выполнить такие действия:

1. Ознакомиться со списком версий операционной системы Mac OS, доступном в Википедии по ссылке https://ru.wikipedia.org/wiki/MacOS.
2. В пункте «Хронология версий» узнать точную дату релиза и номера сборки, которую планируется установить.
3. В окошке с предупреждением нажать на кнопку «ОК», а в верхней панели меню выбрать пункт «Утилиты».
4. В этом пункте перейти на вкладку «Терминал».
5. Задать требуемые параметры в формате — месяц / число / время / год. На практике это будет выглядеть так. Предположим, пользователь собирается установить операционную систему macOS 10.14 Mojave 10.14.5, выпуск которой состоялся 13 мая 2019 года. Нужно от официальной даты релиза отсчитать вперед один месяц. В результате получится 13 июня 2019 года. Именно эту дату и следует указывать в параметрах. Также нужно указать точное время — например, 09:00. Следовательно, в терминале нужно ввести такую команду: 051309002019.
6. Подтвердить ввод команды, для того чтобы установились произведенные изменения.
7. Для дальнейшей установки выйти из терминала панели.

Рассмотренный способ прост и удобен, однако не исключены сбои. Вероятно, что будет автоматически происходить сброс установленной даты к текущим параметрам. Поэтому следует обратиться к настройкам БИОС.

Настройки BIOS

Чтобы избежать
оповещения о том, что экземпляр
программы установка high sierra поврежден, нужно войти в BIOS.

Инструменты для
изменения находятся во вкладках «Main», «Standart CMOS Features» или «Sysinfo».
После этого произвести соответствующие изменения в опциях «System Time» и
«System Date».

При чистой установке Мак ОС может появляться уведомление о том, что «не удалось проверить экземпляр программы, так как он мог быть поврежден или подвергнуться изменениям в процессе загрузке».

Для решения проблемы иногда достаточно перезагрузить компьютер и повторить процесс. При слишком частом возникновении оповещения — единственным верным решением станет изменение даты на устройстве Mac.

Сообщение о
поврежденных экземплярах программы установки Мак — не сложная проблема.
Устранить ее можно путем изменения даты под конкретный релиз. Если этот метод
не сработает, нужно сменить версию установщика. Рекомендуется выбирать сборки с
поздними датами выхода.

I have a similar problem. Tried installing on a variety of USB drive and hard disks, all to no avail. The system I’m patching on is running Catalina (I’m doing the download and patching on a newer Mac, and I intend to use it to install Catalina on my older Mac). I thought perhaps Catalina was the issue so I tried using my partners Mac which is running Mojave. Same problem persists.

The error message I get:

Error Saving BaseSystem Image
An error occurred while attempting to save the BaseSystem image. Ensure that there is at least 10GB of free space on your Startup Disk, then try again.

And when I click View Log:

Mounting BaseSystem.dmg…

/dev/disk4 GUID_partition_scheme
/dev/disk4s1 Apple_HFS /private/tmp/basesystem

Patching BaseSystem.dmg…

hdiutil: couldn’t unmount «disk4» — Resource busy

I definitely have more than enough space on my startup disk, so the error message is incorrect.

I tried re-running the installation as suggested above, but this didn’t work on my Catalina Mac. On the Mojave Mac the installation then progressed almost to the end, but then the same error and log messages came up, except the image it couldn’t unmount this time was InstallESD.dmg instead of BaseSystem.dmg.

Any suggestions would be much appreciated.

Many thanks,
Jack

I’m trying to install Catalina on my late 2008 MacBook running on El Capitan using a patcher

I’ve gotten to the point where I create the bootable installer on an external drive. When I start the creation, I get about half way through before receiving this error message:

Error Mounting InstallESD Image

An error occurred while mounting the InstallESD image. Verify that InstallESD.dmg is not mounted using Disk Utility, then try again.

Here is the log:

Mounting BaseSystem.dmg...

/dev/disk3          	GUID_partition_scheme          	
/dev/disk3s1        	Apple_HFS                      	/private/tmp/basesystem


Patching BaseSystem.dmg...

"disk3" unmounted.
"disk3" ejected.
Preparing imaging engine…
Reading Protective Master Boot Record (MBR : 0)…
   (CRC32 $05BD9B8F: Protective Master Boot Record (MBR : 0))
Reading GPT Header (Primary GPT Header : 1)…
   (CRC32 $0B9401A9: GPT Header (Primary GPT Header : 1))
Reading GPT Partition Data (Primary GPT Table : 2)…
   (CRC32 $DFDDEEE9: GPT Partition Data (Primary GPT Table : 2))
Reading  (Apple_Free : 3)…
   (CRC32 $00000000:  (Apple_Free : 3))
Reading disk image (Apple_HFS : 4)…
   (CRC32 $BB653CB5: disk image (Apple_HFS : 4))
Reading  (Apple_Free : 5)…
   (CRC32 $00000000:  (Apple_Free : 5))
Reading GPT Partition Data (Backup GPT Table : 6)…
   (CRC32 $DFDDEEE9: GPT Partition Data (Backup GPT Table : 6))
Reading GPT Header (Backup GPT Header : 7)…
   (CRC32 $0A9BF70B: GPT Header (Backup GPT Header : 7))
Adding resources…
Elapsed Time: 40.625s
File size: 697873585 bytes, Checksum: CRC32 $C02663E9
Sectors processed: 4189376, 3563452 compressed
Speed: 42.8Mbytes/sec
Savings: 67.5%
created: /private/tmp/BaseSystem.dmg


Restoring BaseSystem.dmg...

	Validating target...done
	Validating source...done
	Retrieving scan information...done
	Validating sizes...done
	Restoring  ....10....20....30....40....50....60....70....80....90....100
	Remounting target volume...done
Volume on disk2s1 renamed to Catinstall


Copying SharedSupport to Volume...



Copying Patched BaseSystem.dmg...



Mounting InstallESD.dmg...

hdiutil: attach failed - no mountable file systems

Anyone know how I can fix this?

I was able to fidget with the Core Storage volumes and get past the recovery disk error.

Not sure if it’s actually doing anything though. About two hours of silence and an uninformative progress bar where I would have expected to hear the backup disk going clackety clack.

Recovering Mac Mini from Time Machine Backup

I have a Mac Mini 2012 with a ~120GB + 1TB fusion drive.

I borked it up a little while trying to install an Ubuntu dual boot and was unable to restore it from my Time Machine backup due to «There was an error creating recovery disk».

To fix that I removed all volumes of all types from the disk and started over, leaving 5gb of space for the recovery partition to be created.

Since I now know what the table ended up looking like (which I’ll post back… tomorrow after the backup is restored), I’m confident that I could have done this by resizing as well.

DANGER

All of these commands are very dangerous if you have data on your disk(s).

I’m using the actual commands that I would use, which are the actual commands that someone else with a factory-installed fusion drive would need to use.

Unless the reason that you’re trying to add a recovery drive happens to be that your drive is already utterly messed up, I would NOT recommend following these steps.

HOWEVER, they may come in as a handy references in addition to other instructions in these posts.

Inspecting Volumes

Look to see what’s there and make proper judgements first:

# See all physical partitions
diskutil list

# See all core storage volumes
diskutil cs list

Removing all volumes

Then delete whatever needs to be deleted:

# Delete a Logical Volume
diskutil cs deleteVolume <lvUUID>

# Delete a Physical Volume
diskutil cs deleteDisk <pvUUID>

# Delete a Logical Volume Group (everything)
diskutil cs delete <lvgUUID>

Recreate the partition table from scratch, if needed:

# Re-partition and format the HDD
# `R` means Remainder
# `5G` means ~4.7GiB
diskutil partitionDisk disk0 2 GPT 
    JHFS+ Macintosh HD R 
    JHFS+ Recovery HD 5G

# Re-partition and format the SSD
# the remainder, `R`, is 100% of the usable disk space
diskutil partitionDisk disk1 1 GPT 
    JHFS+ Macintosh HD R

Create Core Storage

This will be «Macintosh HD» as you know and love

# Create a logical volume group named "Macintosh HD"
diskutil cs create Macintosh HD disk0s2 disk1

# Create a volume (of the same name) using 100% of the group
diskutil cs createVolume <lvgUUID> jhfs+ Macintosh HD 100%

Note: you may want to reboot at this stage to ensure that the volumes are in the right order.

Unmount all-the-things

diskutil unmount "Macintosh HD"
diskutil unmount "Recovery HD"
diskutil unmountDisk /dev/disk0
diskutil unmountDisk /dev/disk1

Free up space

The purpose of creating «Recovery HD» previously — assuming the scenario where you want to restore from a Time Machine backup — is just to reserve extra space at the end of one of the disks so that it doesn’t get absorbed into any other volume.

Now it’s time to free it back up so that the restore process can create it again.

First check again to see what partitions exist. The numbers should match the output of diskutil, but if not either reboot or trust gpt over diskutil.

The sizes are not listed in bytes but sectors, which are probably 4KiB. It may be better to tell which is which by ratio than by exact size.

gpt -r show /dev/disk0

Now remove the partition corresponding to «Recovery HD». After a reboot that had changed from disk0s3 to disk0s4 for me.

gpt remove -i 4

After that I stopped getting the error about not being able to create a recovery partition. I’ll find out tomorrow if the TM recovery actually worked. I’m not sure it will as I don’t hear much in the way of disk activity on the backup drive. :-/

Resources

• https://blog.fosketts.net/2011/08/05/undocumented-corestorage-commands/
• http://hints.macworld.com/article.php?story=2014030311173257

Note: resizing core storage

Many of the things I looked at only showed how to resize AND create a new volume, but you can resize without creating a new volume.

# First resize the logical volume
diskutil coreStorage resizeVolume <lvUUID> 1T

# Next resize the physical volume
diskutil coreStorage resizeDisk <pvUUID> 997G

# Tada! You have free space!

Note: Set Recovery HD`s type

I was not able to get success by creating a blank recovery volume. However, if you have the BaseSystem.dmg and are able to restore it, you may want to set the volume type to be a hidden recovery partition.

# Unmount to be able to make changes
diskutil unmount /dev/disk0s3

# Change the type from Apple_HFS to Apple_Boot
asr adjust -target /dev/disk0s3 -settype Apple_Boot