10-25-2018 07:54 PM - last edited on 03-06-2024 10:24 PM by ROGBot
10-26-2018 03:15 AM
11-11-2018 08:48 PM
HiVizMan wrote:
Thanks for the update mate, let me see if I can bump this issue up the ladder and see if we can get some kind of resolution for users.
Again thanks for taking the time to share.
11-28-2018 02:15 PM
12-01-2018 02:51 AM
12-01-2018 11:16 AM
btrach144 wrote:
Did you read the recent news? Samsung hardware encryption on their SSDs can be easily reversed engineered. Samsung event had a press release that directed customers to use software based encryption if they wish to keep their data secure.
12-01-2018 05:01 AM
12-01-2018 11:31 AM
JustinThyme wrote:
If Samsung is the only drive having the issues cant hardly blame it on ASUS. Not the first time and Im sure it wont be the last. The single biggest thing is Samsung trying to protect their Magician software from working on anything but a Samsung drive, if its encrypted their software wont work. ANY other drives encrypt just fine. I'm running a pair of Intel 900P drives on VROC raid 0 bit locker encrypted. You can encrypt the Samsung drives as non boot drives and the magician software wont work. You cant even put two drives in raid 0 and have the software or drivers work because neither can see past a raid controller. This is on Samsung, same results on any other MOBO.
12-05-2018 12:52 AM
Outontheporch wrote:
I'm not entirely blaming it on Asus. Samsung is blaming Asus, Asus is blaming Samsung. I'm caught in the middle and it's disappointing to me.
SATA drives work just fine with both ASUS and SAMSUNG. Magician is not an issue in my experience. Something is wrong either in Samsung's firmware or Asus' bios. Samsung claims to have fixed the problem, but the solution needs to be done in the BIOS. Whether the problem is a bug in Samsung's implementation of OPAL/Edrive or whether that is an ASUS bios bug is unknown. ASUS has no interest in fixing it apparently. Asrock boards work fine with the Samsung NVME e-drive after a new update.
With your 900P drives - are those boot drives? The issue here is NVME boot drives. Everything apparently works just fine for NVME non-boot drives. If yes, than that at least suggests that the problem might be a bug in the way Samsung implemented e-drive.
12-05-2018 12:55 AM
JustinThyme wrote:
If Samsung is the only drive having the issues cant hardly blame it on ASUS. Not the first time and Im sure it wont be the last. The single biggest thing is Samsung trying to protect their Magician software from working on anything but a Samsung drive, if its encrypted their software wont work. ANY other drives encrypt just fine. I'm running a pair of Intel 900P drives on VROC raid 0 bit locker encrypted. You can encrypt the Samsung drives as non boot drives and the magician software wont work. You cant even put two drives in raid 0 and have the software or drivers work because neither can see past a raid controller. This is on Samsung, same results on any other MOBO.