On 20.03.2021 15:50, Gene Heskett wrote:
Greetings all;
I have been using amanda on this machine to back up the rest of my
machines for over 2 decades. So I'm not a new user.
But I installed a 240 gig SSD about 6 months back, because its use as a
holding disk tripled amanda's speed at backing up this 6 machine system.
But amanda has been increasingly plagued with bad crc checksums of the
data in this holding disk, which usually leaves the files on that disk
as it redoes that disklist entry bypassing the holding disk, which
obviously takes longer as it is then doing the backup directly to the
archive medium.
I just initiated a "-t long" test on it. So since its an SSD, what is
the best command to extract the most complete test report possible when
the test has finished? Its now done, and the -a option gives it a clean
report, along with a list of this and thats not supported. Cheap adata
drive.
Thank you.
Cheers, Gene Heskett
You can see SMART test results with "--log=selftest" parameter.
# smartctl --log=selftest /dev/sdZ
Can you post back the output from "smartctl" with "--all" parameter for
this device?
Usually cheap and\or old SSDs have a limited SMART information, but it
still worth to look.
For reference, here is the output for one of my consumer grade SSDs
(2-bit 2D MLC NAND), used as system disk for two OSs:
https://paste.debian.net/1190136
It was used daily for 23932 hours (attribute #9) and still reports 99%
health left (attribute #231).
--
With kindest regards, Alexander.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀⠀⠀⠀