[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

[hitINdaGs]

Hey guys, I am trying to get rid of my numerous maintenance wakes. Here's what my logs say:

Spoiler: Log

2020-07-21 16:03:43 +0200 Assertions PID 206(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd0000833a [System: PrevIdle BGTask SRPrevSleep kCPU]

2020-07-21 16:03:43 +0200 Assertions PID 206(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd0000833a [System: PrevIdle BGTask]

2020-07-21 20:35:48 +0200 Assertions PID 206(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd00008465 [System: PrevIdle BGTask SRPrevSleep kCPU]

2020-07-21 20:35:50 +0200 Assertions PID 206(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:02 id:0x0xd00008465 [System: PrevIdle]

2020-07-23 12:28:17 +0200 Assertions PID 205(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd0000858b [System: PrevIdle BGTask SRPrevSleep kCPU]

2020-07-23 12:28:19 +0200 Assertions PID 205(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:02 id:0x0xd0000858b [System: PrevIdle]

2020-07-23 12:29:56 +0200 Sleep Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using AC (Charge:0%) 755 secs

2020-07-23 12:41:37 +0200 Assertions PID 205(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd000085c1 [System: PrevIdle BGTask SRPrevSleep kCPU]

2020-07-23 12:41:37 +0200 Assertions PID 205(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd000085c1 [System: PrevIdle BGTask]

2020-07-23 12:43:16 +0200 Sleep Entering Sleep state due to 'Maintenance Sleep':TCPKeepAlive=disabled Using AC (Charge:0%) 1241 secs

2020-07-23 13:03:04 +0200 Assertions PID 205(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd000085f8 [System: PrevIdle BGTask SRPrevSleep kCPU]

2020-07-23 13:03:04 +0200 Assertions PID 205(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:00 id:0x0xd000085f8 [System: PrevIdle BGTask]

Currently in use:

autorestart 0
Sleep On Power Button 1
hibernatefile /var/vm/sleepimage
proximitywake 0
powernap 0
gpuswitch 2
networkoversleep 0
disksleep 10
sleep 20 (sleep prevented by sharingd)
hibernatemode 0
ttyskeepawake 1
displaysleep 20
tcpkeepalive 0
womp 0

 

[CaseySJ]

@CaseySJ its not a backup disk, i just copied my efi folder to my macbook when i finally got the hackintosh all set so i would have a backup of a known good efi if i ever messed it up. I just checked my bios version and its F8, i dont recall ever having to unlock anything on it, i havent updated it since i got it and i had mojave booted on it and now i have catalina booted on a spare disk so i can get into the mojave drive, i would think that rules out a bios config problem right? i dont know what unlocking msr does

I can examine the EFI folder from the Mojave disk as mentioned in the last bullet of the previous reply.

As a not-so-gentle reminder to everyone:

I posted the following rant on the Z490 Vision D thread, but it's worth repeating here:

... SOAP BOX ... (I am not singling anyone out)

We live in a digital age. Our data is our life. Photos, videos, music, tax filings, calendars, reminders, email, shopping, social networking, gaming, online banking, video and music streaming, etc. are all digital.

We pay thousands of dollars a year for car insurance and home insurance and property insurance, but we don't give a rat's &%$* about insuring our digital data?

A Hackintosh is not a real Macintosh, and it will never be. Apple never tests their software on our hardware. Apple does not care if MacOS works or fails miserably on our hardware. We take a risk with Hackintosh. There is no guarantee it's going to be reliable day in and day out, but we risk it anyway. But risk must be balanced by a safety net. A full bootable backup is that safety net; it is the life-saver we all must have.

A full bootable backup can cost less than $100. Not $100 per year or $1000 per year as for insurance, but $100 one time only.

THERE IS NO EXCUSE FOR NOT MAKING A FULL BOOTABLE BACKUP. THERE WILL NEVER BE AN EXCUSE FOR THIS INCOMPREHENSIBLE OVERSIGHT.

... END OF SOAP BOX ...

 

[Inqnuam]

I can examine the EFI folder from the Mojave disk as mentioned in the last bullet of the previous reply.

As a not-so-gentle reminder to everyone:

I posted the following rant on the Z490 Vision D thread, but it's worth repeating here:

... SOAP BOX ... (I am not singling anyone out)

We live in a digital age. Our data is our life. Photos, videos, music, tax filings, calendars, reminders, email, shopping, social networking, gaming, online banking, video and music streaming, etc. are all digital.

We pay thousands of dollars a year for car insurance and home insurance and property insurance, but we don't give a rat's &%$* about insuring our digital data?

A Hackintosh is not a real Macintosh, and it will never be. Apple never tests their software on our hardware. Apple does not care if MacOS works or fails miserably on our hardware. We take a risk with Hackintosh. There is no guarantee it's going to be reliable day in and day out, but we risk it anyway. But risk must be balanced by a safety net. A full bootable backup is that safety net; it is the life-saver we all must have.

A full bootable backup can cost less than $100. Not $100 per year or $1000 per year as for insurance, but $100 one time only.

THERE IS NO EXCUSE FOR NOT MAKING A FULL BOOTABLE BACKUP. THERE WILL NEVER BE AN EXCUSE FOR THIS INCOMPREHENSIBLE OVERSIGHT.

... END OF SOAP BOX ...

Questions
i'v Time Capsule that I use for my MacBook Pro backups,
Q1: can I use Time Machine to backup my Hackintosh like a real Mac?
Q2: My OC EFI folder is copied in my iCloud Drive also in my MacBook Pro and on a USB key.
Q3: Finally if for some reason my Hackintosh breaks, can I use my EFI folder to create a new bootable USB, make a fresh new install of macOS and use Time Machine to restore all my macOS data?

 

[Badf1sh]

I agree 100%, i have a backup server with a hardware raid controller for my projects, but the machine is currently down because i moved recently and havent had time to set it back up, i need to do that, I am attaching the EFI folder from the mojave disk though i don't suspect it to be the problem since I can get into clover from either the mojave disk or the catalina disk and both display the catalina install, neither show the mojave install

 

[Badf1sh]

Im not sure if this is relevant but I'm on the Catalina install at the moment and opened disk utility and I notice there is a Catalina - data partition but there isn't one for the Mojave

 

[gandem]

THERE IS NO EXCUSE FOR NOT MAKING A FULL BOOTABLE BACKUP. THERE WILL NEVER BE AN EXCUSE FOR THIS INCOMPREHENSIBLE OVERSIGHT.

As a video creative, I managed a production house for decades. Even on real Macs and raid appliances, failures happen- sometimes hardware, sometimes human. It only takes one time getting burned and you'll never do it again. I had a raid controller go bad, and destroy the entire array. Technical guys said it was a 1/1,000,000 kind of failure that never happens. Ugh! That was the last time I ever trusted a single appliance in my career. Backup everything! Data management should be job #1.

 

[tchit]

Hello,
I don't know if this issue has been discussed by other people in this thread but I can't perform a search in these 2391 pages :

I booted on Linux from a portable Linux USB key. After that when I wanted to start OS X, I got the good old "Couldn't allocate runtime area". I was able to start after clearing my CMOS AND keeping a USB key plugged (the Linux key, I haven't tried with other keys.)
I've run into this issue a few other times. I'm not 100% sure clearing CMOS and plugging the key is the solution each time, I think another time I had to unplug to key to be able to start, but when I boot my portable Linux distribution I know that I will get runtime allocation errors next and that I'll have to clear the CMOS and try a few times to be able to boot OS X. Any ideas on how to fix this?
I'm using OcQuircks and FwRuntimeServes.

Thanks a lot!

 

[CaseySJ]

Questions
i'v Time Capsule that I use for my MacBook Pro backups,
Q1: can I use Time Machine to backup my Hackintosh like a real Mac?
Q2: My OC EFI folder is copied in my iCloud Drive also in my MacBook Pro and on a USB key.
Q3: Finally if for some reason my Hackintosh breaks, can I use my EFI folder to create a new bootable USB, make a fresh new install of macOS and use Time Machine to restore all my macOS data?

Technically speaking, this is actually okay. Time Machine does not back up the EFI partition, but since you're backing up EFI manually, you have everything you need to restore the system. If you're comfortable with this procedure, it's okay with me.

However, having a single consolidated bootable backup is considerably more efficient when something goes wrong. Here are some of the many benefits of a single consolidated bootable backup:

• You can boot from the backup disk and try to repair the original disk.
• The EFI and macOS partitions are consolidated in one place so you never have to guess if you're using the right EFI with the right macOS.
• If you know which files have been corrupted on the original disk, you can copy selected files from the backup disk and move them to the original.
• You can even create a backup of the backup, and store that off-site at work, at a family member's home, in a bank safe deposit box, etc.

 

[CaseySJ]

I agree 100%, i have a backup server with a hardware raid controller for my projects, but the machine is currently down because i moved recently and havent had time to set it back up, i need to do that, I am attaching the EFI folder from the mojave disk though i don't suspect it to be the problem since I can get into clover from either the mojave disk or the catalina disk and both display the catalina install, neither show the mojave install

Oh I see. The problem is that the option to "Boot macOS Mojave" does not appear in the Clover Boot Menu? But "Boot macOS Catalina" is there and it works?

If so, you're right -- this this not a Clover configuration problem. Please try this:

• Boot into Catalina
• Run Disk Utility
• Select the the Mojave disk if it appears in Disk Utility
• Select First Aid and let it scan for problems

Im not sure if this is relevant but I'm on the Catalina install at the moment and opened disk utility and I notice there is a Catalina - data partition but there isn't one for the Mojave

This is correct. Mojave does not contain the "- Data" volume. That was first added in Catalina.

 

[Badf1sh]

@CaseySJ Which volume should I run first aid on, Samsung SSD 970, container disk1, or Mojave?