#1 ·
Greetings
I picked up a Samsung 870 EVO, hooked everything up, booted the machine, and confirmed the drivers are installed. Everything looks fine on paper, yet the drive refuses to show up in File Explorer.
It didn't seem like a major issue at first since I could locate it in the Device Manager. I went into Disk Management, selected the unallocated space, and attempted to create a new simple volume. I left the volume size alone, assigned it the drive letter Z, kept the file system as NTFS with default allocation unit size, and checked the box for a quick format. I hit finish, only to be met with an error stating, "The device is not connected," and just like that, it vanished.
Now, it isn't even appearing in the Device Manager anymore, unless I manually trigger a scan for hardware changes, which brings it back momentarily.
When I attempt to repeat the process in Disk Management, I'm greeted with: "The specified network resource or device is no longer available."
I have spent a significant portion of my evening chasing this ghost. I will admit, I am not exactly an expert in these matters, and I foolishly assumed this would be a straightforward task... Does anyone have any insight into what might be causing this failure?
P.S. If this is entirely my own doing, feel free to tear me apart...
I picked up a Samsung 870 EVO, hooked everything up, booted the machine, and confirmed the drivers are installed. Everything looks fine on paper, yet the drive refuses to show up in File Explorer.
It didn't seem like a major issue at first since I could locate it in the Device Manager. I went into Disk Management, selected the unallocated space, and attempted to create a new simple volume. I left the volume size alone, assigned it the drive letter Z, kept the file system as NTFS with default allocation unit size, and checked the box for a quick format. I hit finish, only to be met with an error stating, "The device is not connected," and just like that, it vanished.
Now, it isn't even appearing in the Device Manager anymore, unless I manually trigger a scan for hardware changes, which brings it back momentarily.
When I attempt to repeat the process in Disk Management, I'm greeted with: "The specified network resource or device is no longer available."
I have spent a significant portion of my evening chasing this ghost. I will admit, I am not exactly an expert in these matters, and I foolishly assumed this would be a straightforward task... Does anyone have any insight into what might be causing this failure?
P.S. If this is entirely my own doing, feel free to tear me apart...