error writing to destination disk

A partition and disk imaging/cloning program

Brought to you by: steven_shiau

#137 error writing to destination disk

Milestone: stable_clonezilla_live

Status: open

Owner: Steven Shiau

Labels: clonezilla live (129)

Priority: 5

Updated: 2012-03-08

Created: 2012-03-06

Creator: Jim Michaels

Private: No

I get a different error at a different time every time I use a different USB hard drive interface.
this time it was a thermaltake blackx duet dock. I don't care for the name, so I will probably be sending it back for a refund.

Discussion

Jim Michaels - 2012-03-06

more details: src disk is a toshiba 80GB, destination is a seagate momentus 500GB. both have 512 byte sectors. I was doing a local disk to disk copy.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2012-03-08

It looks like the problem is on hardware, or kernel/hardware support.
Are you sure your hardware is flawless?
Did you try different version of Clonezilla live?
E.g. Clonezilla live 1.2.12-29 or 20120305-precise?

Steven.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Steven Shiau - 2012-03-08

assigned_to: nobody --> steven_shiau
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jim Michaels - 2012-03-09

I am beginning to wonder now.
after doing a chkdsk /r a 2nd time, the hardware seems to disconnect (it is also warm). I have 2 new 2.5" seagate momentus 500GB drives. fssdev.com said to do a chkdsk /r a few times to fix any "bad blocks". I thought those would have been marked out at the factory. they usually are to my best understanding.

I have had no end of trouble trying to use these 2.5" drives over USB. I know 2 of my front USB ports are flaky, so I usually try to avoid using them and instead use my 7-port hub.

the drives format full NTFS fine. I get no messages about bad blocks when I use chkdsk /r (then maybe it doesn't say anything).

I am going to try a bad blocks check using the system rescue cd and see if that makes any difference.
I need something that's actually going to give me a list of bad blocks.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Jim Michaels - 2012-03-09

20120127

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.