Clover General discussion

[naiclub]

Now 2 terabytes of disk I broke it

[iCanaro]

7 hours ago, ameenjuz said:

@Slice do not boot sandy bridge machine intel hd graphic 3000 with OpenRuntime.efi high sierra

how to boot high sierra using openrunetime.efi in Clover 5127

see clover quirks that i have signed if they can help you

 

55 minutes ago, LIMITANT said:

How this could happened? Clover is the reason

we're not kidding, a bootloader can't cause a disc to break.

[naiclub]

1 hour ago, LIMITANT said:

How this could happened? Clover is the reason !!! It's SSD or HDD ?

It's not really about the clover boot. Is that it does not boot at all And also pulled the windows down as well A Hard disk rotating disc

24 minutes ago, iCanaro said:

see clover quirks that i have signed if they can help you

 

we're not kidding, a bootloader can't cause a disc to break.

Yep, it's not about clover.

Edited January 3, 2021 by naiclub

[Max.1974]

17 hours ago, Slice said:

I don't know about Configurator but there are Custom entries that allow you to rename any entry you want.

The name of Windows entry depends on the entry.

If you want to start from /EFi/BOOT/BOOTX64.EFi then it is "EFI boot from EFI".

If you started from /EFI/Microsoft/boot/bootmgfw.efi then it is "Windows boot from EFI"

 

Thanks @Slice for everething!!! You are the Man!!! 

[deeveedee]

Just booted my rig with CLOVER r5127 for the very first time and on the very first try!  I've been selfishly waiting for the dust to clear while many of you have been developing and testing.  It is the super-easy bootloader that I've grown to know and love!  Well done!  I won't risk naming the names for fear of leaving some out, but thank you VERY MUCH for doing an AWESOME job on r5127!

 

EDIT:

The 'only' major difference I see between CLOVER r5127 and OC 0.6.3 booting Catalina 10.15.7 is something that @MacKonsti previously mentioned: there are more Energy Saver options when booting with OC.  I don't really care, but it is curious.  When booting with CLOVER r5127, options are 'Put hard disks to sleep...' and 'Wake for Ethernet ...'  With OC, the options are as shown...  Note that in this particular rig, I'm booting OC 0.6.3 and CLOVER r5127 with a custom DSDT (not using on-the-fly patching) for this (except for Plugin-Type).

 

Energy Saver Options with OC 0.6.3

Spoiler

 

Edited January 4, 2021 by tonyx86

[Henry2010]

Happy new year and wish clover gets better and better!

[MacKonsti]

12 hours ago, tonyx86 said:

EDIT:

The 'only' major difference I see between CLOVER r5127 and OC 0.6.3 booting Catalina 10.15.7 is something that @MacKonsti previously mentioned: there are more Energy Saver options when booting with OC.  I don't really care, but it is curious.  When booting with CLOVER r5127, options are 'Put hard disks to sleep...' and 'Wake for Ethernet ...'  With OC, the options are as shown...  Note that in this particular rig, I'm booting OC 0.6.3 and CLOVER r5127 with a custom DSDT (not using on-the-fly patching) for this (except for Plugin-Type).

Yes and this is strange, considering nothing else has changed at all, no parameters, no SMBIOS nothing.

Plus, on my hack (NUC8i7BEH from Intel) a perfectly working sleep breaks BADLY

I was able to even verify the SLEEP options via Hackintool or pmset -g assertions in Terminal, less options there too!

 

I hope you figure out faster than me the causes for this @tonyx86 as it seems you were able to invest some studying time this festive season on OC and Clover, certainly more than I did...

 

EDIT:

 

@Slice hello, please remind us: From the old days of hackintoshing, I remember VERY WELL that it was fully advised to TICK the option "Startup automatically after a power failure". This was in every guide. Is this still the case? Perhaps it was for Chameleon, and early Clover. Any idea if we need this ticked/active at all times? I have it anyway, from old habits... your feedback would be very significant, as usual. Спасибо

Edited January 4, 2021 by MacKonsti

[ameenjuz]

On 1/3/2021 at 6:31 PM, iCanaro said:

see clover quirks that i have signed if they can help you

 

we're not kidding, a bootloader can't cause a disc to break.

i don't know what we should say about this guys 

he do not give ans clearly and ignore with joking

[geticus]

Hi,

