Can't save Tvheadend recordings to NAS

Glowazowski · February 16, 2018 at 7:59 PM

Hi there,

I'm trying to get Tvheadend to store recordings to my NAS. Trying...

I created the file /storage/.config/system.d/storage-tvhrec.mont

[Unit]

Description=TCH Aufnahmen

Requires=network-online.service

After=network-online.service

Before=kodi.service

[Mount]

What=//192.168.24.3/tvhrec

Where=/storage/tvhrec/

Options=username=***,password=***,rw

Type=nfs

[Install]

WantedBy=multi-user.target

Then I ran systemctl enable storage-music.mount and after rebooting my machine set the Tvheadend recording path to /storage/tvhrec .

What happens confuses me: Inside the tvhrec-share on my NAS I find a recording I made weeks ago when I first set up Tvheadend which was not in the folder my previous recordings were. Strange to me but ok. The real problem to me is, that new recordings are someplace I do not know but not in the tvhrec-share on my NAS.

Where did I go wrong?

Aroosha · February 16, 2018 at 10:11 PM

This is the typo "systemctl enable storage-music.mount" you should enable this with ssh "systemctl enable storage-tvhrec.mount"

**CvH** · February 17, 2018 at 1:30 PM Official Post

btw additional to what Aroosha stated, Mounting network shares [LibreELEC.wiki] covers exactly that use case

depending at the NAS it could be necessary to add vers=2.1 to the options line like described at the wiki article

Glowazowski · February 17, 2018 at 10:39 PM

Aroosha : My mistake... typo is in my first post. In fact I entered exactly what you posted.

CvH : As adding vers=2.1 did not help, I started all over following the article you directed me to. Sadly that did not work. systemctl status ... tells me there ist some error 255

**CvH** · February 18, 2018 at 10:37 AM Official Post

Quote from Glowazowski

As adding vers=2.1 did not help

if your NAS is old crap or misconfigured vers=1.0 might work

rhartinger · February 18, 2018 at 10:40 AM

IIn my case Vers 1.0 works

Glowazowski · February 18, 2018 at 1:26 PM

Ok... now things become interesting: I completely reinstalled my NAS an my LE machine.

With the exeption of setting static IP addresses I did not change any settings.

Still I had the same errors.

Setting vers=1.0 did work. That is a good start for me

Still I think it is not a goot idea to use that old SMB version. Probably there is some problem with my NAS. But it is not really old - It is a Synology DS216j on the latest software.

Any ideas what I have to change here?

**blueribb** · February 18, 2018 at 2:25 PM

Precaution for a Potential SMB Vulnerability | Synology Inc.

Download Center - DS216j | Synology Inc.

**CvH** · February 18, 2018 at 10:01 PM Official Post

Quote from Glowazowski

Any ideas what I have to change here?

with latest software update you have an nice ui for that

Glowazowski · February 19, 2018 at 8:39 AM

Strange... I tried exactly the same settings that can be seen in your screenshot.

Good news: I works now. What seems to have done the trick is this:

1) Keep NAS set up to accept min SMB1 and max SMB2

2) Use storage-xxx.mount with vers=1.0

3) Disable storage-xxx.mount

4) Change NAS settig as in your screenshot

5) Use storage-xxx.mount without vers=xx

It did not work for me, when I started with step 4.

b_ignatov · February 26, 2018 at 12:57 AM

Very useful thread!

I have exactly the same issue. After update to Libreelec 8.2, I'm not able to mount my SMB. I know that Libreelec 8.2 has some problem and difference with SMB versions, but I can't get it to work. I use my Linksys Wrt1200ac router as storage, but how can I find out which SMB version is?

**blueribb** · February 26, 2018 at 4:02 AM

Quote from b_ignatov

Very useful thread!

I have exactly the same issue. After update to Libreelec 8.2, I'm not able to mount my SMB. I know that Libreelec 8.2 has some problem and difference with SMB versions, but I can't get it to work. I use my Linksys Wrt1200ac router as storage, but how can I find out which SMB version is?

