Recent content by brianx

Thanks for quoting that. It was indeed my question in the first place. Is it a common sign/behaviour when a drive is not recognised? I searched a lot but was unable to find similar cases on the internet (or probably I do not know the right keyword).

If it is faulty, how is it detected on the BIOS list? And why does it stop the OS drive to boot? It is under warranty, and I can easily return it for a replacement, but what my claim should be? It is recognised by the system.

Yes, it is 3.90 (https://www.asrock.com/mb/AMD/X399%20Taichi/index.asp#BIOS)

What do you exactly mean by the latest motherboard? It is https://www.asrock.com/mb/AMD/X399%20Taichi/index.asp with Threadripper 1950x I had updated the BIOS a few months ago. You mean removing Intel drives and using Seagate only? Then, there is no OS to boot from it. With Seagate, it gets...

I have ASRock X399 Taichi with two M.2 NVMe (Intel 660P 2TB). One is used for the OS (Ubuntu) and the other is for the storage. I installed another NVMe (Seagate FireCuda 510 2TB), but the system does not boot (the boot drive is still one of the Intel 660P drives). When I remove the third NVMe...