My sister owns a HP laptop. Recently, while powered up, she knocked it off an ottoman. This caused a head crash and intermittent clicking noises indicating a broken hard disk. When powered, the drive responded, but would no longer boot into Windows. I put the drive in an external enclosure and was able to quickly backup all of her data. The majority of the data was luckily intact and accessible.

I ordered a new hard disk, and asked her for the recovery discs. Of course, she’d never made them. When the new drive arrived, rather than installing a different OS, I wanted to simply run the recovery software I knew was on her old drive. First, I tried cloning the recovery partition to the new drive and making it bootable/active. The bad sectors were all in the main drive, so the data copy was successful. Booting the partition resulted in a useless black screen. After some additional testing, I worked out a method using an Ubuntu live CD.

This method was created on a HP laptop, but can be adjusted for many other systems:

  1. Install the new hard disk in the laptop.
  2. Install the old hard disk in an external enclosure and connect to the computer.
  3. Boot the laptop with the Ubuntu live CD (10.10 in this case)
  4. Open a Terminal window
  5. Confirm the new empty drive is /dev/sda and the old drive is /dev/sdb. Confirm the recovery partition is /dev/sdb2.
  6. Type: dd if=/dev/sdb of=/dev/sda bs=512 count=1 to copy the exact partition table and MBR (Master Boot Record) to your new drive.
  7. Next type: partprobe to re-read the partition tables.
  8. Finally type: dd if=/dev/sdb2 of=/dev/sda2 bs=1M to copy the entire second partition containing the recovery software to the newly created partition.
  9. Reboot
  10. Run the recovery software as if you were using the original drive. (Pressing F11 on HP systems.)
  11. Once the recovery is completed, resize the partition to full size of the drive. (For re-size details see Google.)

This method works because the dd software copies the data exact drive data, while accessing the minimum amount of the drive. We skip the areas of the drive we know are bad. If we created a partition table ourselves, we can’t guarantee that the HP system BIOS would recognize how to run the recovery software. Since the important pieces of data are exactly the same, the recovery software can run correctly.


(Statically copied from previous site)

Andy replied on December 6, 2011 - 9:57am

Many Thanks Brad

An excellent article. Saved my bacon! (Eventually)

Like you I had tried a disk clone, which failed as the main partition was faulty. Being a Windows user I had to get my head around some of the Linux commands.

I ended up using Ubuntu 9.x on a workstationwith old and new drives connected via SATA.

The recovery partition was /dev/sdb3 on my old drive, once I had the drives connected in the right order.

I found the commands sudo fdisk –l /dev/sda and sudo fdisk –l /dev/sdb useful in identifying which drive was which. Made sure the new drive is “new” (not formatted) as that helped too.

So I created a new drive as per the above. Same size, and manufacturer. In the faulty computer F11 went into the recovery, and all seemed to go well, until right at the end, and after the actual recovery had completed, I got a small window “Windows setup could not configure Windows to run on this hardware”!!!


So I went back again to your procedure, but this time used an older drive, same size, but a different manufacturer.

This time I got an error in Ubuntu, when it came to copy the recovery partition. Can’t remember it exactly but it was along the lines of “not enough space to copy”.

Finally I tried a clone using Acronis. I cloned the first drive I made. The one with the Windows setup error, to the second older drive from a different manufacturer.

Put this older one back in the faulty system, but received same Windows setup error when I booted of the system partioion.

So on this older drive I started a F11 recovery, and this time it worked. Must have been something the windows setup didn’t like on the new drive I used first.

Downloaded updates and configured etc. Then again using Acronis cloned this older drive onto the new drive that failed windows setup originally.

Finally got there !!!!

Thanks again, and Kind Regards Andy (Wales UK)

brad replied on March 23, 2012 - 3:24pm

Glad I could help! Hopefully your detailed description can help someone else too.

use3r replied on March 21, 2012 - 5:34am

