F5F Stay Refreshed Hardware Desktop Issue with m.2 drive functionality

Issue with m.2 drive functionality

Issue with m.2 drive functionality

P
phlip9
Member
128
04-08-2022, 03:20 AM
#1
I checked the BIOS to confirm if the drive was listed, but it wasn't there. Then I searched for Gen 3 and found a drive labeled MN-5216 instead of the expected MKNSSDTS2TB-D8. The motherboard model is MSI B650 Tomahawk Wi-Fi, with a Ryzen 7 7700X CPU and an MSI MAG A850G chipset. Storage is Mushkin Tempest – 2TB PCIe Gen3 x4 NVMe 1.4. I've tried another drive (Mushkin Vortex – 2TB PCIe Gen4 x4 NVMe) in all slots, but it still doesn't appear. Now I'm manually changing the boot order and hoping it shows up, but only 2GB. Any advice would be greatly appreciated.
P
phlip9
04-08-2022, 03:20 AM #1

I checked the BIOS to confirm if the drive was listed, but it wasn't there. Then I searched for Gen 3 and found a drive labeled MN-5216 instead of the expected MKNSSDTS2TB-D8. The motherboard model is MSI B650 Tomahawk Wi-Fi, with a Ryzen 7 7700X CPU and an MSI MAG A850G chipset. Storage is Mushkin Tempest – 2TB PCIe Gen3 x4 NVMe 1.4. I've tried another drive (Mushkin Vortex – 2TB PCIe Gen4 x4 NVMe) in all slots, but it still doesn't appear. Now I'm manually changing the boot order and hoping it shows up, but only 2GB. Any advice would be greatly appreciated.

K
kervinc
Posting Freak
804
04-08-2022, 07:02 AM
#2
Consider testing on a different machine if possible, as it appears the drive is faulty.
K
kervinc
04-08-2022, 07:02 AM #2

Consider testing on a different machine if possible, as it appears the drive is faulty.

S
Selrahcc
Member
224
04-09-2022, 01:25 AM
#3
S
Selrahcc
04-09-2022, 01:25 AM #3

F
FureaMC
Senior Member
564
04-09-2022, 12:20 PM
#4
Is the product still covered by its warranty? As Kilrah mentioned, it seems this device appears to be defective, displaying just 2GB instead of the expected capacity.
F
FureaMC
04-09-2022, 12:20 PM #4

Is the product still covered by its warranty? As Kilrah mentioned, it seems this device appears to be defective, displaying just 2GB instead of the expected capacity.

E
eskzz
Posting Freak
909
04-10-2022, 05:43 AM
#5
I purchased it from Amazon and I can exchange it.
E
eskzz
04-10-2022, 05:43 AM #5

I purchased it from Amazon and I can exchange it.

P
Pangaea_
Member
191
04-10-2022, 06:20 AM
#6
I'll return it.
P
Pangaea_
04-10-2022, 06:20 AM #6

I'll return it.

T
TotalGamer144
Member
180
04-11-2022, 05:42 AM
#7
I signed up to share my observations about this matter. Experiencing the same issue led me to purchase an additional NVMe drive and a motherboard to narrow down the cause. I tried two motherboards: A) Gigabyte B650 AORUS ELITE AX (bios: F3h) and B) ASUS ROG STRIX B650-A GAMING WIFI (bios: 0823 x64). I also used two SSDs—Mushkin Tempest 2TB M.2 and Kingston NV2 NVMe PCIe 4.0 SSD 1TB M.2.

My setup included installing one SSD at a time per slot, using PCIe protocols gen4, gen3, and auto. I didn’t have a GPU and relied on CPU graphics. Disabled Secure Boot for the SSD (Kingston) and it worked well on both boards A and B.

For SSD1:
- After BIOS reset, first boot detected correctly but with 0 GB space.
- On every second boot, it failed to recognize the model as MN-5261 with 2.1 GB.
- Removing SSD1 and rebooting restored detection with 0 GB.

I’ve gathered more details now, but still no resolution. On my old Z170 board and laptop, SSD1 functions properly. I suspect a compatibility issue with the B650 chipset or perhaps an unfortunate coincidence with the CPU. I’ve used "AMD Ryzen 5 7600x" in all tests. I’m currently contacting Gigabyte support (no luck) and Mushkin support (helpful). I’ll keep you updated on any developments.
T
TotalGamer144
04-11-2022, 05:42 AM #7

I signed up to share my observations about this matter. Experiencing the same issue led me to purchase an additional NVMe drive and a motherboard to narrow down the cause. I tried two motherboards: A) Gigabyte B650 AORUS ELITE AX (bios: F3h) and B) ASUS ROG STRIX B650-A GAMING WIFI (bios: 0823 x64). I also used two SSDs—Mushkin Tempest 2TB M.2 and Kingston NV2 NVMe PCIe 4.0 SSD 1TB M.2.

My setup included installing one SSD at a time per slot, using PCIe protocols gen4, gen3, and auto. I didn’t have a GPU and relied on CPU graphics. Disabled Secure Boot for the SSD (Kingston) and it worked well on both boards A and B.

For SSD1:
- After BIOS reset, first boot detected correctly but with 0 GB space.
- On every second boot, it failed to recognize the model as MN-5261 with 2.1 GB.
- Removing SSD1 and rebooting restored detection with 0 GB.

I’ve gathered more details now, but still no resolution. On my old Z170 board and laptop, SSD1 functions properly. I suspect a compatibility issue with the B650 chipset or perhaps an unfortunate coincidence with the CPU. I’ve used "AMD Ryzen 5 7600x" in all tests. I’m currently contacting Gigabyte support (no luck) and Mushkin support (helpful). I’ll keep you updated on any developments.

B
BernieSand3rs
Member
153
04-12-2022, 03:58 AM
#8
Hello, I encountered the same issue with a 1Tb Mushkin M.2 Tempest drive. It displayed as MN-5216 only after updating my BIOS from F15 to the latest F16g version. Now that I’ve switched back to the older F15 BIOS, it shows correctly and functions properly. I hope this helps someone else in the future. It’s possible the drive isn’t compatible with certain BIOS versions, which I’m not sure about.
B
BernieSand3rs
04-12-2022, 03:58 AM #8

Hello, I encountered the same issue with a 1Tb Mushkin M.2 Tempest drive. It displayed as MN-5216 only after updating my BIOS from F15 to the latest F16g version. Now that I’ve switched back to the older F15 BIOS, it shows correctly and functions properly. I hope this helps someone else in the future. It’s possible the drive isn’t compatible with certain BIOS versions, which I’m not sure about.

X
xanderzone317
Posting Freak
957
05-03-2022, 01:48 AM
#9
The SSD firmware seems to have reacted unexpectedly. In such cases, it boots in ROM mode and recognizes itself using the factory name of its controller. It appears "MN-5216" is the controller's alias. Reach out to the manufacturer to obtain a firmware update or flash for this drive. Wishing you success.
X
xanderzone317
05-03-2022, 01:48 AM #9

The SSD firmware seems to have reacted unexpectedly. In such cases, it boots in ROM mode and recognizes itself using the factory name of its controller. It appears "MN-5216" is the controller's alias. Reach out to the manufacturer to obtain a firmware update or flash for this drive. Wishing you success.