mountpoint

keesg · 16. August 2012

When I log in to the server with putty, then I find my shares on a location /media/bdd79..........................a#/backup etc.
When I log in to the web administration the shares seem to be in /dev/md127/backup etc.
When I want to make a task or a cron job than I have to refer to /media/bdd79............a# instead of /dev/md127/backup. Is it possible to change (rename) the bdd79.....................a#.
For example I want to make a simple task for renaming a directory on my backup share.

when I make a job with /dev/md127... the answer is "folder does not exist"
When I want to change dir to md127 in putty it also says folder does not exist.

Hopefully a simple answer.

regards

Kees Geerts

votdev · 16. August 2012

/dev/<xxx> = devicefiles
/media/<UUID> = Mount points

E.g. /dev/md127/backup is your RAID device with the label 'backup'. It will be mounted to /media/<xxxxx-xxxx-xxxxx>.

keesg · 16. August 2012

So far I understand. But is it possible to rename that <xxxxx-xxxx-xxxxxx> into something more simpel

biohazard · 16. August 2012

You don't have to type the entire mount point name, just type a * wildcard and you're fine:

# cd /media/bdd79*

votdev · 16. August 2012

Zitat von "keesg"

So far I understand. But is it possible to rename that <xxxxx-xxxx-xxxxxx> into something more simpel

No

capathor · 28. August 2012

create mountpoints (i.e. mkdir /path/to/mount/point)
open /etc/fstab
there is a section (for example)
# >>> [openmediavault]
UUID=xxxxx-xxxx-xxxxxx /media/xxxxx-xxxx-xxxxxx ext4 defaults.....
# <<< [openmediavault]

change the part after the first whitespace to /path/to/mount/point
let the stuff after the second whitespace stay as it is.

For further information google "linux fstab edit"

votdev · 28. August 2012

Be warned, changing internal issues will break other things. The ugly and unhandily mount points have their reasons. But finally you're the admin of your NAS.

capathor · 28. August 2012

I should have warned at that point... I'm sorry. Haven't much more thought about that.

The more I wonder why it is not possible to change the mount point and afterwards links to those via a link named with the UID of that harddisk...

It seems to be a bug, or am I wrong?

I just tried to figure out what happens exactly and find myself creating a link within the mountpoint instead of to the mountpoint at the same tier although the link-command was correct...

*EDIT*
I was wrong, but I didn't try that way anymore. Linking at least works as expected.
*/EDIT*

capathor · 28. August 2012

I just took a look at the /etc/openmediavault/config.xml . I changed the <dir> to the new one (eg. /media/sdb instead /media/fsnamexxx-x-xxx) in the <mntent>-Part and creating a new OpenVPN-CA certificate worked. Before that change I got an err-message that the drive could not be found.

So, is that the only point that needs additional changes to avoid internal issues? Whereelse do plugins take their information about the system from?

Jetzt mitmachen!