On 01/07/13 12:05, Chris Walker wrote:
On Sun, 30 Jun 2013 23:51:41 +0100 steve-ALUG@hst.me.uk wrote:
sudo -i
mount.cifs //sharename /mountpoint/ --verbose #This should error with Permission denied if you've disabled root as a login name on your NAS mount error(5): Input/output error
mount.cifs //sharename /mountpoint/ -o user=AUserName --verbose #Should connect OK
As root by using su, mount.cifs //storage_server/Epox_Share /media/Epox_Share/ -o user=Epox --verbose
When I enter the Epox password I get this :- mount.cifs kernel mount options: ip=192.168.1.25,unc=\storage_server\Epox_Share,user=Epox,pass=******** mount error(5): Input/output error
OK. That's pretty fundamentally wrong then!
I googled mount error(5): Input/output error and have come up with 2 possibilities 1) one thread mentioned that adding nounix made their mounting work.
Try as root:
mount.cifs //storage_server/Epox_Share /media/Epox_Share/ -o nounix,user=Epox --verbose
2) I wonder if your machine is in the right samba domain? If it's not then perhaps conencting to the share won't work. On my machine, the domain is listed in /etc/resolv.conf as
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.1.1 search MY_SAMBA_DOMAIN_NAME
I don't know if this is where it's set on your version of linux, nor how to set it.
Other thoughts: 3) Is there a firewall enabled? Could that be causing problems?
4) the user you're using (chris), it has been set up with a permission to use the NAS hasn't it, and you are using the right password?
5) presumably you have all the relevant cifs and samba or smb packages installed?
6) try these commands on your virtual machine and see if they work. If they don't it may be your installation that's in error.
umount //sharename
mount.cifs //sharename /mountpoint -o credentials=PathToYourCredentialsFile --verbose #should connect OK
If I enter the above, when I type in credentials=/et and press tab for the system to complete /etc, it doesn't. If I leave a space it does but then it complains about a bad credentials file.
That's to be expected. Tab completion works with whole file names. It doesn't understand credentials= so pressing tab after you've entered credentials=\et, it will think it's not a file name. Leaving a space and entering \et[tab] it will think it's a file name and complete it for you, but then mount doesn't expect a space between credentials= and the filename, so it will error.
[snip other stuff, not much point looking at the other stuff if the first bit isn't working!]
This thread gave me some ideas https://forums.mageia.org/en/viewtopic.php?f=8&t=5263
Perhaps you should/could ask for help in the mageia forums?
from that thread, try (as normal user) smbclient -L storage_server
and see if it lists the shares and domain name you expect.
Try smbclient \\storage_server\Laptop_Share -U=chris
You have to double up the 's!
Hopefully should connect and give you something like Domain=[YourDomain] OS=[Unix] Server=[Samba x.y.z] smb: >
If so, you can type ls and see if there's a list of files.
Does DMESG show anything when drive mounting goes wrong?
If you get it working, check that the file permissions on your credentials file are very restrictive - mine are -rw------- 1 root root so only root can read and write it, that's it. Here, they're as follows :- ls -la /etc/samba/auth* -rwxrwxrwx 1 root root 32 Jun 25 12:06 /etc/samba/auth.storage_server.Epox* -rwxrwxrwx 1 root root 33 Jun 25 12:06 /etc/samba/auth.storage_server.Laptop* -rwxrwxrwx 1 root root 36 Jun 25 12:06 /etc/samba/auth.storage_server.Mandriva* -rwxrwxrwx 1 root root 29 Jun 25 12:06 /etc/samba/auth.storage_server.xbox*
When you get it mounting, you should probably change those file permissions, unless you don't care about people reading the username and password in there.
In a 'clutching at straws' sort of way, do I have to be in any particular groups to do any of this? Bear in mind that this is a new installation and another of the problems I have is that all the windows open at maximum size despite having the flags ticked to save position and size - konsole for example. So I wondered if there's something else going on which is having an effect outside all my efforts. To try and identify if something is amiss, I created a Mageia installation inside VirtualBox. That doesn't exhibit the same issue of window sizes. Would it help for me to compare permissions from the virtual machine to this one on things like the files mentioned above? The VBox installation is also 64bit so I'm assuming I could copy stuff over without issue should I need to. Is that a fair assumption?
The short answer to this is I don't know - sorry. You could try the mounting stuff inside your vbox and see if they work. If they don't then there may be a problem with your full installation.
Hope that helps.
Cheers Steve