-----Original Message-----
> Be careful with smartctl if you use it for anything other than
> reading
> information from the drive.  Heed the warnings in the 'man' page, and
> before you do anything like setting or changing drive characteristics
> search online for reports from people who've done similar things with
> your particular drive model.  One wrong move could be serious.  Maybe
> it won't be necessary.  I've used it to stop drives from spinning
> down
> in problem cases but only when the timeouts interacted very badly
> with
> the Linux kernel timeouts for flushing sectors from RAM to disc. 
> I've
> been prepared to take the risk of damaging drives, but only because
> my
> alternative would have been to put them in the recycling bin. :/
> 
> Don't forget I'm still guessing. :)
> 
> > I checked in the syslog and I can't see any other log files that it
> > might be using.
> 
> You can spend hours trawling through logs, but mostly I'd search in
> /var/log/(daemon.log|debug|kern.log|messages|syslog) - not
> necessarily
> in that order.
> 
> > How would I run something automatically before backup? Or do you
> > mean manually?
> 
> I meant automatically.  I was thinking of one of these:
> 
>      $Conf{DumpPreUserCmd}
>      $Conf{DumpPostUserCmd}
>      $Conf{DumpPreShareCmd}
>      $Conf{DumpPostShareCmd}
>      $Conf{RestorePreUserCmd}
>      $Conf{RestorePostUserCmd}
>      $Conf{ArchivePreUserCmd}
>      $Conf{ArchivePostUserCmd}
> 
> Check the documentation for "Optional commands to run before and
> after
> dumps and restores, and also before and after each share of a dump."

Warning registered re smartctl. Thanks for the references to the
config, which immediately draw attention to the fact that I have no
idea what the error is. 

Looking through those logs for anything at the time of the modification
timestamp on the backuppc xferlog, I can see this one line which
appears about 25 mins after the backup fails:

   Oct 17 16:13:48 localhost smartd[1302]: Device: /dev/sdb [SAT], 1
   Currently unreadable (pending) sectors

The target USB drive is /dev/sdb1.

But as I said, I scanned the drive and it didn't log any errors. Is
that useful info?

Thanks
Adam
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/

Reply via email to