actual Antix: how can I get write access to built-in second hard disk?

[Member waldmattis]

Good evening.
I have installed a second hard drive in my laptop instead of the DVD drive with a caddy.
This build in second harddrive is called ARBEITSPLATTE (see second screenshot).

Antix is installed and booted from the first hard drive.
I installed Thunar and hoped I could change the properties of this harddrive.
But did not succeed (see second screenshot)

But when I try to save a file from a program, I get the messageshown in screenshot 1)

How can I permanently organize for programs to access this second hard drive?

Thanks for any tips.

Regards
Karl

• This topic was modified 1 year, 6 months ago by waldmattis.

Attachments:

1. 

   antix_save_error.jpg
   

2. 

   Arbeitsplatte_no_write_access.jpg
   

[Member ModdIt]

Helpful

Up

0

::

Below should work, but is the intent allow all users read write or just you yourself.
Letting all users have full access is a bit iffy security wise.

Open a terminal in fullscreen.
Run lsblk to find out where the partition is mounted in the filesystem.
Run: sudo chown $USER:$USER /path/to/mountpoint.
Replace /path/to/mountpoint with the real one.

[Member waldmattis]

Helpful

Up

0

::

@Moddit
thank you very much for answering so fast.
I followed your advice.
Result please see screenshot.
Harddrive ARBEITSPLATTE is sdb/sdb1 with 465 GB.

I do not know how to find the mounting point for ARBEITSPLATTE
from terminal output.

Can you help?
Regards
Karl

Attachments:

1. 

   lsblk_screenshot.jpg
   

[Member ModdIt]

Helpful

Up

0

::

Hi karl, what is the size of the disk, I am guessing 500GB.Safest is take the disk out of the bay, print save or note
result of lsbk command, reinsert read again, the new disk will appear.

Sometimes I check with Gparted, having a graphical view of disk and its partitions is nice.

[Member Xecure]

Helpful

Up

0

::

Mount the device in thunar and run in terminal
findmnt | grep sdb1
You will see the permissions that were set (be it by /etc/fstab or by whatever Thunar uses, maybe udisks).
That would be a good starting point.

• This reply was modified 1 year, 6 months ago by Xecure.
• This reply was modified 1 year, 6 months ago by Xecure.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member waldmattis]

Helpful

Up

0

::

@Moddit
Thank you for advising again and again.

I now used gparted – see screenshot.
I can read on this hard drive and even copy files from there to my first (boot) hard drive.

But can not write.

HhmmH
Karl

Attachments:

1. 

   screenshot_from_gparted.jpg
   

[Member waldmattis]

Helpful

Up

0

::

@Xecure
I mounted the drive in Thunar and ran in terminal
pmount | grep sdb1

there was no output at all

see screenshot
Thank you.
Regards
Karl

Attachments:

1. 

   pmount-grep-sdb1.jpg
   

[Member marcelocripe]

Helpful

Up

0

::

Hello waldmattis.

I had a similar problem with SpaceFM, I could only record files using SpaceFM root mode.
Can you open Thunar with root mode?

I don’t know how to write in English and I send my texts translated by the internet translator.

marcelocripe
(Original text in Brazilian Portuguese language)

– – – – –

Olá waldmattis.

Eu tive um problema semelhante a este com o SpaceFM, eu só conseguia gravar arquivos utilizando o modo root do SpaceFM.
Você consegue abrir o Thunar com o modo root?

Eu não sei escrever em idioma Inglês e envio os meus textos traduzidos pelo tradutor da internet.

marcelocripe
(Texto original em idioma Português do Brasil)

[Member sybok]

Helpful

Up

0

::

Hi,

if you plan to use the 2nd built-in HDD regularly, you may wish to add a new item to ‘/etc/fstab’.
I am used to do this manually; I admit that there may be a better way of doing it.

1) [Optional] Backup all the data on the disk
2) [Optional] Backup the existing ‘/etc/fstab’ e.g. using
sudo cp /etc/fstab /etc/bckp_fstab.old
3) Identify the HDD using size, e.g. the output of ‘lsblk’
Assume you use /dev/sdb1
4) Run ‘blkid’ to get UUID of the drive, example output:
/dev/sdb1 UUID="6da5a1fc-0cb3-43b3-b14a-53fa250efb12" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="80808080-01"
5) Create a mountpoint
sudo mkdir -p <full-path to the mountpoint>
In principle, you could re-use the ‘/media/Arbeitsplatte’ but I find that problematic if e.g. a USB-disk with same name would be connected.
6) Own it and change group,
sudo chown <username> -R <full-path to the mountpoint> && sudo chgrp <username> -R <full-path to the mountpoint>
6) Edit ‘/etc/fstab/’ by adding the below lines:

