That would imply the disk itself found the errors on one of its scans. You could do a "dd if=/dev/sdx of=/dev/null conv=noerror bs=1M" that should mean the dd will continue on when it hits the error and you will get the list of bad sectors in the messages file. You would have to use fsdebugger or something similar to find the specific stuff in that sector. On Sat, Mar 14, 2015 at 5:09 PM, Tom Horsley <horsley1953@xxxxxxxxx> wrote: > On Sat, 14 Mar 2015 16:53:15 -0500 > Roger Heflin wrote: > >> Also usually the errors are found by linux doing a read against it, so >> there should be error messages on the reads in the messages file when >> it happened, that is usually what I use to determine what sectors are >> getting the error. > > Yea, I poked around in the logs and the very first thing > that looks like any kind of error is the smart message > showing up for the first time (and repeating every > 30 minutes since then in an attempt to fill up the logs :-). > -- > users mailing list > users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
