Installed:
samba-4.14.11.1-mga8.x86_64, cifs-utils-6.11-2.1.mga8.x86_64

However, #cat /proc/filesystems does not list cifs
and
#lsmod|grep cifs
cifs_md4 16384 0

(Sorry: a bit of line folding here)
Trying to mount manually fails
# mount -t cifs
credentials=/etc/samba/auth.192.168.1.6.graeme,vers=1.0,noserverino,defaults
//192.168.1.6/data /mnt/nasdata
mount: bad usage

Whereas a machine that has access to //192.168.1.6/data has:
#cat /proc/filesystems|grep cifs
nodev cifs
and

#lsmod|grep cifs
cifs 1236992 2
cifs_arc4 16384 1 cifs
cifs_md4 16384 1 cifs
and the fstab entry is
//192.168.1.6/data /mnt/nasdata cifs
credentials=/etc/samba/auth.192.168.1.6.graeme,vers=1.0 0 0

It seems that some package is missing but I can't work out what.
--
Grimble
Machine 'Haydn' running Plasma 5.20.4 on 5.15.10-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64

On Sun, 02 Jan 2022 09:21:01 -0500, Grimble <grimble@nomail.afraid.org> wrote:

> Installed:
> samba-4.14.11.1-mga8.x86_64, cifs-utils-6.11-2.1.mga8.x86_64
>
> However, #cat /proc/filesystems does not list cifs
> and
> #lsmod|grep cifs
> cifs_md4 16384 0
>
> (Sorry: a bit of line folding here)
> Trying to mount manually fails
> # mount -t cifs
> credentials=/etc/samba/auth.192.168.1.6.graeme,vers=1.0,noserverino,defaults
> //192.168.1.6/data /mnt/nasdata
> mount: bad usage
>
> Whereas a machine that has access to //192.168.1.6/data has:
> #cat /proc/filesystems|grep cifs
> nodev cifs
> and
>
> #lsmod|grep cifs
> cifs 1236992 2
> cifs_arc4 16384 1 cifs
> cifs_md4 16384 1 cifs
> and the fstab entry is
> //192.168.1.6/data /mnt/nasdata cifs
> credentials=/etc/samba/auth.192.168.1.6.graeme,vers=1.0 0 0
>
> It seems that some package is missing but I can't work out what.

Is it running the latest kernel? There was a regression that slipped through, that
has been fixed ...
https://bugs.mageia.org/show_bug.cgi?id=29641#c45

Regards, Dave Hodgins

On 02/01/2022 19:49, David W. Hodgins wrote:
> On Sun, 02 Jan 2022 09:21:01 -0500, Grimble <grimble@nomail.afraid.org>
> wrote:
>
SNIP
>
> Is it running the latest kernel? There was a regression that slipped
> through, that
> has been fixed ...
> https://bugs.mageia.org/show_bug.cgi?id=29641#c45
>
> Regards, Dave Hodgins
Oh dear, time to reopen the catalogue of woes. I had downloaded 5.15.11
but hadn't rebooted. When I did, I got dumped into emergency mode
(either when doing level 5 or level 3). Xorg.0.log contains a message
every 10 seconds:
dbus-core: error connecting to system bus
Googled this: Is dbus service running? No it isn't, bet when I start it,
the system reverts to the emergency screen with a locked-up system.
Plasma working OK with root log-in
Wanted to change/install a different DM, but can't get into MCC either
from the launcher or the icon on the bottom screen bar.

What do I need to get the network up? I've done
systemctl stas systemd-networkd.service and
systemctl start systemd-resolved.service.
If I can get access to my data, at least I can do some important
start-of-year processing. I suppose I need dbus running to do anything. BAH!
--
Grimble
Registered Linux User #450547
Machine 'Bach' running Plasma 5.20.4 on 5.15.6-desktop-2.mga8 kernel.
Mageia release 8 (Official) for x86_64

