© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
I am also experiencing this on a few drives. Their regular smartctl -a output passes with a return code of 0, however when run with --xall old errors present in the log cause the test to fail.
In my case, the errors are all related to failed WRITE FPDMA QUEUED commands. These were caused by a faulty backplane, rather than a faulty disk. However, as a result the disk is now persistently marked as failing smartctl tests by MAAS despite smartctl reporting that it has passed every single test after the WRITE FPDMA QUEUED errors as well as a badblocks test.
Personally, it feels wrong to mark the drive as failed in this instance since the fault was caused by other hardware in the past, and the drive has subsequently passed any checks performed against it*.
* checking the log again, I see that i've not performed an extended test at any point, I wonder if I were to perform an extended test and it passed, smartctl would disregard the old entries in the log and return an RC of 0? smartctl's man page does seem to imply that this is the case for bit 7 - "The device self-test log contains records of errors. [ATA only] Failed self-tests outdated by a newer successful extended self-test are ignored.". However, as RC=64 is bit 6 it may not work. I'll try it and report back here...
I've attached a log showing the output of;
1) smartctl -a
2) echo $?
3) smartctl --xall
4) echo $?