Long time reader. First time poster.
So I'm hoping someone can help explain something I find a bit confusing.
Based on threads read here, SAS drives don't show extended SMART attributes even though each device claims to be SMART capable.
Someone here hypothesized it was due to SCSI & ATA protocol differences which might be true. Need to RTFM on that...
Anyway if you can't report extended attributes...
What's the point of running any SMART tests on a SAS drive?
Further, how do you know you can actually trust what's been reported if unable to inspect?
Bonus points to anyone that has a pre-built parallel background test script. I mean sure could launch a bunch of tmux sessions but nicer to have something already automated. Seen a few half working or non-functional ones due to dependencies (bht & disk-burnin come to mind). Trying to not reinvent the wheel.
So I'm hoping someone can help explain something I find a bit confusing.
Based on threads read here, SAS drives don't show extended SMART attributes even though each device claims to be SMART capable.
Someone here hypothesized it was due to SCSI & ATA protocol differences which might be true. Need to RTFM on that...
Anyway if you can't report extended attributes...
What's the point of running any SMART tests on a SAS drive?
Further, how do you know you can actually trust what's been reported if unable to inspect?
Bonus points to anyone that has a pre-built parallel background test script. I mean sure could launch a bunch of tmux sessions but nicer to have something already automated. Seen a few half working or non-functional ones due to dependencies (bht & disk-burnin come to mind). Trying to not reinvent the wheel.