Great info, I need to copy a functional recovery partition, I have just downloaded acronis but will try ur way first. Cheers.

Robin replied on March 21, 2012 - 2:26pm

Thanks a million Brad for posting this. You got me out of a complex harddrive switching nightmare. It worked for me just as you described in your post.

brad replied on March 23, 2012 - 3:22pm

Great to hear. You are welcome!

Majster-pl replied on March 24, 2012 - 3:59pm

Great tutorial! Thanks Brad! Im in the process of copping RECOVERY partition right now… it takes time as old drive have few Bad Sectors… Hopefully wont get any error :-)

Simon ( UK )

Erik replied on April 3, 2012 - 5:58am

Thanks for the tips, they were very helpful. I tried to take a different approach at first but failed. First attempt, I kept the bad/old hard drive in the laptop, hook up a usb external drive and tried to copy the recovery console to the external by taking your directions and reversing some of the steps. This didn’t work for all who will try. I had to take the replacement/new laptop hard drive and take out the old/bad drive and hook them into my tower. I unhook all my other hard drives and just had the two laptop drives in the box, booted with Ubuntu and followed your instructions. The only thing I had to do was use the “sudo” command before each command because the old hard drive wouldn’t give me permissions. Put the new hard drive back into the laptop and was able to boot from the recovery console. Thanks again.

Chris replied on April 29, 2012 - 4:54pm

Hi, I am a newbie at this so please bear with me.

I worked out how to get root access as permissions were denied but the second set of instructions about copying the recovery partition don’t make sense to me. We only had one large partition which we copied the boot sector to (in my case dd if=/dev/sdb3 of=/dev/sda1 bs=512 count=1). This gave me result of 1+0 records in 1+0 records out 512 bytes copied.

Do I still have the one large partition on my new drive (sda1)? I then typed dd if=/dev/sdb1(my original recovery drive) of=/dev/sda2 bs=1M and the laptop froze. Is this because /dev/sda2 doesnt yet exist??? I am slightly confused.

Any help appreciated

Chris (UK)

Karl Kranich replied on May 21, 2012 - 5:43am

Thank you! I was able to recover my neighbor’s laptop. The main windows partition went bad, and I needed a way to get the recovery partition over to a new hard drive. This did it!

Jason replied on May 31, 2012 - 10:35am

This info was instrumental in getting a client’s HP recovered. I followed all directions changing them to match my disk identifiers. It didn’t work at first it still asked for a missing winload.exe file. I booted back into Linux and set the recovery partition as the boot then it started recovery immediately.

Thanks again, Jason FL USA

Duke replied on June 8, 2012 - 4:57am

Hi Brad,

Just brilliant.

HP TouchSmart IQ522pt Ubuntu Desktop 12.04 LTS i386 copy + paste instructions

It couldn’t be more simple.

Thanks very much.



aj replied on July 28, 2012 - 9:25pm

When my HD took a dump, I thought how clever I was when I pulled out the HP recovery CDs I had created a few years ago. Installed the new sata drive and loaded the first restore CD and restarted the recovery. Unfortunately when I loaded the second recovery CD, it would not read. After determining the recovery partition on the damaged HD was still functional, thats when I came upon your simple solution. I followed your instructions explicitly and after rebooting with Ubuntu Live 12.04 and determining the first attempt left my new HD with a partial restore partition, I simply deleted the corrupted partion on the new drive with the Ubuntu disk utility. The only problem I encountered was the permissions issue when copying. Not being familiar with Ubuntu, it took a little time to figure out the Sudo and running as root. After that it worked perfect!!! Since the new drive was twice as big as the original, the recovery partition was in the middle of the drive. I simply created an addition partition with the remaining available space. The bonus by restoring this way I was able to create new recovery CDs (maybe next time they will work?)

Thanks again Brad for such an elegant solution.


Anonymous replied on August 9, 2012 - 12:23pm