On 2022-01-03, Grimble <grimble@nomail.afraid.org> wrote:
> On 02/01/2022 19:49, David W. Hodgins wrote:
>> On Sun, 02 Jan 2022 09:21:01 -0500, Grimble <grimble@nomail.afraid.org>
>> wrote:
>>
> SNIP
>>
>> Is it running the latest kernel? There was a regression that slipped
>> through, that
>> has been fixed ...
>> https://bugs.mageia.org/show_bug.cgi?id=29641#c45
>>
>> Regards, Dave Hodgins
> Oh dear, time to reopen the catalogue of woes. I had downloaded 5.15.11
> but hadn't rebooted. When I did, I got dumped into emergency mode

So, boot a different kernel. I do hope that you did not erase all prior
kernels when you you installed 5.15.11
That is ALWAYS a bad idea. Always make sure that your new kernel is
working before erasing all the older kernels.
And never follow the advice to remove all orphaned packages. You will
almost certainly destroy your installation. The test for what is an
orphaned package leaves something to be desired.

> (either when doing level 5 or level 3). Xorg.0.log contains a message
> every 10 seconds:
> dbus-core: error connecting to system bus
> Googled this: Is dbus service running? No it isn't, bet when I start it,
> the system reverts to the emergency screen with a locked-up system.
> Plasma working OK with root log-in

I am confused. You say you were dumped into emergency but then that
Plasma works with root login.

> Wanted to change/install a different DM, but can't get into MCC either
> from the launcher or the icon on the bottom screen bar.

You can always type mcc into a terminal.

>
> What do I need to get the network up? I've done
> systemctl stas systemd-networkd.service and
> systemctl start systemd-resolved.service.
> If I can get access to my data, at least I can do some important
> start-of-year processing. I suppose I need dbus running to do anything. BAH!

On 03/01/2022 18:55, William Unruh wrote:
> On 2022-01-03, Grimble <grimble@nomail.afraid.org> wrote:
>> On 02/01/2022 19:49, David W. Hodgins wrote:
>>> On Sun, 02 Jan 2022 09:21:01 -0500, Grimble <grimble@nomail.afraid.org>
>>> wrote:
>>>
>> SNIP
>>>
>>> Is it running the latest kernel? There was a regression that slipped
>>> through, that
>>> has been fixed ...
>>> https://bugs.mageia.org/show_bug.cgi?id=29641#c45
>>>
>>> Regards, Dave Hodgins
>> Oh dear, time to reopen the catalogue of woes. I had downloaded 5.15.11
>> but hadn't rebooted. When I did, I got dumped into emergency mode
>
> So, boot a different kernel. I do hope that you did not erase all prior
> kernels when you you installed 5.15.11
> That is ALWAYS a bad idea. Always make sure that your new kernel is
> working before erasing all the older kernels.
> And never follow the advice to remove all orphaned packages. You will
> almost certainly destroy your installation. The test for what is an
> orphaned package leaves something to be desired.

Makes no difference, William, tried 5.15.10 and 5.10.16, recovery mode,
level 3: always ends in emergency mode. I believe the problem lies in
setting up the user (i.e. my) graphic environment. As I said (below, to
your confusion), I can enter startx as root and up comes a beautiful
Mageia screen with the usual basic icons on the bottom line.

>> (either when doing level 5 or level 3). Xorg.0.log contains a message
>> every 10 seconds:
>> dbus-core: error connecting to system bus
>> Googled this: Is dbus service running? No it isn't, bet when I start it,
>> the system reverts to the emergency screen with a locked-up system.
>> Plasma working OK with root log-in
>
> I am confused. You say you were dumped into emergency but then that
> Plasma works with root login.
>

See above

>> Wanted to change/install a different DM, but can't get into MCC either
>> from the launcher or the icon on the bottom screen bar.
>
> You can always type mcc into a terminal.
>

If I type mcc in at erminal, I get Error getting authority: Error
initialising authority: could not connect: no such file or directory
(/root/.config/gtk-3.0/window-decorations.css)

