Arch Linux

Slacker133701 · 07-04-2017, 02:50 PM

Hello,

I cannot seem to figure out why this share will not automatically mount on boot.

//192.168.1.4/music /mnt/pandora/Music cifs credentials=/home/mike/.smbcredentials,uid=1000,gid=1000,iocharset=utf8,sec=ntlm 0 0

I am running Arch Linux with i3wm. The share is not even accessible pre/post launching i3

I have tried _netdev I thought maybe it was because there was a lag in the networking that did not help.

Everything mounts fine if I do "sudo mount -a "

How do I check the logs for this? I looked into /var/logs/journal but could not find anything.

I tried also using x-systemd.automount however this WORKS but it only works when I try to access the path. I need these paths readily available upon boot.

What am I doing wrong?!

Thanks in advance,
Slacker133701

WFV · 07-04-2017, 03:18 PM

I'm not familiar with cifs mounts or network mounts, but

Quote:

Everything mounts fine if I do "sudo mount -a "

have you checked mtab after running that command? then copy the mtab entry for that mount to fstab?

Slacker133701 · 07-04-2017, 03:30 PM

Hmm, this does not work has it comes up with invalid arguments when sudo mount -a after using mtabs contents.

I'm guessing it has to do with the network possibly.

What logs should i be looking at?

I enabled systemctl enable network-online.target but _netdev does not seem to do anything.

Slacker133701 · 07-04-2017, 03:49 PM

that is journalctl output

Code:

Jul 04 11:32:30 mm systemd[1]: mnt-pandora-Music.mount: Mount process exited, code=exited status=32
Jul 04 11:32:30 mm systemd[1]: Failed to mount /mnt/pandora/Music.
Jul 04 11:32:30 mm systemd[1]: mnt-pandora-Music.mount: Unit entered failed state.
Jul 04 11:34:05 mm systemd[1]: Mounting /mnt/pandora/Music...
Jul 04 11:34:05 mm systemd[1]: mnt-pandora-Music.mount: Mount process exited, code=exited status=32
Jul 04 11:34:05 mm systemd[1]: Failed to mount /mnt/pandora/Music.
Jul 04 11:34:05 mm systemd[1]: mnt-pandora-Music.mount: Unit entered failed state.

Slacker133701 · 07-04-2017, 04:37 PM

This has been SOLVED!

sudo systemctl disable dhcpcd
sudo pacman -S NetworkManager
sudo systemctl enable NetworkManager
sudo systemctl start NetworkManager
Reboot
has solved this issue!