24 replies to this topic

[Bastelbox]

Hi,

 

yesterday I bought a VU+ Zero.

 

It's the second VU+ for me. My first one is a VU+ Solo2 that has no HDD inside. Instead of this the VU+ Solo2 is connected by CIFS to a Synology NAS. To let this work I configured automounts.xml in /etc/enigma2 and created folders in /media/net. Works without any issues for two years now.

 

Now I try to do the same thing on the tiny Zero: Created a user "vuzero" with read/write permissions to the stream folder, where the TV recordings are strored. The installation was successful and I could watch all films in "stream". But after a reboot the folders in media/net were gone. Nothing threre.

 

So I created the same folders again. but after a reboot they are deleted. I created the folders with root permissions with a ftp-client and in a terminal. It made no difference, all shared folders are away.

 

Do you have an idea, why this happens?

 

Thanks and regards

 

Bastelbox

[MiLo]

/media is in RAM, hence volatile, which means it will not survive a reboot.

Either use enigma2 to mount, or use /etc/fstab to create the mounts. Both will automatically create folders as needed.

Otherwise, you'll have to create a "volatile" package to pre-populate the /media/ RAM filesystem.

[Bastelbox]

/media is in RAM, hence volatile, which means it will not survive a reboot.

Either use enigma2 to mount, or use /etc/fstab to create the mounts. Both will automatically create folders as needed.

Otherwise, you'll have to create a "volatile" package to pre-populate the /media/ RAM filesystem.

 

Ok, I understand. Is this different to the VU+ Solo2? Because it works there without any issues.

 

To which folder should the entry in the fstab link, if /media is part of the RAM? For example: Right now the fstab looks like this:

rootfs               /                    auto       defaults              1  1
proc                 /proc                proc       defaults              0  0
devpts               /dev/pts             devpts     mode=0620,gid=5       0  0
usbdevfs             /proc/bus/usb        usbdevfs   noauto                0  0
tmpfs                /var/volatile        tmpfs      defaults              0  0
#CIFS stream
//[LAN_IP_OF_SYNO]/stream etc/NASstream cifs username=[USER-ID_ON_SYNO],password=[PASSWD_ON_SYNO],sec=ntlmv2,iocharset=utf8,noperm,auto 0 0

 

But this doesn't work (the Syno fits with ntlmv2).

 

Regards

 

Bastelbox

[WanWizard]

As MiLo said, the folder will be automatically created.

 

My boxes have several mounts in fstab, to different folders in /media, and these folders are all created on the fly without problems.

 

Perhaps it has something to do with the fact that you don't use folders in /media, but in /media/net? Perhaps those aren't properly detected? Or creation fails because /media/net doesn't exist either?

[Bastelbox]

As MiLo said, the folder will be automatically created.

 

My boxes have several mounts in fstab, to different folders in /media, and these folders are all created on the fly without problems.

 

Perhaps it has something to do with the fact that you don't use folders in /media, but in /media/net? Perhaps those aren't properly detected? Or creation fails because /media/net doesn't exist either?

 

Yes, I guess, that's the problem. Something's destroyed in the Vu+ Zero system. There is no /media/net anymore and I don't find a way to recreate it. So i will flash again and will have a look, if it will work better.

[WanWizard]

There hasn't been a /media/net for a very long time, what software version is your box running?

 

As MiLo said, /media is dynamically created in tmpfs (in memory), so NOTHING exists anymore, everything is created on the fly whenever it is referenced in fstab or automount.xml.

 

The point I'm trying to make is that perhaps the "on the fly" creation fails because /media/net needs to be created before you can create /media/net/mountpoint, and I can imagine that the logic that does this on-the-fly creation does not take care of recursive folder creation.

 

So I suggest you  use a mountpoint in /media for the time being, while MiLo confirms or denies my assumption.

[Bastelbox]

So, finally I flashed a new image (nightly build from tonight), and it seems to work now with the automount.xml. Dunno what went wrong with the previous installation...

 

I'm sorry, but my english is not really good. Did I understand you right, when I say:

 

- it's not necessary to create the share folders in /media anymore ?

 

- 'cause they will be build up on-the-fly after every boot ?

 

- e.g. the share should be named /media/net/NASstream -> so I don't have to create neither /media/net nor /media/net/NASstream. The only requirement is to set the entry /media/net/NASstream in the /media/net/NASstream or in /etc/fstab ?

 

Regards

 

Bastelbox

[WanWizard]

I am not sure it will automatically create /media/netNASstream, I am very sure it will create /media/NASstream.

 

Other than that, you are correct, you have understood it fine.

[Bastelbox]

Ok, switched on the VU+ Zero today and the network shares are missing again. 

 

But now I'm one step further. When I press "connect again" (german: erneut verbinden) in the Mountmanager the shares are back and everything's fine. But it doesn't work automatically.

 

Here's the automounts.xml:

 

<?xml version="1.0" ?>

<mountmanager>

<cifs>

 <mount>

  <active>True</active>

  <hdd_replacement>False</hdd_replacement>

  <ip>XXX.XXX.XXX.XXX</ip>

  <sharename>NASstream</sharename>

  <sharedir>stream</sharedir>

  <options>rw</options>

  <username>[USER]</username>

  <password>[PASS]</password>

 </mount>

</cifs>

