У меня проблема с двумя серверами Proxmox, которые имеют удаленные монтирования на два разных NAS (TrueNAS и Unraid). Все работало прекрасно. Я настроил это так, что если один NAS недоступен, мои контейнеры LXC, такие как Plex, Jellyfin, arrs и т.д., все равно могут работать, потому что у меня есть копия, указывающая на каждый NAS. Я внес изменения в сеть на TrueNAS, которые потребовали изменения IP-адресов. Я использовал `umount` для размонтирования SMB-шар, чтобы создать точку монтирования заново, но с другим IP-адресом для NAS. Один сервер был в порядке, но на другом я не могу смонтировать SMB-шары TrueNAS вручную или через графический интерфейс. Ошибка, которую я получаю, кажется ложной. Я потратил на это более 10 часов и подумываю просто перетереть Proxmox и начать заново, но решил спросить, может быть, у кого-то есть какие-то идеи, какие еще шаги я могу предпринять, чтобы найти первопричину этой проблемы.
Команда и результирующая ошибка:
```
root@pve3:~# mount -t cifs -o user=myusername,uid=100000,gid=100000 //192.168.30.182/movies /mnt/pve/smashy-movies -v
```
```
Password for myusername@//192.168.30.182/movies:
```
```
mount.cifs kernel mount options: ip=192.168.30.182,unc=\\192.168.30.182\movies,uid=100000,gid=100000,user=myusername,pass=********
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) Here is the relevant output from dmesg [ 1954.434152] CIFS: Attempting to mount //192.168.30.181/movies [ 1976.169960] CIFS: VFS: cifs_mount failed w/return code = -112 [ 5260.583030] perf: interrupt took too long (2504 > 3130), lowering kernel.perf_event_max_sample_rate to 79000 [ 7786.775036] perf: interrupt took too long (3148 > 3130), lowering kernel.perf_event_max_sample_rate to 63000 [19013.942340] perf: interrupt took too long (3944 > 3935), lowering kernel.perf_event_max_sample_rate to 50000 [45411.107844] CIFS: VFS: Autodisabling the use of server inode numbers on \\192.168.30.170\unraiddata [45411.107849] CIFS: VFS: The server doesn't seem to support them properly or the files might be on different servers (DFS) [45411.107849] CIFS: VFS: Hardlinks will not be recognized on this mount. Consider mounting with the "noserverino" option to silence this message. [77321.249424] CIFS: enabling forceuid mount option implicitly because uid= option is specified [77321.249427] CIFS: enabling forcegid mount option implicitly because gid= option is specified [77321.249428] CIFS: Attempting to mount //192.168.30.182/movies [77342.809337] CIFS: VFS: cifs_mount failed w/return code = -112 [83370.085175] CIFS: enabling forceuid mount option implicitly because uid= option is specified [83370.085179] CIFS: enabling forcegid mount option implicitly because gid= option is specified [83370.085180] CIFS: Attempting to mount //192.168.30.182/movies [83391.515133] CIFS: VFS: cifs_mount failed w/return code = -112 [83584.911092] CIFS: enabling forceuid mount option implicitly because uid= option is specified [83584.911097] CIFS: enabling forcegid mount option implicitly because gid= option is specified [83584.911098] CIFS: Attempting to mount //192.168.30.182/movies [83606.552890] CIFS: VFS: cifs_mount failed w/return code = -112 What I have tried so far 1. Tried mounting from GUI - Not possible 2. Tried enabling SMB1 and connecting - Didn't work 3. Tried specifying SMB1, SMB 2.0, SMB 2.1, and SMB 3.0 when mounting - Same error 4. Restarting SMB service and restarting NAS, and restarting the Proxmox host - No luck 5. Pinging the NAS from the host and from LXC containers - it responds immediately 6. Deleted and recreated the directories I want to mount - No change All I did was to unmount and then go straight back and manually mount like a minute later so there aren't a whol;e lot of changes where I can think of that could cause this. The other server used the same commands exactly. In fact, I documented each step in my wiki and just copy and pasted after it worked on one, to the other so all the names and mounts would be the same. Any ideas of что I could try in order to pinpoint where the issue might lie are greatly appreciated.
Команда и результирующая ошибка:
```
root@pve3:~# mount -t cifs -o user=myusername,uid=100000,gid=100000 //192.168.30.182/movies /mnt/pve/smashy-movies -v
```
```
Password for myusername@//192.168.30.182/movies:
```
```
mount.cifs kernel mount options: ip=192.168.30.182,unc=\\192.168.30.182\movies,uid=100000,gid=100000,user=myusername,pass=********
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) Here is the relevant output from dmesg [ 1954.434152] CIFS: Attempting to mount //192.168.30.181/movies [ 1976.169960] CIFS: VFS: cifs_mount failed w/return code = -112 [ 5260.583030] perf: interrupt took too long (2504 > 3130), lowering kernel.perf_event_max_sample_rate to 79000 [ 7786.775036] perf: interrupt took too long (3148 > 3130), lowering kernel.perf_event_max_sample_rate to 63000 [19013.942340] perf: interrupt took too long (3944 > 3935), lowering kernel.perf_event_max_sample_rate to 50000 [45411.107844] CIFS: VFS: Autodisabling the use of server inode numbers on \\192.168.30.170\unraiddata [45411.107849] CIFS: VFS: The server doesn't seem to support them properly or the files might be on different servers (DFS) [45411.107849] CIFS: VFS: Hardlinks will not be recognized on this mount. Consider mounting with the "noserverino" option to silence this message. [77321.249424] CIFS: enabling forceuid mount option implicitly because uid= option is specified [77321.249427] CIFS: enabling forcegid mount option implicitly because gid= option is specified [77321.249428] CIFS: Attempting to mount //192.168.30.182/movies [77342.809337] CIFS: VFS: cifs_mount failed w/return code = -112 [83370.085175] CIFS: enabling forceuid mount option implicitly because uid= option is specified [83370.085179] CIFS: enabling forcegid mount option implicitly because gid= option is specified [83370.085180] CIFS: Attempting to mount //192.168.30.182/movies [83391.515133] CIFS: VFS: cifs_mount failed w/return code = -112 [83584.911092] CIFS: enabling forceuid mount option implicitly because uid= option is specified [83584.911097] CIFS: enabling forcegid mount option implicitly because gid= option is specified [83584.911098] CIFS: Attempting to mount //192.168.30.182/movies [83606.552890] CIFS: VFS: cifs_mount failed w/return code = -112 What I have tried so far 1. Tried mounting from GUI - Not possible 2. Tried enabling SMB1 and connecting - Didn't work 3. Tried specifying SMB1, SMB 2.0, SMB 2.1, and SMB 3.0 when mounting - Same error 4. Restarting SMB service and restarting NAS, and restarting the Proxmox host - No luck 5. Pinging the NAS from the host and from LXC containers - it responds immediately 6. Deleted and recreated the directories I want to mount - No change All I did was to unmount and then go straight back and manually mount like a minute later so there aren't a whol;e lot of changes where I can think of that could cause this. The other server used the same commands exactly. In fact, I documented each step in my wiki and just copy and pasted after it worked on one, to the other so all the names and mounts would be the same. Any ideas of что I could try in order to pinpoint where the issue might lie are greatly appreciated.
