Contribute
Register

Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

mm2margaret said:
So, @CaseySJ, I think you'll like this analysis and recommendation:

if Apple continue to push this as hard as they are (no bootable backups), and you need a great spare/backup Mac, well then this is a great argument for a Hackintosh spare! It's obviously cheaper, easier to upgrade, alter in many ways and put into production. As long as Macs support x86, then this can be a viable option!

So, there, another argument for a Hackintosh....if you need a spare, well, here is one viable (and affordable) option!
Click to expand...
Let's assume for a moment that bootable backups are no longer an option and we have (a) many third-party licensed applications, (b) many third-party licensed plug-ins, (c) lots of project files, data files, etc.

We know that:
  • macOS system files are installed in their own APFS sealed volume.
  • All of our applications, plug-ins, project files, data files, etc. are stored on the "data" volume.
We can:
  • Make full and incremental backups of the "data" volume freely.
    • Understandably, this is the 'stuff' that's most important to us.
In the event of a system crash or other major or minor disaster:
  • We can reformat the internal SSD and reinstall macOS from scratch.
  • We can then clone our backed-up "data" volume to the internal "data" volume that is located in the same volume group as the newly installed macOS.
    • Question 1: Is this viable?
    • Question 2: If not viable, then we can clone our backed-up data volume to a new APFS volume created on the internal SSD.
  • We can then go to System Preferences --> Users & Groups --> Advanced and point our home directory to the restored data volume.
So total recovery time would be:
  • Time to install macOS from scratch
  • Time to clone backup "data" volume to new internal data volume
Does anyone see a technical glitch in this scenario?
 
mm2margaret said:
Clonezilla and maybe Acronis, and yes, for the most part (but not absolute) drive of equal or greater capacity. I use Clonezilla, boot from a USB and it works. Bought Acronis, but haven't tested it yet.
Click to expand...
I mean a hardware based cloner not software.
Typically has two slots and you plug the source into one and the target into another, press a button and it makes an exact copy.
 
hhargreaves said:
Just upgraded to Monterey, and am experiencing very long boot times (also have a Samsung 970 pro). I am using the latest opencore with z490 version D and 10900k.

Wondering if there are any known fixes/workarounds (like using Hfs+, or formating and reinstalling)?
Click to expand...
Do you have a spare SATA SSD or a spare NVMe SSD that is not made by Samsung? If so, you could try cloning the internal SSD (that is running Monterey) to that drive and boot directly from that drive. Does it boot quickly?
 
sckn said:
I've just tried, nothing has changed. Sorry.
Click to expand...
It may be necessary to report this issue to OpenIntelWireless group on GitHub -- but please check their Issues section to see if others are experiencing the same problem.

Meanwhile, we'll continue to see what we can do here.
 
Trepamuros said:
I've just updated my Hackintosh to Monterey. 25 minutes and a few automatic reboots.

Smooth and easy process! :)

Z490 Vision D + i7 10700 + RX580 (OC 0.7.4)

Boot time: 1 min. aprox. (1 TB WD Black SN750 NVMe)
Click to expand...
Awesome!! 100 points for WD Black!
 
Hey planning upgrade to Monterey macos. Have same build, any tips or warnings before that?
Also, is there any information about RX 6600 XT GPU support on new OS?
What model identifier is best to use? Currently on Big Sur I use iMac20,2
By the way, I saw that Intel WiFi card support got better, does this offers native Wi-Fi on board activity?
 
Build 1
Z390 I AORUS PRO WIFI |  i7 9700K |  AORUS Radeon RX 580
Build 2
Z490 Vision D |  i7 10700K |  Radeon Red Dragon RX 570 4GB
Build 3 : Z590I Vision D
Z490 Vision D |  i7 10700K |  Radeon RX 580 GTS XXX Edition
CaseySJ said:
Let's assume for a moment that bootable backups are no longer an option and we have (a) many third-party licensed applications, (b) many third-party licensed plug-ins, (c) lots of project files, data files, etc.

We know that:
  • macOS system files are installed in their own APFS sealed volume.
  • All of our applications, plug-ins, project files, data files, etc. are stored on the "data" volume.
We can:
  • Make full and incremental backups of the "data" volume freely.
    • Understandably, this is the 'stuff' that's most important to us.
In the event of a system crash or other major or minor disaster:
  • We can reformat the internal SSD and reinstall macOS from scratch.
  • We can then clone our backed-up "data" volume to the internal "data" volume that is located in the same volume groupas the newly installed macOS.
    • Question 1: Is this viable?
    • Question 2: If not viable, then we can clone our backed-up data volume to a new APFS volume created on the internal SSD.
  • We can then go to System Preferences --> Users & Groups --> Advanced and point our home directory to the restored data volume.
So total recovery time would be:
  • Time to install macOS from scratch
  • Time to clone backup "data" volume to new internal data volume
Does anyone see a technical glitch in this scenario?
Click to expand...

Wow. You are really stuck on this. Yes, there is a glitch. Its the time to do that versus booting a bootable disk. I already went through a scenario. What more do you want?
 
Hackintosh-ProVirgin said:
I am installing Monterey right now and hope the new OS will resolve the long boot time issue. I was on Samsung 970 EVO (the not plus version) , but I switched to the Western Digital SN550. The boot time fluctuate a lot on SN 550. Sometimes it takes less than 20 seconds to boot and sometimes takes around 90 seconds to boot. @manfriday Does your sidecar work? What config are you running on? Did enable internal graphics in the BIOS? Please let me know and thank you for sharing!
Click to expand...
This is worth doing:
  • In Terminal, type:
Bash: 
log show --last boot | grep "trims took"
  • Give it a few seconds to run then press CTRL-C to stop.
  • Post the output.
Here's the result from my Z490 Vision D with release version of Monterey:
Code: 
kernel: (apfs) spaceman_scan_free_blocks:3153: disk3 scan took 1.913441 s, trims took 1.786507 s
kernel: (apfs) spaceman_scan_free_blocks:3153: disk2 scan took 2.299866 s, trims took 2.262432 s
Note that both operations took less than 3 seconds.
 
You must log in or register to reply here.
Copyright © 2010 - 2023 tonymacx86 LLC
Back
Top