Closed sempervictus closed 2 years ago
Interesting, happens with DAS systems too, with many more false positives (i think they're echoes of real devices somehow):
My initial thought is that those are things like a /dev/bus/0
RAID controller where some indexed drives are behind.
If you look in the details for all those 0 components, can you confirm that the Device Path is the same/similar?
Hoping this just how issue #4 is manifesting.
I have almost no RAID hardware in my targets, pretty much all HBAs here. :-\
Unfortunately removing the errant entries doesnt fly - they come back.
Pull the latest, remodel, and see if anything's better.
Your smartctl examples have been really helpful since I don't have any SCSI/SAS gear around. Also, a friend has sent me a bunch of output from his various servers with SAS and NVMe that I'll be looking over.
Confirm, the 0
devices seem to stay down now. Cleaning up as i go, will watch for their return.
Good to hear, I'll keep an eye out for an update.
megaraid devices now coming up in LUN mode on a host - excellent. BTW, the SMART status and health columns are empty all over.
Hm, I would've thought status & health test indicators would've been fixed after e5f8bf305034d8e1c8d28808fe6a3c0dc45cf6de or ced07e346fb85123bbde0e600f660b767fd74e20 . Are the indicators gray?
Could you post smartctl --info --health --quietmode=noserial
from a device whose status and health columns are empty?
This has been working for a few revisions now - closing as "fixed"
Not sure what to make of this one:
All of the detected drives are correct, all of the
0
one have no equivalent in the system.