Question Hard Drive not recognized through ANY SATA port but recognized via USB after NVME SSD installation

Toggle sidebar Toggle sidebar
O

Oyavo

May 6, 2025
13
0
10
Back in January I bought a Samsung 990 EVO 2TB SSD NVME, and installed it into the M.2 slot. Since then my 2TB Hard Drive is completely unrecognizable by my PC unless via a SATA to USB adapter, yet my older 500 GB HD and 256 GB SSD are completely fine.

NOTE: SATA ports 5 and 6 are disabled on my motherboard using an m.2 SSD, however this problem is occurring in ports 1-4, NOT 5-6.

Here's my PC build:
  • CPU: AMD Ryzen 5 3600 3.6 GHz 6-Core Processor
  • Motherboard: MSI B450 TOMAHAWK MAX ATX AM4 Motherboard
  • Memory: G.Skill Ripjaws V 16 GB (2 x 8 GB) DDR4-3200 CL16 Memory
  • Storage:
    • (Boot Drive) Samsung 990 EVO 2 TB M.2-2280 PCIe 5.0 X2 NVME Solid State Drive = [50% full]
    • [PROBLEM AREA] Toshiba MQ01ABD050 500 GB 2.5" 5400 RPM Internal Hard Drive (2 TB Hard Drive) - [0% full]
    • Samsung Spinpoint M9T 2 TB 2.5" 5400 RPM Internal Hard Drive - [0% full]
    • Samsung 860 Evo 250 GB 2.5" Solid State Drive - [80% full]
  • GPU: MSI GeForce RTX 3080 GAMING X TRIO 10G GeForce RTX 3080 10GB 10 GB Video Card
  • PSU: Corsair AX760 760 W 80+ Platinum Certified Fully Modular ATX Power Supply

I've tried all of the following:
  • Formatting and repartitioning to NTFS simple volume;
  • Repartitioning to both F: (unused) and E:/D: (used)
  • Formatting and not repartitioning
  • SATA slots 1,2,3,4 all same result; 5 and 6 appear to be disabled since the M.2 installation (SSD and 500GB HD work from all 4 slots however)
  • Daisy-chaining drive power cables
  • Giving the drive its own power cable
  • Connecting drive while PC is on
  • Connecting drive before turning pc on
  • Converting drive to GPT from MBR

Some further notes:
  • PC was purchased secondhand ~8 years ago, nearly all parts have been replaced since except the non-NVME hard drives and PSU which have had no problems prior to adding the 2TB SSD into the m.2 slot.
  • Only shows up in disk manager / bios when connected via USB
  • The 500 GB HD was formatted and partitioned using the exact same USB adapter
  • The one time it did show up was when I connected it to SATA3 daisy-chained with only the 256GB SSD and NVME, but once I connected the 500 GB HD it stopped showing up again no matter what.
  • The drive is almost always spinning when plugged in, yet still does not appear.

Update: I managed to get the hard drive to show up again via SATA 3, however it took around 30 seconds to show up after system boot, and has since disconnected after connecting the remaining drives to SATA 1 and 2. Despite then disconnecting the other two drives, the 2TB hard drive hasn't reappeared.

Update 2: In the process of updating this post, the drive has shown up again, after nearly 1-2 minutes post-boot despite spinning the whole time.


Any help is immensely appreciated, I've spent hours on this and only had the drive show up a single time, which then went away on reset.
 
Last edited:
Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how full?

List all attached peripherals.

= = = =

Check the motherboard's User Guide/Manual for supported storage devices and configurations.
 
Ralston18 said:
Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how full?

List all attached peripherals.

= = = =

Check the motherboard's User Guide/Manual for supported storage devices and configurations.
Click to expand...
I've updated the post with more information, please let me know if any further info is needed. I've already consulted the manual, and while SATA 5 and SATA 6 should be disabled, I am only using SATA 1-3 with the problem persisting across all three for exclusively the 2TB hard drive.
 
