roms on NAS - feature doesn't work?

tomeq

Hi,

I tried to mount my roms dir located on NAS. It looked fairly easy - editing recalbox-boot.conf with:
sharedevice=NETWORK
sharenetwork_smb1=ROMS@192.168.1.131:storage/ROMs:username=tomek,password=somepass
sharenetwork_smb2=BIOS@192.168.1.131:storage/ROMs/bios:username=tomek,password=somepass

System is reachable both ways in the networks, so here is not an issue.

and then reboot. What should I expect? 🙂 As nothing has changed in the ES. Refreshing games list doesn't help.

I also tried to mount using name instead of IP - no change. Are there any special magic to be done to mount external directories? Frankly, this method is very cryptic. Why don't just use normal samba shares and point ES to these shares?

If you need any logs/debugs just let me know. Thanks!

Tomek

sooprtruffaut

Hello, have you seen this page? https://batocera-linux.xorhub.com/wiki/doku.php?id=en:store_games_on_a_nas

I followed this and was able to get everything set up. I find that if I set this up on a new image, I need to start the system, then power down, edit recalbox-boot.conf with details from my network, then when I power batocera back on, the ROMS show up in ES from the NAS. Make sure you have the correct address to the ROM folder as well.

It's worth trying with NFS, provided your NAS is set up to use it. (should be if it's a decent model.)

tomeq

sooprtruffaut
Yes, I followed this page but it just doesn't work at all, no matter if I used IP or dns name. I get CIFS errors in /var/log/messages (error code -101) - I suppose it tries to mount CIFS shares before network is really up. I tried to increase sleep timers in init.d scripts - no help.

NFS - yes, my nas supports it as it is custom built 😉 maybe I'll try it later.

The only soultion I found is to manually mount cifs shares and "overmount" on /recalbox/share/roms dir

Logs:
[ 9.283587] CIFS VFS: Error connecting to socket. Aborting operation.
[ 9.283662] CIFS VFS: cifs_mount failed w/return code = -101
[ 13.290515] CIFS VFS: Error connecting to socket. Aborting operation.
[ 13.290591] CIFS VFS: cifs_mount failed w/return code = -101
[ 17.297136] CIFS VFS: Error connecting to socket. Aborting operation.
[ 17.297215] CIFS VFS: cifs_mount failed w/return code = -101
[ 21.303560] CIFS VFS: Error connecting to socket. Aborting operation.
[ 21.303641] CIFS VFS: cifs_mount failed w/return code = -101

sooprtruffaut

tomeq If Samba isn't working then try NFS. I've had no issues with it, setting things up the way I mentioned. Good luck with it

EmmersoN

Hello, thank you very much for this great project.

I have the same problem after the update from 5.11 (x86 32 bits) to 5.12 or 5.13 the connection to the NAS doesn't work anymore..

My NAS is a Fritz.Box 3490 which doesn't support NFS.

LOG:
Feb 5 19:32:20 batocera user.warn kernel: [ 6.815686] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or
Feb 5 19:32:20 batocera user.err kernel: [ 6.834405] CIFS VFS: Error connecting to socket. Aborting operation.
Feb 5 19:32:20 batocera user.err kernel: [ 6.834416] CIFS VFS: cifs_mount failed w/return code = -101

Feb 5 19:32:24 batocera user.warn kernel: [ 10.861881] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or
Feb 5 19:32:24 batocera user.err kernel: [ 11.096489] CIFS VFS: cifs_mount failed w/return code = -112
Feb 5 19:32:28 batocera user.warn kernel: [ 15.124279] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or
Feb 5 19:32:28 batocera user.err kernel: [ 15.359541] CIFS VFS: cifs_mount failed w/return code = -112
Feb 5 19:32:32 batocera user.warn kernel: [ 19.387042] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or
Feb 5 19:32:33 batocera user.err kernel: [ 19.619783] CIFS VFS: cifs_mount failed w/return code = -112
Feb 5 19:32:37 batocera user.warn kernel: [ 23.647405] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or
Feb 5 19:32:37 batocera user.err kernel: [ 23.882573] CIFS VFS: cifs_mount failed w/return code = -112

recalbox-boot:
sharedevice=NETWORK
sharenetwork_smb1=ROMS@192.168.100.10:nas/hdd/emu/roms:username=root,password=linux
sharenetwork_smb2=SAVES@192.168.100.10:nas/hdd/emu/saves:username=root,password=linux
sharenetwork_smb3=BIOS@192.168.100.10:nas/hdd/emu/bios:username=root,password=linux

Please help us find a solution

translated by deepl.com

EmmersoN

Okay, I found the solution.

I have added the parameter vers=1.0

For example:
sharenetwork_smb1=ROMS@192.168.100.10:nas/hdd/emu/roms:username=root,password=linux,vers=1.0