-
The forum software that supports hummy.tv has been upgraded to XenForo 2.3!
Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.
[network-shares-automount] package released
- Thread starter Drutt
- Start date
Hi,
Has anyone managed to get this working on a modern Synology NAS (running DSM 7.2.2)?
All I get is permission denied in the scanmounts.log, and looking on the NAS logs I get connection attempt via SMB denied due to NTLMv1 not permitted, and NFSv1 not supported both due to security vulnerabilities than cannot be corrected?
I've looked though the posts, but they are years old!
Has anyone managed to get this working on a modern Synology NAS (running DSM 7.2.2)?
All I get is permission denied in the scanmounts.log, and looking on the NAS logs I get connection attempt via SMB denied due to NTLMv1 not permitted, and NFSv1 not supported both due to security vulnerabilities than cannot be corrected?
I've looked though the posts, but they are years old!
Black Hole
May contain traces of nut
If you don't want to (or can't, but mostly you can) install/enable SMB1 on the remote server, you're in experimental territory. Try googling "synology nas smb1". Security hardly matters if you're running it on a local network.
You could try the Samba 3 package (which confers SMB2).
You could try the Samba 3 package (which confers SMB2).
Last edited:
I have tried that, and found options for NTLMv1 authentication, but I'm still getting either permission denied or connection refused?
I installed the samba package also, but still no luck, I'll try and see how to try the samba 3 package.
Where can I find the samba 3 package, it's not on the package lists (advanced)?
I installed the samba package also, but still no luck, I'll try and see how to try the samba 3 package.
Where can I find the samba 3 package, it's not on the package lists (advanced)?
Last edited:
Black Hole
May contain traces of nut
Don't you think that would be more appropriately asked in the Samba 3 thread, where the people who know might see the question?
Terrahawk
Member
@phd, Your post peaked my interest. Over the last week I've made several attempts to manually mount my Synology (DS723+) shared folder on the Humax. Unfortunately each has been unsuccessful. Each time giving the error "no such file or directory".
I don't have the beta samba package installed yet, just the cifs package in the standard repository.
I've tried:
I've tried mount points in /mod/nas, /mnt/hd2/nas, "/mnt/hd2/My Video/nas"
Each time giving the mount points chmod 755 permission.
I've tried the below command which successfully enumerated the available Synology shared folders, downloads included.
The synology credentials used have RW access to the downloads directory.
If if deliberately use an invalid password during the mount command, I receive an authentication failed, rather than a no such file or directory error.
On the Synology side, I've enabled ...
Maybe I'm missing something but can't see spot it.
Any ideas?
Does the Samba 3 package include an updated cifs client? I might need to ask this in the respective thead.
I don't have the beta samba package installed yet, just the cifs package in the standard repository.
I've tried:
Code:
mkdir /mnt/hd2/nas
chmod 755 /mnt/hd2/nas
a. mount -t cifs //[IP address]/downloads /mnt/hd2/nas -o vers=1.0,user="[username]",password="[password]"
b. mount -t cifs //[IP address]/downloads /mnt/hd2/nas -o vers=1.0,username="[username]",password="[password]"I've tried mount points in /mod/nas, /mnt/hd2/nas, "/mnt/hd2/My Video/nas"
Each time giving the mount points chmod 755 permission.
I've tried the below command which successfully enumerated the available Synology shared folders, downloads included.
Code:
smbclient -L //[IP address] -U [username]The synology credentials used have RW access to the downloads directory.
If if deliberately use an invalid password during the mount command, I receive an authentication failed, rather than a no such file or directory error.
On the Synology side, I've enabled ...
- Minimum SMB protocol = SMB1
- Server signing and transport encryption = client defined
- NTLMv1 Authentication = enabled
- TLS version compatibility level support (TLS v1) = enabled
Maybe I'm missing something but can't see spot it.
Any ideas?
Does the Samba 3 package include an updated cifs client? I might need to ask this in the respective thead.
Attachments
Terrahawk
Member
Just to add that I have verified the user name and password are good. I'm able to connect / mount the shared folder on my linux machine using the same credentials.
Edit:
It just occurred to me to ask if the Samba service must be enabled in order to mount a remote share. My next test I think!!
Edit:
It just occurred to me to ask if the Samba service must be enabled in order to mount a remote share. My next test I think!!
Last edited:
prpr
Well-Known Member
Samba and cifs are different things. One is connections in, the other is connections out.
You might wish to review the info. in this post and apply it: https://hummy.tv/forum/posts/109528
No. See above. That would violate package rules in any case.
Terrahawk
Member
Great. Thanks prpr
I thought Samba and cifs were different. Samba being the server and cifs being the client. Was clutching at straws
I'll try adding the UNC part and see how I get on.
I thought Samba and cifs were different. Samba being the server and cifs being the client. Was clutching at straws
I'll try adding the UNC part and see how I get on.
Code:
mount -t cifs //192.168.0.nnn/Video "/media/My Video/MediaShare" -o username=xxxxx,password=xxxxx,unc=\\\\192.168.0.nnn\\VideoTerrahawk
Member
Excellent. Successfully mounted my Synology shared folder on the Humax. 
The issue was indeed the need to have the UNC path included.
@phd
Make sure you have the cifs package installed and running. No need for beta samba 3 just for network-shares-automount to work.
Can you try manually mounting a share on your box via telnet connection. If that works, the focus can change to settings related to the automount package setup.
These settings on the Synology work.
The issue was indeed the need to have the UNC path included.
Code:
mount -t cifs //192.168.x.x/video "/media/My Video/Synology" -o username=xxxx,password=xxxx,unc=\\\\192.168.x.x\\video@phd
Make sure you have the cifs package installed and running. No need for beta samba 3 just for network-shares-automount to work.
Can you try manually mounting a share on your box via telnet connection. If that works, the focus can change to settings related to the automount package setup.
These settings on the Synology work.
- Minimum SMB version = SMB1
- Transport Encryption Mode = Client Defined
- Server Signing Status = Client Defined (any of the 3 settings work)
- Enable NTLMv1 Authentication = Selected
- TLS version = No need to change your current setting.
@Terrahawk Thanks.
I'm sure I tried all those things apart from the TLS version, and couldn't get it working.
I recently got a replacement box as my original keeps freezing.
After installing all the Custom Firmware and packages, I thought I'd try this again.
I eventually was able to mount using the cli mount, then I installed the automount package and setup the ModSettings.
I then found it mounted in the USB virtual drive, so am able to access my off-loaded files.
The only thing that doesn't seem to work is deleting files via the handset, even though the network share has read/write permissions.
I can see the delete requests in the NAS log files, but they don't seem to be removed.
Are you able to delete files or is this functionality not available?
I'm sure I tried all those things apart from the TLS version, and couldn't get it working.
I recently got a replacement box as my original keeps freezing.
After installing all the Custom Firmware and packages, I thought I'd try this again.
I eventually was able to mount using the cli mount, then I installed the automount package and setup the ModSettings.
I then found it mounted in the USB virtual drive, so am able to access my off-loaded files.
The only thing that doesn't seem to work is deleting files via the handset, even though the network share has read/write permissions.
I can see the delete requests in the NAS log files, but they don't seem to be removed.
Are you able to delete files or is this functionality not available?
Last edited:
So here I have a 64GB microSD card that is being used as recording media in a CF3.14 HD-Fox T2.
After originally formatting it with CF3.13, humaxtv showed plausible values in the on-screen Settings>System>Data Storage display, like 58GB total, 20GB reserved, whatever (<38GB) used.
Subsequently it decided that there was exactly twice as much capacity, ie 116GB. Eventually it gave up and would only mount the storage RO.
Investigation seemed to show that the double capacity report was unrelated to the eventual filesystem errors, but actually caused by network_shares_automount. It turns out that I rediscovered BH's https://hummy.tv/forum/threads/network-shares-automount-package-released.1126/post-148078. Did this only appear in CF3.1x and not for any of the posters in the previous 37 pages?
The solution seems to be using the
After originally formatting it with CF3.13, humaxtv showed plausible values in the on-screen Settings>System>Data Storage display, like 58GB total, 20GB reserved, whatever (<38GB) used.
Subsequently it decided that there was exactly twice as much capacity, ie 116GB. Eventually it gave up and would only mount the storage RO.
Investigation seemed to show that the double capacity report was unrelated to the eventual filesystem errors, but actually caused by network_shares_automount. It turns out that I rediscovered BH's https://hummy.tv/forum/threads/network-shares-automount-package-released.1126/post-148078. Did this only appear in CF3.1x and not for any of the posters in the previous 37 pages?
The solution seems to be using the
--rbind mount option in /mod/sbin/scanmounts:
Diff:
...
# set up links to where we can get at the settings folder (a bit messy due to HDR / HD differences)
mounted=$(mount | grep "\[ModSettings\]")
if [ ! "$mounted" ]; then
if [ -d "/media/My Video/[ModSettings]" ]; then # HDR - add link to settings
- mount /mod/settings "/media/My Video/[ModSettings]"
+ mount --rbind /mod/settings "/media/My Video/[ModSettings]"
elif [ -d "/media/drive1/[ModSettings]" ]; then # HD put [Modsettings] on root and add link to settings
- mount /mod/settings "/media/drive1/[ModSettings]"
+ mount --rbind /mod/settings "/media/drive1/[ModSettings]"
fi
fi
...I carried out this procedure
At this point the on-screen disk information showed the plausible values. But after using the system, installing other packages, restarting, etc, for a few days, the incorrect capacity was displayed again.
In a second test I installed the desired packages alphabetically and observed that the double capacity issue appeared after installing network_shares_automount. After removing it and restarting, the correct capacity was shown.
Previously, I also tried this:
This caused the double capacity to be shown immediately, while the actuality was shown in Webif and using
(network_shares_automount being in the stashed non-precious data).
Additionally, although the card was clearly readable (working Webif, playable content) and rw-mounted, the on-screen menu didn't allow me to set the card as the recording medium.
- extracted the card
- stashed the "precious" content
- formatted it as a non-ext volume externally
- re-introduced it to the Humax, formatted it for use, made it the recording device, installed Webif, and shut down
- copied over the precious content
- re-introduced it to the Humax, restarted.
At this point the on-screen disk information showed the plausible values. But after using the system, installing other packages, restarting, etc, for a few days, the incorrect capacity was displayed again.
In a second test I installed the desired packages alphabetically and observed that the double capacity issue appeared after installing network_shares_automount. After removing it and restarting, the correct capacity was shown.
Previously, I also tried this:
- extracted the card
- stashed the non-precious card contents (ie, except
.../Video; 13k files in/mod) - formatted it as an ext3 volume externally
- copied back the content, precious and not
- re-introduced it to the Humax.
This caused the double capacity to be shown immediately, while the actuality was shown in Webif and using
df -h /dev/sda1
Code:
Filesystem Size Used Available Use% Mounted on
/dev/sda1 58.0G 3.7G 51.4G 7% /media/drive1Additionally, although the card was clearly readable (working Webif, playable content) and rw-mounted, the on-screen menu didn't allow me to set the card as the recording medium.
Last edited:
Black Hole
May contain traces of nut
Black Hole
May contain traces of nut
The answer is the Humax reported figures are indeed double, but it is working like that.