Re: Auto Mount of Device Direct Connected to Router Fails

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sounds like a timing issue. On my phone so can't form a proper solution but search for boot priority. Should give you some answers.

Fred Roller

On Jun 22, 2016 6:35 PM, "Stephen Morris" <samorris@xxxxxxxxxxxxxxx> wrote:
Hi,

    I have a Nas storage device that is direct connected to my router via ethernet. The auto mount at boot time that occurs as a result of the fstab entry fails to be able to mount the device. After I boot into KDE I can quite happily mount the device albeit via using sudo. If I try specifying the users and user options in the mount definition in fstab I get errors saying that CIFS doesn't support those options, hence the only option is to use root to mount the device. Does anyone know if this is deliberate on the part of CIFS or is this a defect? Reading the man page pointed at below is seems that CIFS will only allow Superuser mounts, is that likely to change?


    Looking at the systemctl output below, I have removed the userid and password for security reasons, it seems to be indicating that the boot mount failed because the network wasn't up. If that is indeed the case, how do modify systemd to not attempt the auto mount until the network is up?


systemctl status mnt-nas.mount
● mnt-nas.mount - /mnt/nas
   Loaded: loaded (/etc/fstab)
   Active: failed (Result: exit-code) since Thu 2016-06-23 07:03:48 AEST; 53min ago
    Where: /mnt/nas
     What: //192.168.1.12/Volume_1
     Docs: man:fstab(5)
           man:systemd-fstab-generator(8)
  Process: 1390 ExecMount=/usr/bin/mount //192.168.1.12/Volume_1 /mnt/nas -t cifs -o username=,password=,cache=strict,rw (code=exited, status=32)

Jun 23 07:03:48 localhost.localdomain systemd[1]: Mounting /mnt/nas...
Jun 23 07:03:48 localhost.localdomain mount[1390]: mount error(101): Network is unreachable
Jun 23 07:03:48 localhost.localdomain mount[1390]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
Jun 23 07:03:48 localhost.localdomain systemd[1]: mnt-nas.mount: Mount process exited, code=exited status=32
Jun 23 07:03:48 localhost.localdomain systemd[1]: Failed to mount /mnt/nas.
Jun 23 07:03:48 localhost.localdomain systemd[1]: mnt-nas.mount: Unit entered failed state.


regards,

Steve

--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux