[SOLVED] What would prevent opening a Samba share on a linux box from another linux box

rlx · 11-09-2018, 07:16 PM

Hi everyone,

I am running Clonezilla from a TabletPC and I issue the following command from a command prompt after eth0 is configured. I am asked for the password. The command should mount a share on my Linux server. Unfortunately the mount fails saying it cant find the file path,

mount.cifs //192.168.1.100/root/sa602/cz.d /user/partimag -o "user=root"

That command fails when run from a TabletPC booted with Clonezilla but succeeds if I run it on the Linux server.

I just updated Clonezilla to the latest version.

The above command (or something similar) has worked for many years with the older version of Clonezilla, but it stopped working just after I upgraded the Clonezilla USB boot key to the latest version a few days ago.

I have a router configured with fixed IP addresses for the Linux server and two tabletPC's so there is no adressing error here.

Samba is running on the Linux server and the above command works fine if I type it in the Linux server.

The Samba communications work fine in all directions between the TabletPC's (when they run Windows and not Clonezila) and the Linux server.

So my question is what are the tools available to investigate that problem from the Clonezilla prompt?

ping 192.168.1.100 works fine. What other test might help?

Thanks for any clue

(Edit) I can mount a share from another TablePC running Windows from the pc running Clonezilla, but I can't mount a share from the Linux server that has my larger disks and will store the backup.

rlx · 11-09-2018, 09:03 PM

I applied nino09's suggestion from another post and that solved the mount issue. I added the following line to my server smb.cfg file and mount.cifs now works from the Clonezilla prompt. I still have some work to do to understand why Clonezilla still fails but that's another step.

[global]
min protocol = SMB2

(Edit) I am not sure though that the above edit was the actual solution. It was a Friday, this was the first time I upgraded Clonezilla in many years. The real issue was more likely that initially I didn't provide the right IP address to initialize the Ethernet on the Clonezilla PC initially and later I ended up doing it right at the time I edited the Samba config file. The actual problem was most likely a user error.