We’d like to remind Forumites to please avoid political debate on the Forum.
This is to keep it a safe and useful space for MoneySaving discussions. Threads that are – or become – political in nature may be removed in line with the Forum’s rules. Thank you for your understanding.
📨 Have you signed up to the Forum's new Email Digest yet? Get a selection of trending threads sent straight to your inbox daily, weekly or monthly!
The Forum now has a brand new text editor, adding a bunch of handy features to use when creating posts. Read more in our how-to guide
Disk boot failure
garcia
Posts: 214 Forumite
in Techie Stuff
Hi all,
I've recently upgraded my hard disk to a bigger size. Copied over my partitions fine. Replaced my old hd with the new one. Only I can't boot into the new hd. I get the message "Disk boot failure, insert system disk and press enter".
Any ideas whats going on??
Many thanks.
I've recently upgraded my hard disk to a bigger size. Copied over my partitions fine. Replaced my old hd with the new one. Only I can't boot into the new hd. I get the message "Disk boot failure, insert system disk and press enter".
Any ideas whats going on??
Many thanks.
0
Comments
-
what did you use to copy the data?
If ide, have you made sure it's set to master or cable select?Ever get the feeling you are wasting your time? :rolleyes:0 -
Its ide, set to cable select.
I used a freeware prog. to copy over the data - its called DriveImage XML. Received good reviews, and seemed to work well.0 -
you could try fdisk, to make sure the partition is set to active, and if that doesn't work fixmbr or fixbootEver get the feeling you are wasting your time? :rolleyes:0
-
You were right it was a question of setting the active partition.
Windows boots. But instead of my usual log-in screen I get a low-graphics version, which asks for my password then says "logging out" and hangs.
I strongly suspect that its to do with drive letter assignment. I have my old hdd as c: and d: and my new hdd as e: and f:, e: being the partition which I've just made active.
Now I can boot from e: but only if I have the old hdd hooked up.
Any way I can change drive letter assignments??0 -
Try setting the new drive to Master and the old one to Slave (or leave out altogether initially). With Cable Select and both old and new drives on the same IDE cable the BIOS may be getting confused over which drive to boot from.garcia wrote:Its ide, set to cable select.0 -
You could try putting in the old disk as master, new disk as slave, go into driveimagexml, tools, new disk id.
If it still doesn't work, are either of the drives maxtors..
http://www.maxtor.com/portal/site/Maxtor/menuitem.3c67e325e0a6b1f6294198b091346068/?channelpath=%2Fen_us%2FSupport%2FSoftware+Downloads%2FTop+Downloads&downloadID=19Ever get the feeling you are wasting your time? :rolleyes:0 -
@Chippy: both drives are on different cables (only 1 drive per cable).
@albertross: I think you are right. The initial problem I had was I hadn't set the partition to be active. Once I did that it booted fine, but just got the drive assignments wrong and would hang if I didn't connect up the old drive too. I think the new disk id should do the trick (I'm in the middle of copying it again, but as soon as its done I'll try it).
Thanks both for the help.
P.S. Neither of the drives are maxtors. Old one is seagate barracuda. New one is Samsung Spinpoint.0 -
Just an update for albertross - it worked!
Chkdsk needed to fix a few errors on the new disk, but once done everything worked perfectly.
I highly recommend DriveImage XML for anyone who wants to:
-Backup logical drives and partitions to image files
-Browse these images, view and extract files
-Restore these images to the same or a different drive
-Copy directly from drive to drive
-Schedule automatic backups with your Task Scheduler
Thanks to all who helped,
Garcia.0 -
I tried it several ways, including the "raw image" option - which is actually a weird option because it resizes the target partition so that its the same size as your original partition (so not a very useful option as you lose disk space).
I needed to do the disk id thing. I suspect that windows "remembered" that my new disk was drive E: and F: and so got confused when I tried to boot from it. Giving it a new id eliminates this possibility, with no down side. Of course it might work for some without having to do this.
I imagine that the chkdsk errors were because I was using the computer whilst backing up, rather than anything serious - e.g. it recovered some temp files that I had deleted.
P.S. I see that you can run the prog. from winpe / bartpe.
http://www.runtime.org/peb.htm
If you had one of those disks handy you could then just back up and not worry about things like disk id until you actually needed to restore a copy.0
This discussion has been closed.
Confirm your email address to Create Threads and Reply
Categories
- All Categories
- 353.5K Banking & Borrowing
- 254.2K Reduce Debt & Boost Income
- 455.1K Spending & Discounts
- 246.6K Work, Benefits & Business
- 603K Mortgages, Homes & Bills
- 178.1K Life & Family
- 260.6K Travel & Transport
- 1.5M Hobbies & Leisure
- 16K Discuss & Feedback
- 37.7K Read-Only Boards