Linux

48220 readers

648 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

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

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

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

No permissions - Did I bonk my LUKS encryption? (lemmy.ml)

submitted 1 month ago* (last edited 1 month ago) by drid@lemmy.ml to c/linux@lemmy.ml

21 comments fedilink hide all child comments

Hello Linux Helpdesk. ;)

I use Fedora (currently 40), and have done for a while.

I always LUKS+Ext4 encrypt my local drive and decided to do the same to my external hard drive.

Last week I reinstalled Fedora 40 from a Bootable USB, but when I tried to access my files om my external drive it now gives me the error

You do not have permission to view the content of "Files".

I've read online it's due to me no longer being the "Owner" of the drive I was in my previous install of Fedora and now I'm a different user and apparently no users a part from Owner have any permissions on an EXT4+LUKS drive.

Is there any way to give myself permission to see the content again or did I bonk my backup? As a note, I DO have the correct Luks password, it shows me the name of the encrypted disk after decrypting, which is "Files"

Thank you in advance.

Edit: Thank you everybody, thanks to you I've been able to rescue my files. Y'all deserve a great day!

you are viewing a single comment's thread
view the rest of the comments

[–] wildbus8979@sh.itjust.works 3 points 1 month ago* (last edited 1 month ago) (2 children)

sudo chown -R youruser:youruser /path/to/mountpoint

Will make all the files in the path owned by you. Be careful if you have more complex permissions on there they will be lost.

[–] FigMcLargeHuge@sh.itjust.works 1 points 1 month ago

Will make all the files in the path owned by you. Be careful if you have more complex permissions on there they will be lost.

This is where ACL permissions would help. He could give his new id ACL permissions to the files and that wouldn't mess with the current permissions.

From the root/beginning subdir: sudo setfacl -R -m u:{replace with your new id}:rwx .

[–] drid@lemmy.ml 1 points 1 month ago (2 children)

Will try tomorrow when I get up.

Would /dev/sda suffice as mounting point or?

Haven't set any permissions outside standard given ones by usage.

Thanks for answering.

[–] mlfh@lemmy.ml 2 points 1 month ago

/dev/sda is the whole raw disk - you typically don't want to directly interact with /dev/sda, unless you are partitioning or overwriting it. There are a few layers between that device and the files:

raw disk - /dev/sda
disk partition - /dev/sda1
luks container - when unlocked, mapped to /dev/mapper/{name}
ext4 filesystem inside the luks container, mounted somewhere like /mnt, /media, etc

You'll need to find where that ext4 filesystem is mounted, and run the chown command on that. You can run lsblkand see a tree of the above hierarchy, with the ext4 filesystem's mountpount shown in the right-hand column.

[–] wildbus8979@sh.itjust.works 1 points 1 month ago

You need the mount point not the device. Probably something like /media/Files