I’m finding that in a GUI-less nixos installer (see here) lsblk is only aware of of my usb stick that has the .iso on it. and df -h has shows more available space than the stick, but way less than 2 Terrabytes which is the size of my SSD.
BIOS view doesn’t show anything related to SSD, the number 2000 GB, etc.
EDIT: I should mention I double checked that the SSD is physically snug in the hardware slot for it. After I first had this problem I shut down, unplugged, and cracked the thing open to remove it and put it back. Problem persists.
I also have the same WD SSD, with no issues in Linux - I am not sure what you would need to update the firmware for.
As for it now showing in the BIOS screen, apparently it doesn’t show on the released versions. There is a new beta of the BIOS that will show it, though. From the notes:
Show detected PCIe NVME and USB storage list on BIOS boot page
I’m currently using the 970 EVO which works well, FWIW. Didn’t want to go with the 980 b/c of concerns around heat buildup (my personal rule of thumb is: if the thing comes with a heatsink and there isn’t enough room to fit it in, don’t bother with the version without the heatsink since it will likely thermally throttle anyway). Maybe my rule of thumb is too ‘conservative’, but I doubt that my bottleneck will ever really be the storage or the write speeds anyway (much more likely to be either the CPU or the network).
Not sure if it is my case. Samsung 980 Pro 500 GB did not detect at first-time install but after a few tries. It can be detectable after jumping back and forth during the windows installation. My thought is that an NVME related problem may be the protocol, driver, or something else. On the other hand, Samsung 980 1 TB did not have any issues. So, maybe it is the HBM problem? If more information is needed for my case. Please let me know.