I'm running High Sierra on a Jingsha x99 d8 motherboard, e5-2678 v3, GTX 1060, everything is fine except USB 3.

I finally managed to do an usb mapping with USB.Map by booting with USBInjectAll.kext and XHCI-unsupported.kext but rebooting with USBMap.kext the Usb 3 ports don't work, a usb flash ejects itself, it's very strange, sometimes the usb flash drive appears, sometimes not...

What to do ?

[Pene]

Hi @Slice

 

Happy new year! How are you?

 

Your commit which changes Library/OcAppleKernelLib/KextPatcher.c breaks OC Quirk XhciPortLimit (at least for Big Sur).

This is because PatchUsbXhciPortLimit2 targets "__ZN12AppleUSBXHCI11createPortsEv" and in AppleUSBXHCI exist first "__ZN12AppleUSBXHCI11createPortsEv.cold.1" and then "__ZN12AppleUSBXHCI11createPortsEv", so the wrong one is attempted to be patched.

 

Edited January 4, 2021 by Pene

[Slice]

8 hours ago, Pene said:

Hi @Slice

 

Happy new year! How are you?

 

Your commit which changes Library/OcAppleKernelLib/KextPatcher.c breaks OC Quirk XhciPortLimit (at least for Big Sur).

This is because PatchUsbXhciPortLimit2 targets "__ZN12AppleUSBXHCI11createPortsEv" and in AppleUSBXHCI exist first "__ZN12AppleUSBXHCI11createPortsEv.cold.1" and then "__ZN12AppleUSBXHCI11createPortsEv", so the wrong one is attempted to be patched.

 

Hi @Pene,

Happy New Year!

It is unexpected problem.

I may propose to change

  .Count       = 1,

to 2 to check both procedures.

[Slice]

But where did you find this "__ZN12AppleUSBXHCI11createPortsEv.cold.1"?

[MICKHAEL]

On 1/3/2021 at 11:56 PM, tonyx86 said:

Just booted my rig with CLOVER r5127 for the very first time and on the very first try!  I've been selfishly waiting for the dust to clear while many of you have been developing and testing.  It is the super-easy bootloader that I've grown to know and love!  Well done!  I won't risk naming the names for fear of leaving some out, but thank you VERY MUCH for doing an AWESOME job on r5127!

 

EDIT:

The 'only' major difference I see between CLOVER r5127 and OC 0.6.3 booting Catalina 10.15.7 is something that @MacKonsti previously mentioned: there are more Energy Saver options when booting with OC.  I don't really care, but it is curious.  When booting with CLOVER r5127, options are 'Put hard disks to sleep...' and 'Wake for Ethernet ...'  With OC, the options are as shown...  Note that in this particular rig, I'm booting OC 0.6.3 and CLOVER r5127 with a custom DSDT (not using on-the-fly patching) for this (except for Plugin-Type).

 

Energy Saver Options with OC 0.6.3

  Hide contents

 

I think you have a problem) check again your config

 

Quote

 

Edited January 5, 2021 by MICKHAEL
quote image

[deeveedee]

2 hours ago, MICKHAEL said:

I think you have a problem) check again your config

