Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations cowski on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

New HDD - No bootable device found

Status
Not open for further replies.

JBinCA

Electrical
Jun 25, 2005
98
Hi all,

I normally take images of my entire laptop HDD about every six months using Symantec ghost , and back-up all data much more often.

When attempting to create a new image last week, ghost failed and informed me that there were bad sectors on the HDD. I have two partitions on the drive, one for system / program files, the other for Data. Somewhere along the line, I got a message that the corrupt sectors pertained to my data partition. Since I have loaded a decent number of programs since my last image, I created an image of just the system partition (which was theoretically intact).

My system is runing fine on hte existing HDD. The first indication of a problem was the failed image attempt. The two data files that were flagged as being on currupt sectors are no longer readable from within windows either.

I bought a new HDD and created the necessary partitions from control panel / computer manageent / storage. I then attempted to load the system / program partition from file onto the desired partition in the new HDD. This seemed to work. When I swapped the new HDD for the old HDD in my laptop, I receieved an error on start-up (at the black screen stage) that says "no bootable device found" (or words to that effect).

I have also used ghost to do a direct clone from the old HDD to the new HDD and have the same problem when attempting to start the system.

My laptop is a dell Lattitude D610, it is about 1.5 years old. I am runing XP pro SP 2.

The old HDD is an 80Gb 2.5 in IDE sytle. The new HDD is a 120Gb 2.5 in EIDE style. I was under the impression that the EIDE would be used in place of IDE, but could this be my problem?

I also used an external HD enclosure to set-up the new HDD. I found an article on the web that mentioned that the temporary drive letter assigned to the drive could be retaied in the registry. I would have thought this would have been blown out when I cloned directly (which was my last operation).

Does know what the problem might be? Any advice?
 
Replies continue below

Recommended for you

The problem is now solved, but I can't be sure as to why.

I reformatted the entire new HDD (removing the new partitions) and recreated the partition from the image file to the "unallocated space" on the new HDD. This did the trick.

Perhaps the issue with XP "remembering" the partition from when it was first created explains things, but I don't know.

IRStuff - Thanks for the response. Yes I am sure that hte partition was activated, I was able to read and write to it, and was able to verify that the files and folders were identical to the original. This lends further support to the theory that the registry was the issue...

Also, Tektips registration process was broken today. I noticed your referal to that site on a post I found while searching this issue out.

Regards, JB
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor