F5F Stay Refreshed Hardware Desktop M.2 intermittent connection identification

M.2 intermittent connection identification

M.2 intermittent connection identification

S
SpankinNoobs
Junior Member
14
11-14-2016, 06:37 AM
#1
I've been facing issues with my SATA M.2 not detecting properly. It only shows up when the computer was off or when another storage device was connected, not otherwise. The specific M.2 here is a Kingston A400 with a Gigabyte B550i Pro Ax in the rear slot. Other drives like an NVMe Sabrent Rocket and a Western Digital Blue WD10SPZX are installed. This M.2 came from a laptop—any advice would be appreciated. Thanks!
S
SpankinNoobs
11-14-2016, 06:37 AM #1

I've been facing issues with my SATA M.2 not detecting properly. It only shows up when the computer was off or when another storage device was connected, not otherwise. The specific M.2 here is a Kingston A400 with a Gigabyte B550i Pro Ax in the rear slot. Other drives like an NVMe Sabrent Rocket and a Western Digital Blue WD10SPZX are installed. This M.2 came from a laptop—any advice would be appreciated. Thanks!

C
ChrisM1601
Junior Member
12
11-14-2016, 01:12 PM
#2
Consider shifting the HDD's SATA cable to various SATA ports on the motherboard. I'm not sure about the exact setup, but it might be related to the HDD and the M.2 slot using the same lanes.
C
ChrisM1601
11-14-2016, 01:12 PM #2

Consider shifting the HDD's SATA cable to various SATA ports on the motherboard. I'm not sure about the exact setup, but it might be related to the HDD and the M.2 slot using the same lanes.

M
MCCrafter100
Member
159
11-27-2016, 03:23 AM
#3
I tried everything and it didn’t work. I ended up replacing another M.2 drive on a different laptop, which seems to be functioning properly now. It might have been a strange issue with that specific drive. Appreciate you taking the time to reply!
M
MCCrafter100
11-27-2016, 03:23 AM #3

I tried everything and it didn’t work. I ended up replacing another M.2 drive on a different laptop, which seems to be functioning properly now. It might have been a strange issue with that specific drive. Appreciate you taking the time to reply!