I’m not sure what fixed it because I tried multiple things yesterday, but it shutdown normally last night.

  • jellyfish@beehaw.org
    link
    fedilink
    arrow-up
    6
    ·
    edit-2
    1 year ago

    Personally I’d be worried there’s a transient disk issue. I’d ensure my backups are good and files aren’t being silently corrupted. I assume you’re on an NVME, they tend to fail instantly, but sometimes you’ll get transient file errors beforehand (like not being able to open a system library). Look at something like debsums to start with maybe.

    • vortexal@sopuli.xyzOP
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      I’m not having the issue anymore, I’m not sure what fixed it though as I tried multiple things yesterday.

      Also, I’m not using an NVME, I’m actually just using an old laptop hard drive with one of those hard drive cases that basically converts it into an external hard drive.

      • jellyfish@beehaw.org
        link
        fedilink
        arrow-up
        3
        ·
        edit-2
        1 year ago

        That type of error is usually indicative of hdd issue. I only mentioned NVMEs because they tend to fail all at once, without recovery options. Spining disks usually fail slower (but not always). Take a peek at smart info, maybe run a scan. My guess is the cord got jostled though tbh

        • vortexal@sopuli.xyzOP
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Like I said, I’m not having the issue anymore.

          Also, I tried to check the smart info but the option is gray-out, is there something I need to do before I can check it?