[SOLVED] Second M.2 drive only allows 1mb of space.

[JPWestmas]

Hi there! I Installed two identical kingston NV2 1 TB m.2 drives into an MPG B550I mini ATX motherboard. Drive 1 was fine and I could install windows 11 on it. The other one, Drive 0, would not accept windows during the installation phase on a new computer setup. Reason was that Drive 0 only had 1MB of space on it. Not sure why that is. I tried allocating more to it in the windows drive manager but there was no option to do so even after initializing the drive. It does not show up as a drive option in the explorer by default (that's normal before initialization I am told). Is there a tool I can use or is this usually an indication of a broken drive?

​

 

[JPWestmas]

If it helps this is the information for the odd Kingston 1MB drive:
Device SCSI\Disk&Ven_NVMe&Prod_Merak_Nvme_Ssd_C\5&37e040a9&0&000000 was configured.

Driver Name: disk.inf
Class Guid: {4d36e967-e325-11ce-bfc1-08002be10318}
Driver Date: 06/21/2006
Driver Version: 10.0.22621.2506
Driver Provider: Microsoft
Driver Section: disk_install.NT
Driver Rank: 0xFF0007
Matching Device Id: GenDisk
Outranked Drivers:
Device Updated: false
Parent Device: PCI\VEN_FE19&DEV_0001&SUBSYS_02801D89&REV_00\4&2c30e64&0&0009


This is the info for the Drive that works fine (Notice the names are quite different):
Device SCSI\Disk&Ven_NVMe&Prod_KINGSTON_SNV2S10\7&328d3e04&0&000000 was configured.

Driver Name: disk.inf
Class Guid: {4d36e967-e325-11ce-bfc1-08002be10318}
Driver Date: 06/21/2006
Driver Version: 10.0.22621.2506
Driver Provider: Microsoft
Driver Section: disk_install.NT
Driver Rank: 0xFF0007
Matching Device Id: GenDisk
Outranked Drivers:
Device Updated: false
Parent Device: PCI\VEN_2646&DEV_5017&SUBSYS_50172646&REV_03\6&ae301c0&0&0000020A

 

[JPWestmas]

Is it possible that the Merak_Nvme_Ssd is not the Kingston drive I installed. There are no other drives in the Bios.

 

[JPWestmas]

I sent it back to amazon after going through Kingston customer service. I'm going to say this is a faulty nvme. It doesn't make any sense. I bought a different nvme and it works fine.

 

[fzabkar]

I refer to this thread, now closed:

https://forums.tomshardware.com/threads/second-m-2-drive-only-allows-1mb-of-space.3851067/

The OP had a Kingston SNV2S10 NVMe SSD which was detected with a 1MB capacity and a PCI VID of FE19. The Product Name was reported as "Merak_Nvme_Ssd". The good SSD had a PCI VID of 2646 and a Product Name of "KINGSTON_SNV2S10".

A search of the PCI database identifies 2646 as "Kingston Technology Company" and FE19 as "TenaFe Inc."

https://pcisig.com/membership/member-companies?combine=&page=3&order=field_vendor_id&sort=asc

TenaFe Inc is a manufacturer of SSD controllers and SSDs:

https://www.tenafe.com/

The TC2200 Merak controller is made by TenaFE. Therefore, it would appear that the OP's Kingston SSD encountered a firmware problem and then reverted to identifying itself with the factory alias of its controller.

https://www.tenafe.com/tc2200

Hopefully this information will be of help to others.