Blog - Migrating Data from one Hard Drive to Another
A short while ago I had a failure in my MythTV server. Luckily, all of my data was ok so I just transplanted the hard drives and tuners into my development system and was on my way again. While I had everything open it quickly became obvious exactly how loud my OS hard drive had become. I knew that it was noisy but the P180 case did a good job of keeping things quiet. So I figured that now is a good time to replace it as long as I had everything all strewn about anyway.
To give you a bit of background, the OS hard drive that I am starting with is a 10GB PATA drive that is about 10 years old. The "new" drive is a 250GB drive that is only a couple of years old. The utility that I used to image the drive is called Clonezilla. This is a tool that you load on to a bootable drive (i.e. a CD or a USB flash drive). With both the old and the new drive installed in the PC you boot into Clonezilla, select the drive or partition that you want to back up (clone), select the new drive or partition and wait till everything is copied. Depending on the amount of data being copied this can take anywhere from a couple of minutes to a couple of hours.
Once everything was copied I pulled the original drive from my system, plugged in the new drive and away I went. The only problem that I ran into in this process was the drive order in the BIOS. My PATA drive is recognized first by my BIOS and all of my data drives were found after. However, when I plugged in my new drive I took the next available SATA port. While I was able to change the boot order in the BIOS and boot from it, my software RAID device was unable to load because it was looking for the drives on the second, third and fourth devices but they were now (and always had been) connected to the first, second and third SATA ports on the motherboard. Since it couldn't find the drives to make the software RAID device, the system refused to fully boot. After quickly reordering the SATA cables making the new OS drive first everything was up and running and the OS was none the wiser for being cloned. And in addition to being much quieter, which was my original goal, I've also found the new drive to boot a bit after (on the rare occasion that I need to reboot my MythTV server) and also load data from the database faster. All-in-all I think that this was a great success.