SSD problem

CountMike · Aug 10, 2023

Check your MB manual, in some cases M.2 and another SATA ports clash.

Scannerman · Aug 10, 2023

CountMike said:
Check your MB manual, in some cases M.2 and another SATA ports clash.

Yes, sir. In fact a second stick of NVMe can cost you two SATA ports in some cases.

It's all about the bandwidth. That's why I opted for a system board with 40 lanes.

CountMike · Aug 10, 2023

Scannerman said:
Yes, sir. In fact a second stick of NVMe can cost you two SATA ports in some cases.
It's all about the bandwidth. That's why I opted for a system board with 40 lanes.

My has 16 PCIe lanes from CPU and another 24 from chipset to supply 4 NVMe SSDs. 5th is a SATA M.2 SSD. so 5 M.2 SSDs altogether, no 2.5" drives. It doesn't disable any SATA ports.

Scannerman · Aug 10, 2023

CountMike said:
My has 16 PCIe lanes from CPU and another 24 from chipset to supply 4 NVMe SSDs. 5th is a SATA M.2 SSD. so 5 M.2 SSDs altogether, no 2.5" drives. It doesn't disable any SATA ports.

Yup. 40 lanes total is mighty handy. :)

Scannerman · Aug 10, 2023

Scannerman said:
Yup. 40 lanes total is mighty handy. :) I have two SATA ports disabled but then I'm also running 5 RAID arrays in addition to two sticks of NVMe.

Harleygjc · Aug 10, 2023

@Scannerman who the hell do you think you are having a go at me when you know nothing about me? just to make you aware I have no communication skill troubles and I find it quite offensive,you know nothing about me so are not in the position to say anything like that,oh and for your info,the drive was busted,I sent it back and got a new one which worked fine!

Scannerman · Aug 11, 2023

Harleygjc said:
@Scannerman who the hell do you think you are having a go at me when you know nothing about me? just to make you aware I have no communication skill troubles and I find it quite offensive,you know nothing about me so are not in the position to say anything like that,oh and for your info,the drive was busted,I sent it back and got a new one which worked fine!

I apologize if I've offended you. Perhaps you considered the help you were were being offered wasn't worthy of a response.

Scannerman said:
Wish I had been here sooner to read this. rockyanexp and others repeatedly told this fellow to install the driver, or install IRST. There seemed to be some issue with the OP's communication skills more than that of an issue with the hardware. I would have suggested that they check the NVMe settings in the UEFI as this is a common oversight. Despite what some might think there are some NVMe that will not work in some system boards unless IRST is active. I know that this is an issue with some ASUS system boards but I'm not as familiar with GIGABYTE in that regard. I would always recommend ASUS to clients so most of my builds were ASUS systems. I make no such recommendation anymore because ASUS today is a far cry from what they used to be. To be fair, I am running two GIGABYTE boards on the home front on a regular basis, both builds are by yours truly. GIGABYTE has come a long way. I have no idea what they are like for support because I never needed it.

One more thing: There are some issues with Samsung's 980 NVMe. In fact, many of these have been recently recalled. Also, some system boards simply cannot function with it. This is not a new issue with Samsung NVMe. In fact, I recall having to return a stick after contacting Samsung and being told by them that it would not work on my platform because it was made more specifically for laptops. Always helps to check QVL.

I hope this little tid bit helps any readers in the future.

I stated that "There seemed to be some issue with the OP's communication skills..." That is how it appeared to me. I believe we are all entitled to our opinions here. Admittedly, things are not always as they seem, but you were being offered a good deal of help that appeared to be ignored. I also mentioned that there was a problem with this particular NVMe you took issue with. I hope your replacement continues to work well for you and I'm sorry you took my words so personally. I suppose we can call this thread solved then. It's a wrap.