5 ms·
>In memtesting we boot a custom MemTest86 image and monitor it while it completes a full pass. Our custom version of MemTest86 changes the color of the failure
by sandGorgon 9y ago
>In memtesting we boot a custom MemTest86 image and monitor it while it completes a full pass. Our custom version of MemTest86 changes the color of the failure message to red which allows us to detect trouble. We’ve hacked together a Ruby script that retrieves a console screenshot via IPMI and checks the color in the image to determine if we’ve hit a failure or not.
Wow. Why is this done this way? Is there no other way to receive hardware memtest info? I would have thought that there was some way to revive machine serial output status in a datacenter.
- hueving 9y agoYeah, this seems pretty terrible compared to a modified memtrest that reports results.
- dom0 9y agoOver network? Needs a networking stack in memtest. Over serial? Physical serial is rare. SOL would work, but since it is connection-based you can't poll it. This seems like a simple and reliable method to me.
- sschueller 9y agoSince they take a screenshot of the console they could output a qr code and read that.
- fapjacks 9y agoThat's sort of what they're doing. It's just a two-bit QR code: Red, and Not Red.
- gumoro 9y agoSo, one bit ;)
- fapjacks 9y agoHah! Yes, totally. Haha I wonder why I said that?
- BraveNewCurency 9y agoThere is also a "not decided yet" state. Hence, you were right, it needs two bits. :)
- dom0 9y agoPatching the font colours are probably a few lines of diff, adding a QR code to a text-mode display... way more complicated.
- RX14 9y agoBecause its a couple line patch to memtest and a short ruby script. It obviously works well, why bother over engineering it?