Jump to content

elbaecartnu

Member
  • Posts

    3
  • Joined

  • Last visited

Awards

This user doesn't have any awards

elbaecartnu's Achievements

  1. Okay, I've solved my problem. The issue was that my computer regonized the physical disk and its presence, but it wouldn't allow me to access it in Disk Manager. Also, I could create storage spaces and pools with the drive, but not use the drive alone. After some googling, I went into Powershell and used Get-PhysicalDisk and then changed the usage from "retired" to "AutoSelect", following parts of this tutorial. Then, when that didn't work, I used the command Reset-PhysicalDisk and rebooted my computer. Then, it showed up in DiskPart in cmdprmt, so I went to Disk Manager, rescaned for disks, and added a simple volume, and success! The SSD now is fully installed and operational. I'm not sure why windows automatically marked it as retired, but I'm glad I solved the problem.
  2. Is there more to this than just switching the modes in the BIOS? I feel like I should back up my data first after looking into this.
  3. Hello, I recently bought this 500gb Samsung 970 Evo NVMe SSD from Amazon and installed it onto my MSI x570 Gaming Plus motherboard in the top M.2 slot. In the BIOS, it sees the drive, and in Device Manager, it shows up as a drive. However, I can't see the drive in Disk Manager, and when I try to populate the drive in Device Manager it says "Volume information for this disk cannot be found". I've tried looking up the various solutions, but to no effect. Interestingly, I can create a Storage Space in the windows storage settings and use the 970 SSD as the location for this storage space and it will show up in Disk Management, but when I delete the storage space, the drive disappears from Disk Manamgement again. I have installed the drivers from Samsung's website. Here https://imgur.com/gallery/5dW0lV0 is an imgur link with images. Is this a BIOS update that I'm missing, or is it a problem with the drive itself? It's brand new, but I honestly don't know what else could be causing the problem.
×