piCorePlayer 8.2.0 - mount CIFS problem

[TomS]

I have two piCorePlayers on two different rPis - one is a pi Zero and one is a pi 3. Both have piCorePlayer 8.2.0 installed.

After upgrading both to 8.2.0, I cannot mount a remote (smb/cifs) drive on the zero player. I have the same options for mounting on both machines, but the zero refuses to mount. Perhaps I am missing an extension or something on the zero? Can anyone give a hint given the logs/info below? I have updated extensions/minor patch etc on both devices.

Edit: this is trying to mount against an Ubuntu 20.04.5 machine.

Edit2: I now realize I had this same problem when moving from 7.x to 8.0, only on the pi zero, paul- did some magic and updated something somewhere - see message here . Perhaps that fix needs to be added to 8.2 or I need to do something to update? I tried updating extensions in various ways already (command line, ui etc).

Thanks for any advice.

TomS

====================

Pi Zero (failed mount):

piCorePlayerZero | piCorePlayer v8.2.0 | www v00017 | linux 5.15.35-pcpCore (32) | piCore v13.2 | Squeezelite v1.9.9-1419-pCP

[ 47.394072] FS-Cache: Netfs 'cifs' registered for caching
[ 47.417045] Key type cifs.spnego registered
[ 47.417172] Key type cifs.idmap registered
[ 47.422101] CIFS: Attempting to mount \\192.168.5.163\pcp
[ 47.497301] CIFS: VFS: Could not allocate crypto hmac(sha256)
[ 47.543934] CIFS: VFS: Could not allocate crypto hmac(sha256)
[ 47.594140] CIFS: VFS: Could not allocate crypto hmac(md5)
[ 47.594186] CIFS: VFS: Error -2 during NTLMSSP authentication

Pi 3 (successful mount):

piCorePlayer | piCorePlayer v8.2.0 | www v00017 | linux 5.15.35-pcpCore-v7 (32) | piCore v13.2 | Squeezelite v1.9.9-1392-pCP

[ 172.967836] FS-Cache: Netfs 'cifs' registered for caching
[ 172.971387] Key type cifs.spnego registered
[ 172.971418] Key type cifs.idmap registered
[ 172.972138] CIFS: Attempting to mount \\192.168.5.163\pcp


(and this is a manual mount from UI)
[ INFO ] Mount configuration changed for 192.168.5.163:/pcp

[ INFO ] Unmounting Old Mount Point: /mnt/musicmanbackup.

[ INFO ] Checking new Mount Point /mnt/musicmanbackup.

[ INFO ] Mounting Disk.

[INFO] mount -v -t cifs -o username=xxx,password="xxxxx",uid=1001,gid=50,ver s=3.0 //192.168.5.163/"pcp" /mnt/musicmanbackup

mount: //192.168.5.163/pcp mounted on /mnt/musicmanbackup.
[ INFO ] Disk Mounted Successfully.

[d6jg]

Although both 8.2 they have different versions of Squeezelite suggesting they aren’t the same piCorePlayer build version?

[TomS]

Although both 8.2 they have different versions of Squeezelite suggesting they aren’t the same piCorePlayer build version?

yes, I saw that too. That may be b/c they are different rpi boards (? dunno) - I've done every update I could do on both systems (patch update/minor update, extensions update). I also think this is more of a linux kernel thing than a squeezelite thing - and yes I see slightly different linux versions between the two boards (pi 3 = linux 5.15.35-pcpCore-v7, pi zero linux 5.15.35-pcpCore, both 32 bit) .

[Greg Erskine]

Because we use piCore, the extension feature means certain extensions can be updated independently of the version of piCorePlayer.

In this example, Ralphy can update squeezelite and we do not need to make a new version of piCorePlayer.

Usually, the piCorePlayer image will contain the latest version of squeezelite only at the time of creation.

There are also 3 kernels, single core 32-bit, quad core 32-bit and quad core 64-bit. Each has its own repository. Somehow, Paul maintains thousands of extensions for each version piCorePlayer in these 3 repositories. Plus, there is the mirror repository server where everything is duplicated.

[Paul Webster]

I think when I saw the error
"[ 47.497301] CIFS: VFS: Could not allocate crypto hmac(sha256)"
I tried setting things up to use CIFS version that did not need hmac.
However, it depends on what can be supported by the remote file server.
From memory, SMB 1.0 uses MD5 (if any) and not HMAC.

[paul-]

The PiZero is a different processor than the Pi3. There is a missing crypto library on the piZero, normally just changing to a lower SMB protocol will solve the problem. The reason I have not fixed it, is because I cannot reproduce it in my configurations. Hmac is compiled in to the PiZero kernel, The kernel config will automatically compile in all hard dependencies for hmac. Which means it is a soft dependency. Which makes it hard to track down.

[gordonb3]

I believe there used to be a licensing issue with HMAC prohibiting this to be included in binary distributions. It is possible that some components in your system still obey this former restriction thus causing this algorithm to not be supported while at the same time other components may be configured to enforce its use. e.g. current Samba (SMB/CIFS) client and server can still do SMB 1.0 but default to ignore it. To allow communication with my Dune media player (applies to Popcorn as well) I had to add the following lines to my smb.conf:

   ntlm auth = yes
   min protocol = NT1
   client min protocol = CORE
   client use spnego = no

[TomS]

I believe there used to be a licensing issue with HMAC prohibiting this to be included in binary distributions. It is possible that some components in your system still obey this former restriction thus causing this algorithm to not be supported while at the same time other components may be configured to enforce its use. e.g. current Samba (SMB/CIFS) client and server can still do SMB 1.0 but default to ignore it. To allow communication with my Dune media player (applies to Popcorn as well) I had to add the following lines to my smb.conf:

ntlm auth = yes
min protocol = NT1
client min protocol = CORE
client use spnego = no

Thanks - I actually already had ntlm auth=yes in my smb.conf, but added client min protocol = NT1 yesterday and lowered the version in pcp to vers=1.0, but it still failed. I will try your complete 4 lines to see if that helps.

TomS

[TomS]

Thanks - I actually already had ntlm auth=yes in my smb.conf, but added client min protocol = NT1 yesterday and lowered the version in pcp to vers=1.0, but it still failed. I will try your complete 4 lines to see if that helps.

TomS

Sadly no luck with the config options you listed. Not the end of the world (just doing a backup) but will keep poking at it.

[CJS]

FYI, with my pCP 8.2.0 player on a Pi Zero I also was not able to connect to the Samba share on my Linux Mint server (using CIFS). For me the sole purpose of connecting to a network share was to be able to create an SD card backup image of pCP over the network. My workaround was to setup an NFS share on my Linux Mint 20.3 server. I could then connect to that share using the NFS protocol. In my case I needed to specify vers=4 as NFS mount option.