Thank you very much for this page. I had a damaged hard drive and no recovery CDs, so I was able to use this process to copy the recovery partition to the new, empty hard drive. Just a couple of things from my experience that might help others.

  1. I couldn’t figure out how to confirm which drive was which, so I had to go to Google. I found a program in Ubuntu called “gparted” that let me see the partitions graphically. It was already installed by default. I just typed “sudo gparted” to run it. It showed me all the drives (including the USB) and where they were located. My new drive was /dev/sba and the old drive was /dev/sdb and the recovery partition was /dev/sdb1

  2. I was using Ubuntu 12.04 LTS (LiveCD) and at first I couldn’t get permission because I was using the “ubuntu@ubuntu” terminal login (the default). I had to google how to get root access by typing “sudo -s”.

  3. Once I had root access and I copied the partition table and MBR over, I typed “partprobe” and got a partition table error on the new drive. To fix it, I had to run fdisk on the new drive. I typed “fdisk /dev/sda” (without “sudo” because I was in a root terminal). Then I typed “p” to print out the partitions table, and then “w” to write the partition table back to the new drive.

  4. Once that was done, I could copy the recovery partition to the new drive and then recover the laptop.

Anonymous replied on October 21, 2013 - 7:59am

This is exactly what I need to complete the recovery partition transfer!

Zach replied on September 9, 2012 - 9:42pm

