• 1 Post
  • 61 Comments
Joined 3 years ago
cake
Cake day: August 6th, 2023

help-circle








  • since im not sure where in the boot process linux recognizes my raid and when the decryption happens

    Usually raid and decryption happen in the initram. This is because these are too complex to sit purely in the kernel, requiring userspace tools like cryptsetup, but you want to be able to boot off of them so they have to be handled before the disk is mounted.

    Usually that initram is dracut. Why dracut only partially completes the process here, likely figuring out the raid but not decryption, is anyones guess. In my experience dracut is quite hard to debug and configure.

    The simplest approach is probably to just eat it and write a startup service that does it. Basically a startup command. No need to worry about timing, as when the initram finishes the raid should already be up.
    There might be a prebuilt systemd service for it too iirc…

    If you really wanns go for it, there are other initram systems like ugrd, which are easier to configure and might figure your setup out properly. But you’ll probably have to manually install and update them. That would definitely be a very involved approach.


    There are some guesses I made here on your boot timeline. If you show your dmesg I can confirm if the raid really comes up at initramfs time. But it should be s solid bet.











  • Maybe. It’s been a while so I don’t know 100% this was put to the test, but I wanna say the system has a weird kernel which leads to it not swapping out tmpfs properly.

    But ordinarily you should be right, this would simply ruin the stats visually until something forced it to swap out, since konsole shouldn’t be accessing it.


  • There was a dedicated person on call, but it happened to be when they were away.
    The Konsole was left running from a local access, with a while true loop of a service status command. When that service was stopped later, the while loop started rerunning the script every second, filling the buffer with error messages.
    The tab was then killed remotely, but the Konsole window left running. Process ram usage went down but the file remained on tmpfs, which is not counted as ram usage so wasn’t noticed.
    Then it took some time to notice the ram usage mismatch so noone thought of that konsole incident.