MP 1,1-5,1 WD Blue SA510 SATA SSD not seen after reboot

[czs]

Is anyone using the WD Blue SA510 SATA drive as a boot drive? The reason I ask is because on my cMP5,1 + OpenCore, the drive is only seen on a cold start; never seen after a warm reboot. I have tried a plain vanilla OpenCore config.plist and also clearing the PRAM\SMC but nothing has worked thus far. I know some other SSDs, such as the Samsung EVO870, exhibit similar behavior and I'm wondering if OpenCore might be the issue.

Any thoughts?

 

[TzunamiOSX]

This is a known problem with SATA III drives on the Mac Pro SATA II ports. As I know the crucial MX 500 does not have the problem. I have a WD Red and a MX 500 here and can test these drives, if you want.

 

[czs]

This is a known problem with SATA III drives on the Mac Pro SATA II ports. As I know the crucial MX 500 does not have the problem. I have a WD Red and a MX 500 here and can test these drives, if you want.

Hey @TzunamiOSX - yeah, I encountered this with the Samsung EVO 870 & Crucial BX500 series but also heard the MX line was safe. I also thought I had read all WDs were safe so if you wanna test your BX and Red, it would be good to know especially if you are also using OpenCore. Either way, it seems baffling that some SATA-based SSDs would exhibit this behavior so I'm wondering if maybe OpenCore plays a role here...

 

[Macschrauber]

Hey @TzunamiOSX - yeah, I encountered this with the Samsung EVO 870 & Crucial BX500 series but also heard the MX line was safe. I also thought I had read all WDs were safe so if you wanna test your BX and Red, it would be good to know especially if you are also using OpenCore. Either way, it seems baffling that some SATA-based SSDs would exhibit this behavior so I'm wondering if maybe OpenCore plays a role here...

Sometimes it works, when placing the SSD in the DVD bay on 2nd port. Those are the same ports, but timing is differently.

 

[czs]

Sometimes it works, when placing the SSD in the DVD bay on 2nd port. Those are the same ports, but timing is differently.

OK - so if that actually works, whereas the SATA slots never work, then this would be a pretty great clue. Not sure how we would translate that into a fix but still - could be some progress...

 

[reader50]

I have two Samsung 870 EVOs - a 4TB and a 1TB. They always show in OpenCore boot picker. And they're usually in the 4,1->5,1 SATA bays (not the optical bays).

After macOS boot (to a different drive) the 870 EVO volumes are sometimes invisible, with macOS saying the drive bay is empty. This can happen after cold boot, or occasionally after a reboot. But only when booted from a different drive (usually an M.2). Reboots usually (but not always) cause my 870 to reappear.

If I choose a volume on the 870 from the OC boot picker (or if the system is set to a volume on the 870) then boot proceeds as normal. And all volumes hosted on my 870 mount as usual.

This behavior applies to the 4TB. My 1TB 870 has been out of circulation for awhile. I think it behaved the same way, but can't recall with certainty.

It took me awhile to realize my 870 exhibited any problems, as it didn't when set as the boot drive. Note that OCLP is installed to the EFI partition of the 4TB 870 EVO, so it would be immediately obvious if the drive totally failed to mount. But the OC boot picker always appears, cold boot or reboot. So when my 870 vanishes, it does so after OC has loaded.

 

[TzunamiOSX]

Hey @TzunamiOSX - yeah, I encountered this with the Samsung EVO 870 & Crucial BX500 series but also heard the MX line was safe. I also thought I had read all WDs were safe so if you wanna test your BX and Red, it would be good to know especially if you are also using OpenCore. Either way, it seems baffling that some SATA-based SSDs would exhibit this behavior so I'm wondering if maybe OpenCore plays a role here...

I have tested 3 different SSDs, and it looks like all working well inside a Mac Pro 5,1
All were tested inside a ICY DOCK MB882SP-1S-2B 3,5 to 2,5 Adapter
I have restarted every SSD 3 times in the first slot to the front and then 3 times in the second slot. The Drives were recognized after every restart.

These are the Drives

 

[TzunamiOSX]

After macOS boot (to a different drive) the 870 EVO volumes are sometimes invisible, with macOS saying the drive bay is empty. This can happen after cold boot, or occasionally after a reboot. But only when booted from a different drive (usually an M.2). Reboots usually (but not always) cause my 870 to reappear.

I had the same problem with a 870 EVO inside my Mac Pro 5,1, but the SSD is working well inside my MacBook Pro Mid 2012