Simon, I don't know if there is a better way but last time I had to deal with the similar problem, I just used a simple loop in bash script to write zero (or actually anything) to affected bad blocks. This way hard drive will automatically relocate the bad sectors or if the sectors still good, let you read them back without I/O errors.
On Fri, Jul 22, 2011 at 10:14 PM, Simon Males <[email protected]> wrote: > Hi Slug, > > I'm trying to save a failing NTFS hard drive. It manages to mount and > during copying the following error will appear in dmesg: > > Buffer I/O error on device sdc3, logical block 786433 > > I don't mind corrupting some files. Can I instruct badblocks to add > the failings blocks to the bad block register (I'm assuming that's how > badblocks/hard drives work). > > Thus whilst copying, I will not get any block errors. > > -- > Simon Males > -- > SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ > Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html > Cheers, Masood -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
