• sometimes ashley@lemmygrad.ml
    link
    fedilink
    arrow-up
    2
    ·
    2 years ago

    on second thought, it may have been a function of it going to sleep since right after it completed the installation, it booted once, went to sleep, and never came back. the drive isn’t detected anywhere anymore, not in bios, not by nvme list, not by lspci. I went “huh weird” and just popped a spare ssd in, meaning to figure it out later and never remembered to go back to it. that drive is still in here doing nothing lol

    so now that i say all that, it probably is sleep related.

    • Arsen6331 ☭@lemmygrad.ml
      link
      fedilink
      arrow-up
      2
      ·
      2 years ago

      Yeah, if it’s not detected by lspci or BIOS, I’d say it’s most likely dead forever. I’d say that it’s more likely to have been due to a defective drive than sleep. An NVMe drive like that is not easy to brick to that point. It would be either an electrical fault, or corruption of the controller firmware. There really isn’t anything else that would cause that, and I don’t see how sleep would have done it.

      • sometimes ashley@lemmygrad.ml
        link
        fedilink
        arrow-up
        2
        ·
        2 years ago

        Hmm. Interesting. Those drives are very new tech to me (despite not really being that new lol) and idk much about them. Needless to say I’m nervous to try another one