this post was submitted on 23 Aug 2023
75 points (95.2% liked)

Linux

47344 readers
1361 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
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
75
Unable to access the harddisk after the installation of Ubuntu. (lemmy.dbzer0.com)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
20 comments fedilink hide all child comments
 

How can I access this without formatting it.

all 23 comments
sorted by: hot top controversial new old
[–] [email protected] 28 points 1 year ago* (last edited 1 year ago) (4 children) 
#!/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.

[–] [email protected] 20 points 1 year ago (1 children)

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.

[–] [email protected] 4 points 1 year ago

This is some very good advice, OP!

[–] [email protected] 4 points 1 year ago

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

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (2 children)

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.

[–] [email protected] 7 points 1 year ago (1 children)

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

[–] [email protected] 1 points 1 year ago

Thanks for the info. Makes sense.

[–] [email protected] 2 points 1 year ago (1 children)

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

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

<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.

[–] [email protected] 4 points 1 year ago (1 children)

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.

[–] [email protected] 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."

[–] [email protected] 2 points 1 year ago

Code link for anyone that wants it.

[–] Spider89 6 points 1 year ago (1 children)

fsck?

[–] [email protected] 5 points 1 year ago

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

[–] [email protected] 4 points 1 year ago

Do you still have windows installed?

[–] [email protected] 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?

[–] prYsm 1 points 1 year ago

dusshy

[–] NeoNachtwaechter 1 points 1 year ago* (last edited 1 year ago) (1 children)

Maybe just the 'standard' UEFI boot trouble, see:

https://askubuntu.com/questions/1406886/does-ubuntu-22-04-require-a-uefi-instead-of-a-bios