> I have some error log entries which were symptomatic of a brief power supply
> deficiency and I'd like to clear them out of the SMART log records on these
> drives, if possible, to keep from seeing the output of smartctl -a polluted
> by these "uninteresting failures".
As far as I know, the only way to clear the SMART error and self-test logs
is with a firmware upgrade. If your disk vendor has a 'firmware upgrade'
utility, you may be able to replace the firmware with the same or a more
recent version, clearing the logs in the process.
Also, remember that smartd will monitor these logs and inform you if the
number of entries CHANGES. So if you use smartd to monitor the disk, the
existence of these annoying entries doesn't matter.
> I also have some Barracuda IVs which reported a bunch of spurious Seek
> BadCRC [which clear up after the auto IDE reset] after booting a freshly
> installed 2.4.25 Slackware, despite having booted the same kernel from
> CD-ROM to do the actual install! [Not to mention with a vast number of
> reads/writes to format the fs's and install the packages.] Anyway. I'd
> like to prune some of these, as they just make my log reporting noisy.
These bad CRCs usually come about because of a cabling problem. These
problems can be transient, and are often fixed by replugging the IDE
> I have a funny feeling these can't be removed, right?
I think the only poisslble way to remove the log entries is with a