Hard drive disconnected and things started happening. Doesn't feel like the type of hdd situation I've had in the past. Details:
Rig:
z87-gd65 mobo
i4770k the best cpu ever
gigabyte 1070gtx
32 gb ram
seasonic 650watt power supply [ https://www.newegg.com/seasonic-g-series-ssr-650rm-650w/p/N82E16817151118?Item=N82E16817151118 ]
win10 20h2
C:\ 512 ssd: windows and programs that didn't want to be installed elsewhere
G:\ 128 ssd: couple of games
E:\ 1tb hdd: programs and some data
H:\ 1tb hdd: data
I:\ 3tb hdd: backup and some games
Story:
In the past, H: and I: have sometimes silently dropped, and I've had to open the case and jiggle a cord to get them to reconnect. This stopped happening and I always assumed it was bad cord management on my part.
E drive is where most of my programs are installed, and for some reason a lot of my data despite my intention to us H for data.
E has recently suddenly gone dark, and never had the problem before, so I cracked open the case and prodded some wires around.
By taking H out and putting it into an external case, I can boot the pc from C drive and all drives show up including E. This might not be the only way to mount E but it's the one that worked and thus I'll stick to as I'm in the danger zone.
No Apps installed on E want to launch. My backup service is installed on E, and does not want to launch. The system seems to freeze up as if it knows the drive is there, but can't connect to any of the apps.
I have most of the items on E already backed up in a couple of places though slightly out of date. I am attempting to get another backup while I'm still able to access the drive.
Currently Disk Management says E: is a healthy ntfs partition, but night before last it was showing up as unknown, not initialized, unallocated.
Questions:
1- Since C is working, what should I do about all of the programs installed on E that won't launch? Poke them? Uninstall them? Haven't attempted anything with them yet aside from launching and having nothing happen.
2- I have a replacement for E ready to slot in. Should I do that then try to mount E externally and finish any safety backups?
3- E is transferring files at only 20kb - 1mb per second. Is this a sign the drive is dying, or is the drive being manhandled by windows (or something else). How can I tell what the drive is actually doing aside from staring at a progress bar? Sometimes it will break up into 70mb/second for no reason and sustain. Sometimes it acts like it's not even there, though the system says it's there.
Rig:
z87-gd65 mobo
i4770k the best cpu ever
gigabyte 1070gtx
32 gb ram
seasonic 650watt power supply [ https://www.newegg.com/seasonic-g-series-ssr-650rm-650w/p/N82E16817151118?Item=N82E16817151118 ]
win10 20h2
C:\ 512 ssd: windows and programs that didn't want to be installed elsewhere
G:\ 128 ssd: couple of games
E:\ 1tb hdd: programs and some data
H:\ 1tb hdd: data
I:\ 3tb hdd: backup and some games
Story:
In the past, H: and I: have sometimes silently dropped, and I've had to open the case and jiggle a cord to get them to reconnect. This stopped happening and I always assumed it was bad cord management on my part.
E drive is where most of my programs are installed, and for some reason a lot of my data despite my intention to us H for data.
E has recently suddenly gone dark, and never had the problem before, so I cracked open the case and prodded some wires around.
By taking H out and putting it into an external case, I can boot the pc from C drive and all drives show up including E. This might not be the only way to mount E but it's the one that worked and thus I'll stick to as I'm in the danger zone.
No Apps installed on E want to launch. My backup service is installed on E, and does not want to launch. The system seems to freeze up as if it knows the drive is there, but can't connect to any of the apps.
I have most of the items on E already backed up in a couple of places though slightly out of date. I am attempting to get another backup while I'm still able to access the drive.
Currently Disk Management says E: is a healthy ntfs partition, but night before last it was showing up as unknown, not initialized, unallocated.
Questions:
1- Since C is working, what should I do about all of the programs installed on E that won't launch? Poke them? Uninstall them? Haven't attempted anything with them yet aside from launching and having nothing happen.
2- I have a replacement for E ready to slot in. Should I do that then try to mount E externally and finish any safety backups?
3- E is transferring files at only 20kb - 1mb per second. Is this a sign the drive is dying, or is the drive being manhandled by windows (or something else). How can I tell what the drive is actually doing aside from staring at a progress bar? Sometimes it will break up into 70mb/second for no reason and sustain. Sometimes it acts like it's not even there, though the system says it's there.
Last edited: