36 replies to this topic

[Pike_Bishop]

ok thanks - it's no longer importand for me, because with fstab it works - that's good enogh for me.

 

regards

Biki3

[WanWizard]

That means we will never find out what the cause of your problems was, which is a shame. Because if it is a bug somewhere, it needs to be fixed.

[Pike_Bishop]

ok - then we find it out if it's possible, but for that i need your help.

what shall i do or what can i do now to find out what's the problem ?

 

regards

Biki3

[WanWizard]

Start by using the xml I posted in #20.

 

I just put that in the automounts.xml in ET10K, changed the IP address and credentials to match my NAS, restarted Enigma to have it read the new automounts.xml, and it mounts fine.

root@et10000:~# ls -l /media/net/
drwxrwxrwx    4 root     root             0 Oct 11 14:47 MiniDLNAMEDIENFRITZBOX_7390

(although I would use a shorter mount point name )

[Pike_Bishop]

hi WanWizard,

 

i have testet now your settings from post #20, but it didn't work.

 

 one.jpg   61.58KB   1 downloads

 

 two.jpg   79.37KB   1 downloads

 

if i mount it with fstab also then in picture two i have instead of the icon with the red cross a green icon.

same as you can see by the other two mounts (cifs and nfs)

 

 

 

regards

Biki3

Edited by Biki3, 27 November 2015 - 20:35.

[WanWizard]

I can't explain it, there isn't anything different in it compared to your fstab entry.

 

Your log should list any errors, did you ever try a "dmesg" directly after an enigma startup, or after a remount, to see if you have any errors?

[Pike_Bishop]

 

I can't explain it, there isn't anything different in it compared to your fstab entry.

 

yes i know - it's curious.

 

i will make a dmesg  after e2 startup directly in the next days and look if i see an error in it.

 

 

regards

Biki3

[blzr]

and what happens if you try with blank user/password?

[Pike_Bishop]

hi blzr,

 

that also doesn't  work.

 

regards

Biki3

Edited by Biki3, 28 November 2015 - 21:42.

[Pike_Bishop]

hi WanWizard,

 

i have two logs one with name dmesg.txt and a second log with name debug.log

in the dmesg.txt i found no errors, but in the debug.log i see in

line 231 that;

[AutoMount.py] U/MOUNTCMD---> mount -t cifs -o rw,utf8,noatime,noserverino,iocharset=utf8,username=guest,password= '//192.168.178.1/MiniDLNA-MEDIEN' '/media/net/MiniDLNAMEDIENFRITZBOX_7390'
[ePopen] command: mount -t cifs -o rw,utf8,noatime,noserverino,iocharset=utf8,username=guest,password= '//192.168.178.1/MiniDLNA-MEDIEN' '/media/net/MiniDLNAMEDIENFRITZBOX_7390'

and in line 324 this;

[AutoMount.py] CheckMountPointFinished unc name specified twice, ignoring second
mount error(22): Invalid argument
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
mount: mounting //192.168.178.1/MiniDLNA-MEDIEN on /media/net/MiniDLNAMEDIENFRITZBOX_7390 failed: Invalid argument
32
[AutoMount.py] CheckMountPointFinished None None
[AutoMount.py] CheckMountPointFinished None None

so this is an error, but i didn't understand how can i fix it.

 

 

regards

Biki3

Attached Files

•  dmesg.txt   9.15KB   1 downloads
•  debug.log   39.73KB   1 downloads

Edited by Biki3, 29 November 2015 - 15:22.

[WanWizard]

You seem to keep on adding the "utf8" option back in there. It is a non-supported option, and this is why the mount fails.

[Pike_Bishop]

but i have testet it also in automount.xml only with "rw" and without "utf8"

and it didn't works also - but i will test it again only with "rw".

 

and why it works in fstab with "utf8" ?

 

 

regards

Biki3

[WanWizard]

Maybe it's ignored, or fstab is parsed a different way before it's contents is passed on to mount. Maybe someone with more OE experience can comment on this.

 

All I can say is that when I try to create the mount on the commandline (with "mount -t cifs"), I have to remove the "utf8" from the automount.py output, after which it mounts without problems.

 

You have to remember that the STB runs busybox, and most commands are stripped-down versions of their desktop linux counterpart, to save space. So not everything that works in "regular" linux works on the box.

[Robinson]

i have two logs one with name dmesg.txt and a second log with name debug.log

[AutoMount.py] U/MOUNTCMD---> mount -t cifs -o rw,utf8,noatime,noserverino,iocharset=utf8,username=guest,password= '//192.168.178.1/MiniDLNA-MEDIEN' '/media/net/MiniDLNAMEDIENFRITZBOX_7390'
[ePopen] command: mount -t cifs -o rw,utf8,noatime,noserverino,iocharset=utf8,username=guest,pa

regards

Biki3

 

How to get debug.log, please?

[Pike_Bishop]

hi,

 

@WanWizard,

ok thanks for the infos - as i said i will test it again only with "rw".

 

@Robinson,

when the box is running in telnet with command;

init4 (that stops enigma2)

then wait a little bit (5 seconds) and then with command;

enigma2 > /tmp/debug.log 2>&1 you can make the logfile.

with ctrl+c you can stop that

and with init 3 you start enigma2

then you have on your box in /tmp the debug.log

 

regards

Biki3

Edited by Biki3, 29 November 2015 - 23:18.

[WanWizard]

For reference, this is the command I used

mkdir /media/net/test
mount -t cifs //172.16.1.31/test-share /media/net/test  -o rw,noatime,noserverino,iocharset=utf8,username=openpli,password=xxxxx

[Robinson]

when the box is running in telnet with command;

init4 (that stops enigma2)

then wait a little bit (5 seconds) and then with command;

enigma2 > /tmp/debug.log 2>&1 you can make the logfile.

with ctrl+c you can stop that

and with init 3 you start enigma2

then you have on your box in /tmp the debug.log

Thanks, Biki3.