32 replies to this topic

[twol]

 

"You don't need to create it yourself, it is automatically created when the automounter runs."
 

That is the problem, not created and therefore cannot mount there.
 

Interestingly, in a PURE2 system, this happens without error.

Also mount windows shares immediately and use curftpfs (in fstab) to mount the remote FTP server automatically.

However, Openpli is not. Only manual, in terminal can mount.

Openatv is the same.

So not the windows sharing is faulty.

 

Have you looked to see if the appropriate drivers are actually downloaded?? In OpenATV, its likely because of the desire to support older boxes that NFS and other file access methods need to be installed, they are not all installed by default.

[WanWizard]

No problem with Windows mounts here, and no other people reporting this problem, so for now the problem is at your end.

 

So what have you done or changed to get

[AutoMount.py] Failed to create /media/net/nas Error: [Errno 13] Permission denied: '/media/net/nas'

everything on the box runs as root, so there is no logical reason to get a permission denied, other than something in /media that isn't standard.

[Kenderice]

Unfortunately, this solution doesn't work either.

After a few hours, the STB crashes when I try to browse the mounted directory.

Works after restarting.

 

I found a script for curlftpfs.

I put this in the / usr/script directory, name: mountftpfs.sh .

I gave him the right to run

 

I assigned it to the LONG RED hotkey.

 

Unfortunately, it doesn't start.

It shows the shellscript screen but does nothing:
Running the command from a terminal is mounted by curftps, But not from the shell script.

Is the script faulty?

 

This is the script:

#!/bin/sh
#
# Run-level Startup script for curlftpfs
#
# chkconfig: 345 91 19
# description: Startup/Shutdown the curlftpfs

# FTP user, password, and host (you can specify the port also eg. ftp.example.com:2002)
ftpUser=nas
ftpPass=123456
ftpHost=192.168.0.103

# Mounted to folder
mPath="/media/ftp"

# Create the mounted to dir if doesn't exist
if [ ! -d $mPath ]; then
    mkdir -p $mPath
fi

case "$1" in
    start)
        curlftpfs $ftpHost $mPath -o user=$ftpUser:$ftpPass,allow_other
        ;;
    stop)
        fusermount -u $mPath        
        ;;
    reload|restart)
        $0 stop
        $0 start
        ;;
    *)
        echo "Usage: $0 start|stop|restart|reload"
        exit 1
esac
exit 0

 

[WanWizard]

How can an STB crash on a mount? Either it responds, or it doesn't (and then you get an error message after a timeout).

 

Are you trying to mount a PC or something, that reboots often, and perhaps even via wireless? mounts (cifs and nfs) are made for servers, which are expected to be on all the time...

[Kenderice]

"How can an STB crash on a mount?"

I do not know.

It doesn't answer, I only see the "busy signal" for a long time.

It must be restarted.

 

The server is a notebook with Windows10. Always run.

 

The question is to issue the "curlftpfs 192.168.0.103 / media / ftp / -o user = nas: 123456" command from terminal, can mount the FTP directory.

 

Write to FSTAB or from a script (automatically) not mount.

 

I am looking for an answer to this ...

 

[WanWizard]

If by "busy signal" you mean the rotating spinner, that means it can't be connected to, and it is waiting for a timeout.

 

The problem is on the Windows side, not the box side. Power saving mode active on the network interface perhaps? Windows firewall blocking the connection?

 

You should fix your problem, instead of constantly trying to work around if with even worse solutions... But hey, it's your time you're wasting...

[Kenderice]

If by "busy signal" you mean the rotating spinner, that means it can't be connected to, and it is waiting for a timeout.

 

The problem is on the Windows side, not the box side. Power saving mode active on the network interface perhaps? Windows firewall blocking the connection?

 

You should fix your problem, instead of constantly trying to work around if with even worse solutions... But hey, it's your time you're wasting...

If this were true, the command issued in the terminal would not mount the FTP share either.

But it works.

Is there no error in the script?

I'm looking for the answer.

 

Why this terminal command works:

"curlftpfs 192.168.0.103 / media / ftp / -o user = nas: 123456"

 

 

Why doesn't this work (in FSTAB):

"curlftpfs # nas: 123456 @ ftp: //192.168.0.103/ / media / ftp fuse auto, user, uid = 1000, allow_other, _netdev 0 0"

 

And why doesn't the script work too?

 

If windows were faulty, the terminal command would not work either ...

[WanWizard]

I am not talking about FTP, we do not support FTP in the GUI. I was talking about CIFS.

[Kenderice]

Because the CIFS sharing instable, I returned to an FTP-based connection.

CIFS is no longer relevant to me.

I'm trying to solve now why curlftpfs doesn't want to start automatically from FSTAB or shellscript.

Why does it only work properly when issuing a terminal command ...

[Pr2]

But if your CIFS is instable why the FTP should be stable?

Everything seems to indicate that you have network or server issues.

[Kenderice]

But if your CIFS is instable why the FTP should be stable?

Everything seems to indicate that you have network or server issues.

I think so.

So I eliminated the windows PC and set up a Raspberry pi2 with Open Media Vault and an external HDD.

 

This is handled properly by openpli.

[littlesat]

Box connected via (intermittent) Wi-Fi or PowerLan?

Edited by littlesat, 17 April 2021 - 09:34.

[Kenderice]

Box connected via (intermittent) Wi-Fi or PowerLan?

Via LAN cable.
I think, the windows sharing was instable.
The FTP server buildt with Filezilla, it was fast.