Migration from Vero 4K to Vero 5

Help and Support Vero V
66

Did you do mkdir /mnt/AVOIR?

67

now yess (sorry for my very low skills )

osmc@osmcvero5:~$ mount -t cifs -o username=XXX,password=yyy,iocharset=utf8,uid=osmc,gid=osmc //192.168.1.50/avoir /mnt/avoir

mount.cifs: permission denied: no match for /mnt/avoir found in /etc/fstab

68

Apologies need to put sudo infront so sudo mount -t cifs -o username=XXX,password=yyy,iocharset=utf8,uid=osmc,gid=osmc //192.168.1.50/avoir /mnt/avoir

But I really do not understand why you are using lower cap avoir where I clearly have said to use captial case AVOIR.

69

osmc@osmcvero5:~$ sudo mount -t cifs -o username=XXX,password=ZZZ,iocharset=utf8,uid=osmc,gid=osmc //192.168.1.50/avoir /mnt/avoir
mount error: Server abruptly closed the connection.
This can happen if the server does not support the SMB version you are trying to use.
The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0.
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

osmc@osmcvero5:~$ ping 192.168.1.50
PING 192.168.1.50 (192.168.1.50): 56 data bytes
64 bytes from 192.168.1.50: seq=0 ttl=128 time=1.150 ms
64 bytes from 192.168.1.50: seq=1 ttl=128 time=0.873 ms
64 bytes from 192.168.1.50: seq=2 ttl=128 time=0.877 ms
64 bytes from 192.168.1.50: seq=3 ttl=128 time=0.923 ms
^C
— 192.168.1.50 ping statistics —
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 0.873/0.955/1.150 ms

70

and in same time i did a nmap :
osmc@osmcvero5:~$ nmap --script smb-protocols 192.168.1.50
Starting Nmap 7.80 ( https://nmap.org ) at 2025-04-17 18:07 CEST
Nmap scan report for ordi-salon.home (192.168.1.50)
Host is up (0.79s latency).
Not shown: 994 closed ports
PORT STATE SERVICE
22/tcp open ssh
135/tcp open msrpc
139/tcp open netbios-ssn
445/tcp open microsoft-ds
1236/tcp filtered bvcontrol
5357/tcp open wsdapi

Host script results:
| smb-protocols:
| dialects:
| 2.02
| 2.10
| 3.00
| 3.02
|_ 3.11

Nmap done: 1 IP address (1 host up) scanned in 9.10 seconds
osmc@osmcvero5:~$

71

While I find this strange especially if you haven’t changed anything on your Windows machine, you can try with vers=1.0 but not sure if it makes a difference.

sudo mount -t cifs -o vers=1.0,username=XXX,password=ZZZ,iocharset=utf8,uid=osmc,gid=osmc //192.168.1.50/avoir /mnt/avoir

While I am still confused about your ignorance of the uper case of your share name (while it might not make a difference it surely doesn’t harm to follow

72

osmc@osmcvero5:~$ sudo mount -t cifs -o vers=1.0,username=xxx,password=zzz,iocharset=utf8,uid=osmc,gid=osmc //192.168.1.50/avoir /mnt/avoir
mount error: Server abruptly closed the connection.
This can happen if the server does not support the SMB version you are trying to use.
The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0.
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

73

Sorry I am out of ideas. Surely something wrong.

74

I have tryed with other vero4K i have with no update (it’s a release 2024) and the is no latency… I belevied it’s occur when i update on march 2025 release (i have several Vero 4K and one Vero 5).

I have this problem on all 2025 release and NOT with 2024 one…

75

Does

mkdir /mnt/AVOIR
mount -t cifs -o username=your_username,password=your_password,iocharset=utf8,uid=osmc,gid=osmc //192.168.1.50/AVOIR /mnt/AVOIR
ls -lah /mnt/AVOIR

work on that device?

76

Hello, i have (same after disabling all firewall) :

osmc@osmc:~$ sudo mount -t cifs -o username=YYY,password=XXX,iocharset=utf8,uid=osmc,gid=osmc //192.168.1.50/AVOIR /mnt/AVOIR

mount error: Server abruptly closed the connection.
This can happen if the server does not support the SMB version you are trying to use.
The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0.
mount error(112): Host is down
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
osmc@osmc:~$

77

Ok, while this is still super strange and might still also be source of your issue let’s focus why the old version might work while the new one doesn’t. Suggest to provide debug enabled logs from the working and not working system.

To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.

Depending on the used skin you have to set the settings-level to standard or higher, in summary:

  • enable debug logging at settings->system->logging

  • reboot the OSMC device twice(!)

  • reproduce the issue

  • upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A

  • publish the provided URL from the log set upload, here

Thanks for your understanding. We hope that we can help you get up and running again shortly.

OSMC skin screenshot:

image
image960×539 41.4 KB