Brilliant diagnosis    'The problem' may be that, when converting from OC config.plist to CLOVER config.plist (after already booting a system with OC), copying the following from OC to CLOVER changes the system definition (in ways that I don't understand as I stated here ).  It is possible that after converting from OC to CLOVER, I need to remove the com.apple.PowerManagement...plist kexts from /Library/Preferences and reconfigure.  I am not running that system at the moment and will need to test again later.

 

OC > CLOVER

PlatformInfo.Generic.MLB > Rt Variables.MLB

PlatformInfo.Generic.ROM > Rt Variables.ROM

PlatformInfo.Generic.SystemProductName > SMBIOS.Product Name

PlatformInfo.Generic.SystemSerialNumber > SMBIOS.Serial Number

PlatformInfo.Generic.SystemUUID > SMBIOS.SmUUID

Edited January 5, 2021 by tonyx86

[Pene]

4 hours ago, Slice said:

But where did you find this "__ZN12AppleUSBXHCI11createPortsEv.cold.1"?

 

In /System/Library/Extensions/IOUSBHostFamily.kext/Contents/PlugIns/AppleUSBXHCI.kext/Contents/MacOS/AppleUSBXHCI, a search for __ZN12AppleUSBXHCI11createPortsEv results in this:

 

I also tried your proposal of changing to ".Count = 2" in OpenCorePkg/Library/OcAppleKernelLib/CommonPatches.c, but it still doesn't get applied.

(I will mention that previously, I also checked reverting the commit pointed above in Library/OcAppleKernelLib/KextPatcher.c to the original state, and it works properly when reverted).

 

Edited January 5, 2021 by Pene

[Slice]

But hex search inside the binary found one occurrence

[Pene]

1 hour ago, Slice said:

But hex search inside the binary found one occurrence

Just checked with hex search inside the binary, and there are 4 occurrences on the Big Sur binary: two with __ZN12AppleUSBXHCI11createPortsEv and two with __ZN12AppleUSBXHCI11createPortsEv.cold.1

I attach the 11.1 binary just in case: AppleUSBXHCI

 

I also checked the Catalina binary, and there are 2 occurrences: one with __ZN12AppleUSBXHCI11createPortsEv and one with __ZN12AppleUSBXHCI11createPortsEv.cold.1

 

Actually, first I put a debug in OpenCorePkg/Library/OcAppleKernelLib/CommonPatches.c at PatchUsbXhciPortLimit2(...) and see that:

with your change at Library/OcAppleKernelLib/KextPatcher.c -> PatcherApplyGenericPatch(Patcher, &mRemoveUsbLimitV2Patch) returns Error

without that change -> it returns Success.

 

So then I looked in the binary to see why it could happen, and saw the two names, so it seemed to make sense and explain the problem.

 

Edited January 5, 2021 by Pene

[ameenjuz]

@tonyx86 @MICKHAEL

i m facing same behavoir i mentioned and posted on opencore disussion  but noone answered me

 

[deeveedee]

@ameenjuz I posted my guess.  I'm not currently running Big Sur (I occasionally "visit" BS only to test it), so I can't be certain.  Hopefully my guess offers you a clue.

Edited January 6, 2021 by tonyx86

[joevt]

8 hours ago, Pene said:

Just checked with hex search inside the binary, and there are 4 occurrences on the Big Sur binary: two with __ZN12AppleUSBXHCI11createPortsEv and two with __ZN12AppleUSBXHCI11createPortsEv.cold.1

I attach the 11.1 binary just in case: AppleUSBXHCI

 

I also checked the Catalina binary, and there are 2 occurrences: one with __ZN12AppleUSBXHCI11createPortsEv and one with __ZN12AppleUSBXHCI11createPortsEv.cold.1

 

Actually, first I put a debug in OpenCorePkg/Library/OcAppleKernelLib/CommonPatches.c at PatchUsbXhciPortLimit2(...) and see that:

with your change at Library/OcAppleKernelLib/KextPatcher.c -> PatcherApplyGenericPatch(Patcher, &mRemoveUsbLimitV2Patch) returns Error

without that change -> it returns Success.

 

So then I looked in the binary to see why it could happen, and saw the two names, so it seemed to make sense and explain the problem.

 

It's BigSur so there's a ARM and an x86 binary inside which means there's going to be two of everything.

I used Hopper to disassemble the x86 (because Hackintosh doesn't use ARM). It got the second one:

                                    __ZN12AppleUSBXHCI11createPortsEv.cold.1:        // AppleUSBXHCI::createPorts() [clone .cold.1]
000000000004305a 55                     push       rbp                          ; CODE XREF=sub_17210+1427
000000000004305b 4889E5                 mov        rbp, rsp
000000000004305e 488D3D084E0000         lea        rdi, qword [aAppleinternalb_47e6d] ; argument #1 for method _panic, "@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/IOUSBHostFamily_Drivers/IOUSBHostFamily-939.60.10/AppleUSBXHCI/AppleUSBXHCI.cpp:2439"
0000000000043065 31C0                   xor        eax, eax
0000000000043067 E8FC990400             call       _panic                       ; _panic

but the first one did not get turned into a proc correctly - I guess this is a bug in Hopper.app. According to your screenshot, the first one is supposed to start at 0x15826:

        ; ================ B E G I N N I N G   O F   P R O C E D U R E ================


                                    sub_15825:
0000000000015825 90                     nop
0000000000015826 55                     push       rbp
0000000000015827 4889E5                 mov        rbp, rsp
000000000001582a 4157                   push       r15
000000000001582c 4156                   push       r14
000000000001582e 4155                   push       r13
0000000000015830 4154                   push       r12
0000000000015832 53                     push       rbx
0000000000015833 4881ECC8000000         sub        rsp, 0xc8
000000000001583a 4989FE                 mov        r14, rdi
000000000001583d 488B05C4880300         mov        rax, qword [qword_4e108]     ; qword_4e108
0000000000015844 488B00                 mov        rax, qword [rax]
0000000000015847 488945D0               mov        qword [rbp+-48], rax
000000000001584b C78554FFFFFF00000000   mov        dword [rbp+-172], 0x0
0000000000015855 488D87BC040000         lea        rax, qword [rdi+0x4bc]
000000000001585c 48894588               mov        qword [rbp+-120], rax
0000000000015860 F687BC04000008         test       byte [rdi+0x4bc], 0x8
0000000000015867 48897D98               mov        qword [rbp+-104], rdi
000000000001586b 0F84D2010000           je         loc_15a43

Anyway, shouldn't Clover be searching for the null string terminator so that it doesn't confuse these two symbols? Or if you want to keep the substring option then add an option to not do substring.

 

[Slice]

@Pene

Look my commit if this is a solution.

[deeveedee]

Just upgraded my production rig to r5127.  Upgrade was flawless/easy!  I'm noticing the same ACPI parse error caused by r5127's "Fix SBUS" that I observed in r5122:

 

2021-01-06 10:22:19.632515-0500 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:

2021-01-06 10:22:19.632515-0500 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) ACPI Error:

2021-01-06 10:22:19.632516-0500 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) Method parse/execution failed

