Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deal with Seagate Mixing Other Data with Error Counts #108

Open
psa opened this issue Jan 29, 2023 · 4 comments
Open

Deal with Seagate Mixing Other Data with Error Counts #108

psa opened this issue Jan 29, 2023 · 4 comments

Comments

@psa
Copy link

psa commented Jan 29, 2023

Seagate, in their infinite wisdom, decided to combine reads/access/etc and errors in several stats.

As noted here and here Seagate data needs to have -v 7,raw48:54 added to the call to smartctl in order to properly report errors.

Can smartctl_exporter clean up the data before export?

@psa psa changed the title Deal with Seagate Bad Data Deal with Seagate Mixing Other Data with Error Counts Jan 29, 2023
@NiceGuyIT
Copy link
Member

Hi @psa, this is the same as #26: Non standard device accessors such as -d cciss,N do not work.

@NiceGuyIT
Copy link
Member

Actually, #26 and #89 both deal with -d TYPE, --device=TYPE, not -v ID,FORMAT[:BYTEORDER][,NAME], --vendorattribute=ID,FORMAT mentioned in this issue.

@NiceGuyIT NiceGuyIT reopened this Aug 26, 2023
@NiceGuyIT
Copy link
Member

@psa, to help troubleshoot your request, can you provide the following as attachments?

sudo smartctl --scan --json

For the device in question:

smartctl --json --info --health --attributes --tolerance=verypermissive --nocheck=standby --format=brief --log=error <device>

@psa
Copy link
Author

psa commented Aug 26, 2023

Thank you, here's the scans:
ada3.txt
scan.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants