My new HDD is having some issues.

Toggle sidebar Toggle sidebar
D

Dark Cloud

Reputable
Nov 17, 2015
26
0
4,540
So I got a new hard drive for my old pc to get it working again and some odd issues are happening with it. I have two pc's. With my new pc, I installed windows 10 onto the new hard drive. I took the new hard drive out of my new pc and put it into my old pc to try to get it working again. It says no bootable device detected. I went into the bios and selected this new hard drive as boot sequence #1. I tried putting my current pc's hard drive into the older pc to see if it was any of my older pc's hardware screwing up, but my hard drive loaded to the desktop just fine. After installing windows 10 onto my new hard drive from my new pc, I was able to get to the desktop and do whatever. Only on my new pc though. My old computer simply won't recognize this new hard drive's bootability, but it will boot with my current pc's hard drive. So my question is, why won't my older pc boot from my newer hard drive? It detects it just fine.
To make sure you get everything: My new hard drive and my current hard drive have windows 10 and can boot on my current pc. My older pc can boot from my current hard drive but, not from the newer hard drive. Why? Is the hard drive I bought for my old pc incompatible? Thanks for reading, I look forward to seeing your solutions. If you need any additional information, let me know.
 
Solution
USAFRet
This is the issue:
You installed the OS on this new drive while it was in System 1.
You then took that drive out and put it in System 2, the previously dead system.

The actual boot info for this OS lives on the other drive that was already in System 1.

Additionally, an OS should really be installed on the drive while it lives in the PC where it will live. Sometimes it works otherwise, but it is MUCH better to install the OS in the actual system.

So...to fix:
Put the new drive in System 2, the used to be dead one
Install the OS
Done.
Sort by date Sort by votes
USAFRet

USAFRet

Titan
Moderator
Mar 16, 2013
171,731
18,104
184,590
This is the issue:
You installed the OS on this new drive while it was in System 1.
You then took that drive out and put it in System 2, the previously dead system.

The actual boot info for this OS lives on the other drive that was already in System 1.

Additionally, an OS should really be installed on the drive while it lives in the PC where it will live. Sometimes it works otherwise, but it is MUCH better to install the OS in the actual system.

So...to fix:
Put the new drive in System 2, the used to be dead one
Install the OS
Done.
 
Upvote 0 Downvote
Solution
D

Dark Cloud

Reputable
Nov 17, 2015
26
0
4,540


So, I need to put my new hard drive into the old pc then use my bootable usb to reinstall windows?

 
Upvote 0 Downvote
USAFRet

USAFRet

Titan
Moderator
Mar 16, 2013
171,731
18,104
184,590


Yes.
 
Upvote 0 Downvote
W

waltercarroll

Commendable
Sep 21, 2016
16
0
1,510
The biggest issue is a pitfall of all types of flash memory. You have a limited number of read/write cycles. But, the good news is that usually only the write portion is affected if you run into a read/write issue. In other words, you’ll be able to recover all of that data still on your SSD and put it somewhere else. While an SSD is less likely to malfunction considering that there are no moving parts, it’s still susceptible to the everyday wear and tear.
 
Upvote 0 Downvote
USAFRet

USAFRet

Titan
Moderator
Mar 16, 2013
171,731
18,104
184,590


1. What does this have to do with the OP's original question?
2. The "limited number of read/write cycles" for current consumer grade SSD's is wildly overblown.
Please link a report of any current drives dying 'soon' from normal consumer types of use.
(Heavy database I/O does not count)
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom