How can I access this without formatting it.

  • Illecors
    link
    fedilink
    English
    30
    edit-2
    10 months ago
    #!/usr/bin/env bash
    
    exec > /tmp/sda-debug.log 2>&1 # The last "word" of this line is 4 chars - two, greater than, ampersand and one
    
    # strict mode
    set -euxo pipefail
    IFS=$'\n\t'
    
    TARGET="/tmp/myprecious"
    
    umount /dev/sda4 || true
    mkdir -p "$TARGET"
    mount /dev/sda4 "$TARGET"
    ls -la "$TARGET" # attempt read
    touch "$TARGET"/testfile # attempt write
    
    rm "$TARGET"/testfile
    umount "$TARGET"
    rmdir "$TARGET"
    
    • Save this to a file somewhere, let’s call it sda-debug.sh
    • Make the script executable: chmod +x sda-debug.sh
    • Run it as root: sudo ./sda-debug.sh
    • Paste the content of /tmp/sda-debug.log here

    EDIT: changed the script to log everything to a file for easier copy-past-ability.

    • Programmer Belch
      link
      fedilink
      English
      2010 months ago

      This script will unmount the problematic drive and try to mount it to another place /tmp/myprecious, a temporary place. Then, as it says, will attempt to read and then write to the drive. Finally, it removes the file it wrote to test writeability, unmounts the drive again and removes the temporary mount place. The scripts needs root access to mount and unmount and possibly to write and read.

      Please don’t run a script you found on the internet with root access without knowing what it does.

    • fmstratA
      link
      English
      410 months ago

      Make this a gist and post a link. Will solve all formatting errors.

    • pjhenry1216
      link
      fedilink
      3
      edit-2
      10 months ago

      I would remove the formatting of the script. For me that would never run as a bash script as it’s filled with markup. Not sure if it shows up nicely for you or not so figured I’d let.you know it may not be displaying for others at least.

      • Illecors
        link
        fedilink
        English
        310 months ago

        Ampersand was escaped in web UI, editted to reflect that. Everything else is displayed fine.

        • pjhenry1216
          link
          fedilink
          1
          edit-2
          10 months ago

          <span>#!/usr/bin/env bash

          \

          Considering the first line is a span block, I don’t think you realize what you see is not necessarily what others see.</span>

          • Illecors
            link
            fedilink
            English
            410 months ago

            I now understand the issue better, but since it’s a request from a lemmy user and the issue appears to be on kbin - I’ll leave it as is.

            • pjhenry1216
              link
              fedilink
              110 months ago

              Makes sense. Though I’ll note I find folks find help via methods of others asking for the same thing so a Kbin user could easily come across this post trying to find an answer to a similar problem. That being said, I don’t have a good suggestion for a workaround so leads me back to “makes sense.”

          • JWBananas
            link
            fedilink
            110 months ago

            Only kbin users are seeing what you see. It looks fine on other Lemmy instances.

            Lemmy and kbin do weird things with code blocks. From the source, the post itself clearly only contained backticks. Lemmy sends out marked-up text. kbin escapes it.

            curl -i -X GET -H 'Accept: application/activity+json' https://lemmy.cafe/comment/1368187

            https://pastebin.com/VT4gmJTJ

    • @jayandp@sh.itjust.works
      link
      fedilink
      310 months ago

      Also, if you’re dual booting, Disable Fast Start in Windows! That’ll prevent drives from being mounted on Linux since Windows never technically “shutsdown” when Fast Boot is enabled.