Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1613
  • Last Modified:

Difficulty Upgrading to Larger Hard Drive in HP D530 Desktop

I have been unsuccessful in trying to upgrade the original Maxtor 40GB HD in my HP D530 business desktop to a Western Digital 160GB HD.  The BIOS automatically recognizes the new drive when I install it, but the system will not boot from a WINXP CD to load the operating system, even when the boot order is set to the CD Drive option.  I typically get either a "NTLDR is Missing error" or the system attempts to boot from the CD, but then halts with a "Bad Disk" error.  Using the Western digital Lifeguard tools, I can reformat the new drive and prepare it for Windows XP, but the same failures occur.  If I remove all HDDs , the system boots into the Windows XP setup from the CD just fine, except that it has no drive to install the OS on.  

I have also attempted to clone the existing 40GB drive onto the 160GB Drive which, by all indications goes through successfully, but when I remove the 40GB drive and make the 160GB drive the primary, I get a "NTLDR is missing error".  I have tried this using partitions larger than 37GB and partitions smaller than 30GB, to no avail.

I have verified that the hard drive jumpers are set to cable select and even went so far as to reset the CMOS and BIOS password jumper.  Nothing seems to be working to get the system to work with the new hard drive.  

Also, another oddity, not sure if this is related but thought I should mention it, I cannot get into the system's BIOS setup when hitting F10 at startup.  I can get to the F9 boot sequence screen though.  

Something is not right somewhere, but I can't seem to pin this one down.  Any suggestions for things to try would be appreciated.
0
Intech_IT
Asked:
Intech_IT
1 Solution
 
PUNKYCommented:
How did you clone the drive?
- copy disk to disk
- copy mbr
- set active
- do not assign drive letter
0
 
Intech_ITAuthor Commented:
I used Drive Clone Home Ver. 5 from Farstone.  I have used this technique on other systems without any issues or modifications to the default settings.  
0
 
Intech_ITAuthor Commented:
Also, I have tried cloning with the new drive attached via a USB external HDD Enclosure and then a second time attached to the secondary IDE connector on the MB.  
0
 
akahanCommented:
I guess I have a theory....and the first question is, are you using a USB keyboard?...maybe you
see where I'm going with this...
0
 
nobusCommented:
try setting the drive as master - or slave, instead of cable select (and the cd drive too)
0
 
jgmontgoCommented:
You mention a very imporntant clue here "Also, another oddity, not sure if this is related but thought I should mention it, I cannot get into the system's BIOS setup when hitting F10 at startup.  I can get to the F9 boot sequence screen though."
I am wondering if we have a problem with the BIOS not supporting that hard drive, or some other oddity that is causing this. So a couple of questions:
  1. I assume the original drive was PATA, is this correct?
  2. Is the replacement drive SATA or PATA?
  3. If the drive is SATA is it SATA-I or II?
  4. If it is SATA what connector is it connected to (should be SATA 0 according to HP)
Here is a link to the Hardware Reference:
http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c00059123/c00059123.pdf
I am wondering if this is related to the drive and how it is installed. If the original was set to Cable Select, you should use the same connector on the cable and set the new drive to Cable Select. If you are using SATA, make sure you connect to the SATA 0 connector and initially try SATA-I 1.5 Gbit/s, then try SATA-II 3.0 Gbit/s.
Pay special attention to how the original drive was setup and how the replacement is.
I checked the BIOS version history and saw nothing to indicate an issue, so BIOS update is not warranted. However, the fact that you are experiencing some difficulty in getting into the BIOS with this drive installed may be a clue.
0
 
Intech_ITAuthor Commented:
I am using a standard PS2 keyboard and mouse.  The old drive is a PATA and the new drive is a PATA. I have updated the BIOS to the latest version available, ver 2.43 I believe, but that had no impact on the BIOS access issue.  I just tried to use the drive as a secondary/backup drive, connected via a USB enclosure, and the strange thing is, the BIOS recognized the drive.  I was able to format the drive in Windows and subsequently was able to R/W any amount of data to it.  Is it possible that in order for the drive to become a bootable drive, this HP system requires some sort of hidden partition on the drive that my cloning program isn't seeing?  I found fleeting references to such a thing, but no concrete steps on how  to set that up on the new drive.  
 
0
 
jgmontgoCommented:
I am really seeing nothing with the computer or BIOS that should be causing this.
I do have an idea that might work. There is a program that I love for cloning hard drives that I would love to see you try. This program will clone everything including the MBR and any special partitions.
Here is a link to the product:
http://www.acronis.com/homecomputing/products/migrateeasy/
They do offer a free 15 day trial, way more than enough time to see if it will work for you. You can click on the Download Free Trial button or the link below:
 http://www.acronis.com/homecomputing/download/migrateeasy/
You should be able to reinstall the 40GB drive as the Master, the 160GB as a slave (they should support USB if you need to keep it as an external drive). It will copy everything and resize the partitions appropriately.
I am thinking it might be an issue with the software you were using to clone the disks with. Acronis® Migrate Easy 7.0 is a great product and should work well for you.
0
 
Intech_ITAuthor Commented:
Thanks jgmontgo! I downloaded the acronis software and that seemed to do the trick.  I connected the new drive up to the secondary IDE connector and teh software cloned the primary drive without much effort.  I moved the new drive to the primary and everything booted right up.  Thanks again.  
0
 
Intech_ITAuthor Commented:
Thanks for the help.  
0
 
jgmontgoCommented:
Very nice! I am happy to hear that it worked well for you!
Thanks for the points!
0
Tackle projects and never again get stuck behind a technical roadblock.
Join Now