#-> /dev/sdb1
UUID=<UUID value> <full-path to the mountpoint> <value of (filesystem) TYPE> auto,exec,users,rw 1 1

7) Run ‘sudo mount -a’ (mounts all records from ‘/etc/fstab’ except for those containing ‘noauto’).

The selected partition on the drive should be always mounted at the <full-path to the mountpoint> with permissions as set ‘/etc/fstab’.
No need to remount after reboot.

• This reply was modified 1 year, 6 months ago by sybok. Reason: Improve code/command emphasizes

[Member ModdIt]

Helpful

Up

0

::

Hi Karl at present the drive is owned by root, the super user, group is also root (according to your info)

Open a terminal.
Run lsblk to find out where the partition is mounted in the filesystem. If we are talking about the 500GB drive
with a single partition it is /dev/sdb

do sudo chown $USER:$USER /path/to/mountpoint. Replace /path/to/mountpoint with the real one.

Which looks like you can translate to sudo chown theo:theo /dev/sdb
That changes owner to theo group to theo If you have files on the drive as it seems you have you will need to
change permissions on those too, to do so you can use the -R or recursive switch.

sudo chown -R theo:theo /dev/sdb

It is well worth doing some reading on linux permissions, lot of info in the internet, just use metager and search chown.
Seems you or a group you are in has read permission, that allows you to open read copy. You want to be able to write
without becoming root.
https://devconnected.com/how-to-chown-recursive-on-linux/ is a pretty good introduction
https://devconnected.com/linux-file-permissions-complete-guide/#b_Using_chown in depth, maybe more than you or I will ever need.

Should work, this is not always the case as other building blocks of linux can and do influence rights. Should we need more I have some
experiments to make but will find time fairly quickly.

OT: I prefer to recommend Metager as first search engine, it is a very open project and not creating huge user profiles. Lot of Linux users
involved. Good meta search engine.
Duck duck go just came from darkness, I do not think it likely more private than alphabet daughter all pervasive googli.

EDIT Good answers from sybok ;_) lot of ways to get things done in linux. I had asked what you want to use the disk for,
he goes in to that regarding naming.

• This reply was modified 1 year, 6 months ago by ModdIt.
• This reply was modified 1 year, 6 months ago by ModdIt.
• This reply was modified 1 year, 6 months ago by ModdIt.

[Member waldmattis]

Helpful

Up

0

::

@Moddit
Thank you for helping again.
Unfortunately sudo chown $USER:$USER /path/to/mountpoint.
Replace /path/to/mountpoint with the real one.
did not help.
I will try sybok’s recipe.

@sybok
Thank you for your advice!

lsblk gives:
/dev/sdb1: LABEL=”Arbeitsplatte” UUID=”4be0acc3-e7a6-4bc7-8b15-b32de01c745a” BLOCK_SIZE=”4096″ TYPE=”ext4″ PARTUUID=”4b824c16-01″

You wrote:
5) Create a mountpoint
sudo mkdir -p <full-path to the mountpoint>

which part of the lsblk-output do I have to put instead of <full-path to the mountpoint> ?

Thank you!
Regards
Karl

[Member ModdIt]

Helpful

Up

0

::

please tell us, what exactly did you enter in the terminal.

Like this ? sudo chown -R theo:theo /dev/sdb assuming username is theo or something else

[Member waldmattis]

Helpful

Up

0

::

@Moddit
I typed into the terminal:

sudo chown theo:theo /dev/sdb
and
sudo chown theo:theo /dev/sdb1

and
sudo chown -R theo:theo /dev/sdb
and
sudo chown -R theo:theo /dev/sdb1

I tried sdb1 in addition, because sdb did not work

[Member ModdIt]

Helpful

Up

0

::

Ok Karl I am learning too, never had exactly the same problem as you before.
Seems my commands work on a file or directory bit not a device, sorry.

If you have not had success using the instruction from sybok please give output of
ls -l /dev/sdb

[Member waldmattis]

Helpful

Up

0

::

@marcelocripe

In the meantime, I have installed MX19.4, 64bit on a trial basis, which also uses Antix basics.

When I open Thunar in MX, I can choose to open certain partitions or folder as root.
Then I can, for example, create new folders or copy files into them.
But I cannot save there from within programmes.

When I open Thunar in Antix, I cannot open partitions, folders etc. as root.

Hmmh.

By the way: the best internet translator is deepl.com
Do you know it?

Regards
Karl

[Author]

Posts