Pumpkin Escobar

u/PumpkinEscobar@lemmy.world
0 posts · 349 comments

Recent posts

No posts.

Recent comments

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]

**

Sorry, I think my reading comprehension was shit there… I got fixated on rescue usb not seeing the disk.

No, I wouldn’t expect it to be a bad port if grub is loading (and the grub partition is on the same disk). Bios not booting at all with disk removed is strange too, I’d expect it to just boot the usb if that were plugged in while disk is not.

You said usb rescue lsblk doesn’t list the disk, guessing it doesn’t show up under /dev/disk/by-id either? lspci? How about with a windows install usb, does it see the disk?

Like others said, sounds like hardware. But before you toss the drive, you said SSD, if it’s an ssd try different cables connecting to different ports. If it’s nvme try reseating it at least, moving it to another port if you have a 2nd. Just saying that sometimes ports and cables fail, so make sure you rule those out before losing hope.

Also possible it’s a bios thing, like maybe the port itself on got disabled in bios or controller got switched to raid mode.

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

I start to wonder if we need something sitting between extra and aur, few more trusted maintainers and well secured update process that’s more than the aur Wild West

Also, some sort of yay hook to do some scanning for suspicious diffs and warning or skipping those packages…

I don’t want / need a system where I can blindly update everything, but something to help me avoid having to visually check every package diff would be nice

I was still using my copilot account, figured I’d see how the new pricing worked. I blew through 60% of my max+ limit in 1 day on absurdly light usage, promptly cancelled rather than upgrade from the $39 / month plan to the $100 /month plan.

I do think there’s a productivity help from AI but vibe coding everything is miserable and gives awful results. Targeted AI usage makes sense and I’ll refine my local AI usage and tooling for that.

It works pretty well for greenfield, that’s where I’ve been using it. A pretty involved monorepo with a decent bit of code and things are still going reasonably well.

Also, leaning on documents as deliverable artifacts for people and for AI awareness / consumption helps me.

Like put together an architecture document for either the entire application or specific parts and subsystems (or multiple documents with different granularity) those can list future considerations.

I pretty often will include those documents when generating proposals / specs to make sure the AI is building in the right direction. It’s not perfect, there are some rough edges and these are the early days of this whole process.

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

Phillip Island is awesome. If you can see the return of the tiny penguins in the evenings, it’s a pretty nice way to spend a chill hour or two as penguins waddle by.