>>
>> What do I need to get the network up? I've done
>> systemctl stas systemd-networkd.service and
>> systemctl start systemd-resolved.service.
>> If I can get access to my data, at least I can do some important
>> start-of-year processing. I suppose I need dbus running to do anything. BAH!
I just found I could use Network Centre to start the network. Pinging
works, but when I tried to download some updates, Plasma aborted and
threw me back to the emergency mode screen, but with a frozen system
(doesn't even respond to Ctl/Shift/Del)

--
Grimble
Registered Linux User #450547
Machine 'Bach' running Plasma 5.20.4 on 5.15.6-desktop-2.mga8 kernel.
Mageia release 8 (Official) for x86_64

On 2022-01-04, Grimble <grimble@nomail.afraid.org> wrote:
> On 03/01/2022 18:55, William Unruh wrote:
>> On 2022-01-03, Grimble <grimble@nomail.afraid.org> wrote:
>>> On 02/01/2022 19:49, David W. Hodgins wrote:
>>>> On Sun, 02 Jan 2022 09:21:01 -0500, Grimble <grimble@nomail.afraid.org>
>>>> wrote:
>>>>
>>> SNIP
>>>>
>>>> Is it running the latest kernel? There was a regression that slipped
>>>> through, that
>>>> has been fixed ...
>>>> https://bugs.mageia.org/show_bug.cgi?id=29641#c45
>>>>
>>>> Regards, Dave Hodgins
>>> Oh dear, time to reopen the catalogue of woes. I had downloaded 5.15.11
>>> but hadn't rebooted. When I did, I got dumped into emergency mode
>>
>> So, boot a different kernel. I do hope that you did not erase all prior
>> kernels when you you installed 5.15.11
>> That is ALWAYS a bad idea. Always make sure that your new kernel is
>> working before erasing all the older kernels.
>> And never follow the advice to remove all orphaned packages. You will
>> almost certainly destroy your installation. The test for what is an
>> orphaned package leaves something to be desired.
>
> Makes no difference, William, tried 5.15.10 and 5.10.16, recovery mode,
> level 3: always ends in emergency mode. I believe the problem lies in
> setting up the user (i.e. my) graphic environment. As I said (below, to
> your confusion), I can enter startx as root and up comes a beautiful
> Mageia screen with the usual basic icons on the bottom line.

So, it is not a problem with the latest kernel.

In emergency mode, go into /boot/grub2/grub.cfg file and in the first
entry, look for
linux /boot/vmlinuz-5.15.11-desktop.....
line, and remove the quiet and splash options from that line and save
it. That way yo u will be able to see what the system is doing befor it
dumps you into emergency mode.

Or as soon as you see the spash screen, hit esc to see what is
happening.

I have no idea when you enter startx as root. When you are in emergency
mode? It is no wonder that is problematic.

>
>
>>> (either when doing level 5 or level 3). Xorg.0.log contains a message
>>> every 10 seconds:
>>> dbus-core: error connecting to system bus
>>> Googled this: Is dbus service running? No it isn't, bet when I start it,
>>> the system reverts to the emergency screen with a locked-up system.
>>> Plasma working OK with root log-in
>>
>> I am confused. You say you were dumped into emergency but then that
>> Plasma works with root login.
>>
>
> See above
>
>>> Wanted to change/install a different DM, but can't get into MCC either
>>> from the launcher or the icon on the bottom screen bar.
>>
>> You can always type mcc into a terminal.
>>
>
> If I type mcc in at erminal, I get Error getting authority: Error
> initialising authority: could not connect: no such file or directory
> (/root/.config/gtk-3.0/window-decorations.css)
>
>>>
>>> What do I need to get the network up? I've done
>>> systemctl stas systemd-networkd.service and
>>> systemctl start systemd-resolved.service.
>>> If I can get access to my data, at least I can do some important
>>> start-of-year processing. I suppose I need dbus running to do anything. BAH!
> I just found I could use Network Centre to start the network. Pinging
> works, but when I tried to download some updates, Plasma aborted and
> threw me back to the emergency mode screen, but with a frozen system
> (doesn't even respond to Ctl/Shift/Del)
>