From d4c4dce832f227d6dcb90cdba8f487739f798010 Mon Sep 17 00:00:00 2001 From: MacRimi <123239993+MacRimi@users.noreply.github.com> Date: Sun, 18 Oct 2026 13:47:58 +0200 Subject: [PATCH] Describe the storage sharing behaviour as the scripts run it - A local disk is registered in Proxmox only when As Proxmox storage is marked - Test NFS Connectivity checks ping, port 2049 and the export list - Proxmox keeps CIFS passwords with mode 0600, protected by access control --- web/messages/de/docs/storage-share/host-local-disk.json | 2 +- web/messages/de/docs/storage-share/host-nfs.json | 2 +- web/messages/de/docs/storage-share/host-samba.json | 2 +- web/messages/en/docs/storage-share/host-local-disk.json | 2 +- web/messages/en/docs/storage-share/host-nfs.json | 2 +- web/messages/en/docs/storage-share/host-samba.json | 2 +- web/messages/es/docs/storage-share/host-local-disk.json | 2 +- web/messages/es/docs/storage-share/host-nfs.json | 2 +- web/messages/es/docs/storage-share/host-samba.json | 2 +- web/messages/fr/docs/storage-share/host-local-disk.json | 2 +- web/messages/fr/docs/storage-share/host-nfs.json | 2 +- web/messages/fr/docs/storage-share/host-samba.json | 2 +- web/messages/it/docs/storage-share/host-local-disk.json | 2 +- web/messages/it/docs/storage-share/host-nfs.json | 2 +- web/messages/it/docs/storage-share/host-samba.json | 2 +- web/messages/pt/docs/storage-share/host-local-disk.json | 2 +- web/messages/pt/docs/storage-share/host-nfs.json | 2 +- web/messages/pt/docs/storage-share/host-samba.json | 2 +- web/messages/sk/docs/storage-share/host-local-disk.json | 2 +- web/messages/sk/docs/storage-share/host-nfs.json | 2 +- web/messages/sk/docs/storage-share/host-samba.json | 2 +- web/messages/sv/docs/storage-share/host-local-disk.json | 2 +- web/messages/sv/docs/storage-share/host-nfs.json | 2 +- web/messages/sv/docs/storage-share/host-samba.json | 2 +- 24 files changed, 24 insertions(+), 24 deletions(-) diff --git a/web/messages/de/docs/storage-share/host-local-disk.json b/web/messages/de/docs/storage-share/host-local-disk.json index 0a2753e8..7f66e57a 100644 --- a/web/messages/de/docs/storage-share/host-local-disk.json +++ b/web/messages/de/docs/storage-share/host-local-disk.json @@ -78,7 +78,7 @@ "Wählen Sie das Dateisystem aus - siehe Tabelle oben für Kompromisse.", "Storage ID (default disk-<device>), Mount-Pfad, Voreinstellung des Inhaltstyps.", "Bestätigen Sie im FINAL CONFIRMATION — DATA WILL BE ERASED Dialog.", - "ProxMenux löscht die Partitionstabelle und erstellt eine Partition über den Datenträger. Es führt mkfs.<fs> oder zpool create aus und hängt das Ergebnis ein. Normale Dateisysteme erhalten einen UUID-Eintrag in /etc/fstab mit defaults,nofail; ZFS verwendet die Mount-Konfiguration des Pools. Die Registrierung erfolgt mit pvesm add dir oder pvesm add zfspool." + "ProxMenux löscht die Partitionstabelle und erstellt eine Partition über den Datenträger. Es führt mkfs.<fs> oder zpool create aus und hängt das Ergebnis ein. Normale Dateisysteme erhalten einen UUID-Eintrag in /etc/fstab mit defaults,nofail; ZFS verwendet die Mount-Konfiguration des Pools. Ist Als Proxmox-Speicher markiert (bei ZFS immer), wird er anschließend mit pvesm add dir oder pvesm add zfspool registriert; andernfalls bleibt er nur ein Host-Mount." ], "tipTitle": "Warum UUID + nofail in /etc/fstab", "tipBody": "Das Skript schreibt UUID=… /mnt/<id> <fs> defaults,nofail 0 2. UUID überlebt die Geräteumordnung über Neustarts hinweg (so dass /dev/sdc, das /dev/sdd wird, den Boot nicht unterbricht). nofail bedeutet, dass, wenn die Festplatte jemals verschwindet (Hardwarefehler, Unplugged), Proxmox immer noch bootet - der Speicher wird nur als inaktiv angezeigt, bis die Festplatte zurückkommt." diff --git a/web/messages/de/docs/storage-share/host-nfs.json b/web/messages/de/docs/storage-share/host-nfs.json index 4295dbeb..bb131054 100644 --- a/web/messages/de/docs/storage-share/host-nfs.json +++ b/web/messages/de/docs/storage-share/host-nfs.json @@ -145,7 +145,7 @@ "showmountTitle": "\"Failed to connect\" von showmount", "showmountBody": "Der Server lehnte die Exportlistenabfrage ab. Häufige Ursachen: Der Server erzwingt strenge Client-ACLs (Ihre Proxmox-IP steht nicht auf der erlaubten Liste), rpcbind läuft nicht auf dem Server oder der Server stellt nur NFSv4 mit deaktiviertem showmount bereit. Der Exportpfad kann weiterhin manuell hinzugefügt werden, wenn Sie ihn kennen.", "inactiveTitle": "Storage zeigt als inaktiv in der Proxmox UI", - "inactiveBody": "Starten Sie NFS-Verbindung testen, um DNS, Ports und Mount-Zugriff zu prüfen. Bleibt der Speicher bei funktionierender Verbindung inaktiv, prüfen Sie journalctl -u pvestatd und Server-/Exportkonfiguration. Beheben Sie zuerst Verbindungs- oder Berechtigungsprobleme. pvesm set <id> --disable 0 aktiviert einen deaktivierten Speicher und ist keine allgemeine NFS-Reparatur.", + "inactiveBody": "Starten Sie zuerst NFS-Verbindung testen: Es prüft, ob der Server auf Ping antwortet, Port 2049 offen ist und die Exportliste (showmount -e) verfügbar ist. Bleibt der Speicher bei funktionierender Verbindung inaktiv, prüfen Sie journalctl -u pvestatd und Server-/Exportkonfiguration. Beheben Sie zuerst Verbindungs- oder Berechtigungsprobleme. pvesm set <id> --disable 0 aktiviert einen deaktivierten Speicher und ist keine allgemeine NFS-Reparatur.", "lxcNoWriteTitle": "fstab mount funktioniert, aber unprivilegierte LXC kann nicht durch ein bind-mount schreiben", "lxcNoWriteBody": "NFS-Zugriff hängt von Eigentümern, ACLs und Squash-Einstellungen auf dem Server ab. CIFS-Optionen wie uid= und file_mode= gelten nicht für NFS. Bei der Standard-LXC-Zuordnung wird CT-root zu Host-UID 100000, nicht zu Remote-UID 0. Gewähren Sie der tatsächlich zugeordneten UID/GID oder anonymen Serveridentität Zugriff. no_root_squash betrifft nur Remote-UID 0 und löst Probleme mit UID 100000 nicht allgemein. Das Skript versucht chmod 1777, kann Serverrechte aber nicht umgehen.", "fstabBootTitle": "fstab Mount wird nach dem Neustart nicht angezeigt", diff --git a/web/messages/de/docs/storage-share/host-samba.json b/web/messages/de/docs/storage-share/host-samba.json index 2a7048ea..1a09af4d 100644 --- a/web/messages/de/docs/storage-share/host-samba.json +++ b/web/messages/de/docs/storage-share/host-samba.json @@ -91,7 +91,7 @@ "warnTitle": "VM-Disks auf CIFS", "warnBody": "Die Auswahl images löst eine ProxMenux-Warnung aus: CIFS/SMB kann Sperrprobleme bei VM-Festplattenoperationen verursachen. Das Skript empfiehlt NFS, lässt Sie aber fortfahren. Sicherungen und ISOs sind typische CIFS-Anwendungen. Prüfen Sie Sperren, Snapshots, Migration und Last vor der Verwendung für images.", "credsTitle": "Wo pvesm Anmeldeinformationen speichert", - "credsBody": "Das Passwort steht nicht in /etc/pve/storage.cfg. Proxmox schreibt Klartext-Zugangsdaten in /etc/pve/priv/storage/<storage-id>.pw, geschützt durch das private Cluster-Dateisystemverzeichnis für root. Nehmen Sie weder einen festen Dateimodus 0600 noch Verschlüsselung an. Nach einer Passwortänderung am Server verwenden Sie pvesm set <id> --password <new> oder entfernen und ergänzen den Speicher über ProxMenux erneut." + "credsBody": "Das Passwort steht nicht in /etc/pve/storage.cfg. Proxmox schreibt Klartext-Zugangsdaten in /etc/pve/priv/storage/<storage-id>.pw, im privaten Bereich des Cluster-Dateisystems, den nur root lesen kann (Modus 0600); geschützt sind sie durch Zugriffsrechte, nicht durch Verschlüsselung. Nach einer Passwortänderung am Server verwenden Sie pvesm set <id> --password <new> oder entfernen und ergänzen den Speicher über ProxMenux erneut." }, "fstabBranch": { "heading": "Methode B — nur ein fstab-Mount auf dem Host", diff --git a/web/messages/en/docs/storage-share/host-local-disk.json b/web/messages/en/docs/storage-share/host-local-disk.json index 44b0d065..056fbd3e 100644 --- a/web/messages/en/docs/storage-share/host-local-disk.json +++ b/web/messages/en/docs/storage-share/host-local-disk.json @@ -78,7 +78,7 @@ "Pick the filesystem — see the table above for trade-offs.", "Storage ID (default disk-<device>), mount path, content-type preset.", "Confirm at the FINAL CONFIRMATION — DATA WILL BE ERASED dialog.", - "ProxMenux clears the partition table and creates one partition spanning the disk. It runs mkfs.<fs> or zpool create and mounts the result. Regular filesystems get an entry in /etc/fstab by UUID with defaults,nofail; ZFS uses its pool mount configuration instead. Registration uses pvesm add dir or pvesm add zfspool." + "ProxMenux clears the partition table and creates one partition spanning the disk. It runs mkfs.<fs> or zpool create and mounts the result. Regular filesystems get an entry in /etc/fstab by UUID with defaults,nofail; ZFS uses its pool mount configuration instead. If As Proxmox storage is marked (always the case for ZFS), it is then registered with pvesm add dir or pvesm add zfspool; otherwise it stays a host mount only." ], "tipTitle": "Why UUID + nofail in /etc/fstab", "tipBody": "The script writes UUID=… /mnt/<id> <fs> defaults,nofail 0 2. UUID survives device reordering across reboots (so /dev/sdc becoming /dev/sdd does not break boot). nofail means that if the disk ever disappears (hardware failure, unplugged), Proxmox still boots — storage will just show as inactive until the disk comes back." diff --git a/web/messages/en/docs/storage-share/host-nfs.json b/web/messages/en/docs/storage-share/host-nfs.json index ffcda4d5..fdff8644 100644 --- a/web/messages/en/docs/storage-share/host-nfs.json +++ b/web/messages/en/docs/storage-share/host-nfs.json @@ -145,7 +145,7 @@ "showmountTitle": "\"Failed to connect\" from showmount", "showmountBody": "The server refused the export-list query. Common causes: the server enforces strict client ACLs (your Proxmox IP is not on the allowed list), rpcbind is not running on the server, or the server exposes only NFSv4 with showmount disabled. The export path can still be added manually if you know it.", "inactiveTitle": "Storage shows as inactive in the Proxmox UI", - "inactiveBody": "Run Test NFS Connectivity first to investigate DNS, ports and mount access. If connectivity works but storage remains inactive, inspect journalctl -u pvestatd and the server/export configuration. Restore the underlying connectivity or permissions first. pvesm set <id> --disable 0 enables a disabled storage; it is not a general repair for NFS failures.", + "inactiveBody": "Run Test NFS Connectivity first: it checks that the server answers ping, that port 2049 is open and that the export list (showmount -e) is available. If connectivity works but storage remains inactive, inspect journalctl -u pvestatd and the server/export configuration. Restore the underlying connectivity or permissions first. pvesm set <id> --disable 0 enables a disabled storage; it is not a general repair for NFS failures.", "lxcNoWriteTitle": "fstab mount works but unprivileged LXC can't write through a bind-mount", "lxcNoWriteBody": "NFS access depends on server-side ownership, ACLs and squash settings. CIFS-style options such as uid= and file_mode= do not apply to NFS. With default LXC mapping, CT root becomes host UID 100000, not remote UID 0. Configure access for the actual mapped UID/GID or the server’s anonymous identity. no_root_squash only affects remote UID 0, so it is not a universal fix for UID 100000. The script attempts chmod 1777 but cannot override the server’s permissions.", "fstabBootTitle": "fstab mount does not come up after reboot", diff --git a/web/messages/en/docs/storage-share/host-samba.json b/web/messages/en/docs/storage-share/host-samba.json index 99955bd8..bd3de8d7 100644 --- a/web/messages/en/docs/storage-share/host-samba.json +++ b/web/messages/en/docs/storage-share/host-samba.json @@ -91,7 +91,7 @@ "warnTitle": "Live VM disks on CIFS", "warnBody": "Selecting images triggers a ProxMenux warning that CIFS/SMB can cause locking issues with VM disk operations. The script recommends NFS for VM disk images but lets you continue. Backups and ISOs are common CIFS uses. Assess locking, snapshots, migration and workload requirements before using CIFS for images.", "credsTitle": "Where pvesm stores credentials", - "credsBody": "The password is not written in /etc/pve/storage.cfg. Proxmox writes plaintext credentials in /etc/pve/priv/storage/<storage-id>.pw, protected by the private cluster filesystem directory accessible to root. Do not assume a fixed file mode of 0600 or encryption. After a server password change, use pvesm set <id> --password <new> or remove and re-add through ProxMenux." + "credsBody": "The password is not written in /etc/pve/storage.cfg. Proxmox writes plaintext credentials in /etc/pve/priv/storage/<storage-id>.pw, inside the private area of the cluster filesystem, readable only by root (mode 0600); it is protected by access control, not by encryption. After a server password change, use pvesm set <id> --password <new> or remove and re-add through ProxMenux." }, "fstabBranch": { "heading": "Method B — Host fstab mount only", diff --git a/web/messages/es/docs/storage-share/host-local-disk.json b/web/messages/es/docs/storage-share/host-local-disk.json index d07de410..513f9f0e 100644 --- a/web/messages/es/docs/storage-share/host-local-disk.json +++ b/web/messages/es/docs/storage-share/host-local-disk.json @@ -78,7 +78,7 @@ "Elige el sistema de archivos — mira la tabla de arriba para las contrapartidas.", "Storage ID (por defecto disk-<device>), ruta de montaje, preset de content type.", "Confirma en el diálogo FINAL CONFIRMATION — DATA WILL BE ERASED.", - "ProxMenux limpia la tabla de particiones y crea una partición que abarca el disco. Ejecuta mkfs.<fs> o zpool create y monta el resultado. Los sistemas de archivos normales reciben una entrada en /etc/fstab por UUID con defaults,nofail; ZFS usa la configuración de montaje del pool. El registro usa pvesm add dir o pvesm add zfspool." + "ProxMenux limpia la tabla de particiones y crea una partición que abarca el disco. Ejecuta mkfs.<fs> o zpool create y monta el resultado. Los sistemas de archivos normales reciben una entrada en /etc/fstab por UUID con defaults,nofail; ZFS usa la configuración de montaje del pool. Si Como almacenamiento Proxmox está marcado (siempre en ZFS), se registra con pvesm add dir o pvesm add zfspool; si no, queda solo como montaje del host." ], "tipTitle": "Por qué UUID + nofail en /etc/fstab", "tipBody": "El script escribe UUID=… /mnt/<id> <fs> defaults,nofail 0 2. El UUID sobrevive a reordenaciones de dispositivos entre reinicios (así que /dev/sdc pasando a ser /dev/sdd no rompe el arranque). nofail significa que si el disco desaparece alguna vez (fallo de hardware, desconectado), Proxmox arranca igualmente — el almacenamiento simplemente se mostrará como inactive hasta que el disco vuelva." diff --git a/web/messages/es/docs/storage-share/host-nfs.json b/web/messages/es/docs/storage-share/host-nfs.json index 47a046c4..9354db11 100644 --- a/web/messages/es/docs/storage-share/host-nfs.json +++ b/web/messages/es/docs/storage-share/host-nfs.json @@ -145,7 +145,7 @@ "showmountTitle": "\"Failed to connect\" desde showmount", "showmountBody": "El servidor rechazó la consulta de la lista de exports. Causas comunes: el servidor aplica ACLs de cliente estrictas (tu IP de Proxmox no está en la lista permitida), rpcbind no está corriendo en el servidor o el servidor expone solo NFSv4 con showmount deshabilitado. La ruta del export se puede añadir manualmente igualmente si la conoces.", "inactiveTitle": "El almacenamiento aparece como inactive en la UI de Proxmox", - "inactiveBody": "Ejecuta Probar la conectividad NFS para revisar DNS, puertos y acceso al montaje. Si la conectividad funciona pero sigue inactivo, consulta journalctl -u pvestatd y la configuración del servidor/export. Corrige primero la conectividad o los permisos. pvesm set <id> --disable 0 habilita un almacenamiento deshabilitado; no repara fallos NFS en general.", + "inactiveBody": "Ejecuta primero Probar la conectividad NFS: comprueba que el servidor responde al ping, que el puerto 2049 está abierto y que la lista de exports (showmount -e) está disponible. Si la conectividad funciona pero sigue inactivo, consulta journalctl -u pvestatd y la configuración del servidor/export. Corrige primero la conectividad o los permisos. pvesm set <id> --disable 0 habilita un almacenamiento deshabilitado; no repara fallos NFS en general.", "lxcNoWriteTitle": "El montaje fstab funciona pero un LXC unprivileged no puede escribir por un bind mount", "lxcNoWriteBody": "El acceso NFS depende de propiedad, ACL y squash en el servidor. Las opciones CIFS como uid= y file_mode= no se aplican a NFS. Con el mapeo LXC predeterminado, root del CT se convierte en UID 100000 del host, no en UID remoto 0. Da acceso al UID/GID mapeado real o a la identidad anónima del servidor. no_root_squash solo afecta al UID remoto 0, por lo que no resuelve todos los casos de UID 100000. El script intenta chmod 1777, pero no anula permisos del servidor.", "fstabBootTitle": "El montaje fstab no se levanta tras el reinicio", diff --git a/web/messages/es/docs/storage-share/host-samba.json b/web/messages/es/docs/storage-share/host-samba.json index 051f995d..25e45b47 100644 --- a/web/messages/es/docs/storage-share/host-samba.json +++ b/web/messages/es/docs/storage-share/host-samba.json @@ -91,7 +91,7 @@ "warnTitle": "Discos de VM en vivo en CIFS", "warnBody": "Seleccionar images muestra un aviso: CIFS/SMB puede causar problemas de bloqueo en operaciones con discos de VM. El script recomienda NFS para imágenes de VM, pero permite continuar. Backups e ISO son usos habituales de CIFS. Evalúa bloqueos, instantáneas, migración y carga antes de usar CIFS para images.", "credsTitle": "Dónde guarda pvesm las credenciales", - "credsBody": "La contraseña no se escribe en /etc/pve/storage.cfg. Proxmox guarda credenciales en texto plano en /etc/pve/priv/storage/<storage-id>.pw, protegidas por el directorio privado del sistema de archivos del clúster accesible a root. No asumas un modo fijo 0600 ni cifrado. Tras cambiar la contraseña en el servidor, usa pvesm set <id> --password <new> o elimina y vuelve a añadir desde ProxMenux." + "credsBody": "La contraseña no se escribe en /etc/pve/storage.cfg. Proxmox guarda credenciales en texto plano en /etc/pve/priv/storage/<storage-id>.pw, dentro del área privada del sistema de archivos del clúster, que solo puede leer root (modo 0600); están protegidas por permisos, no por cifrado. Tras cambiar la contraseña en el servidor, usa pvesm set <id> --password <new> o elimina y vuelve a añadir desde ProxMenux." }, "fstabBranch": { "heading": "Método B — Solo montaje fstab del host", diff --git a/web/messages/fr/docs/storage-share/host-local-disk.json b/web/messages/fr/docs/storage-share/host-local-disk.json index 9eed4e8f..cc173c72 100644 --- a/web/messages/fr/docs/storage-share/host-local-disk.json +++ b/web/messages/fr/docs/storage-share/host-local-disk.json @@ -78,7 +78,7 @@ "Choisissez le système de fichiers — voir le tableau ci-dessus pour les compromis.", "ID de stockage (disk-<device> par défaut), chemin de montage, préréglage de type contenu.", "Confirmez dans le dialogue CONFIRMATION FINALE — LES DONNÉES SERONT EFFACÉES.", - "ProxMenux efface la table de partitions et crée une partition sur tout le disque. Il exécute mkfs.<fs> ou zpool create, puis monte le résultat. Les systèmes de fichiers classiques reçoivent une entrée UUID dans /etc/fstab avec defaults,nofail ; ZFS utilise la configuration de montage du pool. L’enregistrement utilise pvesm add dir ou pvesm add zfspool." + "ProxMenux efface la table de partitions et crée une partition sur tout le disque. Il exécute mkfs.<fs> ou zpool create, puis monte le résultat. Les systèmes de fichiers classiques reçoivent une entrée UUID dans /etc/fstab avec defaults,nofail ; ZFS utilise la configuration de montage du pool. Si Comme stockage Proxmox est coché (toujours le cas pour ZFS), il est ensuite enregistré avec pvesm add dir ou pvesm add zfspool ; sinon, il reste un simple montage de l’hôte." ], "tipTitle": "Pourquoi UUID + nofail dans /etc/fstab", "tipBody": "Le script écrit UUID=… /mnt/<id> <fs> defaults,nofail 0 2. UUID survit à la réorganisation de l'appareil à travers les reboots (ainsi /dev/sdc devenir /dev/sdd ne casse pas le démarrage). nofail signifie que si le disque disparaît un jour (défaut de matériel, débranché), Proxmox démarre quand même — le stockage se montrera comme inactif jusqu'à ce que le disque revienne." diff --git a/web/messages/fr/docs/storage-share/host-nfs.json b/web/messages/fr/docs/storage-share/host-nfs.json index 3b8dab3e..f6371e5f 100644 --- a/web/messages/fr/docs/storage-share/host-nfs.json +++ b/web/messages/fr/docs/storage-share/host-nfs.json @@ -145,7 +145,7 @@ "showmountTitle": "« Impossible de se connecter » depuis showmount", "showmountBody": "Le serveur a refusé la requête de la liste d'exportation. Causes communes : le serveur fait respecter les CLA du client (votre IP Proxmox n'est pas sur la liste autorisée), rpcbind ne fonctionne pas sur le serveur, ou le serveur n'expose que NFSv4 avec showmount désactivé. Le chemin d'exportation peut encore être ajouté manuellement si vous le connaissez.", "inactiveTitle": "Le stockage est inactif dans l'UI Proxmox", - "inactiveBody": "Lancez Tester la connectivité NFS pour examiner DNS, ports et accès au montage. Si la connexion fonctionne mais que le stockage reste inactif, consultez journalctl -u pvestatd et la configuration serveur/export. Rétablissez d’abord connexion ou permissions. pvesm set <id> --disable 0 active un stockage désactivé ; ce n’est pas une réparation générale de NFS.", + "inactiveBody": "Lancez d’abord Tester la connectivité NFS : il vérifie que le serveur répond au ping, que le port 2049 est ouvert et que la liste des exports (showmount -e) est disponible. Si la connexion fonctionne mais que le stockage reste inactif, consultez journalctl -u pvestatd et la configuration serveur/export. Rétablissez d’abord connexion ou permissions. pvesm set <id> --disable 0 active un stockage désactivé ; ce n’est pas une réparation générale de NFS.", "lxcNoWriteTitle": "Le montage fstab fonctionne mais le LXC non privilégié ne peut pas écrire à travers un montage de liaison", "lxcNoWriteBody": "L’accès NFS dépend des propriétaires, ACL et réglages de squash du serveur. Les options CIFS uid= et file_mode= ne s’appliquent pas à NFS. Avec le mappage LXC par défaut, root dans le CT devient l’UID 100000 de l’hôte, pas l’UID distant 0. Autorisez l’UID/GID réellement mappé ou l’identité anonyme du serveur. no_root_squash concerne seulement l’UID distant 0 et ne résout pas tous les cas d’UID 100000. Le script tente chmod 1777 sans pouvoir contourner les permissions serveur.", "fstabBootTitle": "fstab mount ne vient pas après le redémarrage", diff --git a/web/messages/fr/docs/storage-share/host-samba.json b/web/messages/fr/docs/storage-share/host-samba.json index 95ce45fd..2c5d06d9 100644 --- a/web/messages/fr/docs/storage-share/host-samba.json +++ b/web/messages/fr/docs/storage-share/host-samba.json @@ -91,7 +91,7 @@ "warnTitle": "Live VM disques sur CIFS", "warnBody": "Sélectionner images déclenche un avertissement ProxMenux : CIFS/SMB peut poser des problèmes de verrouillage lors des opérations sur disques VM. Le script recommande NFS mais permet de continuer. Sauvegardes et ISO sont des usages courants de CIFS. Évaluez verrouillage, instantanés, migration et charge avant d’utiliser CIFS pour images.", "credsTitle": "Où pvesm stocke les identifiants", - "credsBody": "Le mot de passe n’est pas écrit dans /etc/pve/storage.cfg. Proxmox écrit les identifiants en clair dans /etc/pve/priv/storage/<storage-id>.pw, protégé par le répertoire privé du système de fichiers du cluster accessible à root. Ne supposez ni mode fixe 0600 ni chiffrement. Après un changement de mot de passe serveur, utilisez pvesm set <id> --password <new> ou supprimez puis ajoutez le stockage via ProxMenux." + "credsBody": "Le mot de passe n’est pas écrit dans /etc/pve/storage.cfg. Proxmox écrit les identifiants en clair dans /etc/pve/priv/storage/<storage-id>.pw, dans la zone privée du système de fichiers du cluster, lisible uniquement par root (mode 0600) ; ils sont protégés par les droits d’accès, pas par un chiffrement. Après un changement de mot de passe serveur, utilisez pvesm set <id> --password <new> ou supprimez puis ajoutez le stockage via ProxMenux." }, "fstabBranch": { "heading": "Méthode B — Montage fstab de l'hôte uniquement", diff --git a/web/messages/it/docs/storage-share/host-local-disk.json b/web/messages/it/docs/storage-share/host-local-disk.json index a7c63a4b..ebc56176 100644 --- a/web/messages/it/docs/storage-share/host-local-disk.json +++ b/web/messages/it/docs/storage-share/host-local-disk.json @@ -78,7 +78,7 @@ "Scegli il filesystem — vedi la tabella sopra per i trade-off.", "ID di archiviazione (default disk-<device>), percorso di montaggio, preimpostazione del tipo di contenuto.", "Conferma nel dialogo CONFERMA FINALE — I DATI SARANNO CANCELLATI.", - "ProxMenux cancella la tabella delle partizioni e crea una partizione sull’intero disco. Esegue mkfs.<fs> o zpool create e monta il risultato. I file system normali ricevono una voce UUID in /etc/fstab con defaults,nofail; ZFS usa la configurazione di montaggio del pool. La registrazione usa pvesm add dir o pvesm add zfspool." + "ProxMenux cancella la tabella delle partizioni e crea una partizione sull’intero disco. Esegue mkfs.<fs> o zpool create e monta il risultato. I file system normali ricevono una voce UUID in /etc/fstab con defaults,nofail; ZFS usa la configurazione di montaggio del pool. Se Come storage Proxmox è selezionato (sempre per ZFS), viene poi registrato con pvesm add dir o pvesm add zfspool; altrimenti resta solo un montaggio dell’host." ], "tipTitle": "Perché UUID + nofail in /etc/fstab", "tipBody": "Lo script scrive UUID=… /mnt/<id> <fs> defaults,nofail 0 2. UUID sopravvive al riordino del dispositivo attraverso i reboots (così /dev/sdc diventando /dev/sdd non rompe l'avvio). nofail significa che se il disco scomparirà mai (guasto hardware, scollegamento), Proxmox si avvia comunque — lo storage mostra solo come inattivo fino a quando il disco torna indietro." diff --git a/web/messages/it/docs/storage-share/host-nfs.json b/web/messages/it/docs/storage-share/host-nfs.json index c54162ad..47dd3b19 100644 --- a/web/messages/it/docs/storage-share/host-nfs.json +++ b/web/messages/it/docs/storage-share/host-nfs.json @@ -145,7 +145,7 @@ "showmountTitle": "\"Failed to connect\" da showmount", "showmountBody": "Il server ha rifiutato la query della lista delle esportazioni. Cause comuni: il server applica il client rigoroso ACLs (il vostro IP Proxmox non è nell'elenco consentito), rpcbind non è in esecuzione sul server, o il server espone solo NFSv4 con showmount disabilitato. Il percorso di esportazione può ancora essere aggiunto manualmente se lo conosci.", "inactiveTitle": "Lo stoccaggio mostra come inattivo nell'UI Proxmox", - "inactiveBody": "Esegui Testa connettività NFS per verificare DNS, porte e accesso al montaggio. Se la connessione funziona ma lo storage rimane inattivo, controlla journalctl -u pvestatd e la configurazione server/esportazione. Ripristina prima connessione o permessi. pvesm set <id> --disable 0 abilita uno storage disabilitato; non è una riparazione generica di NFS.", + "inactiveBody": "Esegui prima Testa connettività NFS: verifica che il server risponda al ping, che la porta 2049 sia aperta e che l’elenco delle esportazioni (showmount -e) sia disponibile. Se la connessione funziona ma lo storage rimane inattivo, controlla journalctl -u pvestatd e la configurazione server/esportazione. Ripristina prima connessione o permessi. pvesm set <id> --disable 0 abilita uno storage disabilitato; non è una riparazione generica di NFS.", "lxcNoWriteTitle": "Il montaggio fstab funziona ma il LXC non privilegiato non può scrivere tramite bind mount", "lxcNoWriteBody": "L’accesso NFS dipende da proprietari, ACL e squash sul server. Le opzioni CIFS uid= e file_mode= non si applicano a NFS. Con la mappatura LXC predefinita, root nel CT diventa UID 100000 sull’host, non UID remoto 0. Configura l’accesso per l’UID/GID mappato effettivo o l’identità anonima del server. no_root_squash riguarda solo l’UID remoto 0 e non risolve ogni caso di UID 100000. Lo script tenta chmod 1777 ma non aggira i permessi del server.", "fstabBootTitle": "fstab mount non arriva dopo il riavvio", diff --git a/web/messages/it/docs/storage-share/host-samba.json b/web/messages/it/docs/storage-share/host-samba.json index 52c70806..7d820d08 100644 --- a/web/messages/it/docs/storage-share/host-samba.json +++ b/web/messages/it/docs/storage-share/host-samba.json @@ -91,7 +91,7 @@ "warnTitle": "Live dischi VM su CIFS", "warnBody": "Selezionare images attiva un avviso ProxMenux: CIFS/SMB può causare problemi di blocco nelle operazioni sui dischi VM. Lo script consiglia NFS ma consente di continuare. Backup e ISO sono usi comuni di CIFS. Valuta blocchi, snapshot, migrazione e carico prima di usare CIFS per images.", "credsTitle": "Dove pvesm memorizza le credenziali", - "credsBody": "La password non è scritta in /etc/pve/storage.cfg. Proxmox salva credenziali in chiaro in /etc/pve/priv/storage/<storage-id>.pw, protette dalla directory privata del file system del cluster accessibile a root. Non presumere una modalità fissa 0600 o la cifratura. Dopo un cambio password sul server usa pvesm set <id> --password <new> oppure rimuovi e aggiungi lo storage tramite ProxMenux." + "credsBody": "La password non è scritta in /etc/pve/storage.cfg. Proxmox salva credenziali in chiaro in /etc/pve/priv/storage/<storage-id>.pw, nell’area privata del file system del cluster, leggibile solo da root (modalità 0600); sono protette dai permessi di accesso, non dalla cifratura. Dopo un cambio password sul server usa pvesm set <id> --password <new> oppure rimuovi e aggiungi lo storage tramite ProxMenux." }, "fstabBranch": { "heading": "Metodo B — solo montaggio tramite fstab sull’host", diff --git a/web/messages/pt/docs/storage-share/host-local-disk.json b/web/messages/pt/docs/storage-share/host-local-disk.json index cdb3a4ad..88588111 100644 --- a/web/messages/pt/docs/storage-share/host-local-disk.json +++ b/web/messages/pt/docs/storage-share/host-local-disk.json @@ -78,7 +78,7 @@ "Escolha o sistema de arquivos — veja a tabela acima para trade-offs.", "ID de armazenamento (padrão disk-<device>), caminho de montagem, tipo de conteúdo predefinido.", "Confirme no diálogo CONFIRMAÇÃO FINAL — OS DADOS SERÃO APAGADOS.", - "O ProxMenux limpa a tabela de partições e cria uma partição que ocupa o disco. Executa mkfs.<fs> ou zpool create e monta o resultado. Sistemas de arquivos comuns recebem uma entrada UUID em /etc/fstab com defaults,nofail; o ZFS usa a configuração de montagem do pool. O registro usa pvesm add dir ou pvesm add zfspool." + "O ProxMenux limpa a tabela de partições e cria uma partição que ocupa o disco. Executa mkfs.<fs> ou zpool create e monta o resultado. Sistemas de arquivos comuns recebem uma entrada UUID em /etc/fstab com defaults,nofail; o ZFS usa a configuração de montagem do pool. Se Como armazenamento Proxmox estiver marcado (sempre no caso do ZFS), ele é registrado com pvesm add dir ou pvesm add zfspool; caso contrário, fica apenas como montagem do host." ], "tipTitle": "Porquê UUID + nofail em /etc/fstab", "tipBody": "O script escreve UUID=… /mnt/<id> <fs> defaults,nofail 0 2. O UUID sobrevive à reordenação do dispositivo através de reinicialização (então o /dev/sdc tornando-se o /dev/sdd não quebra a inicialização). nofail significa que se o disco desaparecer (falha de Hardware, desconectado), o Proxmox ainda inicia — o armazenamento só será mostrado como inativo até que o disco volte." diff --git a/web/messages/pt/docs/storage-share/host-nfs.json b/web/messages/pt/docs/storage-share/host-nfs.json index 52396bfa..2e8471a4 100644 --- a/web/messages/pt/docs/storage-share/host-nfs.json +++ b/web/messages/pt/docs/storage-share/host-nfs.json @@ -145,7 +145,7 @@ "showmountTitle": "\"Falhou em conectar\" do showmount", "showmountBody": "O servidor recusou a consulta da lista de exportação. Causas comuns: o servidor obriga ACLs cliente restrito (seu IP Proxmox não está na lista permitida), rpcbind não está em execução no servidor, ou o servidor expõe apenas NFSv4 com showmount desabilitado. O caminho de exportação ainda pode ser adicionado manualmente se você souber.", "inactiveTitle": "O armazenamento mostra como inativo na UI Proxmox", - "inactiveBody": "Execute Testar conectividade NFS para verificar DNS, portas e acesso à montagem. Se a conexão funcionar mas o armazenamento continuar inativo, consulte journalctl -u pvestatd e a configuração do servidor/exportação. Corrija primeiro a conexão ou os privilégios. pvesm set <id> --disable 0 habilita um armazenamento desabilitado; não é um reparo geral de NFS.", + "inactiveBody": "Execute primeiro Testar conectividade NFS: ele verifica se o servidor responde ao ping, se a porta 2049 está aberta e se a lista de exportações (showmount -e) está disponível. Se a conexão funcionar mas o armazenamento continuar inativo, consulte journalctl -u pvestatd e a configuração do servidor/exportação. Corrija primeiro a conexão ou os privilégios. pvesm set <id> --disable 0 habilita um armazenamento desabilitado; não é um reparo geral de NFS.", "lxcNoWriteTitle": "A montagem fstab funciona mas o LXC sem privilégios não consegue gravar por bind mount", "lxcNoWriteBody": "O acesso NFS depende de proprietários, ACLs e squash no servidor. Opções CIFS como uid= e file_mode= não se aplicam a NFS. Com o mapeamento LXC padrão, root no CT vira UID 100000 no host, não UID remoto 0. Configure o acesso para o UID/GID mapeado real ou a identidade anônima do servidor. no_root_squash afeta apenas o UID remoto 0 e não resolve todos os casos de UID 100000. O script tenta chmod 1777, mas não ignora permissões do servidor.", "fstabBootTitle": "A montagem do fstab não aparece após reiniciar", diff --git a/web/messages/pt/docs/storage-share/host-samba.json b/web/messages/pt/docs/storage-share/host-samba.json index 1d75713a..c0bf69fc 100644 --- a/web/messages/pt/docs/storage-share/host-samba.json +++ b/web/messages/pt/docs/storage-share/host-samba.json @@ -91,7 +91,7 @@ "warnTitle": "Discos de VM vivos em CIFS", "warnBody": "Selecionar images mostra um aviso ProxMenux: CIFS/SMB pode causar problemas de bloqueio em operações com discos de VMs. O script recomenda NFS, mas permite continuar. Backups e ISOs são usos comuns de CIFS. Avalie bloqueios, snapshots, migração e carga antes de usar CIFS para images.", "credsTitle": "Onde o pvesm armazena credenciais", - "credsBody": "A senha não é gravada em /etc/pve/storage.cfg. O Proxmox salva credenciais em texto simples em /etc/pve/priv/storage/<storage-id>.pw, protegidas pelo diretório privado do sistema de arquivos do cluster acessível a root. Não suponha modo fixo 0600 nem criptografia. Após mudar a senha no servidor, use pvesm set <id> --password <new> ou remova e adicione o armazenamento pelo ProxMenux." + "credsBody": "A senha não é gravada em /etc/pve/storage.cfg. O Proxmox salva credenciais em texto simples em /etc/pve/priv/storage/<storage-id>.pw, na área privada do sistema de arquivos do cluster, legível apenas por root (modo 0600); elas são protegidas por permissões de acesso, não por criptografia. Após mudar a senha no servidor, use pvesm set <id> --password <new> ou remova e adicione o armazenamento pelo ProxMenux." }, "fstabBranch": { "heading": "Método B — Montagem fstab da máquina", diff --git a/web/messages/sk/docs/storage-share/host-local-disk.json b/web/messages/sk/docs/storage-share/host-local-disk.json index 035633f7..e3ca9cbb 100644 --- a/web/messages/sk/docs/storage-share/host-local-disk.json +++ b/web/messages/sk/docs/storage-share/host-local-disk.json @@ -78,7 +78,7 @@ "Vyberte súborový systém — porovnanie výhod a nevýhod je v tabuľke vyššie.", "ID úložiska (predvolene disk-<device>), cesta pripojenia a predvoľba typu obsahu.", "Potvrďte v dialógu KONEČNÉ POTVRDENIE — DÁTA SA VYMAŽÚ.", - "ProxMenux vymaže tabuľku oddielov a vytvorí jeden oddiel na celom disku. Spustí mkfs.<fs> alebo zpool create a výsledok pripojí. Bežné súborové systémy dostanú položku UUID v /etc/fstab s defaults,nofail; ZFS používa konfiguráciu pripojenia poolu. Registrácia používa pvesm add dir alebo pvesm add zfspool." + "ProxMenux vymaže tabuľku oddielov a vytvorí jeden oddiel na celom disku. Spustí mkfs.<fs> alebo zpool create a výsledok pripojí. Bežné súborové systémy dostanú položku UUID v /etc/fstab s defaults,nofail; ZFS používa konfiguráciu pripojenia poolu. Ak je označené Ako úložisko Proxmoxu (pri ZFS vždy), následne sa zaregistruje cez pvesm add dir alebo pvesm add zfspool; inak zostane len pripojením na hostiteľovi." ], "tipTitle": "Prečo UUID + nofail v /etc/fstab", "tipBody": "Skript zapíše UUID=… /mnt/<id> <fs> defaults,nofail 0 2. UUID zostane rovnaké aj pri zmene poradia zariadení po reštarte, takže premenovanie /dev/sdc na /dev/sdd nenaruší štart. S nofail sa Proxmox spustí aj pri chýbajúcom disku (porucha alebo odpojenie); úložisko sa bude zobrazovať ako neaktívne, kým sa disk nevráti." diff --git a/web/messages/sk/docs/storage-share/host-nfs.json b/web/messages/sk/docs/storage-share/host-nfs.json index 88602472..fd90b99a 100644 --- a/web/messages/sk/docs/storage-share/host-nfs.json +++ b/web/messages/sk/docs/storage-share/host-nfs.json @@ -145,7 +145,7 @@ "showmountTitle": "„Failed to connect“ z príkazu showmount", "showmountBody": "Server odmietol dotaz exportného zoznamu. Bežné príčiny: server vymáha prísne klientske ACL (vaše Proxmox IP nie je na povolenom zozname), rpcbind nebeží na serveri, alebo server vystaví iba NFSv4 s showmount vypnutým. Exportná cesta môže byť stále pridaná ručne, ak ju poznáte.", "inactiveTitle": "Úložisko ukazuje ako neaktívne v systéme Proxmox UI", - "inactiveBody": "Spustite Testovať pripojenie NFS a overte DNS, porty aj prístup. Ak spojenie funguje, ale úložisko zostáva neaktívne, skontrolujte journalctl -u pvestatd a konfiguráciu servera/exportu. Najprv opravte spojenie alebo oprávnenia. Príkaz pvesm set <id> --disable 0 zapne vypnuté úložisko; nie je všeobecnou opravou chýb NFS.", + "inactiveBody": "Najprv spustite Testovať pripojenie NFS: overí, či server odpovedá na ping, či je otvorený port 2049 a či je dostupný zoznam exportov (showmount -e). Ak spojenie funguje, ale úložisko zostáva neaktívne, skontrolujte journalctl -u pvestatd a konfiguráciu servera/exportu. Najprv opravte spojenie alebo oprávnenia. Príkaz pvesm set <id> --disable 0 zapne vypnuté úložisko; nie je všeobecnou opravou chýb NFS.", "lxcNoWriteTitle": "Pripojenie fstab funguje, ale neprivilegovaný LXC nemôže zapisovať cez bind mount", "lxcNoWriteBody": "Prístup NFS závisí od vlastníkov, ACL a nastavení squash na serveri. Voľby CIFS uid= a file_mode= pre NFS neplatia. Pri predvolenom mapovaní LXC má root z CT na hostiteľovi UID 100000, nie vzdialené UID 0. Povoľte prístup skutočnému mapovanému UID/GID alebo anonymnej identite servera. no_root_squash ovplyvňuje iba vzdialené UID 0 a nie je všeobecným riešením pre UID 100000. Skript skúsi chmod 1777, ale oprávnenia servera neobíde.", "fstabBootTitle": "fstab mount nepríde po reštarte", diff --git a/web/messages/sk/docs/storage-share/host-samba.json b/web/messages/sk/docs/storage-share/host-samba.json index a17b0da9..dca9ba3c 100644 --- a/web/messages/sk/docs/storage-share/host-samba.json +++ b/web/messages/sk/docs/storage-share/host-samba.json @@ -91,7 +91,7 @@ "warnTitle": "Živé disky VM na CIFS", "warnBody": "Výber images zobrazí varovanie ProxMenuxu: CIFS/SMB môže spôsobovať problémy so zámkami pri operáciách s diskami VM. Skript odporúča NFS, ale umožní pokračovať. Zálohy a ISO sú bežným použitím CIFS. Pred použitím pre images posúďte zámky, snímky, migráciu a záťaž.", "credsTitle": "Kde pvesm ukladá údaje", - "credsBody": "Heslo sa nezapisuje do /etc/pve/storage.cfg. Proxmox uloží údaje v otvorenom texte do /etc/pve/priv/storage/<storage-id>.pw, chránené súkromným adresárom klastrového súborového systému prístupným pre root. Nepredpokladajte pevný režim 0600 ani šifrovanie. Po zmene hesla na serveri použite pvesm set <id> --password <new> alebo úložisko odstráňte a pridajte cez ProxMenux." + "credsBody": "Heslo sa nezapisuje do /etc/pve/storage.cfg. Proxmox uloží údaje v otvorenom texte do /etc/pve/priv/storage/<storage-id>.pw, v súkromnej oblasti klastrového súborového systému, ktorú môže čítať iba root (režim 0600); chránia ich prístupové práva, nie šifrovanie. Po zmene hesla na serveri použite pvesm set <id> --password <new> alebo úložisko odstráňte a pridajte cez ProxMenux." }, "fstabBranch": { "heading": "Metóda B — iba pripojenie cez fstab hostiteľa", diff --git a/web/messages/sv/docs/storage-share/host-local-disk.json b/web/messages/sv/docs/storage-share/host-local-disk.json index 030c4af2..f0e1d7ae 100644 --- a/web/messages/sv/docs/storage-share/host-local-disk.json +++ b/web/messages/sv/docs/storage-share/host-local-disk.json @@ -78,7 +78,7 @@ "Välj filsystemet - se tabellen ovan för avvägningar.", "Lagring ID (standard disk-<device>), monteringsväg, innehållstyp förinställd.", "Bekräfta i dialogen SLUTLIG BEKRÄFTELSE — DATA KOMMER ATT RADERAS.", - "ProxMenux rensar partitionstabellen och skapar en partition över hela disken. Det kör mkfs.<fs> eller zpool create och monterar resultatet. Vanliga filsystem får en UUID-post i /etc/fstab med defaults,nofail; ZFS använder poolens monteringskonfiguration. Registreringen görs med pvesm add dir eller pvesm add zfspool." + "ProxMenux rensar partitionstabellen och skapar en partition över hela disken. Det kör mkfs.<fs> eller zpool create och monterar resultatet. Vanliga filsystem får en UUID-post i /etc/fstab med defaults,nofail; ZFS använder poolens monteringskonfiguration. Om Som Proxmox-lagring är markerat (alltid för ZFS) registreras den sedan med pvesm add dir eller pvesm add zfspool; annars förblir den bara en montering på värden." ], "tipTitle": "Varför UUID + nofail i /etc/fstab", "tipBody": "Skriptet skriver UUID=… /mnt/<id> <fs> defaults,nofail 0 2. UUID överlever enhetsreordering över omstart (så /dev/sdc blir /dev/sdd inte bryta start). nofail innebär att om disken någonsin försvinner (hårdvarufel, urkopplad), startar Proxmox ändå - lagring kommer bara att visas som inaktiv tills disken kommer tillbaka." diff --git a/web/messages/sv/docs/storage-share/host-nfs.json b/web/messages/sv/docs/storage-share/host-nfs.json index c520353e..bf3fe357 100644 --- a/web/messages/sv/docs/storage-share/host-nfs.json +++ b/web/messages/sv/docs/storage-share/host-nfs.json @@ -145,7 +145,7 @@ "showmountTitle": "\"Fel att ansluta\" från showmount", "showmountBody": "Servern vägrade exportlistafrågan. Vanliga orsaker: servern genomdriver strikta klient ACL (din Proxmox IP är inte på den tillåtna listan), rpcbind körs inte på servern, eller servern exponerar endast NFSv4 med showmount inaktiverat. Exportvägen kan fortfarande läggas manuellt om du vet det.", "inactiveTitle": "Lagring visar som inaktiv i Proxmox UI", - "inactiveBody": "Kör Testa NFS-anslutning för att undersöka DNS, portar och monteringsåtkomst. Om anslutningen fungerar men lagringen förblir inaktiv, kontrollera journalctl -u pvestatd och serverns/exportens inställningar. Återställ först anslutning eller behörigheter. pvesm set <id> --disable 0 aktiverar inaktiverad lagring; det är ingen allmän reparation av NFS-fel.", + "inactiveBody": "Kör först Testa NFS-anslutning: den kontrollerar att servern svarar på ping, att port 2049 är öppen och att exportlistan (showmount -e) är tillgänglig. Om anslutningen fungerar men lagringen förblir inaktiv, kontrollera journalctl -u pvestatd och serverns/exportens inställningar. Återställ först anslutning eller behörigheter. pvesm set <id> --disable 0 aktiverar inaktiverad lagring; det är ingen allmän reparation av NFS-fel.", "lxcNoWriteTitle": "fstab montering fungerar men oprivilegierad LXC kan inte skriva genom en bind-mount", "lxcNoWriteBody": "NFS-åtkomst beror på serverns ägare, ACL:er och squash-inställningar. CIFS-alternativ som uid= och file_mode= gäller inte för NFS. Med LXC:s standardmappning blir CT-root värdens UID 100000, inte fjärr-UID 0. Ge åtkomst till det faktiska mappade UID/GID:t eller serverns anonyma identitet. no_root_squash påverkar endast fjärr-UID 0 och löser inte alla fall med UID 100000. Skriptet försöker köra chmod 1777 men kan inte kringgå serverns behörigheter.", "fstabBootTitle": "fstab montering kommer inte upp efter omstart", diff --git a/web/messages/sv/docs/storage-share/host-samba.json b/web/messages/sv/docs/storage-share/host-samba.json index c80a971c..2ec63e3b 100644 --- a/web/messages/sv/docs/storage-share/host-samba.json +++ b/web/messages/sv/docs/storage-share/host-samba.json @@ -91,7 +91,7 @@ "warnTitle": "Live VM diskar på CIFS", "warnBody": "Valet images visar en ProxMenux-varning om att CIFS/SMB kan ge låsningsproblem vid VM-diskoperationer. Skriptet rekommenderar NFS men låter dig fortsätta. Säkerhetskopior och ISO-filer är vanliga CIFS-användningar. Bedöm låsning, ögonblicksbilder, migrering och arbetslast innan CIFS används för images.", "credsTitle": "Var pvesm lagrar inloggningsuppgifter", - "credsBody": "Lösenordet skrivs inte i /etc/pve/storage.cfg. Proxmox sparar klartextuppgifter i /etc/pve/priv/storage/<storage-id>.pw, skyddade av klusterfilsystemets privata katalog för root. Förutsätt varken ett fast filläge 0600 eller kryptering. Efter ett lösenordsbyte på servern använder du pvesm set <id> --password <new> eller tar bort och lägger till lagringen via ProxMenux." + "credsBody": "Lösenordet skrivs inte i /etc/pve/storage.cfg. Proxmox sparar klartextuppgifter i /etc/pve/priv/storage/<storage-id>.pw, i klusterfilsystemets privata område som bara root kan läsa (läge 0600); de skyddas av åtkomstbehörigheter, inte av kryptering. Efter ett lösenordsbyte på servern använder du pvesm set <id> --password <new> eller tar bort och lägger till lagringen via ProxMenux." }, "fstabBranch": { "heading": "Metod B - Värd fstab montering endast",