• Grass@sh.itjust.works
        link
        fedilink
        arrow-up
        1
        ·
        11 months ago

        Oh man I would do this all the time. When I worked a grocery store it had suse and later they switched to windows. Before if anything didn’t work it was user error like rebooting with personal items left on the keyboard. After we had self checkouts that would bluescreen and other than myself only two people knew how to reboot them. If it had arch I would make sure everyone knew.

        • Apathy Tree@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          11 months ago

          Or orange pi. Banana pi.

          The best thing I learned when writing this comment (because I know there are other fruity labeled pi computers) is that you can look up “other fruit pi” and actually find results. Semi-relevant ones. (I use ecosia, not google/bing/askjeves, so ymmv)

  • RustyNova@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    11 months ago

    Can a linux/systemd nerd explain what the error is? I know it’s a shutdown sequence, but I’m curious on the fault

    • CameronDev@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      11 months ago

      It is actually a boot failure. Normally the kernel reads some config from the initrd (the bootloader loads initrd and passes it to the kernel - thanks dan) and then does a bunch of setup stuff, and then it mounts the actual root filesystem, and then switches to using that. In this case, the root filesystem has failed to mount.

      Hardware failure is most likely the cause, but misconfiguration can also make this happen. Probably hardware though.

      If its misconfiguration, an admin can reattempt to mount the root drive on /new_root, and then ctrl-d to get the init system to try again

      ELI5: couldnt open C:/ drive

      Edit: clarified what loads the initrd - as per dans comment.