geofelt said:
The specs say that sata ports 5 and 6 will be unavailable with a populated m.2 device:
Click to expand...
As OP has said twice now that they're aware of and that they're not using those ports (although given the post timing maybe that wasn't noted before the edits and this reply happened just before it was added).
Oyavo said:
I am only using SATA 1-3 with the problem persisting across all three for exclusively the 2TB hard drive.
Click to expand...
Truly bizarre and I can't offer any suggestions for this if it it's actually an intermittent issue. If it had never suddenly appeared at all, you could say there's a solid issue with compatibility somehow. You say it won't even appear in the BIOS? If you remove the new Samsung drive does the problem magically disappear?
Oyavo said:
  • [PROBLEM AREA] Toshiba MQ01ABD050 500 GB 2.5" 5400 RPM Internal Hard Drive (2 TB Hard Drive) - [0% full]
  • Samsung Spinpoint M9T 2 TB 2.5" 5400 RPM Internal Hard Drive - [0% full]
Click to expand...
One of those you've got indicated as both a 500GB and a 2TB, and you said the 500GB was fine. Which is the actual problem drive? What was your previous boot drive? Is the BIOS current? Have you tried just resetting the BIOS to defaults?

I had a weird issue with my ASUS X570 board and the Ryzen 5 3600 XT, in that NVMe drive activity didn't cause the drive activity light on the case to light up, but use of a SATA disk did light it up. It was my first NVMe drive and I thought since it wasn't on the SATA ports, and NVMe is just a PCIe slot, maybe it wasn't a "disk" to the BIOS so the activity light didn't work for it. Then I upgraded to a 5600X and suddenly the light started working for the NVMe drive. I have no explanation for that, either but there clearly can be really odd issues in regard to drives.
 
This appears not to be unique to this board or MSI...

https://forums.tomshardware.com/threads/msi-tomahawk-b450-max-no-sata-drives-detected.3639059/ (bad SATA drives apparently)

The SATA configuration in the BIOS is set to AHCI and not RAID, right? (That ought not to be a problem given that the other SATA drive works fine, of course. Just throwing the kitchen sink at the problem.)

This one was apparently just had a power issue.

Do your SATA power connectors have the orange 3.3V cable? This drive did work previously, with the only change being the boot SSD, right?
 
Oyavo said:
I've already consulted the manual, and while SATA 5 and SATA 6 should be disabled,
I am only using SATA 1-3 with the problem persisting across all three for exclusively the 2TB hard drive.
Click to expand...
Which ports do you think are SATA5/SATA6 ?

Furthest away from cpu are ports SATA1/SATA2 (you're probably thinking those are SATA5/SATA6).
SATA5/SATA6 are closest to cpu.
SATA3/SATA4 - between them.

B450_BlockDiagram_EDIT.jpg
 
fzabkar said:
Show us a SMART report
Click to expand...
Kinda hard to do that if the drive isn't recognized by the motherboard or OS.

SkyNetRising said:
Which ports do you think are SATA5/SATA6 ?
Click to expand...
Not really relevant, since OP tried every port that they thought was 1 to 4, so even if 5 and 6 were accidentally being tried, there would have been at least two others that would have been valid and should have functioned. (It is kind of poor/non-intuitive design to have the ports that are on the chipset separated like that, while having the ones via the CPU mounted directly next to the non-CPU ports.)
 
@Oyavo

I suggest trying to learn more about the drives and drive configurations on your system.

One other way to do that is to use Powershell (built into Windows) and a simple cmdlet ("commandlet") to obtain more information.

Start with the cmdlet Get-PNPDevices

(Results can be lenthy but still informative....)

And then next focus on just the Disk drives.

Specifically the cmdlet to do specifically that is:

Get-PNPDevice -Class DiskDrive
Reference:

https://learn.microsoft.com/en-us/p...evice/get-pnpdevice?view=windowsserver2025-ps

Get cmdlets do not change anything.

You can either type the cmdlet after the PS prompt or copy and paste in the cmdlet if you chose to do so.

For example here are the results from my computer ( Powershell run as non-admin).

= = = =

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows

PS C:\Users\REDACTED> Get-PNPDevice -Class DiskDrive

Status Class FriendlyName InstanceId
------ ----- ------------ ----------
OK DiskDrive Samsung SSD 860 EVO 500GB SCSI\DIS...
OK DiskDrive KBG30ZMS256G NVMe TOSHIBA 256GB SCSI\DIS...
Unknown DiskDrive Verbatim STORE N GO USB Device USBSTOR\...
Unknown DiskDrive WDC WD10 EARS-00MVWB0 USB Device USBSTOR\...
Unknown DiskDrive SABRENT SCSI Disk Device SCSI\DIS...
Unknown DiskDrive SABRENT SCSI Disk Device SCSI\DIS...
Unknown DiskDrive Apple iPod USB Device USBSTOR\...
Unknown DiskDrive KINGSTON SV300S37A120G USB Device USBSTOR\...
OK DiskDrive ATA Samsung SSD 870 SCSI Disk Device SCSI\DIS...
Unknown DiskDrive ST350032 0AS USB Device USBSTOR\...
Unknown DiskDrive ATA Samsung SSD 870 USB Device USBSTOR\...
Unknown DiskDrive SanDisk Cruzer USB Device USBSTOR\...


PS C:\Users\REDACTED>

= = = =

Those are, of course, the drives installed on my system (present = OK, past = Unknown).

If the cmdlet is run on your system do the "OK" Status drives match the drives installed on your system?

Are there any drives not recognized or unexpected?

You can make comparisons with Device Manager (Disk Drives) and Disk Management as well.

Much more detail can be obtained. However the above cmdlets are a good starting point.

What would be interesting to discover is if drives appear/disappear (i.e., intermittently) even in Powershell.
 
evermorex76 said:
Kinda hard to do that if the drive isn't recognized by the motherboard or OS.
Click to expand...

The OP can sometimes see the missing drive(s). However, the OP seems to be confusing the MQ01ABD050 HDD, a 500GB model, with a 2TB drive.

Since then my 2TB Hard Drive is completely unrecognizable by my PC unless via a SATA to USB adapter,

Update: I managed to get the hard drive to show up again via SATA 3, however it took around 30 seconds to show up after system boot, and has since disconnected after connecting the remaining drives to SATA 1 and 2. Despite then disconnecting the other two drives, the 2TB hard drive hasn't reappeared.

Update 2: In the process of updating this post, the drive has shown up again, after nearly 1-2 minutes post-boot despite spinning the whole time.
Click to expand...
 
fzabkar said:
The OP can sometimes see the missing drive(s). However, the OP seems to be confusing the MQ01ABD050 HDD, a 500GB model, with a 2TB drive.
Click to expand...
That is correct, the drive will show up anywhere from 30 seconds to upwards of 10 minutes after booting up, and has never shown up in bios since the installation of the NVME ssd.

My apologies, I actually do have both a 500GB and a 2TB hard drive but formatted my post incorrectly. The 500GB one has no issues at all whereas the 2TB one is the problem area, yet both are approximately the same age (as well as the 256GB drive; same age as well around almost 8 years old). I'm going to run cmdlet shortly as @Ralston18 mentioned as well as perform a SMART report requested by @fzabkar. In the meantime, these are the results of a 5 hour chkdsk I performed yesterday:

Code: 
C:\Windows\system32> chkdsk f: /f /v /b
The type of the file system is NTFS.
Volume label is Hard Drive.

Stage 1: Examining basic file system structure ...
  256 file records processed.
File verification completed.
 Phase duration (File record verification): 1.46 milliseconds.
  0 large file records processed.
 Phase duration (Orphan file record recovery): 0.62 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 0.21 milliseconds.

Stage 2: Examining file name linkage ...
  278 index entries processed.
Index verification completed.
 Phase duration (Index verification): 23.87 milliseconds.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 0.23 milliseconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 0.76 milliseconds.
  0 reparse records processed.
  0 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 0.37 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 1 unused index entries from index $SII of file 9.
Cleaning up 1 unused index entries from index $SDH of file 9.
Cleaning up 1 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 1.12 milliseconds.
  11 data files processed.
 Phase duration (Data attribute verification): 0.45 milliseconds.

Stage 4: Looking for bad clusters in user file data ...
  240 files processed.
File data verification completed.
 Phase duration (User file recovery): 189.35 milliseconds.

Stage 5: Looking for bad, free clusters ...
  488333822 free clusters processed.
Free space verification is complete.
 Phase duration (Free space recovery): 0.01 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

1953497087 KB total disk space.
     35904 KB in 7 files.
        72 KB in 13 indexes.
         0 KB in bad sectors.
    125819 KB in use by the system.
     65536 KB occupied by the log file.
1953335292 KB available on disk.

      4096 bytes in each allocation unit.
 488374271 total allocation units on disk.
 488333823 allocation units available on disk.
Total duration: 222.73 milliseconds (222 ms).

I'm not too familiar with chkdsk, SMART data, or cmdlet however based on everything I've seen I'm under the impression something in bios is preventing the drive from appearing right away caused by the m.2 NVME, or the drive is being interpreted as an external drive somehow, which I ran the following command to try to address (with no errors yet also no effect):

Code: 
reg.exe add “HKLM\SYSTEM\CurrentControlSet\Services\storahci\Parameters\Device” /f /v TreatAsInternalPort /t REG_MULTI_SZ /d 1
 
evermorex76 said:
You say it won't even appear in the BIOS? If you remove the new Samsung drive does the problem magically disappear?
Click to expand...

It's been awhile since I've fully removed the NVME (this problem has been going on since January) so I'll have to try again, however from memory I believe removing the NVME allowed for the 2TB hard drive to reappear in bios, however otherwise it is entirely absent.

One of those you've got indicated as both a 500GB and a 2TB, and you said the 500GB was fine. Which is the actual problem drive? What was your previous boot drive? Is the BIOS current? Have you tried just resetting the BIOS to defaults?
Click to expand...

My apologies, I do have both a 500GB and 2TB hard drive but it is the 2TB one having issues; the 500GB appears just fine. The BIOS firmware is from August 2024 I believe, and unfortunately I reset bios to default last night with no success either.

EDIT: Removing the NVME in fact did not cause the 2TB hard drive to appear, unfortunately
 
Last edited:
SkyNetRising said:
This means - your drive is connected to SATA5/SATA6 ports.

Can you show a photo of your system with side panel removed?
(upload to imgur.com and post link)
Click to expand...
Here is a photo of sata ports 1 & 2, and sata port 3 connected. I apologize for the potentially unclear photos, however I can assure you that nothing is plugged into ports 5 or 6, and at the moment the problem drive is plugged into port 1 (with the 500 GB HD plugged into port 2 and the 256 GB SSD plugged into port 3; I've tried each drive in each port and all except the 2TB hard drive work no matter which port).

Furthermore, I was mistaken; removing the NVME did not have any effect on the hard drive reappearing in bios.

Here is a more zoomed out side photo of my system at the moment, as well as the 3 non-m.2 drives (the 2TB hard drive is the only one plugged in at the moment; the one on the far left). Please let me know if anything is still unclear.
 
Last edited:
Chkdsk results would be entirely irrelevant since that's just filesystem and bad sector checking. If the entire drive is just not being detected that's a controller/interface issue (or a completely failing drive). I don't think even SMART results would be of any help, unless they show specific SATA interface errors. The only possibly related entries my one current SATA drive lists are "UDMA CRC Error Count" and "SATA Interface Downshift".

Now that you've shown that even when this drive is the only connected device it doesn't work properly, the only possible causes are bad drive or bad BIOS. Granted, if it was working perfectly fine before changing the SSD I can't see why it wouldn't be working now, but you still haven't said anything about whether the BIOS has been updated or fully reset to defaults to see if either make a difference. Aside from BIOS issues, the only other thing I can think of is that the drive is in fact failing, but not in a way that you can identify, such as the repeated clicking noises that you might hear if it was a mechanical/surface issue and the heads couldn't load and read the platters. But the fact that it works fine in an enclosure makes the problem much more confusing.
 
SkyNetRising said:
Don't do that. This can cause improper connector contact.
Click to expand...
*. As long as it's seated fully and not under pressure that is pushing it up so hard that it might break the socket, it's going to make proper contact. The same requirements apply to a straight connector. The only reason not to do it is that you may block another connector. OP has also seemingly swapped his other drives around to those same ports and they worked fine, and given the apparent cable routing I assume that it wasn't with a different cable without the angle.
 
Ralston18 said:
And then next focus on just the Disk drives.

Specifically the cmdlet to do specifically that is:

Get-PNPDevice -Class DiskDrive
Click to expand...
Here are the results of that search;

Code: 
PS C:\Windows\system32> Get-PNPDevice -Class DiskDrive

Status     Class           FriendlyName                                                                     InstanceId
------     -----           ------------                                                                     ----------
Unknown    DiskDrive       Samsung SSD 860 EVO 250GB                                                        SCSI\DIS...
Unknown    DiskDrive       HGST HTS545050A7E380                                                             SCSI\DIS...
Unknown    DiskDrive       Multi Flash Reader USB Device                                                    USBSTOR\...
Unknown    DiskDrive       Seagate Expansion SCSI Disk Device                                               SCSI\DIS...
Unknown    DiskDrive       Lexar USB Flash Drive USB Device                                                 USBSTOR\...
Unknown    DiskDrive       Samsung SSD 860 EVO 250G SCSI Disk Device                                        SCSI\DIS...
Unknown    DiskDrive       HGST HTS545050A7E380                                                             SCSI\DIS...
[!] Unknown    DiskDrive       ST2000LM 003 HN-M201RAD SCSI Disk Device                                         SCSI\DIS...
Unknown    DiskDrive       HGST HTS545050A7E380                                                             SCSI\DIS...
Unknown    DiskDrive       WD My Passport 259F USB Device                                                   USBSTOR\...
Unknown    DiskDrive       HGST HTS 545050A7E380 SCSI Disk Device                                           SCSI\DIS...
Unknown    DiskDrive       SAMSUNG HD103SI USB Device                                                       USBSTOR\...
Unknown    DiskDrive       Samsung SSD 860 EVO 250GB                                                        SCSI\DIS...
Unknown    DiskDrive       Samsung SSD 860 EVO 250GB                                                        SCSI\DIS...
[!] OK         DiskDrive       ST2000LM003 HN-M201RAD                                                           SCSI\DIS...
Unknown    DiskDrive       Kingston DataTraveler 3.0 USB Device                                             USBSTOR\...
Unknown    DiskDrive       NEC USB UF000x USB Device                                                        USBSTOR\...
Unknown    DiskDrive       Generic STORAGE DEVICE USB Device                                                USBSTOR\...
Unknown    DiskDrive       Samsung SSD 860 EVO 250GB                                                        SCSI\DIS...
OK         DiskDrive       Samsung SSD 990 EVO 2TB

The exact drive names listed in my post originally seem to be correct, however I've put a [!] next to the lines with the 2TB hard drive (ST2000LM003 HN-M201RAD). I'm not too sure what to make of this information, however results are similar to the cmdlet search I also performed:


Code: 
C:\Windows\system32>wmic diskdrive get status
Status
OK
OK


C:\Windows\system32>wmic /namespace:\\root\wmi path MSStorageDriver_ATAPISmartData
Active  Checksum  ErrorLogCapability  ExtendedPollTimeInMinutes  InstanceName                                                Length  OfflineCollectCapability  OfflineCollectionStatus  Reserved                                SelfTestStatus  ShortPollTimeInMinutes  SmartCapability  TotalTime  VendorSpecific                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             VendorSpecific2  VendorSpecific3  VendorSpecific4                                                                                                                                                                                                                                                                                                                                                              
TRUE    248       1                   255                        SCSI\Disk&Ven_&Prod_ST2000LM003_HN-M\5&2b637674&0&010000_0  512     91                        0                        {0, 113, 1, 0, 0, 0, 0, 0, 0, 0, 0, 0}  0               1                       3                22140      {16, 0, 1, 47, 0, 100, 100, 7, 0, 0, 0, 0, 0, 0, 2, 38, 0, 252, 252, 0, 0, 0, 0, 0, 0, 0, 3, 35, 0, 92, 90, 96, 10, 0, 0, 0, 0, 0, 4, 50, 0, 97, 97, 33, 14, 0, 0, 0, 0, 0, 5, 51, 0, 252, 252, 0, 0, 0, 0, 0, 0, 0, 7, 46, 0, 252, 252, 0, 0, 0, 0, 0, 0, 0, 8, 36, 0, 252, 252, 0, 0, 0, 0, 0, 0, 0, 9, 50, 0, 100, 100, 183, 65, 0, 0, 0, 0, 0, 10, 50, 0, 252, 252, 0, 0, 0, 0, 0, 0, 0, 12, 50, 0, 97, 97, 89, 12, 0, 0, 0, 0, 0, 191, 34, 0, 100, 100, 32, 0, 0, 0, 0, 0, 0, 192, 34, 0, 252, 252, 0, 0, 0, 0, 0, 0, 0, 194, 2, 0, 64, 46, 29, 0, 14, 0, 54, 0, 0, 195, 58, 0, 100, 100, 0, 0, 0, 0, 0, 0, 0, 196, 50, 0, 252, 252, 0, 0, 0, 0, 0, 0, 0, 197, 50, 0, 252, 252, 0, 0, 0, 0, 0, 0, 0, 198, 48, 0, 252, 252, 0, 0, 0, 0, 0, 0, 0, 199, 54, 0, 200, 200, 0, 0, 0, 0, 0, 0, 0, 200, 42, 0, 100, 100, 236, 0, 0, 0, 0, 0, 0, 223, 50, 0, 100, 100, 142, 0, 0, 0, 0, 0, 0, 225, 50, 0, 81, 81, 138, 18, 3, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0}  0                0                {0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0}
 
evermorex76 said:
Now that you've shown that even when this drive is the only connected device it doesn't work properly, the only possible causes are bad drive or bad BIOS. Granted, if it was working perfectly fine before changing the SSD I can't see why it wouldn't be working now, but you still haven't said anything about whether the BIOS has been updated or fully reset to defaults to see if either make a difference.
Click to expand...
I reset BIOS to default yesterday with no luck unfortunately.

Aside from BIOS issues, the only other thing I can think of is that the drive is in fact failing, but not in a way that you can identify, such as the repeated clicking noises that you might hear if it was a mechanical/surface issue and the heads couldn't load and read the platters.
Click to expand...
I suppose it's possible that the drive is failing, I've heard it (or at least, assume that was it) make a sort-of thump sound once in awhile but that noise occurs maybe once a week and has been occurring nearly the entire time I've had it, whereas these issues have only started after installing the m.2 SSD.

I bought the NVME for extra storage rather than because of any issues with the hard drive itself, so before January (when I installed the NVME and reinstalled windows) everything worked just fine. I've only had a chance to take a better look at this issue now after having moved everything off the hard drive then formatting it using a sata to USB adapter which again, showed 0 signs of the drive having any problems whatsoever and connects immediately.
 
Just listing the drives won't mean anything when the drive is actually working, and if it's not showing up in Device Manager it won't show up in a command line list so doing it when it's not working won't mean anything either.

You can try running a full SMART self-test with Seagate's SeaTools, but if the thing survived a full "chkdsk /b" then I don't think the SMART test is going to hammer it any harder and cause it to drop out. If there's nothing on the drive you could subject it to a straight-up stress test that reads AND writes all the sectors both sequentially and random and just keeps going until there's an error, but it seems like once it's up and running it's working fine and there won't be any mechanical faults or surface issues found. Bad power that won't let it start up sometimes is the last external (meaning not the drive itself) possibility I can see being possible aside from what I've said before, even though you can hear it spinning, with the external enclosure supplying proper power every time.

Having a spare power supply isn't a bad idea, so you might get one and try it. It doesn't need to be a big expensive thing. Your system could run on a 500W supply and it doesn't need to be modular or have other bells and whistles.
 
evermorex76 said:
What about the version?
Click to expand...

Bios version is E7C02AMS.3K2 (08/30/2024), which I believe I installed back in January when first trying to fix this issue.

Bad power that won't let it start up sometimes is the last external (meaning not the drive itself) possibility I can see being possible aside from what I've said before, even though you can hear it spinning, with the external enclosure supplying proper power every time.
Click to expand...

It's possible that it could be the drive itself I suppose, as there's nothing I've seen to indicate my power supply having issues and I've tried two separate sata power cables with no other drives connected. The only indication of damage to the drive itself is a small broken off piece of plastic for the power segment, however as I've mentioned the drive has no problems connecting via USB whatsoever (which I'd presume would be affected if this was the issue) but it's JUST the plastic and none of the pins with the power cable appearing to be fully connected from what I can see.

Furthermore, I'm almost certain this damage happened within the past few days rather than back when the problem began, as I did not remove the hard drive at all when inserting the NVME and only removed it once I noticed it stopped showing up.
 
@ Oyavo

Continue to try to learn more about disk drive related errors on the system

FYI (Powershell, Performance Monitor, etc.):

https://docs.eazybackup.com/trouble...-find-disks-with-read-write-errors-in-windows

If a disk drive is having intermittent errors (appearing/disappearing and so forth) then the next step is to determine if root problem is the drive itself or its' host.

I would connect the drives in question to other known working systems simply see if the drive works. Most likely with an external USB enclosure. One drive at a time to focus on that drive.

"Works" meaning constantly readable/writable and no errors. If the errors follow the drive then the drive is at fault.


Also checkthe error logs on the host/test system - see if errors start showing up.

As for the damage: could have been small or minor begin with and simply has become worse to to heat related expansion/contractions. Or just being handled no matter what level of care is taken. Maybe vibrations are another factor.

Intermittent problems are difficult to troubleshoot. Take your time, be methodical.


Late note: In your SATA photos, one of the pins appears "split". Leftmost connector, right end.

Cannot quite make it out....
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom