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?

  • Something Burger 🍔
    link
    fedilink
    211 year ago

    What filesystem is on the disk? If it’s NTFS, you’ll need to fix it on Windows (right click, Properties, Tools, Check).

      • Atemu
        link
        fedilink
        231 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.

        • @[email protected]OP
          link
          fedilink
          English
          61 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?

          • Atemu
            link
            fedilink
            91 year ago

            If you’re only using this filesystem on Linux anyways, absolutely.

            • @[email protected]OP
              link
              fedilink
              English
              11 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

              • Possibly linux
                link
                fedilink
                English
                21 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

                • Atemu
                  link
                  fedilink
                  11 year ago

                  From what I’ve seen, that’s a great way to corrupt your filesystem.

                • @[email protected]OP
                  link
                  fedilink
                  English
                  01 year ago

                  Nah, all Linux is good. I don’t really need to use Win and since all my HDDs are for media storage I have no reason not to use them on Linux only. They’re only mine and don’t have to hop from PC to PC. Thanks for the input though

              • Atemu
                link
                fedilink
                21 year ago

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

                What do you mean by that?

          • @[email protected]
            link
            fedilink
            41 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).

            • @[email protected]OP
              link
              fedilink
              English
              01 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!

      • @[email protected]
        link
        fedilink
        31 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.