Problems in cifs mounting in mageia9 [SOLVED]

[rodgoslin]

Following a couple of catastrophic machine failures a while back, left me with only a Lenovo ThinkPad running Mageia, and that running Mageia7. Finally fed up with squinting at the small screen, I had built Mageia9 on a Lenovo ThinkCentre. I hadn't, up until now completed the OS install, since the builder (my son-in-law), seemed to have introduced a major problem in creating a Root user (I did raise this as a problem, in the Forum). However in retrospect, I did discover that this was nothing new. My some years old Mageia 7 would do the exact same thing. So, the OS install was completed and the usual lengthy customisation and software installs were carried out.
Over the years, I have built a significant Local Area Network, using Drobo units to provide house wide services on PC's tablets, mobile phones, etc.So, it came the time to install connection to the LAN. There has always been problems with sharing, within the Mageia Control Centre, and I usually create the sharing protocol manually, without recourse to the MCC facility. All went well with the first setup, and everything worked perfectly. Unfortunately that was the end of the good times. Eventually only three Drobo's out of six would mount. I tried with the official installation, with the same result. This is merely a report on the effect. If there is any response, I'll return the machine back to the start and repeat the install, recording the commands and returns. As a PS, when Drobo's decease appeared imminent, I bought into ma Synergy system, which was a total mistake. Both hardware and software were atrocious and near impossible to set up. I eventually got it going, and it does work, but incredibly slowly. I included it in the 'official' setup and it failed to be recognised and therefore the mount failed, in the same way as the Drobo units

[doktor5000]

So do you want to get all 6 of the Drobo's mounted or not ?
If you want to get it working, there's no need to reinstall and recording the commands. But you definitly need to provide some more information, or any information at all.

For anything network related, and especially network shares, there are basically only 2 important things:
1. name resolution
2. firewall

You'd need to mention at least if you use IP adresses or hostnames, and whether those are resolved centrally by your router or similar, or only locally via /etc/hosts.
If you simply use IP adresses and those don't change then you don't even need to worry about this point.

So for your CIFS shares, at the very least provide the /etc/fstab entry that you use and the mount -v output when you try to mount those shares.
Also some information on the counterpart, so what Drobo model/version you use.

[rodgoslin]

Thank you Doktor. As I pointed out in my post, this was only a declaration of the situation as seen , and that if the topic received any comments, that I would go over once again, the procedure of establishing shares. This I shall do

[rodgoslin]

My apologies for the delay oin replying to your last post. I'm not sure of the best way to present the system. The machine that this setup is being built on is a Lenovo ThinkCentre model M75s gen2. This replaces the first generation of the make and model, which failed in service. This earler model had been working well for some time runn. runing Mageia 7. The setup of /etc/fstab on the new machine is as the older machine with a few minor changes, and changes suggsted as a way around the gaikure to mount extrnal drives.

Code: Select all

# Entry for /dev/nvme0n1p2 :
UUID=9e2234a7-ae37-41ed-8427-0ed1168bb1e1 / ext4 relatime,acl 1 1
# Entry for /dev/nvme0n1p1 :
UUID=A16A-B415 /boot/EFI vfat iocharset=utf8,umask=000 0 0
# Entry for /dev/nvme0n1p4 :
UUID=44231fd8-bdc9-4179-b56a-c146cbdacc0b /home ext4 relatime,acl 1 2
#//drobo-b/Public /mnt/Public2 cifs uid=rod,gid=rod,credentials=/etc/samba/auth.drobo 0 0
#//drobo-c/Public /mnt/Public5 cifs vers=1.0,uid=rod,gid=rod,credentials=/etc/samba/auth.drobo 0 0
#//drobo-5N2/Public /mnt/Public3 cifs vers=1.0,uid=rod,gid=rod,credentials=/etc/samba/aith.drobo 0 0
#//drobo-d/Public /mnt/Public6 cifs vers=1.0,uid=rod,gid=rod,credentials=/etc/samba/auth.drobo 0 0
#//drobo-e/Public /mnt/Public7 cifs vers=1.0,uid=rod,gid=rod,credentials=/etc/samba/auth.drobo 0 0

#
# Entry for /dev/sda1 :
LABEL=home2 /mnt/extra ext4 relatime,acl 1 2
none /proc proc defaults 0 0
# Entry for /dev/nvme0n1p3 :
UUID=714af7cb-d1c5-45fb-9004-25da9f34d8b5 swap swap defaults 0 0


. For the moment, I've commented out the lines in question. The changes I've made to the original are trivial and to do with the Credenshalls aspect. The original version had a separate Credentials file for each mount option, but since all the drives had the same username and password, on that machine I simply created a single Credentials file, and pointed each mount command to it. The options uid= and gid=, I found on a Ubuntu forum. Without them all files on the Drobo, ar owned by root, which made life somewhat difficult. The vers= were in response to a suggestion on the occasion when the mount had failed. It did help, but did not work on all the drives, and unfortunately not on the drives which wer the most important. I'll uncomment the mount lines for the first try.
I'm having a bit of bother with one of the mount commands. I'll get back when this is sorted. So far, three of the drobo's have mounted . This one which seems to be an addres problem, and Publc6 which has failed to mount with a UNC (???) problem. As an engineer, UNC come to me as a screw thread formst!

Code: Select all

[rod@localhost ~]$ su
Password:
[root@localhost rod]# mount -av
/                        : ignored
/boot/EFI                : already mounted
/home                    : already mounted
/mnt/Public2             : already mounted
/mnt/Public5             : already mounted
mount error: could not resolve address for drobo-5N2: Unknown error
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
/mnt/Public6             : already mounted
mount.cifs: bad UNC (/drobo-e/Public)
/mnt/extra               : already mounted
/proc                    : already mounted
swap                     : ignored
[root@localhost rod]#


Oddly, for the UNC entry, the mount has completed and there appears to be no problem. I have tWO more Drives to add, i'll see whetter these have problems

[benmc]

Code: Select all

#//drobo-5N2/Public /mnt/Public3 cifs vers=1.0,uid=rod,gid=rod,credentials=/etc/samba/aith.drobo 0 0

maybe a "fat-finger" issue.

possible fix?

Code: Select all

#//drobo-5N2/Public /mnt/Public3 cifs vers=1.0,uid=rod,gid=rod,credentials=/etc/samba/auth.drobo 0 0

[rodgoslin]

Lol. Yes, fixed that one. Should have taken my gloves off!

[rodgoslin]

And the single slash at the start of a line!

[benmc]

if all good,

please edit your OP by prepending with [Solved]

TIA

Note: I don't use networking AT ALL, so by chance noted the "fat-finger" error.

[rodgoslin]

Finally have all required mounts made. The last was a bit more difficult. It did not want the extra option, which enabled the others. Removing the 'ver=... option , and it was a successful mount.. So, the issue is now closed.
Thank you all for your help