sorry auto piloted Ubuntu paths
Found it
HQLI-MMCMS-01:~/.config/system.d # file storage-multimedia.mount
storage-multimedia.mount: ASCII text
sorry auto piloted Ubuntu paths
Found it
HQLI-MMCMS-01:~/.config/system.d # file storage-multimedia.mount
storage-multimedia.mount: ASCII text
Some additional debug info. The NAS is (temporary) allowing SMB1 so I can get the mount to work. Interestingly the vers=1.0 must be explicitly mentioned or the mount will fail.
So, when leaving out the vers=1.0 doesn't mean that it will attempt to connect over SMB1 (and others) but simply fails again... strange!
Interestingly the vers=1.0 must be explicitly mentioned or the mount will fail.
SMB 1.0 is not activated ootb, so its no surprise that you need it
Found it
file is okay
What kind of NAS do you use ?
It is very strange overall
SMB 1.0 is not activated ootb, so its no surprise that you need it
file is okay
What kind of NAS do you use ?
It is very strange overall
my NAS is a Synology with the latest version of DSM (7.0-41890) running on it.
The strange thing is that I only have this issue on the EL running on x86_64 and not with the LE on my raspberry pi 4 (or 3). They connect by the same means to the same NAS.
that makes really no sense, I have no idea left sorry
that makes really no sense, I have no idea left sorry
No need to apologize
There are gossips that DSM 7 is not yet free of bugs so maybe??
There are gossips that DSM 7 is not yet free of bugs so maybe??
that's very much possible, but then it would fail for all LE mounts to the NAS. In my case, it only fails for the LE x86_64 version which is strange to say the least
Yeah I understand but sometimes there are very strange things between 2 specific devices / OS releases... I don't know much how SMB protocol works but I think it's a bit complex. And recently I was facing to a strange issue with LE on RPi serving files to Windows client...