"Pertains to the system in my signature"
I used Macrium reflect to clone my Intel NVME over to a 1tb 960 pro. All went well doing this but my 1tb Seagate Barracuda is no longer detectable under "This PC" or in disk management.
Things I've tried:
Different data ports and power ports on my mobo. I haven't tried different data and power wires though. But like I said, it was all fine beforehand.
I also tried running windows memory diagnostics tests to see if I had corrupted something in my memory, to no avail.
Any other suggestions to try before canning this $50 drive and buying something better?
Really it was just a drive I had in my drawer so if its junk, no biggie. Needed a reason to go buy a samsung 2.5 ssd anyway![]()
Thanks in advance!
Charlie
-
saturnotaku Notebook Nobel Laureate
Is the drive detected in your BIOS?
KY_BULLET and Vistar Shook like this. -
Vistar Shook Notebook Deity
If the drive is detected in the BIOS there is hope.
Two days ago my 2TB firecuda SSHD just died, doesn't show in diskmanagement or the BIOS, bummer.KY_BULLET likes this. -
Nope doesn't look like it is so I guess it's scrapped.
Last edited: Apr 28, 2018 -
Vistar Shook Notebook Deity
I got the 2TB Micron1100 as a replacement, it is not a samsung but at $320 not bad for a backup drive.
-
It is rare but sometimes cables do fail.
Does it even spin up at all? Any clicking and the like on the drive? -
And I just now tried a different data cable plugged into a different header and even tried a totally different power cable at another port on my PSU just for the heck of it.hmscott likes this. -
Any markings on the traces of the SATA connections? Got a spare SATA cable or another PC to try?
Sometimes when I make alterations to my m4600 the SATA connected drives would disappear. Though I credit that to just being an older high mileage laptop.
Otherwise its likely to be dead, just seems a bit strange to occur immediately the same time you installed your m.2 drive -
hmscott likes this.
-
There was a time when old drives would after a time get thick grease / lubricant freezes after being powered on for the first time in a while, works once, then when powered off, it cools down and freezes, and when powered up they disappear - failing head / arm movement POST.
Try slamming it down on the desk - flat - slap it down on the label side - make sure not to hit fine parts on a circuit board, adjust the area of force, edge of table so as to not hit the circuit board if part of it faces the "face" side.
That should break the stiction of the arm for POST and it might work.
Another way is to "warm up" the drive so it softens the lubricant and free's motion, same idea, depends on what kind of tools you have.
You could also try tapping the drive on it's side on the desk, "tap tap", turn over to the other edge, tap tap, and try that. Less shock to the system, but for different force angle.
Good Luck
Edit: I came back to amend my post. It's been a while since I worked on these issues, and recalled that I warmed up the drives *before* thwacking them. Usually sitting them on top of always on drives would be enough until they heated through and through.
And I also recall some took to being whacked on the corners, some on the edge, some face down. And, some needed this every time to start up... so recover the data after you bring it up and then retire it... most would continue to work as long as they were on 24/7...a reboot works, but don't let them cool down.Last edited: Apr 29, 2018alexhawker, Papusan and KY_BULLET like this. -
I wonder if windows placed boot files on it the last time I did a clean install and since I changed boot drives, it isn't recognizing it? But even still, it should've shown itself in my bios right?
I usually unhook any drives in my system to keep windows from doing this but I forgot this time. -
There were some that blew a fuse on the circuit card as well, also the scsi port on motherboards pulled the same trick, probably outside this situation's issues.
I was coming back to amend my previous post. It's been a while since I worked on these issues, and recalled that I warmed up the drives *before* thwacking them. Usually sitting them on top of always on drives until they heated through and through would be enough.
And I also recall some took to being whacked on the corners, some on the edge, some face down. And, some needed this every time to start up... so recover the data after you bring it up and then retire it... most would continue to work as long as they were on 24/7...a reboot works, but don't let them cool down.Last edited: Apr 28, 2018 -
@hmscott is right, it should show in the BIOS. Do you have an enclosure you could put the HDD in and try to hook it up via USB to a different computer?
I highly doubt it would make a difference, but it is sometimes easier to hear the drive from inside an enclosure than from within a computer if there are some issues that generate some kind of noise. Not necessarily the click of death, sometimes it is a bit more subtle.It helped me figure out that it was one of my desktop HDD that went rather than my SSD. Since the computer was booting slow, I assumed it was the OS drive, but it turned out to be a different drive that behaved fine and only had a faint whine. I dropped it in an enclosure for something totally unrelated and that gave me the hint to run a diagnostic on it since it had a subtle whine to it.
I also ran into cases where Windows on one computer refused to see a drive, but a different computer could recognize it (and also recognize that it was kinda dying). I never checked whether the drive was recognized by the BIOS of said computer though and I am pretty sure it would have been, but at this point, what have you got to lose? -
I actually do not have another computer to try it in but, this is a desktop so I had the data cable and power cable Jerry rigged outside the box with the hdd in hand. I could feel it spinning up.
I'm thinking something is wrong with my sata controller (fried maybe?) and if that's the case, the mobo is getting rma'd.
Good thing is that both of my m.2 nvme slots are working so I'm not without a computer at least...
Vistar Shook and hmscott like this. -
Memory1245 and hmscott like this.
-
I might've found out why it's not working. Apparently the boot nvme needs to be in the #1 m.2 slot which is above my GPU. I have it in the slot below my GPU. I will try this out when I get home tonight and report back.
Vistar Shook and hmscott like this. -
Luck of the draw I guess...See the picture below. When you have 2 X m.2 Pcie NVME installed, it shuts down SATA data ports #5 and #6, which are the only 2 I tried while trouble shooting. Which means 1-4 sata ports should still be active.
Go Figure...So I'm about 95% sure this is my problem.
alexhawker, Robbo99999 and hmscott like this. -
-
-
Robbo99999 Notebook Prophet
-
If I would've just read the manual it would've saved me 60 bucks and a headachePapusan, hmscott, alexhawker and 2 others like this. -
hmscott likes this.
-
Robbo99999 Notebook Prophet
KY_BULLET likes this. -
That was it, all good to go now with 3.5 TB total space
Thanks to everyone for the suggestions and thanks to @Marcel40625 for leading me on the right path!
I learn something new here everyday!Papusan, alexhawker and hmscott like this.
HDD no longer detectable after NVME install
Discussion in 'Windows OS and Software' started by KY_BULLET, Apr 28, 2018.