Question Sandisk SSD is detected as Sata Drive by Bios but not seen in device mgr.

Jul 23, 2019
5
0
10
Sandisk SSD is detected as Sata Drive by Bios but not seen in device mgr. This drive was present internally as a g: drive before I cloned and replace the c: drive. System booted fine with new c: drive but the old g: drive is not seen by windows -- except as an external usb (via sata to usb cable). As thw external it is seen fine by windows and has all previous files present. Any help is very much appreciated.
 
Jul 23, 2019
5
0
10
Have you checked in Disk Management in Windows?

You might have to assign a drive letter to it or change drive letter in case there's another partition with that driver letter and they're conflicting.

Yes - it is nowhere to be found in windows - Not in Device Mgr, Disk drives, or otherwise. The sata cables and power connectors have been tested and it is seen by the bios. Also this drive was previously in machine and worked fine prior to changing the c: drive out.
 

Satan-IR

Splendid
Ambassador
Yes - it is nowhere to be found in windows - Not in Device Mgr, Disk drives, or otherwise. The sata cables and power connectors have been tested and it is seen by the bios. Also this drive was previously in machine and worked fine prior to changing the c: drive out.

No not device manager. Disk Management is a part of Administrative Tool and Computer Management.

What Windows is this? And what is your full system specs? Are the SSD drives SATA or M.2 drives?
 
Jul 23, 2019
5
0
10
No not device manager. Disk Management is a part of Administrative Tool and Computer Management.

What Windows is this? And what is your full system specs? Are the SSD drives SATA or M.2 drives?
Sata drives not M.2
I am looking at Computer Management program, under storage (shows partitions for C: drive properly and CD-ROM, but no other drives/unalloc space/ etc....Drive only appears in BIOS.
 

Satan-IR

Splendid
Ambassador
Sata drives not M.2
I am looking at Computer Management program, under storage (shows partitions for C: drive properly and CD-ROM, but no other drives/unalloc space/ etc....Drive only appears in BIOS.

This issue might be resolved through going to Manage Storage Spaces and removing the drive from the storage pool that has taken ownership of the drive.

  1. Open Control Panel then select Storage Spaces from the list of results that appear
  2. Select change settings > physical drives to see all the drives currently in your pool

  3. Locate the drive you want to remove from the pool

  4. Then select prepare for removal > prepare for removal. Leave the PC plugged in until the drive is ready to be removed

  5. If the PC goes into sleep change when plugged in, PC goes to sleep after, to Never

  6. When the drive is shows as 'ready to remove', select remove > remove drive. Now, you can enter the Disk Management console and see if the drive is now detected by the PC.

  7. You might want to delete the Storage Pool if the drive still isn't detected
 
Last edited:
Jul 23, 2019
5
0
10
Tx - Did check this (was actually in that as your replied) - No luck - it showed that no storage pool as present, so the change option was not available.
 
Bios Detects the old G: drive on Sata 4 as HDD
Windows shows nothing.
Windows Disk Mgmt shows only the 2TB SDD as Disk 0 on Sata 1 and a CD-ROM 0 on Sata 3.

Windows 10 sees the new C: drive as 2TB and all programs run as before the cloning.
Yet neither the old c: drive nor the old g: drive are seen when internally connected to sata.
They work fines as external drives connected via Sata-to-USB.

Your descriptions are rather confusing.
Can you show any screenshots?

Also check BIOS settings. Some sata ports might be disabled. Try connecting your drives to different ports.
 
Jul 23, 2019
5
0
10
Your descriptions are rather confusing.
Can you show any screenshots?

Also check BIOS settings. Some sata ports might be disabled. Try connecting your drives to different ports.

Problem has been corrected - Had to mount drive via USB externally (the only way it was accessible) and then remove the drive letter which it was previously assigned as an internal drive PRIOR to the system drive cloning. Then, power down, install internally and assign same drive letter again. Seems Windows has an issue when cloning a system disk that it cannot see previously assigned drives internally. There is not data loss, just simply removing the drive letter externally and then reassigning internally. No issues with Sata disabled, BIOS, etc. Its an unanticipated Windows quirk. Tx.
 

Feren142

Reputable
Jul 14, 2019
99
14
4,565
Problem has been corrected - Had to mount drive via USB externally (the only way it was accessible) and then remove the drive letter which it was previously assigned as an internal drive PRIOR to the system drive cloning. Then, power down, install internally and assign same drive letter again. Seems Windows has an issue when cloning a system disk that it cannot see previously assigned drives internally. There is not data loss, just simply removing the drive letter externally and then reassigning internally. No issues with Sata disabled, BIOS, etc. Its an unanticipated Windows quirk. Tx.
I was going to ask if it was seen in DiskPart List Disk but, if you got it resolved, awesome!!