But I should also clarify that my long-running fsck isn't always the result of an unclean shutdown. There's something about my combination of iSCSI+crypttab+NFS that causes fsck to be run too often—even if I shut down the machine cleanly while the NAS is running, it usually decides to fsck when it comes back up.
Something to investigate next winter, perhaps.
Interesting about fsck running for unclear reasons. "What is it up to now?" is a valid question at multiple levels!
Glad you enjoyed it. :-)
> I have considered doing something totally ridiculous like setting up a Raspberry Pi with a camera and machine vision software to watch the LED displays on these devices to glean status information. Silly, but...
Ha! I actually have a PoE camera pointed at the display of my UPS. Here's what it looks like right now: https://toroid.org/misc/ups-display.jpg
Notice that horizontal blank row of dead pixels halfway down the right side of the display? The one that makes "54.6" look like "51.6"? That gap defeated my naïve five-minute attempt to use image recognition to extract the battery voltage.
Depending on how the cabling to that display works, you might be able to do all of that without having to disable the display.
grep '[f]sck'* http://mywiki.wooledge.org/ProcessManagement#But_I.27m_on_so...
M. Wooledge's description of ps options is not quite accurate, but that is incidental to xyr main point.