That doesn't matter. If you tried to login with the pi user and the user was not in the _ssh group (or you entered an incorrect password), the system would temporarily lock the account.
As shown in the screenshot above, the pi user was already in the _ssh group - I did not add it.
Anyways - it all seems to be working
Thanks again to all for your patient answering of my questions and explanations etc. I definitely learned something.
But I didn't make any changes to the pi user
Plus even after I created the pir2 user and added it to _ssh, it also failed - despite me using the correct password.
Also, I noticed the ports are different 55841 Vs 62289.
I would be interested in understanding the difference.
Thanks again for all the replies - much appreciated. Cheers!
Completely and utterly bizarre...
Left my MacBook on last night - with the terminal window open , Pi still running.
No changes at my end - nothing...
Tried just logging in again now..
Both pi and pir2 login OK now - same password etc.
I don't suppose anyone can explain what happened?
In terms of auth logs, this was yesterday:
30/12/2024, 18:19:24
sshd[22546]: Failed password for invalid user pi from 192.168.2.10 port 55841 ssh2
30/12/2024, 18:19:23
sshd[22546]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.2.10 user=pi
30/12/2024, 18:19:18
sshd[22546]: User pi from 192.168.2.10 not allowed because none of user's groups are listed in AllowGroups
and this is now:
31/12/2024, 13:38:16
systemd-logind[589]: New session 1295 of user pi.
31/12/2024, 13:38:16
sshd[24190]: pam_unix(sshd:session): session opened for user pi(uid=1000) by (uid=0)
31/12/2024, 13:38:16
sshd[24190]: Accepted password for pi from 192.168.2.10 port 62289 ssh2
As mentioned previously, I did not make any changes to the pi user - as per the screenshot last night, it was already showing as member of _ssh group.
Nope, can't ssh with pi.
Any other way of getting at the sshd_config file?
Hi,
I added pir2 and added this user to groups _ssh and sudo. I then tried to login as pir2 as pasted above:
~ % ssh pir2@192.168.2.29
pir2@192.168.2.29's password:
Permission denied, please try again.
pir2@192.168.2.29's password:
Permission denied, please try
Didn't bother screenshot of pir2. I included the pi user as the UI claims pi is already in _ssh?
Hi gderf and ryecoaaron
I added a new user pir2 and added this user to groups _ssh and sudo.
I saved the changes and applied the change button in the top right of the WebUI.
However, I still cannot ssh to it:
~ % ssh pir2@192.168.2.29
pir2@192.168.2.29's password:
Permission denied, please try again.
pir2@192.168.2.29's password:
Permission denied, please try again.
pir2@192.168.2.29's password:
I am definitely typing the right password - kept it simple for test purposes.
Also, I checked the Groups and the SSH settings and shown in the attachments.
Thanks for the confirmation.
Just one thing puzzles me, why was it working fine prior to the OMV7 upgrade?
Can you please help me understand?
Is the _ssh group something new to OMV7 and if not, why has the upgrade affected my standard PI environment in this way?
Thanks
thanks ryecoaaron
I will try your suggestions - but before I do, I looked at the Authentication logs in the Webgui and see the following:
30/12/2024, 18:19:24
sshd[22546]: Failed password for invalid user pi from 192.168.2.10 port 55841 ssh2
30/12/2024, 18:19:23
sshd[22546]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.2.10 user=pi
30/12/2024, 18:19:18
sshd[22546]: User pi from 192.168.2.10 not allowed because none of user's groups are listed in AllowGroups
Does this corrobrate your post above? Should I still try what you suggested, or is there something more appropriate based on the above...
Thanks!
Hi askbimal
Did you manage to resolve this?
I also upgraded to OMV7 on my Rasp Pi4 using pretty much the same commands as you listed above.
I initially could not login to the Webui - but I tried the following and I can now login to the WebUI:
sudo omv-salt deploy run nginx phpfpm
sudo systemctl restart nginx
sudo systemctl restart php8.2-fpm
However, I still cannot ssh into the Pi - have tried ssh in as pi, admin and root - just says
'Permission denied, please try again.'
I even tried the admin + password I use for the WebUI - but it won't work with SSH.
I have a backup of the microSD card - so I can revert back to OMV6 - but I would prefer to use OMV7 - which appears to be working fine.
ryecoaaron - I checked in the WebUI and I have 600GB+ disk space free...
thanks in advance for any help!
Hi mucriva
I have been getting very similar errors on my OMV for the past few months - whenever I tried to apply the updates.
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color systemd-networkd 2>&1' with exit code '1': RPI:
I am not a CLI guy either - pretty much a Windows person.
But I did some more digging today and I noticed the following in my OMV error log and found the key error for me was the following:
A dependency job for netplan-wpa-wlan0.service failed. See 'journalctl -xe' for details.
Traceback (most recent call last):
File "/sbin/netplan", line 23, in <module>
...
....
subprocess.CalledProcessError: Command '['systemctl', 'start', 'systemd-networkd.service', 'netplan-wpa-wlan0.service', 'netplan-ovs-cleanup.service']' returned non-zero exit status 1.
I did some more digging for the above wlan related errors, and then eventually remembered I had disabled the Wifi on my PI using the config.txt file using
dtoverlay=disable-wifi
and thought it would be worth enabling it back again to see what happened.
I commented out the above line, rebooting the pi and now the OMV updates apply successfully.
Obviously, the above is not the same as your problem - but googling the actual error message below the 'A dependency job for xxx failed' might help you get to the bottom of it.
Good Luck
Hi wrdmail123
I still don't fully understand this, but when accessing OMV Samba shares from Windows, I found sometimes that manually adding the Windows username as a samba user seems to help ..
Hi crashtest
It was a completely new install of Windows 11 - no upgrade - starting from blank disk.
Thanks - and no worries.
I just wanted to share my workaround/fix as above in case it helped others.
Hi crashtest
I created a Windows 11 USB installation disk from the official Microsoft download page and installed onto a clean formatted SSD.
https://www.microsoft.com/en-gb/software-download/windows11
And the version is Windows 11 Pro 21H2
Hi crashtest
thanks for the reply.
I fully agree about the dangers of using the pi username. That was just for demo/screenshot purposes.
I actually used a a personal user name which I had created in OMV previously - I have created different usernames for various family members as per then need to access the various samba shares.
The point of my post was how entering the username and password into Credentials manager was the only way to see the shares under RPI in Windows or map a folder to any of them etc. This was very weird - because I did not have to do this on other PCs in the home - a mixture of Win10 and Win11 devices.
Also - thanks once again for the great work on the forum and OMV. Allowed me to replace a power hunger and noisy QNAP with an RPI+SSD - low powered silent bliss..
Hi crashtest
Thanks for putting the great Connect to OMV with Windows 10 guide together.
I recently had to rebuild a Windows 11 laptop after the boot drive got messed up.
So, I followed your guide - and recognised several of the steps I had tried in previous attempts to get this laptop and others to connect to OMB Samba shares - so it was great to see them all in one place - thanks.
However, despite going to every possible step in your Connect W10 document, I still could not get this laptop to connect.
My RPI server appeared under Network just fine, but when tried to
I would just get the following Windows Popup error - I could not even see the samba shares. On previous computers, I could see the shares, but when I then tried to click on the shares, I would get issue - but here I could not even get as far as seeing the shares.
Network Error
Windows cannot access \\192.168.2.28 (or RPI etc)
Check the spelling of the name. Otherwise, there might be a problem with your network. To try to identify and resolve network problems, click Diagnose.
Error code: 0x80004005
Unspecified error
Off course Diagnose did nothing useful.
In the end, out of sheer desperation, I just thought I would check the Windows Credential manager - because I know I had previously had issues on another PC with saved credentials for the same IP address - even though this was complete re-install of Win 11!!
As you may know the Credential manager can be run by executing
rundll32.exe keymgr.dll, KRShowKeyMgr
in the Run dialog or command prompt etc
I confirmed there were no stored credentials (as you would expect) and then decided to manually add some credentials here for the RPI
Clicked OK, and Close - went back to File Explorer and hey presto RPI was now fully browsable and accessible. Hurrah!!
Just to be Clear - I do NOT recommend using the pi username here - its just for demo purposes. This should also work with other user accounts you have created on OMV.
Perhaps you could consider adding the above to the guide - in case it helps others?
The above Credential manager is also useful for deleting stored credentials - an issue I had on a different PC, when I initially connected to my RPI using a username with read-only samba privileges and I still could not get write-access even when I tried to connect again user a fully permissioned user name!. Once I deleted the read-only credentials from the Credential store, I was then able to access using the other username.
Hi Zoki
Thanks - that seems to have done - it was showing as inactive / not loaded, so I did
systemctl enable systemd-networkd-wait-online
ystemctl start systemd-networkd-wait-online
rebooted and the automount worked.
Thank you!
Hi all,
Apologies if this is not an OMV issue and rather a generic Linux issue but I am a relative Linux noob - so not really sure....
I have OMV 6.0.5-3 running on a Raspberry PI4 and I can access the SMB shares just fine from Windows and my Kodi software running on FireTV sticks etc.
I am trying to automount some of the SMB shares from another RPI4 but it refuses to work.
I added the mount entries to my etc/fstab file and If I execute sudo mount -a from the console that works fine.
However, upon reboot, it will not automount the shares, and I get dmesg output like:
[ 15.531618] CIFS: Attempting to mount //192.168.2.9/Downloads
[ 15.531772] CIFS: VFS: Error connecting to socket. Aborting operation.
[ 15.531792] CIFS: VFS: cifs_mount failed w/return code = -101
[ 15.533194] CIFS: Attempting to mount //192.168.2.9/Movies
[ 15.533336] CIFS: VFS: Error connecting to socket. Aborting operation.
[ 15.533351] CIFS: VFS: cifs_mount failed w/return code = -101
I have tried various combinations of entries in the fstab file e.g.
//192.168.2.9/Downloads /home/pi/RPI/Downloads cifs credentials=/home/pi/.smbcreds,uid=1000,gid=1000,_netdev 0 0
OR
//192.168.2.9/Downloads /home/pi/RPI/Downloads cifs credentials=/home/pi/.smbcreds,uid=1000,gid=1000,_netdev,x-systemd.after=network-online.target 0 0
OR
//192.168.2.9/Downloads /home/pi/RPI/Downloads cifs auto,x-systemd.automount,credentials=/home/pi/.smbcreds,vers=3.1.1,uid=1000,gid=1000 0 0
All of the above fails to automount on reboot and yet mount -a for all of the above works fine.
With the final choice above (auto,,x-systemd.automount) type entry I get systemctl status output as :
PI8G systemd[1]: Mounting /home/pi/RPI/Downloads...
PI8G mount[904]: mount error(101): Network is unreachable
PI8G mount[904]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (>
PI8G systemd[1]: home-pi-RPI-Downloads.mount: Mount process exited, code=exited, status=32/n/a
PI8G systemd[1]: home-pi-RPI-Downloads.mount: Failed with result 'exit-code'.
PI8G systemd[1]: Failed to mount /home/pi/RPI/Downloads.
PI8G systemd[1]: home-pi-RPI-Downloads.mount: Start request repeated too quickly.
PI8G systemd[1]: home-pi-RPI-Downloads.mount: Failed with result 'exit-code'.
PI8G systemd[1]: Failed to mount /home/pi/RPI/Downloads.
With others, the systemctl status output is generally
PI8G systemd[1]: Mounting /home/pi/RPI/Downloads...
PI8G mount[904]: mount error(101): Network is unreachable
PI8G mount[904]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (>
PI8G systemd[1]: home-pi-RPI-Downloads.mount: Mount process exited, code=exited, status=32/n/a
PI8G systemd[1]: home-pi-RPI-Downloads.mount: Failed with result 'exit-code'.
Can anyone please advise where I am going wrong - or should I post this on a generic Linux or RPI forum?
Thanks in advance for any help.
Just want to say - if you are part of the OMV team - thanks for such a great product.
Apart from a few minor issues with accessing the Private folder from Windows - all has been great.
I managed to resolve the above issues by applying ACL and that seems to have fixed it...
Particularly like the new OMV6 interface....
Thanks for confirming and apologies for the dumb question.
Will stick to ln