I’m having a bear of a time with this. I just got an ssd to breathe some new life into an aging laptop but found out the hard way I can’t put recovery discs in a computer without the old recovery partition. I don’t have an external enclosure to copy A to B but logically A to B to C should work if they’re all formatted and partitioned the same, right? Well it’s still not working for me. Now I’m debating a pirated version of windows or linux even tho I paid for the win 7 upgrade already :(

MDVillars replied on September 28, 2012 - 10:54pm

Ubuntu worked great. I used ver. 12 or something like that. This procedure did not work for me but I copieds the entire drive for my HP nc4400 and it worked like a charm! Could not get it to work on a SSD smaller than my original HDD, But once I tried it on a 90GB SSD, it worked great by using:

sudo dd if=/dev/sdb of=/dev/sda bs=1MB

This copied the entire old drive onto my new SSD on a desktop machine and then I used F11 to restore. Victory!

Paul replied on October 3, 2012 - 12:06pm

Just recovered a friends HP laptop using your method, many thanks. I used sudo commands to gain permissions. First time I tried it, the laptop said there was no bootable disc and to try again. Fiddled with a few things to no avail so wiped the new drive using Gparted and tried again ( The new drive was showing 4 partitions all a bit weird with errors ) After wiping and trying for the 2nd time, all worked exactly as stated. Thanks for sharing!

PimpTrizkit replied on November 19, 2012 - 4:53am

Thanks for the great write up! It helped me alot, but I will have to say that in my case this exact method did not work. I was fixing a Dell desktop and the 80GB harddrive crashed. I bought a new harddrive, which is 500GB. After using this method, rebooting to new drive, hitting CTRL-F11 at boot, the system came back with “cannot restore”.

But this article and the comments and some insight, I fixed it! And here is how:

  1. I took insight from #1 comment, Andy. Make sure the drive is unformatted. I’m using a Linux Mint 13 Xfce Live CD, in there is a “Disk Utility” program (which doesnt seem to be in the KDE flavor). In this utility you can easily see your drives and their partitions. I selected the new 500GB drive, and clicked the Format Drive button. In the dialog box which opens, I selected “No Partitions”. Which makes it as blank as possible, I suppose.

  2. In terminal, I ran “sudo fdisk -l”. To see a full list of disks and partitions and made note of my source (/dev/sda) and destination (/dev/sdb) paths.

  3. I followed #13 comment, MDVillars. I ran “sudo dd if=/dev/sda of=/dev/sdb bs=1M”. Which seemed to copy the entire drive, partition tables and boot records. The second partition (the main C drive in Windows), was corrupted, so it died during that part.

  4. Knowing that the third partition is the restore partition (and the fact it didnt get a chance to copy from the above command). I then ran “sudo dd if=/dev/sda3 of=/dev/sdb3”.

  5. Shutdown, unplug old drive, turn on. Hit CTRL-F11 at boot, and presto! I was booted to the restore partition on the new 500GB! Windows installation was successful!

Note: After step 3 above, if you run “fisk -l” again, it marked each partition with some weird warning about it not be in line with the physical sector or something. I ignored this and continued on.

Note: During step 4 above, it gave some error that the device ran out of space. I ignored this and continued on.

Note: I tried all sorts of ways and failed. Until, I did step 1 first. I’m not sure what the command line version of this would be. I had to use Linux Mint 13 Xfce. But I would guess that the “Disk Utility” program is available thru the software manager in any Ubuntu flavor (or heck, any Linux distro with a software manager).

Note: After this, there is 400+ GB of unallocated space at the end of the drive. And since restore partition is the 3rd partition, I assume I cant resize the main partition. So I allocated it as a secondary drive.

I hope this helps others!


Trevor replied on November 30, 2012 - 3:05pm

I would like to add my thanks to all those that provided their help and insights. I had an HP from a friend in the same predicament. No Restore Disks. In my case, the absolutely critical tip here that made my recovery a success was running fdisk on a windows machine on the system partition of my damaged drive. I had been able to copy the partions I needed using the above instructions but the system partition had been corrupted so it still didn’t work. After running Fdisk a few times, I was able to recopy to the new drive and then I was able to access the recovery partition. Well done everyone!!!

Murtaza replied on February 5, 2013 - 4:25am

I understand this is not a discussion forum but if you can help me I would be grateful. I messed up my HP recovery partition but before that I backed it up using EaseUs Todo Backup on another drive. Now I can restore it, but it wont fix the MBR and it wont boot using F11. I made the partition active and recovery manager started but it doesnt show any option to restore to factory OS. All options remain disabled with exception to command prompt

Sheree replied on February 17, 2013 - 2:53pm

It seems that almost everyone who has posted here is very satisfied with the outcome achieved by the instructions.

I was wondering if any monitors or future visitors to this thread could advise if the procedure has been successful in the transfer of the recovery partition to a second drive when a Toshiba laptop has been the test Case?

I am terrified of breaking something that doesn’t need fixing however I have a couple of questions if someone would be so kind:

  1. I would like to know if instead of MOVING in tact partitions to a new drive (if that is indeed the case here), whether they could be COPIED to another drive as a complete “out of the box” backup in the case of total hard drive failure (and while doing so causing no damage to the original drive)?

  2. I am semi literate with Linux and believe I could clearly identify partitions. I would be quite comfortable having a crack at the above procedure but would require commands for the COPY process (once again if that is NOT what is already happening as per the instructional) if they could be provided by a knowledgable user. Can anyone possibly assist?

Apologies for my “newbness” but any assistance is appreciated.

brad replied on March 12, 2013 - 11:22am

This procedure only copies. It does not modify the source drive.

Ankit Batra replied on April 14, 2013 - 11:38am

Hey, I have a HP Pavillion 15-B001tu notebook. I happened to format the complete hard disk. But, I have the recovery partition exactly imaged to an external hard disk using ubuntu live cd. Can I restore my PC. If yes, Please Suggest.

brad replied on June 1, 2013 - 10:33am

Yes, you can clone/copy the partition back to your drive. Recreate the partition table as it was originally, then clone the recovery partition back to the drive. You should be able to get it to work, but it may be complicated.

Fadi replied on May 16, 2013 - 11:20am

i have tried you step using ubuntu 12.4.2 LTS and it worked but the following is to be noted:

1- the first command in ubuntu terminal should be typing “sudo -i” (to gain admin authority, when asked for password just hit enter as there is none.

2- “partprobe” command won’t work in Ubuntu 12.4.2 LTS live CD (i don’t know the reason) but this does not affect the process, you can proceed to the next step with no issues

Fadi replied on May 16, 2013 - 11:23am

the laptop i used was toshiba and the recovery drive was sdb1 not sdb2

brad replied on June 1, 2013 - 10:27am

The exact drive partitions will change depending on manufacturer.

slaeyer replied on May 30, 2013 - 8:57am

Sheree - just to settle your fears, the dd tool does not MOVE a partition, it copies. The exact procedures will vary depending on the individual drive setup i.e. partition 3 on the primary drive would be /dev/sda3 To copy the entire filesystem, including mbr do not specify a partition number, just use the drive device name, i.e. /dev/sda.

There’s lots of detailed instructions on the use of dd if you need more info.

Synergy Solutions replied on June 25, 2013 - 9:19am

The initial instructions worked for the most part. When I tried to run the #partprobe command I received the below error.

[root @ubuntu]# partprobe
Warning: Unable to open /dev/sr0 read-write (Read-only file system). /dev/sr0 has been opened read-only.
Warning: Unable to open /dev/sr0 read-write (Read-only file system). /dev/sr0 has been opened read-only.

Since partprobe (based on what I saw) is used to re-read the partition tables without restarting Ubuntu. I restarted Ubuntu 11.0 (live cd) and continue to step#8. The laptop appear to be doing nothing and when I came back the screen was black but there was no activity on my external drive (old drive). I fired up the system again and voila!!! I am on my way to recovering factory installation. Thanks a million Brad. I have been looking for this solution for the past few system repairs I had.

bof replied on June 30, 2013 - 11:27am

I made a disk image of the recovery partition using ntfsclone and thought that it would suffice but reading this explains why F11 doesn’t work and the depressing black screen I get when I set it to boot from the recovery partition. Is there any way to fix it without a backup of the original MBR?

brad replied on July 3, 2013 - 11:14am

The MBR depends on your specific computer and the manufacturer. Sometimes a simple ntfslcone would work, but I’m sure many MBRs are customized so they won’t work if copied elsewhere.

bof replied on July 4, 2013 - 1:18am

I’s to bad they have to overcomplicate things. Vista is no good anyway so I went with Ubuntu.

D0lapevich replied on July 13, 2013 - 9:14pm

Just for the record, dd_rescue and/or ddrescue are tools to be taken into account to read a partition with surface errors. Regards

Sara replied on August 25, 2013 - 1:38pm

Hello, Thank you so much for your help. I did what you said, but my problem was my new HDD, is 750GB and my old one was 500GB. So I change the commands: type “dd if=/dev/sdb of=/dev/tempsdb.bak bs=512 count=1” then type “dd if=/dev/tempsdb.bak of=/dev/sda bs=446 count=1” then I ran GParted, and Copy partitions from old hdd to new hdd. and everything be fine now


dirk de groote replied on September 16, 2013 - 5:21am

I try to copy the old 320 GB drive from my probook 4730s to a new 750GB drive to have a working recovery partition. So far I failed. I tried the first method first copying one MBR sector and then the recovery partition. I noticed the old disc in my case /dev/sdc has 4 partitions: sdc1 SYSTEM 300 MB, sdc2 noname 275 GB, sdc3 HP_RECOVERY 18 GB and sdc 5 GB HP_TOOLS. Perhaps the SYSTEM part of 300 MB needs to be copied too? Will try to copy the entire disk on a next occasion.

Dirk de Groote replied on September 16, 2013 - 1:29pm

After copying the entire contents of my 320 GB to a new 750 GB disk I could start of the recovery partition and finish the installation. Since the new disk is a 750 GB disk I now have a unallocated space of 400 GB. Is it possible to move the hp recovery and hp tools partition to the end of the 750 GB disk and add the remaining unallocated space to the Windows partition?

brad replied on September 16, 2013 - 1:35pm

You may be able to, but you’ll have to test it. You should be able to resize the main partition correctly, but I cannot say if the tools will continue to work.

Dirk de Groote replied on September 18, 2013 - 6:39am

Somehow I am not able to resize the main partition. Moving HP Recovery and HP Tools partition the the “end” of the disk results in a black screen with an errot that due to a recent hardware or software…..

error 0xc0000255.

As soon as I touch the HP RECOVERY partition the recovery isn’t working. I might format the unallocated space and assigng its own drive letter.

brad replied on September 18, 2013 - 3:11pm

If the system is going to fight you that much, you could leave the existing partitions alone and partition the remaining drive space into a new drive D:. It’s not optimal, but it’ll work.

Diego replied on January 15, 2014 - 2:08am


I’m upgrading to a SSD hard drive which is 120 Gb, while the original drive is 512… will this procedure work? The partition table won’t be the same! I just need to copy the recovery partition and make it work, and then reinstall from scratch… any help?


brad replied on February 8, 2014 - 7:56am

This process replaces your drives partition table with the one from your old drive. Computer manufacturers often customize the partition tables on computers with restore partitions. The restore system will often not bott without this custom partition table.

TLDR: Generally, yes.

Rashid replied on February 2, 2014 - 9:17am

Very good post but unfortunately didn’t work for me. I have an HP Pavilion g4 and somehow managed to get contents of partition table on the USB HDD. What i did was, just ran the first command “dd if=/dev/sdb of=/dev/sda bs=512 count=1” which created partitions on the new drive. Installed Windows 7 Home Premium (Legitimate ISO Image) and of course skipped the Windows key. Once windows is installed, restarted and pressed F11 for recovery. Bingo!!!! I have my hp customized windows again up and running.

Gillo replied on October 9, 2014 - 1:35am

Thank you so much!

I’ve just transferred a 500GB windows 7 system to a 2TB Disk. My ASUS has one hidden partition (with rescue and recovery SW) and two others, the first of which contains windows system and stuffs and the last one is used to save data. After the copy of the MBR and of the hidden partition, I deleted the third partition on the new disk and replaced with one using all the remaining unpartitioned space. To summarize, I’ve ended up with 3 partition: the first one was a clone of the hidden partition, the second one to hold windows and the last one free. Very fast and painless procedure, just be careful to choose the right source and destination disk while copying.

adeisse replied on March 25, 2015 - 3:58pm

excellent post. Done on HP pavilion dv7 but got a C++ runtime error at the beginning of the recovery procedure. I placed the new drive on another PC and formatted NTFS the first partitions, named “SYSTEM” and “OS” like the original disk. I kept the third (RECOVERY) partition intact and then placed the new disk back on the Notebook. F11 and voila ;-) Recovery completed, I could generate de restore DVDs

Som replied on September 22, 2015 - 6:47am

Is this discussion still alive? I’m happy about the positive results people got from your methods brad. However, I’ve been thinking whether this methods work on GPT drives. Cos I’ve tried all the above on my GPT windows 8 installed drive and none worked

brad replied on October 26, 2015 - 10:42pm

GPT is a whole separate issue. You may be able to to handle it with a GPT enabled partition manager, but it’s not something I’ve dealt with in a while. Please let me know if you get something figured out!

fantunes replied on September 29, 2015 - 11:32pm

Good article, it must work a charm for MBR… what about GPT? I tried this very same approach with a slight change as per link: It says the seek operation fails, even after partprobe… ideas?

brad replied on October 26, 2015 - 10:46pm

Seek operation is failing on the new drive or the old one?

lizzie replied on October 14, 2015 - 9:12am

throwing a monkey wrench and a crowbar into this fix. After a windows xp home sp2/3 update/upgrade, the resulting mess has occured on the HP desktop, the main windows C: partition has been named D: and the recovery partition is now identified as C: , can this be fixed with your process?

brad replied on October 26, 2015 - 10:45pm

Haven’t heard of that happening. Interesting result! I know there are ways to change the partition drive letters, but that’s out of scope of this procedure.

Peter replied on January 11, 2016 - 10:15pm

Thanks Brad!

I typed a detailed comment yesterday about how this worked for me using some mods and variations for GPT - unfortunately it disappeared after I hit Save!! (maybe because I had opened the Comment link in a New tab?) Thought I had done a ^C to save the contents but a later ^V revealed an empty clipboard :(. I will try to retype the detailed steps soon when time permits.

Fow now, in a nutshell, I calculated the GPT partition table size using the link provided in a recent comment, I cloned this plus ALL non-Windows partitions (Unknown, EFI System, MS Reserved, and Recovery partitions) to the new drive, then used gdisk to build the backup GPT header and partition table. After this I could boot into Recovery on the new disk.

Cheers, Peter (Oz)

brad replied on February 7, 2016 - 10:59am

Sorry to hear about the missing comment!

Vujadin replied on September 25, 2016 - 11:14am

Worked like a charm accept the part with permission denied but solved with sudo -i command. Thanks!

Michielo replied on November 22, 2016 - 4:09am


Not sure if this is still active, but I’ll try anyway.

I have a Acer Aspire V5-171 with a failing harddrive (500 GB, cannot boot into Windows) and no back-up of the recovery partition. I bought a new 1 TB HDD, took the old drive out and replaced it with new drive, put the old drive in a USB enclosure and hooked it up to a free USB slot on the laptop, burned Lubuntu 16.10 to a USB stick, put the stick in another free USB port on the laptop and booted the laptop into Lubuntu. Opened disk utility to identify drives and partitions (new drive /dev/sda, old drive /dev/sdc and USB stick /dev/sdb.

Then I performed the step as per this tutorial (my comments/results added between ())

Boot the laptop with theLUbuntu live CD (10.10 in this case) - Lubuntu 16.10 in my case Open a Terminal window Confirm the new empty drive is /dev/sda and the old drive is /dev/sdb (/dev/sdc in my case). Confirm the recovery partition is /dev/sdb2 (/dev/sdc6 in my case). Type: sudo dd if=/dev/sdc of=/dev/sda bs=512 count=1 to copy the exact partition table and MBR (Master Boot Record) to your new drive. (Terminal confirms MBR was successfully copied) Next type: sudo partprobe to re-read the partition tables. (I didn’t recieve any output from partprobe and when I refreshed disk utility it shows 1 TB of unallocated space with no partitions on the new drive sda) Finally type: sudo dd if=/dev/sdc6 of=/dev/sda6 bs=1M (dd runs for about 2 minutes then returning an error that it cannot copy sdc6 because there is not enough free space on sda.

Can anyone tell me what I’m doing wrong and how to fix it so I can copy the recovery partition from my old drive to the new drive. I also tried using Ubuntu 16.10 and Ubuntu 12.05, but same result on all steps.



Pete replied on March 28, 2017 - 2:51am

I had similar problems to those described in the original post, I found this article to be the best fix. I have Windows 7 on an ASUS U36S laptop (no DVD drive, Windows 7 recovery partition). When I started I didn’t even know what an enclosure was, but they are dirt cheap on eBay, I purchased an enclosure and a new HDD, and used the original post and all the suggestions listed in the following messages to restore my operating system on my new HDD. I can’t thank you enough. I have another suggestion to add - after restoring my MBR (step 6), the new drive had the setup that existed on my old HDD - but the operating system partition was unformatted. When I copied the recovery partition over to my new drive (step 8) I ran my setup using F9 on reboot, the recovery would start as expected and would run for a few minutes but then just stop with no error message. It just stopped on a blue ASUS setup screen. I finally discovered that formatting the partition allowed the recovery installer to run as expected and install the operating system onto the partition. This was the missing step and final FIX for me! When Windows 7 and all drivers were installed, I ran Windows update and there were 200+ updates to install - took four hours and many restarts.