Any hints? Started well, but now only 47% after 16 hours
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
So I have a Windows 7 HP desktop (UEFI) with a 1 TB drive, mostly empty. Started getting SMART warnings about eminent disk failure, so I got an identical disk and fired up Clonezilla to copy Disk to Local Disk (replacement is USB attached).
First run went well to a point. Seemed to 'hang' at 57.03%, so I killed it and started again after a re-boot, this time watching a bit closer.
The first 30% or so moves along promptly, in about 15 minutes. But then things slow way down. A couple of time checks I made show:
Start @ about 16:00
30% around 16:30
Left for dinner thinking all was good, but then upon return,
43.12% around 19:00
44.47% around 22:00
47.85% following morning at 7:45 am
48.15% as I write this at 9:00 am.
It is still progressing, apparently, but at an absolute snails pace.
Questions;
1) Any 'typical suspects' for this type of behavior, and more importantly suggested fix?
2) Any way to access a log while running to see what is going on?
3) Would moving the target to be a secondary internal (using say the CD drive's connectors) make any difference?
Thanks in advance...
Ok, so reaching way deep in my old Linux memory, I found the alternate consoles and tool a look at /var/log/syslog. In there I see a bunch of I/O errors on my /dev/sdb (target) USB drive.... and uas_he_bus_reset_handler... is this telling me my spanky new disk is bad? Or perhaps my external enclosure is throwing fits?
Will give up on this and try it on the on-board SATA connection since I don't need the CD drive at this time anyway...I guess that will tell me if it is the drive or the enclosure....?
Thanks -
Well, talking to myself, but recording in case it helps anyone else.
Two realities;
1) Moving the target to an on-board SATA connection eliminated all the target errors, so perhaps an issue with my USB enclosure. The clone also flew by a lot faster, getting to 98% in about 30 minutes (/sda1, 2 complete, 98% on sda3, the 956 Gig NTFS main partition).
2) The last two percent took several hours, having reached the failing space on the target. Lots of permanent read errors logged.... But it eventually finished.
3) /dev/sda4 was a complete bomb. Initial run said "bad number of free (-1) or total (4022527) clusters". So figuring I had dev/sda1, 2, and 3 clean, I retried with just a part-to-local-part on just /sda4. Even with fsck, it did not work out well. It was a 15 gig partition, and after letting it run overnight, it was 4% done with 78 hours to go! Uhm, no.
4) /dev/sda4 was the HP Recovery partition so we went forward without it. Interestingly, I was able to create a recovery disk (DVD) before all this, so I have that at least.
New disk is working great, except for no bootable Recovery partition. I did copy the contents of the recovery disk back to a manually formatted D: partition, but it does not boot (either from DVD or that D: partition). Hopefully never any need to restore to factory defaults on this machine!
Overall, Clonezilla did the trick! Thanks!
Cool. Thanks for sharing your experience.
Steven