[Samba] Cannot mount a remote volume after system upgrade
linux at kukkukk.com
Mon Jun 9 13:28:52 MDT 2014
Am 09.06.2014 20:57, schrieb Günter Kukkukk:
> Am 09.06.2014 19:21, schrieb James Moe:
>> On 06/09/2014 08:57 AM, Jeremy Allison wrote:
>>>>> Any suggestions or changes that will allow the remote volume to
>>> Can you post a wireshark trace of the attempt to mount ?
>> Yes. What format is preferred? Does the mailing list allow attachments.
> Hi James,
> i also have opensuse 12.3 and 13.1 and an old OS/2-Warpserver5 around here.
> Just booted that OS/2 box - but it seems that both hard disks were not starting
> spinning up (only the boot drive)- so it needs a 2nd try with a looooong checkdisk ....
> But i'm sure i'll get that old beast running again after months (years?) of
> inactivity. :-)
> Then i'll also check the kernel mounts and keep you informed.
> Cheers, Günter
yup, got the OS/2-server running... :-)
I'm able to mount using *both* opensuse 12.3 and 13.1.
I also checked reading and writing....
The only thing i had to add to the mount cmd now was the ip-address "ip=192.168.200.1",
but that could have many reasons compared to my formerly used environments.
I used the following mount command:
mount -t cifs //server01/UG /mnt/server -o
Note that i also specified (for years) "port=139".
In case you don't get it running, as root use the following when the cifs.ko kernel module
has already been loaded (otherwise first use: modprobe cifs)
echo 7 > /proc/fs/cifs/cifsFYI
This enables the highest cifs module debug level, which you then can watch (during mount) with
tail -f /var/log/messages
More information about the samba