• 0 Posts
  • 70 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle



  • It does look like your storage controller got switched to raid mode. Some ai generated slop-fix:

    Your storage controller actually is visible in the lspci output, but it is currently hidden inside a RAID cluster.

    Look closely at this specific line from your list:
    00:17.0 RAID bus controller: Intel Corporation Comet Lake PCH-H RAID

    Why Your Drive Seems Missing

    • Intel RST Active: Your motherboard BIOS is configured to use Intel Rapid Storage Technology (RST) RAID mode.
    • Controller Hiding: When RAID mode is active, the Intel controller intercepts individual NVMe or SATA drives.
    • Linux Limitation: The standard Linux kernel cannot see individual NVMe drives behind this specific Intel RAID controller without configuration.

    How to Fix It

    You need to switch your storage controller from RAID mode to AHCI/NVMe mode.

    1. Reboot your laptop and enter the BIOS setup (usually by pressing F2F12, or Del at startup).
    2. Locate the Storage ConfigurationSATA Mode, or VMD Setup menu.
    3. Change the setting from RAID or Intel RST to AHCI (or disable VMD).
    4. Save and exit. [1]

    **





  • I used to use them, yes. It’s a pretty solid setup, especially like you say, if the tang server itself requires you enter a password to unlock.

    A while ago I moved to tpm and secureboot to auto-unlock my servers on boot. It’s definitely slightly less secure, tpm vulnerabilities or a severe enough vulnerability in one of the network services on the machine and a hacker could get into them. But it’s quite a bit more secure than storing the unlock key on usb, and requires at least some degree of hacking skill to break in.

    sbctl makes the process of signing boot files pretty easy, systems-cryptenroll for setting up tpm auto-unlock










  • Openspec has an “explore” command you can use to give some thoughts and have agent spit out a high level plan, some back and forth, then create the proposal once you’re happy. I’ve also generated markdown documentation for a subsystem or thought so I can check it in, then continue improving that later, then when ready to turn it into a proposal and implement I start by referencing that document.

    It sounds like a big part of what you’re talking about is just pre-feeding future concerns into one proposal for work that you plan to do in the future, also nothing wrong with that. I’ve used “in the future we will need … so design in that direction without implementing in this first iteration” sort of wording.

    And not sure if this applies but I’ve found big monolithic code bases become too large for AI to work well in… enforcing some boundaries by breaking code into technical foundation and vertical slice functional modules really helps decouple code and focus on cross-module boundaries and interfaces, similarly to how they help reduce cognitive load for developers, helps for AI too