Got reacquainted with a great tool yesterday, Clonezilla. A Windows 10 Pro “server” came into the shop yesterday with a suspected failed hard drive in its RAID 1 array.
Original steps were as follows…
Pulled both drives (making not of where each one was connected on the RAID controller). Connected the first drive to a dock that was hooked up to the bench machine and ran WD Data Lifeguard diagnostics. It immediately found the drive as being faulty.
The failed drive (as well as the good drive) are 146GB 10K RPM WD VelociRaptor drives. Manufacturer date of 2010 I didn’t bother checking to see if there’s a warranty.
Connected the good drive directly to the motherboard and booted. Installed ShadowProtect SPX and performed a full backup – who knows when this good drive will shit the bed not to mention when the last full backup was completed.
So the backup completes and I’m thinking…wtf…why go through this hassle, just clone the drive!
So I grab the latest Clonezilla (http://clonezilla.org/downloads.php) and burn the iso. Shut down the server, connect one of the new SSD’s (Samsung 850 EVO) to the motherboard and boot from my newly created Clonezilla CD.
Clonezilla mirrors the old drive to the new SSD flawlessly. Prior to this cloning epiphany, I checked out the RAID controller card (SiL 3112A iirc…) Anyways, in the “Create a RAID” option, i had the choice of Automagic or Manual. Going the manual route allowed for creating a new array using an existing single hdd even though it had data on it. I don’t know if this is typical for most RAID controllers but it was super convenient and the job that much quicker. Typically as I understand it, both drives would get blown away when the array was built.
With that part of the project done, there’s just some minor issues within Windows that need to be addressed. Thankfully, these issues were there prior to the computer coming to the shop.