Start a new thread. I think you meant to say you use your router to connect external storage. You should google the specs on your exact router to see how it handles SMB.

**CvH** · February 26, 2018 at 8:15 AM Official Post

Quote from b_ignatov

has some problem and difference with SMB versions

we are just forcing the secure and supported samba versions, if your device can't handle "recent" ( => Windows Vista) versions then you have to force the old insecure/broken one (or adjust your NAS/Router/Samba-server settings)

Adding vers=1.0 might do the trick if you router (very likely) only support the EOL samba version that nobody should use today.

b_ignatov · February 26, 2018 at 9:24 AM

Quote from CvH

Adding vers=1.0 might do the trick if you router (very likely) only support the EOL samba version that nobody should use today.

Thanks to you and this topic, I've already done it and everything works perfectly.My .mount file looks like:

Code

[Unit]
Description=cifs mount script
Requires=network-online.service
After=network-online.service
Before=kodi.service

[Mount]
What=//192.168.0.1/Home/Recordings/
Where=/storage/recordings
Options=username=user,password=mypassword,rw,vers=1.0
Type=cifs

[Install]
WantedBy=multi-user.target

Display More

ajdg · March 3, 2018 at 4:14 PM

Hi,

I am also having trouble mounting my NAS, I have created a mount script, using guides on the Libreelec Wiki website, that looks like this:

Code

[Unit]
Description=cifs mount script
Requires=network-online.service
After=network-online.service
Before=kodi.service

[Mount]
What=//192.168.1.92/mnt/md1/Users/AlexGilbert/Media/Videos
Where=/storage/recordings
Options=username=root,password=password,rw,vers=2.1
Type=cifs

[Install]
WantedBy=multi-user.target

Display More

This initially appears to work when enabled but when I run the command: systemctl status storage-recordings.mount

I get this:

● storage-recordings.mount - cifs mount script

Loaded: loaded (/storage/.config/system.d/storage-recordings.mount; enabled;

vendor preset: disabled)

Active: failed (Result: exit-code) since Sun 2018-01-14 15:10:04 GMT; 1 month

s 17 days ago

Where: /storage/recordings

What: //192.168.1.92/mnt/md1/Users/AlexGilbert/Media/Videos

Process: 542 ExecMount=/usr/bin/mount //192.168.1.92/mnt/md1/Users/AlexGilbert

/Media/Videos /storage/recordings -t cifs -o username=root,password=smbpasswd,rw

,vers=2.1 (code=exited, status=255)

Jan 14 15:10:04 LibreELEC systemd[1]: Mounting cifs mount script...

Jan 14 15:10:04 LibreELEC systemd[1]: storage-recordings.mount: Mount process ex

ited, code=exited status=255

Jan 14 15:10:04 LibreELEC systemd[1]: Failed to mount cifs mount script.

Jan 14 15:10:04 LibreELEC systemd[1]: storage-recordings.mount: Unit entered fai

led state.

Curiously the date is wrong in this output but when I run the date command it is correct and it is also correct in Kodi, maybe this has something to do with my issue. I am a complete novice and am sure there is something really obvious I am missing, someone please put me out of my misery!

**chewitt** · March 4, 2018 at 4:09 AM Official Post

/mnt/md1/Users/AlexGilbert/Media/Videos looks like the internal path on the server which is probably not the network visible path. It's technically possible to create a share path like that, but normally an SMB/Samba server would create something like //192.168.1.92/Media/Videos so it looks unusual, and unusual often means wrong.

ajdg · March 4, 2018 at 7:42 PM

Thanks for replying so quickly, I thought it seemed a bit long compared to other examples dotted around the internet!

So, I created a new share "Recordings" and used the path in the windows file explorer address bar: //192.168.1.92/ nas/recordings. Still no joy, same failed output.

When i looked in the samba config via my nas gui the path is shown as I had it in my original mount script, see below.

I

**chewitt** · March 6, 2018 at 7:38 AM Official Post

If that's the active smb.conf on the NAS/server "//192.168.1.92/Recordings" is the network path