2021-01-06 10:22:19.632517-0500 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) Method parse/execution failed

2021-01-06 10:22:19.632518-0500 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) [\_SB.PCI0.SBUS.BUS0.DVL0._DSM] (Node ffffff80524fb210)

2021-01-06 10:22:19.632519-0500 0x71       Default     0x0                  0      0    kernel: (AppleACPIPlatform) [\_SB.PCI0.SBUS.BUS0.DVL0._DSM] (Node ffffff80524fb210)

 

If I disable CLOVER r5127's (and r5122's) "Fix SBUS" and use the attached SSDT instead, this problem is resolved.  Note that the attached SSDT also adds Device (MCHC) (this is an SSDT that I use for OpenCore), so I also disable CLOVER's "Add MCHC" when using the attached SSDT.  My system is completely defined here.

 

 

SSDT-SBUS-MCHC.zip

Edited January 6, 2021 by tonyx86

[deeveedee]

On 1/5/2021 at 5:34 AM, MICKHAEL said:

I think you have a problem) check again your config

 

After upgrading from r5122 to r5127, I "lost" all but two Energy configuration options as shown below.  I tried deleting /Library/Preferences/com.apple.Power...plists and rebooting, but that did not restore the missing energy options.  The only config.plist changes I made from r5122 to r5127 were to add missing Quirks (which I copied directly from the sample plist). Despite the missing Energy Saver options, sleep/wake still works fine after upgrading from r5122 to r5127.

 

@MICKHAEL @MifJpn @Matgen84 @chris1111  I'd value your eagle-eyes to determine the error in my config.  Full problem reporting files are attached.  Thanks!

 

EDIT: On a positive note: I've never had GB5 multi-core benchmarks this good.

 

EDIT2: @MacKonsti Are you by any chance using SMBIOS MacMini8,1 (like I am) with your NUC that is experiencing the Energy Saver issues?

 

Energy Saver Options with CLOVER r5127

Spoiler

 

Energy Saver Options with CLOVER r5122

Spoiler

 

debug_10640.zip

Edited January 7, 2021 by tonyx86
Added link to GB5 benchmarks

[Pene]

8 hours ago, Slice said:

@Pene

Look my commit if this is a solution.

Hi, thanks. Yes, it is working now.

[pctmac]

Hi

I am currently triple booting my Hack with HighSierra, Mojave and Catalina on the same SSD, with one single EFI partition with Clover 5100 in BIOS mode.
 

Spoiler

