73
submitted 1 year ago* (last edited 1 year ago) by Harry_h0udini@lemmy.dbzer0.com to c/linux@lemmy.ml

How can I access this without formatting it.

all 25 comments
sorted by: hot top controversial new old
[-] Illecors@lemmy.cafe 31 points 1 year ago* (last edited 1 year 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@lemmy.dbzer0.com 20 points 1 year 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.

[-] Illecors@lemmy.cafe 4 points 1 year ago

This is some very good advice, OP!

[-] fmstrat@lemmy.nowsci.com 4 points 1 year ago

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

[-] pjhenry1216@kbin.social 3 points 1 year ago* (last edited 1 year 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.

[-] JWBananas@startrek.website 7 points 1 year ago

If you follow the link to the original post, it displays correctly. For some reason, Lemmy sends HTML for code blocks. kbin rightly escapes it on their end for security.

https://codeberg.org/Kbin/kbin-core/issues/649

https://codeberg.org/Kbin/kbin-core/issues/724

https://github.com/LemmyNet/lemmy/issues/3648

[-] pjhenry1216@kbin.social 1 points 1 year ago

Thanks for the info. Makes sense.

[-] Illecors@lemmy.cafe 3 points 1 year ago

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

[-] pjhenry1216@kbin.social 1 points 1 year ago* (last edited 1 year 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.

[-] Illecors@lemmy.cafe 4 points 1 year 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@kbin.social 1 points 1 year 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@kbin.social 1 points 1 year 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

[-] orca@orcas.enjoying.yachts 2 points 1 year ago

Code link for anyone that wants it.

[-] storm_koala@beehaw.org 9 points 1 year ago

What file system is in this partition? Can you verify you have the required drivers (eg. for ntfs3)?

[-] Spider89@lemmy.world 6 points 1 year ago
[-] heartlessevil@lemmy.one 5 points 1 year ago

Yeah, start here. Also, there might be useful info in dmesg.

[-] gabriele97@lemmy.g97.top 4 points 1 year ago

Do you still have windows installed?

[-] immibis@social.immibis.com 4 points 1 year ago

@Harry_h0udini @linux please try to explain better. How did you try to access your hard drive? What happened when you tried it?

[-] NeoNachtwaechter@lemmy.world 1 points 1 year ago* (last edited 1 year ago)
[-] skullgiver@popplesburger.hilciferous.nl 1 points 1 year ago* (last edited 9 months ago)

[This comment has been deleted by an automated system]

[-] NeoNachtwaechter@lemmy.world 1 points 1 year ago

UEFI doesn't cause any errors - the problems are usually between the ears...

[-] skullgiver@popplesburger.hilciferous.nl 2 points 1 year ago* (last edited 9 months ago)

[This comment has been deleted by an automated system]

[-] prYsm@lemmy.world 1 points 1 year ago
this post was submitted on 23 Aug 2023
73 points (95.1% liked)

Linux

47345 readers
1196 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS