Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Page 2 of 2 FirstFirst 12
Results 16 to 26 of 26

Thread: Unable to automount NAS shares anymore.

  1. #16
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,276 Times in 1,089 Posts
    The more times I edit auto.network and reboot, more and more automounter messages appear in var/log/messages...

    Code:
    Mar 19 16:00:37 et10000 daemon.info automount[580]: attempting to mount entry /media/autofs/ets
    Mar 19 16:00:37 et10000 daemon.warn automount[580]: >> mount: mounting //192.168.1.115/ET10000 on /media/autofs/ets failed: Operation not supported
    Mar 19 16:00:37 et10000 daemon.info automount[580]: mount(generic): failed to mount //192.168.1.115/ET10000 (type cifs) on /media/autofs/ets
    Mar 19 16:00:37 et10000 daemon.info automount[580]: failed to mount /media/autofs/ets
    Mar 19 16:01:04 et10000 daemon.notice ntpdate[576]: step time server 85.199.214.101 offset 24.041133 sec
    Mar 19 16:01:06 et10000 daemon.info automount[580]: attempting to mount entry /media/autofs/ets
    Mar 19 16:01:06 et10000 daemon.warn automount[580]: >> mount: mounting //192.168.1.115/ET10000 on /media/autofs/ets failed: Operation not supported
    Mar 19 16:01:06 et10000 daemon.info automount[580]: mount(generic): failed to mount //192.168.1.115/ET10000 (type cifs) on /media/autofs/ets
    Mar 19 16:01:06 et10000 daemon.info automount[580]: failed to mount /media/autofs/ets
    Mar 19 16:01:13 et10000 daemon.info automount[580]: attempting to mount entry /media/autofs/ets
    Mar 19 16:01:13 et10000 daemon.warn automount[580]: >> mount: mounting //192.168.1.115/ET10000 on /media/autofs/ets failed: Operation not supported
    Mar 19 16:01:13 et10000 daemon.info automount[580]: mount(generic): failed to mount //192.168.1.115/ET10000 (type cifs) on /media/autofs/ets
    Mar 19 16:01:13 et10000 daemon.info automount[580]: failed to mount /media/autofs/ets
    Mar 19 16:01:13 et10000 daemon.notice ntpdate[682]: adjust time server 85.199.214.101 offset 0.000888 sec
    Mar 19 16:01:16 et10000 daemon.info automount[580]: attempting to mount entry /media/autofs/logs
    Mar 19 16:01:16 et10000 daemon.crit automount[580]: key "logs" not found in map source(s).
    Mar 19 16:01:16 et10000 daemon.info automount[580]: failed to mount /media/autofs/logs
    Mar 19 16:01:45 et10000 daemon.info automount[580]: attempting to mount entry /media/autofs/ets
    Mar 19 16:01:45 et10000 daemon.warn automount[580]: >> mount: mounting //192.168.1.115/ET10000 on /media/autofs/ets failed: Operation not supported
    Mar 19 16:01:45 et10000 daemon.info automount[580]: mount(generic): failed to mount //192.168.1.115/ET10000 (type cifs)on /media/autofs/ets
    Mar 19 16:01:45 et10000 daemon.info automount[580]: failed to mount /media/autofs/ets
    Mar 19 16:01:56 et10000 authpriv.info login[740]: pam_unix(login:session): session opened for user root by LOGIN(uid=0)
    Mar 19 16:01:59 et10000 authpriv.notice login[743]: ROOT LOGIN  on '/dev/pts/0' from '[::ffff:192.168.1.116]:57491'

  2. #17
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,769
    Thanks
    235
    Thanked 1,656 Times in 1,305 Posts
    Quote Originally Posted by ccs View Post
    This error crops up after a fresh flash of 5.1.020 and nothing else (apart from setting debug logs).

    Code:
    Mar 19 15:18:13 et10000 daemon.info automount[581]: attempting to mount entry /media/autofs/logs
    Mar 19 15:18:13 et10000 daemon.crit automount[581]: key "logs" not found in map source(s).
    Mar 19 15:18:13 et10000 daemon.info automount[581]: failed to mount /media/autofs/logs
    Mar 19 15:18:13 et10000 daemon.info automount[581]: re-reading map for /media/autofs
    Ignore that. Something seems to be looking for /media/autofs/logs (or, possibly, a logs directory in all mountpoints listed in /proc/mounts...) and autofs just reports that it isn't there. Since it's a daemon it reports it to syslog.
    MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD

  3. #18
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,769
    Thanks
    235
    Thanked 1,656 Times in 1,305 Posts
    Quote Originally Posted by ccs View Post
    I'm using a valid nas userid and password - that should be ok?
    It should be. I've never set one (since I only ever run a Samba server to test other people's problems).
    I also use autofs to do the mounting. (I'd never hard-wire a network mount into fstab).
    MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD

  4. The Following User Says Thank You to birdman For This Useful Post:

    ccs (19-03-18)

  5. #19
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,276 Times in 1,089 Posts
    Changing the minimum SMB protocol from SMB2 to SMB1 on the NAS, and it now works!!

    Anyone understand why? The NAS has had lots of samba updates since I last used autofs, so I assume SMB1 used to be the minimum.

    I tried SMB1 yesterday without any success, so I guess other things weren't quite right either at the time.

    Thanks for all the suggestions.

    I'm going to try again from scratch tomorrow to see how it goes.

  6. #20
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,769
    Thanks
    235
    Thanked 1,656 Times in 1,305 Posts
    I've just successfully mounted a share that needs an id/pwd with this on the command line:
    Code:
    mount -t cifs -o username=xxxxxxx,password=yyyyyyy //plug/local local
    That's on both my mbtwin (kernel 3.6.0) and et8000 (kernel 4.10.6) [both cifs-utils 6.6].

    My laptop (kernel 4.13.0) requires me to add vers=1.0 to the -o option [cifs-utils 6.7]. (and vers 1.0 is supposed to be the default here...according to the manpage)
    Last edited by birdman; 19-03-18 at 20:26.
    MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD

  7. #21
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,276 Times in 1,089 Posts
    @birdman - we were posting at the same time, so you may have missed my last post.

  8. #22
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,769
    Thanks
    235
    Thanked 1,656 Times in 1,305 Posts
    Quote Originally Posted by ccs View Post
    @birdman - we were posting at the same time, so you may have missed my last post.
    I did miss it.
    You've changed the server, I changed the client (on my laptop).
    Not sure whether we were changing the same thing, but I'm glad you've got it working now.

    Perhaps I should force my Samba server to use SMB2.....
    MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD

  9. The Following User Says Thank You to birdman For This Useful Post:

    ccs (19-03-18)

  10. #23
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,276 Times in 1,089 Posts
    OK, fresh flash of 5.1.020, no settings or plugins restored - network browser sets up autofs NAS mounts without any issues, using all the default settings.

    No need to install cifs-utils, just need to make sure the NAS hasn't changed any defaults!
    Last edited by ccs; 20-03-18 at 14:25.

  11. #24
    birdman's Avatar
    Title
    Moderator
    Join Date
    Sep 2014
    Location
    Hitchin, UK
    Posts
    7,769
    Thanks
    235
    Thanked 1,656 Times in 1,305 Posts
    Quote Originally Posted by ccs View Post
    No need to install cifs-utils, just need to make sure the NAS hasn't changed any defaults!
    Odd. autofs calls mount, and that will look for mount.cifs to do it. See post #9.
    MiracleBox Prem Twin HD - 2@DVB-T2 + Xtrend et8000 - 5(incl. 2 different USBs)@DVB-T2[terrestrial - UK Freeview HD, Sandy Heath] - LAN/USB-stick/HDD

  12. #25
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,276 Times in 1,089 Posts
    ... it doesn't make sense to me from what you'd said earlier.

    Code:
    root@et10000:~# opkg list-installed | grep cifs
    root@et10000:~# which mount.cifs
    root@et10000:~#

  13. #26
    adm's Avatar
    Title
    Forum Supporter
    Donated Member
    Join Date
    Sep 2014
    Location
    Southend on Sea, UK
    Posts
    1,636
    Thanks
    62
    Thanked 647 Times in 505 Posts
    Quote Originally Posted by ccs View Post
    OK, fresh flash of 5.1.020, no settings or plugins restored - network browser sets up autofs NAS mounts without any issues, using all the default settings.

    No need to install cifs-utils, just need to make sure the NAS hasn't changed any defaults!
    Background 5.1.019 installed via couch flash with a settings restore
    5.1.020 installed via a software update with previous settings maintained.
    No other files downloaded or installed.

    I tried mounting a disk attached to my router via a USB connection.

    1st attempt: The network browser found the router and the hard disk attached to it. I selected the disk and attempted to mount it (no user or password) using the default settings but changing Server IP to that of the router, changing the mount type to CIFs share and having to give the Local share and Server share a name. The result was the same error message about not finding the disk.

    I removed the mount and rebooted the box.
    2nd attempt: the network browser found the router BUT didn’t find the disk attached to it. The browser also found all the other relavant equipment on my network.

    I rebooted the box.
    3rd attempt: The network browser found the router and the hard disk attached to it. I selected the disk and on mounting it (no user or password) the default settings were different to those on the 1st attempt – I only had to change the mount type to CIFs share. The IP was correct, the local share name was filled in and sensible and the server share name was also filled in whereas the latter two names were blank on the 1st attempt. (the names on my 3rd attempt were different to those I typed in the 1st attempt so hadn’t been remembered in some configuration file).
    I can now access the disk from my box.
    Xtrend ET10K, 2 x satellite tuners 28.2 (Sky FTA), 2 x hybrid (UK Freeview), Zgemma H9S (satellite)

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.