Unable to access the harddisk after the installation of Ubuntu.

prYsm, 10 months ago

dusshy

skullgiver, 10 months ago (edited 7 months ago)

deleted_by_author

jayandp, 10 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.

storm_koala, 10 months ago

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

NeoNachtwaechter, 10 months ago

Maybe just the ‘standard’ UEFI boot trouble, see:

askubuntu.com/…/does-ubuntu-22-04-require-a-uefi-…

skullgiver, 10 months ago (edited 7 months ago)

deleted_by_author

NeoNachtwaechter, 10 months ago

UEFI doesn’t cause any errors - the problems are usually between the ears…

Illecors, 10 months ago (edited 10 months ago)

<span style="color:#323232;">#!/usr/bin/env bash
</span><span style="color:#323232;">
</span><span style="color:#323232;">exec > /tmp/sda-debug.log 2>&amp;1 # The last "word" of this line is 4 chars - two, greater than, ampersand and one
</span><span style="color:#323232;">
</span><span style="color:#323232;"># strict mode
</span><span style="color:#323232;">set -euxo pipefail
</span><span style="color:#323232;">IFS=$'nt'
</span><span style="color:#323232;">
</span><span style="color:#323232;">TARGET="/tmp/myprecious"
</span><span style="color:#323232;">
</span><span style="color:#323232;">umount /dev/sda4 || true
</span><span style="color:#323232;">mkdir -p "$TARGET"
</span><span style="color:#323232;">mount /dev/sda4 "$TARGET"
</span><span style="color:#323232;">ls -la "$TARGET" # attempt read
</span><span style="color:#323232;">touch "$TARGET"/testfile # attempt write
</span><span style="color:#323232;">
</span><span style="color:#323232;">rm "$TARGET"/testfile
</span><span style="color:#323232;">umount "$TARGET"
</span><span style="color:#323232;">rmdir "$TARGET"
</span>

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

pjhenry1216, 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, 10 months ago

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

pjhenry1216, 10 months ago

<span style="color:#323232;">#!/usr/bin/env bash

</span>

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

Illecors, 10 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, 10 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, 10 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

JWBananas, 10 months 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.

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

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

github.com/LemmyNet/lemmy/issues/3648

pjhenry1216, 10 months ago

Thanks for the info. Makes sense.

fmstrat, 10 months ago

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

orca, 10 months ago

Code link for anyone that wants it.

programmer_belch, 10 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.

Illecors, 10 months ago

This is some very good advice, OP!

gabriele97, 10 months ago

Do you still have windows installed?

Spider89, 10 months ago

fsck?

heartlessevil, 10 months ago

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