I was playing a game, alt-tabbing froze my system so I waited a bit and then rebooted by using the button on the case, since I couldn’t do differently.

It now throws an error when mounting a drive: error mounting /dev/sdb1 at /media/user/local disk 1: unknown error when mounting (udisks-error-quark, 0)

This drive doesn’t have anything I was using on it, since it’s a media storage drive. I booted up Windows on my second drive and it can see and access this one without problems. How to fix?

    • bec@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 year ago

      It worked, thanks a lot! What would be the Linux alternative to do that?

      • Atemu@lemmy.ml
        link
        fedilink
        arrow-up
        17
        ·
        1 year ago

        There is none. NTFS is a filesystem you should only use if you need Windows compatibility anyways. Eventhough Linux natively supports it these days, it’s still primarily a windows filesystem.

        • bec@lemmy.mlOP
          link
          fedilink
          English
          arrow-up
          5
          ·
          1 year ago

          Oh, I see. So you’re saying that, when I have the chance, I should move to a different filesysten and that would avoid me issues as the one in the OP?

            • bec@lemmy.mlOP
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              Yes, I’ve basically moved permanently over to Linux and do 99.9% of the things on it. Had to boot Windows for the first time in days only to check whether or not my HDD died after I couldn’t mount it

              I’m still in the process of optimizing stuff around Linux (e.g. media drive filesystem) but I’ll get there haha

              • Atemu@lemmy.ml
                link
                fedilink
                arrow-up
                1
                ·
                1 year ago

                I’m still in the process of optimizing stuff around Linux (e.g. media drive filesystem)

                What do you mean by that?

              • Possibly linux@lemmy.zip
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 year ago

                You could use btrfs on Linux and install the windows driver. The Windows driver isn’t what I would call stable but it will work if your mostly using Windows.

                Another option is a windows virtual machine instead of dual booting. With a VM you could simple transfer files with magic wormhole or something similar

          • db2@sopuli.xyz
            link
            fedilink
            arrow-up
            3
            arrow-down
            1
            ·
            edit-2
            1 year ago

            FAT is older and has fewer features but it’s better supported.

        • bec@lemmy.mlOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Guess I’ll need to keep W10 around haha thanks again

          • allywilson@sopuli.xyz
            link
            fedilink
            arrow-up
            3
            ·
            1 year ago

            Can you reformat that drive as exFAT? That should remove NTFS as being a reason to keep Windoze around (and even if you do need Windoze, it should be able to read that format fine as well).

            • bec@lemmy.mlOP
              link
              fedilink
              English
              arrow-up
              1
              ·
              1 year ago

              Yes, I just learned I can use a different filesystem to avoid (or at least minimize) these issues in future. I tried formatting a portable HDD and I could only pick FAT, that should be OK since I picked “Linux compatibility” or something like that in the format wizard!

      • FalseDiamond
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        If it’s just the dirty flag (it was uncleanly unmounted) you can try

        ntfsfix -d /dev/sdc1

        Still probably better to boot into Windows and let it deal with it (ntfs tools are still reverse engineered stuff after all), and check journalctl before doing it, but it works in a pinch.

      • MimicJar@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        I always preferred BUSIER backwards. It’s shorter and alliterative., but whatever helps you remember.

    • TurboWafflz@lemmy.world
      link
      fedilink
      arrow-up
      8
      ·
      1 year ago

      Annoyingly sysrq is disabled on a lot of distributions by default now, so you often have to manually enable it for this to work

    • bec@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      That’s very useful, I’ll try it next time, thanks for the tip!

    • ElderWendigo
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      I’ve always just dropped down into a different virtual terminal with CTRL+ALT+F#, killed the bad process and/or just rebooted from there. Is that not a thing anymore? I haven’t had to do it in so long because of improved stability and not using the DE on my server much, so maybe I’m out of the loop.