So I had a micro PC that was running one of my core services and it only supports NVMe drives. Unfortunately, this little guy cooked itself and I’m not in a position to replace the drive. The system is still good and is fairly powerful, so I want to be able to reuse it.

I’m thinking I want to set up some kind of netboot appliance on another server to be able to allow me to boot the system without ever having a local disk. One thing I want to is run some docker images (specifically Frigate) but i wont be able to write anything to persistent storage locally. NFS shares are common in my setup.

Is it even possible to make a ‘gold image’ of a docker host and have it netboot? I expect that memory limitations (16GB) will be my main issue, but I’m just trying to think of how to bring this system back into use. I have two NAS appliances that I can use for backend long term storage (where I keep my docker files and non-database files anyway), so it shouldn’t be too difficult to have some kind of easily editable storage solution. I don’t want to use USB drives as persistent storage due to lifespan concerns from using them in production environments.

  • @Jimmycakes
    link
    English
    143 days ago

    Unless you are writing petabytes the nvme did not just burn “wear” out. Probably shouldn’t do anything until you figured out what caused this failure

    • @[email protected]
      link
      fedilink
      English
      22 days ago

      Consumer SSDs generally only have a 200-600TBW rating, not petabytes. Its pretty easy to wear one out in a few years installed in a server.

    • @Passerby6497OP
      link
      English
      2
      edit-2
      2 days ago

      Yeah, I didnt think that was a realistic possibility. Given that it was a bitty fan less nuc style system, I’m leaning more to a heat death as I originally surmised.

      E: though another person suggested a frigate misconfig could have worn the drive out early