iMac:~ phil$ sudo gpt -r show disk0
Password:
start size index contents
0 1 PMBR
1 1 Pri GPT header
2 32 Pri GPT table
34 6
40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
409640 156325576 2 GPT part - 7C3457EF-0000-11AA-AA11-00306543ECAC
156735216 156325576 3 GPT part - 7C3457EF-0000-11AA-AA11-00306543ECAC
313060792 155801296 4 GPT part - 7C3457EF-0000-11AA-AA11-00306543ECAC
468862088 7
468862095 32 Sec GPT table
468862127 1 Sec GPT header
iMac:~ phil$ diskutil list
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *240.1 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk2 80.0 GB disk0s2
3: Apple_APFS Container disk1 80.0 GB disk0s3
4: Apple_APFS Container disk3 79.8 GB disk0s4
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +80.0 GB disk1
Physical Store disk0s3
1: APFS Volume Mojave SSD512 28.0 GB disk1s1
2: APFS Volume PreBoot 24.6 MB disk1s2
3: APFS Volume Recovery 517.5 MB disk1s3
4: APFS Volume VM 20.5 KB disk1s4
/dev/disk2 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +80.0 GB disk2
Physical Store disk0s2
1: APFS Volume Catalina SSD512 - Data 16.1 GB disk2s1
2: APFS Volume Catalina SSD512 11.3 GB disk2s2
3: APFS Volume PreBoot 352.1 MB disk2s3
4: APFS Volume Recovery 2.7 GB disk2s4
5: APFS Volume VM 1.1 MB disk2s5
/dev/disk3 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +79.8 GB disk3
Physical Store disk0s4
1: APFS Volume High Sierra SSD512 35.7 GB disk3s1
2: APFS Volume PreBoot 21.6 MB disk3s2
3: APFS Volume Recovery 515.0 MB disk3s3
4: APFS Volume VM 20.5 KB disk3s4

If I put ApfsDriverLoader.efi in the drivers/BIOS folder, Clover as a result shows only the first APFS volumes in the menu, i.e. Catalina.
I do not know which apfs.efi is loaded out of the 2 available on the disk (one per OS) but I guess it's loading the apfs.efi from Catalina as this is the first Volume of the disk. Am I right ?

If I copy the apfs.efi from Catalina (as this is the most recent one, v1412.141.1) to drivers/BIOS and remove ApfsDriverLoader.efi, then Clover show all the APFS Volumes. This allow me to select the OS I want to start.

So apparently it solved my issue but :
1/ is there a better way to do this ? For example by still using ApfsDriverLoader.efi which always load the last version on the disk. But then, why it doesn't work ?
2/ can I really use the same apfs.efi driver for any OS without issue ? I guess I should to use the latest available one, depending on the OS update installed on each of the 3 OS on my SSD ?

3/ is there a way to know which apfs.efi file is loaded by ApfsDriverLoader.efi ? I saw nothing in preboot.log

4/ does ApfsDriverLoader.efi load apfs.efi to show the volumes, but then when you select an OS and start to boot, it does reload the apfs.efi of the selected OS, as part of the normal boot process ?
5/ There is the known side effect : I now face the old issue of messages send to console by apfs.efi when loading : how can I get rid of these and avoid them ?

 

Thanks for your help

Thanks

 

EDIT Jan 10th

I tried to boot with Clover r5128 on a USB Key. Here is an extract from preboot where ApfsDriverLoader.efi is loaded (but do not know which apfs.efi has been loaded) and then all containers are not recognized. Any idea ?
 

3:095 0:000 === [ LoadDrivers ] =============================
3:112 0:016 Loading AudioDxe.efi status=Success
3:129 0:016 - driver needs connecting
3:129 0:000 Loading FSInject.efi status=Success
3:146 0:016 Loading SMCHelper.efi status=Success
3:163 0:016 Loading XhciDxe.efi status=Success
3:180 0:016 - driver needs connecting
3:180 0:000 Loading ApfsDriverLoader.efi status=Success
3:197 0:016 - driver needs connecting
3:197 0:000 3 drivers needs connecting ...
3:197 0:000 PlatformDriverOverrideProtocol->GetDriver overriden
3:197 0:000 APFS driver loaded

../..

