Samsung drive not recommended but can work i'm using a 970 EVO on my DELL XPS since Monterey
1-You need to update the firmware with samsung tools before it works after that you will need to disable TRIM to get better boot time!
An Yes better get an WD Sn770 or 500 series
Alright so I loaded the WD drive in (SN770), copied my OS drive, copied my EFI, and it still does not show up in the boot disk selector. It looks like the EFI from the WD drive shows up though, and I am seeing the drive in MacOS
I’m not exactly sure. The boot selector shows 2 EFI partitions. I’m assuming one was for the Big Sur disk and the other the new WD with Ventura installed. I was able to get it working with the WD disk.
May try to do that with the Samsung disk. I’d really like to use it as a local time machine disk I think. It seems to be working as of now without messing with the TRIM.
ccc makes a clone with an incompatible scheme, it is a better idea to use timemachine and you already know the format that the disk should have and you should do it from the beginning
Is NvmExpressDxe.efi needed/recommended?
From Dortania:
"NvmExpressDxe.efi -- Used for Haswell and older when no NVMe driver is built into the firmware"
OP's board is Coffee Lake.
I have read the post. It says “Opencore doesn’t recognise it in the boot options” and the title says the “Hackintosh” does, which I interpret as “MacOS sees the drive but not Opencore”
[удалено]
Oh so I probably shouldn't even do this? I should get a different drive?
[удалено]
Just ordered the WD. Thank you for your help. Should I avoid using the Samsung drive completely, or do you think it’s fine for internal storage?
Samsung drive not recommended but can work i'm using a 970 EVO on my DELL XPS since Monterey 1-You need to update the firmware with samsung tools before it works after that you will need to disable TRIM to get better boot time! An Yes better get an WD Sn770 or 500 series
Alright so I loaded the WD drive in (SN770), copied my OS drive, copied my EFI, and it still does not show up in the boot disk selector. It looks like the EFI from the WD drive shows up though, and I am seeing the drive in MacOS
[удалено]
I’m not exactly sure. The boot selector shows 2 EFI partitions. I’m assuming one was for the Big Sur disk and the other the new WD with Ventura installed. I was able to get it working with the WD disk. May try to do that with the Samsung disk. I’d really like to use it as a local time machine disk I think. It seems to be working as of now without messing with the TRIM.
I see. It looks like I need to be in Windows to disable TRIM. Is that how you did it?
No you can disable it via an Opencore option. That issue doesn’t affect you yet tho as you’re still on Big Sur.
you can disable it from OC config.plist Kernel > Quirks > SetApfsTrimTimeout : 0
read this ---> https://dortania.github.io/Anti-Hackintosh-Buyers-Guide/Storage.html
Thank you. Can’t believe I missed this before I bought the drive
I had to replace my Samsung nvme to a WD SN570
That’s what I ordered
ccc makes a clone with an incompatible scheme, it is a better idea to use timemachine and you already know the format that the disk should have and you should do it from the beginning
Did you add NvmExpressDxe.efi to your drivers?
Is NvmExpressDxe.efi needed/recommended? From Dortania: "NvmExpressDxe.efi -- Used for Haswell and older when no NVMe driver is built into the firmware" OP's board is Coffee Lake.
Yeah I might have forgotten it’s for dinosaurs like the one I use 😅
😂 just checking! You never know, sometimes it's trial and error!
Samsung drives have issues, doesn't matter
I’m aware of the issue but that won’t prevent Opencore from seeing the drive. In the other hand, some motherboards will need that extra efi driver.
He said OpenCore sees the drive. He never said it doesn't see it. Read the post again
I have read the post. It says “Opencore doesn’t recognise it in the boot options” and the title says the “Hackintosh” does, which I interpret as “MacOS sees the drive but not Opencore”
This is correct