Apr 27, 2021
5
0
10
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 drive, the system boots as usual.

I swapped the places of NVMe drives but no luck.

The only suspicious thing is that: I see Seagate FireCuda NVMe on the list of storages on the BIOS page, but there is a Chinese/Japanese letter/symbol at the end of it.
 
Apr 27, 2021
5
0
10
latest motherboard? could just be the seagate m.2 drive

What do you exactly mean by the latest motherboard? It is https://www.asrock.com/mb/AMD/X399 Taichi/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 stuck at the boot stage. It seems like it tries to boot from Seagate while the boot drive has been chosen to be Intel.
 
Apr 27, 2021
5
0
10
test the m.2 on another working pc? sound like need to rma/return it

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.
 
Apr 27, 2021
5
0
10
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).