8:125 0:016 === [ ScanVolumes ] =============================
8:125 0:000 Found 12 volumes with blockIO
8:125 0:000 - [00]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)
8:125 0:000 Result of bootcode detection: bootable unknown (legacy)
8:125 0:000 - [01]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(1,GPT,C7DCF6FC-3398-4CC0-9281-03DEAB3D2A62,0x28,0x64000)
8:126 0:000 Result of bootcode detection: bootable unknown (legacy)
8:126 0:000 label : EFI
8:126 0:000 - [02]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,GPT,9FEEE078-DFB6-4245-B2E9-DA486A646341,0x64028,0x95156C8)
8:127 0:000 Result of bootcode detection: bootable unknown (legacy)
8:127 0:000 - [03]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(3,GPT,11E01983-12EC-42F8-B831-1BDDB4BF393A,0x95796F0,0x95156C8)
8:127 0:000 Result of bootcode detection: bootable unknown (legacy)
8:127 0:000 - [04]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(4,GPT,93F8DC4A-469D-4203-BEEF-1D6C1BD959E4,0x12A8EDB8,0x94956D0)
8:127 0:000 Result of bootcode detection: bootable unknown (legacy)
8:127 0:000 - [05]: Volume: PcieRoot(0x0)\Pci(0x1A,0x0)\USB(0x0,0x0)\USB(0x3,0x0)
8:139 0:011 Result of bootcode detection: bootable unknown (legacy)
8:139 0:000 - [06]: Volume: PcieRoot(0x0)\Pci(0x1A,0x0)\USB(0x0,0x0)\USB(0x3,0x0)\HD(1,MBR,0x00000000,0x2,0x1EA7FE)
8:150 0:011 Result of bootcode detection: bootable unknown (legacy)
8:167 0:016 label : TESTCLOVER
8:167 0:000 This is SelfVolume !!
8:167 0:000 - [07]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,GPT,9FEEE078-DFB6-4245-B2E9-DA486A646341,0x64028,0x95156C8)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,092A473E02BA4F4995EDAA22A3DF127B)
8:167 0:000 apfsFileSystemUUID=3E472A09-BA02-494F-95ED-AA22A3DF127B, ApfsContainerUUID=733C664D-FD93-4C88-A6F2-711594B28BC6, ApfsRole=0x10
8:168 0:000 label : PreBoot
8:168 0:000 - [08]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,GPT,9FEEE078-DFB6-4245-B2E9-DA486A646341,0x64028,0x95156C8)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,25DDFB1832678B438635A61F885C212A)
8:168 0:000 apfsFileSystemUUID=18FBDD25-6732-438B-8635-A61F885C212A, ApfsContainerUUID=733C664D-FD93-4C88-A6F2-711594B28BC6, ApfsRole=0x40
8:174 0:006 label : Catalina SSD512 - Data
8:174 0:000 - [09]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,GPT,9FEEE078-DFB6-4245-B2E9-DA486A646341,0x64028,0x95156C8)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,9BDBFFC41EFCBA439823488236B031B2)
8:174 0:000 apfsFileSystemUUID=C4FFDB9B-FC1E-43BA-9823-488236B031B2, ApfsContainerUUID=733C664D-FD93-4C88-A6F2-711594B28BC6, ApfsRole=0x1
8:179 0:004 label : Catalina SSD512
8:179 0:000 - [10]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,GPT,9FEEE078-DFB6-4245-B2E9-DA486A646341,0x64028,0x95156C8)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,E5BCDE05309CD74EBA60B0C031600853)
8:179 0:000 apfsFileSystemUUID=05DEBCE5-9C30-4ED7-BA60-B0C031600853, ApfsContainerUUID=733C664D-FD93-4C88-A6F2-711594B28BC6, ApfsRole=0x4
8:179 0:000 label : Recovery
8:179 0:000 - [11]: Volume: PcieRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0x0,0x0)\HD(2,GPT,9FEEE078-DFB6-4245-B2E9-DA486A646341,0x64028,0x95156C8)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,175955BDE4041D4AA5DED75D940A9587)
8:180 0:000 apfsFileSystemUUID=BD555917-04E4-4A1D-A5DE-D75D940A9587, ApfsContainerUUID=733C664D-FD93-4C88-A6F2-711594B28BC6, ApfsRole=0x8
8:180 0:000 label : VM
8:180 0:000 Searching volumes for latest nvram.plist ...
8:180 0:000 loaded Status=Not Found
8:180 0:000 PutNvramPlistToRtVars: nvram.plist not found

Edited January 10, 2021 by pctmac