The other thread on the Seagate fail mentions that I got the 3TB drive successfully RMA'd. viewtopic.php?f=36&t=241548
I tried using Clonezilla again, but the clone failed. It wrote the results to a log, but I don't know where to find the log file, since Clonezilla was hosted on a CD. It was more than 50% complete. Here's part of what the error said:
ata1.01 exception emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Buffer i/o error on device sda1
I've seen similar enough errors on other threads: http://forums.fedoraforum.org/showthread.php?t=219746
People keep blaming SATA cables, PSUs, motherboards, RAM, CPUs, OS kernel errors, and bad drives and controllers. Note that the error was on the source drive, the one that did NOT have the end-to-end errors. I ran diskcheckup, and there weren't enough bad sectors to signal any kind of warning. The point of cloning the drive is to back up the drive and get a new bootable drive rolling; I'm already trying to copy the data off of it. Any bad sectors are not noticeable in normal drive usage, so it probably is restricted to affecting disk imaging for now. DRevitalize v2.42 is scanning the drive in read-only as I write this, and so far has only found nine slow sectors (two of which are probably false positives from loading OSForensics during the scan), and zero bad sectors--the software is unable to refresh slow sectors in Windows Vista mode, so I might use the DOS version to fix the sectors. I keep reading that it won't repair hardware related bad sectors, but since the drive hasn't significantly declined in performance it might be worth it. It's another one of those "backup your data before you fix the drive," "you must fix the drive before you can back it up" paradoxes.
I'm dealing with another challenge/software thing that Clonezilla hasn't bothered to automate: The original OS host drive is 1TB, uses MBR, and booted from a BIOS. The target drive for the backup is 3TB, and I want it to use GPT and UEFI. I found several threads on what to do, but I want to make sure I'm not screwing things up.http://superuser.com/questions/443561/c ... mbr-to-gpthttp://forums.partedmagic.com/viewtopic.php?f=5&t=4752
Microsoft recommends a configuration with a partition for WinRE tools, System, MSR, Windows, and Recovery image. http://technet.microsoft.com/en-us/libr ... 32(v=ws.10
The WinRE partition should be 300MB (and has to be configured as a utility partition with an ID type command in DiskPart or SIM; this link says it has to be 300MB instead of 100MB, but this could just be for Win8: http://technet.microsoft.com/en-us/libr ... 24839.aspx
); EFI System should be 260MB (unless it's going to hold WinRE tools also, in which case the combined partition should be 240MB less than both partitions alone, 300MB) and formatted in FAT32 "For Advanced Format Generation One (4-KB-per-sector) drives, the minimum size of this partition is 260 MB"; the MSR should be 128MB, the big Windows partition (I don't know how to go about setting aside maybe from subtracting the space of the other partitions, but it seems like any measurement might get thrown off by several megabytes due to the way different applications read the hard drive space); and the Windows Recovery Image partition should be at least 2GB (I guess it's left blank until it gets an image written to it, but exactly which parts of Windows would go on it and how to set up the image is unknown to this user). So that's a minimum total of 2736MB worth of overhead in boot and recovery related partitions.
"If you clone a Winows 7 formatted MBR disc to a Windows 7 formatted GPT disc you will trash the mysterious hidden partition." It sounds like it might be resolved by going into Clonezilla's expert settings (which is a questionable idea, since the recommended setting is beginner), and opting not to use the partition table from the source disk. This doesn't resolve how the partition table is supposed to get in there, then, but I guess it's resolved by installing Windows to the target drive first, and only copying the Windows partition.
Step 1. Seems to be cleaning the drive, which seems most easily done from Windows' Disk Manager. RMB on the drive > clean this drive (wipe the data).
Step 2. Install Windows to the drive from an ISO downloaded from Microsoft's website --it doesn't have to be activated (I guess the partition sizes are automated, but they don't mention partition sizing for WinRE and Windows Recovery Image in a clean install context in the links regarding partitions, so those partitions might not be automatically created). This link indicates that for cloning an image to another drive, you can set up the partitions without installing Windows: http://technet.microsoft.com/en-us/libr ... 53(v=ws.10
) Microsoft notes that the partitions need to be the same size on the source and target disks, so I guess I could extend the Windows partition after imaging (I guess imaging and cloning are two different things--clonezilla has a disk to disk option, so imaging is probably different only by paying attention to partitions instead of raw data like the disk to disk copy does). http://technet.microsoft.com/en-us/libr ... 25686.aspx
Step 3. Install PartedMagic to a bootable flashdrive.
Step 4. Clone the MBR from the old drive to the EFI System partition
Step 5. Clone the Windows system partition to the 3TB drive
Step 6. Leave the other partitions alone
Step 7. Run Windows repair from the same ISO DVD supposedly used to install Win7 x64 on the 3TB drive
Step 8. Skip Chkdsk, it's useless and never does anything helpfulhttp://superuser.com/questions/443561/c ... st#tab-top
A ton of stuff to fix; I can't tell if it would be easier to start from scratch or not, but other people have managed to clone their drives, so I'm not giving up on it yet.