Hello again,
On Thu, 20 Oct 2022, Adam Hardy wrote:
I scanned the problem USB drive with smartctl and with
gnome-utilities and it logged nothing.?
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."
--
73,
Ged.
_______________________________________________
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/
