nvme question

[JQam]

This is my build as of now https://pcpartpicker.com/user/jaisonb/saved/#view=wWyFt6

 

The Sabrent 1TB is my windows drive in the PCIe 4 slot.  The Crucial mx500 is my Fedora drive. Kingston 2TB  is my games and media drive in the PCIe3 slot. The Seagate is a backup to the Kingston.

 

 I bought Crucial P5 Plus 1TB Gen4 and Crucial P5 Plus 2TB Gen4 drives to replace the existing NVME drives.  The plan was to replace the Kingston with the 2TB P5 and throw the Kingston into the Thinkpad that needs more storage.    Apparently my system wasn't agreeing with the 2TB P5 gen 4 in the gen 3 slot.  It was up less than a day and the drive would constantly drop off. I thought the drive had overheated and kill itself.  I decided to swap the gen 3 Sabrent and gen 4 crucial  around to match the appropriate lanes.  The drive appears to be working ok with no weird errors. 

 

Now I just don't know if i should bother swapping out the Sabrent for the P5 1TB.

 

I thought these drives were backwards compatible.  Was the 2TB P5 just pulling to much power or something?

[noob0saur]

It is backwards compatible, i have a WD SN750 SE gen4 on 3x slot and i've never had any any issue without doing anything except to connect it, maybe your port is broken? dropping the drive sounds like a disconnection for me or a bad contact, good luck...

 

Also i've just thought about that, check your SATA DRIVES if you have any and change their SATA PORT, some of them interfere with Pcie lanes!

[JQam]

9 minutes ago, noob0saur said:

Also i've just thought about that, check your SATA DRIVES if you have any and change their SATA PORT, some of them interfere with Pcie lanes!

Thanks for the reply. Maybe it was just a weird contact issue.  Yes, I do know that using the second NVME disables SATA 5 and 6.  I do have an SSD and HDD in SATA ports 1 and 2.

 

Here's a shot of an issue I was having. The access I had to the drive in windows would still be there but all the folders were empty.  Eventually it just disappeared altogether even in UEFI BIOS.

 

 

[noob0saur]

59 minutes ago, JQam said:

Thanks for the reply. Maybe it was just a weird contact issue.  Yes, I do know that using the second NVME disables SATA 5 and 6.  I do have an SSD and HDD in SATA ports 1 and 2.

 

Here's a shot of an issue I was having. The access I had to the drive in windows would still be there but all the folders were empty.  Eventually it just disappeared altogether even in UEFI BIOS.

 

 

So probably a weird contact issue, i don't see anything else, i would have said a D.O.A drive but you said it worked on another port...

[JQam]

59 minutes ago, noob0saur said:

So probably a weird contact issue, i don't see anything else, i would have said a D.O.A drive but you said it worked on another port...

 All seems fine.  I haven't done any large fill transfers myself but it hasn't crashed while running CrystalDiskMark.  I'll see what happens when I put the other gen 4 drive in the gen 3 slot.

[kokosnh]

The power problem is only with the first gen M.2 8TB SSD. 

And for the PCIe gen, the device should negotiate the speed they should run at. 
If the mobo max slot is gen 3, and the SSD is gen 4, the the SSD have to downgrade to PCIE 3.0 (so it should be the SSD fault for not downgrading) 
If there's an UEFi update for the mobo, I would update it (it shouldn't matter, but you can try)

[MeowMilev]

My guess is your 2TB NVME is faulty.   I met a lot of NVME users having a defecting drives if size is above 1TB.  Even my previous 2TB NVME drive only lasts me 3 years.  then if i store a lot of data in it, like above 1TB, it will fail to work and not being detected.

[JQam]

On 9/9/2023 at 11:18 AM, MeowMilev said:

My guess is your 2TB NVME is faulty.

Knowing my luck, it probably is.  It has been holding steady in the PCIe4 slot though.  Definitely have some backups.

 

On 9/6/2023 at 6:00 PM, kokosnh said:

And for the PCIe gen, the device should negotiate the speed they should run at. 
If the mobo max slot is gen 3, and the SSD is gen 4, the the SSD have to downgrade to PCIE 3.0 (so it should be the SSD fault for not downgrading) 

That's what I thought.