<cifs>

 <mount>

  <active>True</active>

  <hdd_replacement>False</hdd_replacement>

  <ip>XXX.XXX.XXX.XXX</ip>

  <sharename>NASmusic</sharename>

  <sharedir>music</sharedir>

  <options>ro</options>

  <username>[USER]</username>

  <password>[PASS]</password>

 </mount>

</cifs>

<cifs>

 <mount>

  <active>True</active>

  <hdd_replacement>False</hdd_replacement>

  <ip>XXX.XXX.XXX.XXX</ip>

  <sharename>NASbilder</sharename>

  <sharedir>bilder</sharedir>

  <options>ro</options>

  <username>[USER]</username>

  <password>[PASS]</password>

 </mount>

</cifs>

</mountmanager>

 

The automatically "on-the-fly" built folders are /media/net/NASstream, /media/net/NASbilder und /media/net/NASmusic.

 

However: I have the same automounts.xml for the VU+ Solo2 (only differences are username and password of course) and works since nearly two years now without any issues. And I never had to reconnect the shares manually. Maybe that's an issue in the Zero's image?

 

Thanks and regards

 

Bastelbox

[WanWizard]

You can try to add "sec=ntlm" to the options, for some combinations this is required due to changes in the samba version used.

[Bastelbox]

Thanks, but I'm not sure if this will fix it (read this - incl your posts- also here: http://forums.openpl...e-doesnt-mount/). Because both boxes have exactly the same kernel version and built date. And it works without any issues on the solo2. 

Today I read the log in /var/log, but there no entries that point on the mounts.

 

I still think about, that it could be a network issue. Maybe the VU+ Zero wants to connect to the NAS-folders, but there isn't any network connection yet.

 

Here are the Infos from the WebIF of the Solo2:

 

VU+ Solo2

 

OE-System: PLi-OE

Distribution: openpli

Firmware-Version: 4.0

Treiberversion: 3.13.5+20150109-r0.0

Kernelversion: 3.13.5

GUI-Version: 2015-01-18

 

DHCP: True

IP-Adresse: XXX.XXX.XXX.12/24

Subnetzmaske: 255.255.255.0

Gateway: XXX.XXX.XXX.1

MAC-Adresse: XX:XX:XX:XX:XX:79

 

 

And here from the VU+ Zero:

 

VU+ Zero

 

OE-System: PLi-OE

Distribution: openpli

Firmware-Version: 4.0

Treiberversion: 3.13.5+20150109-r0.0

Kernelversion: 3.13.5

GUI-Version: 2015-01-18

 

DHCP: True

IP-Adresse: 0.0.0.0/0

Subnetzmaske: 0.0.0.0

Gateway: 0.0.0.0

MAC-Adresse: XX:XX:XX:XX:XX:2b

 

So, this is strange. The WebIF shows that VU+ Zero has no proper network connection: no IP-adress and no Subnet-mask. But in fact: it has:

 

root@vuzero:~# ifconfig

eth0      Link encap:Ethernet  HWaddr XX:XX:XX:XX:XX:2b 

          inet addr:XXX.XXX.XXX.9  Bcast:XXX.XXX.XXX.255  Mask:255.255.255.0

 

- Is there a way to get a full boot.log (the file in /var/log is a 0 bit file)?

 

- Does anyone has the VU+ Zero and a CIFS connection to a NAS and similar behaviour?

 

Thanks and regards

 

Bastelbox

[WanWizard]

There are several reports of problems with the network interface of the Zero. Perhaps you have that problem too?

[The_Raven]

Sorry for "hijacking" this thread, but is it possible to remount the shares of network manager (automounts.xml) from console?

I have written a small script to power up my NAS from VU+ and like to mount the shares when the NAS is up.

[WanWizard]

Afaik this code is part of Enigma, so you'll need to restart Enigma for this (using init 4 / init 3).

[MiLo]

There's a "remount" option in the network menu which will attempt to mount everything again.

[The_Raven]

Yes i know, but i like to do it in the script so i need command line. I think i do it with a "work a round" (create the folders and do a normal mount command)

Thx for the answers WanWizard & MiLo.

Edited by The_Raven, 12 February 2015 - 13:36.

[WanWizard]

I personally never use the automount.

 

I just use fstab entries. OpenPLi will automatically create the required mountpoints, and mount the remote filesystems.

[theparasol]

My /etc/fstab entry for my nas:

 

//192.168.1.203/NAS  /media/hdd           cifs       user=guest,password=

[MiLo]

A funky way to create mount points is to have commented-out fstab entries. The script that parses fstab for mountpoints does not understand comments, so if you have an /etc/fstab line like this:

#bogus /media/something bogus bogus

this should create the /media/something directory (mountpoint) at boot time. Try it, I don't know if this is still the case, but it's a rather convenient way since fstab also gets placed into the autobackup.

[The_Raven]

Hm, does not work like expected!

I have 3 shares. With # in front it creates the first share-folder, but delete it soon after creation! Then it goes to the next share-folder, create it but also delete it after creation. The last share does not delete and stays there.

Then i removed the # in front. Problem: If the share (NAS) is down, the box will not boot! It hangs at boot, i think because the box trys to mount the share. Maybe i have to wait until timeout (120s each share?) is reached.

Now i added the parameter "noauto". I think it's ok this way, but i have to test it now.

Edited by The_Raven, 6 March 2015 - 19:56.