Troubleshooting

Explore this Page

Virtual Disk Creation Fails Due to Stale iSCSI Devices

Problem: The SANsymphony Storage Plugin for Proxmox fails to create a new LVM storage or virtual disk.

Cause: This can happen if there are stale iSCSI devices present on the system.

Solution: Remove the stale devices by running the following command (replace sdX with the actual device name):

    Copy
    Command
    echo 1 > /sys/block/sdX/device/delete

This clears the stale device and allows the plugin to create virtual disks successfully.

Proxmox Services Not Responding

Problem: The SANsymphony Storage Plugin for Proxmox is not functioning, and Proxmox operations (storage listing, virtual machine actions) are slow or unresponsive.

Cause: One or more Proxmox VE services may have stopped or become unresponsive.

Solution: Restart the Proxmox services:

    Copy
    Command
    systemctl restart pvedaemon pveproxy pvestatd pvescheduler 

Proxmox Cannot Reach SANsymphony Storage

Problem: Proxmox nodes fail to detect or connect to SANsymphony Storage Plugin for Proxmox.

Cause: Network connectivity issues, such as blocked firewall ports or misconfigured network routes, prevent communication between Proxmox VE and SANsymphony.

Solution:

  • Verify that Proxmox VE nodes can reach SANsymphony over the network.
  • Check and update firewall rules as required.

Missing or Incomplete Multipath Configuration

Problem: Multipath devices are not detected, or storage paths are not balanced.

Cause: The multipath.conf file is misconfigured, or the multipath daemon is not running.

Solution:

  • Verify multipath configuration and list devices:

      Copy
      Command
      multipath -ll
  •   Restart the multipath daemon:
      Copy
      Command
      systemctl restart multipathd

iSCSI Paths Not Detected

Problem: Proxmox is not using all available paths to SANsymphony storage.

Cause: iSCSI sessions were not refreshed after new paths were added or network changes occurred.

Solution: Rescan iSCSI sessions:

    Copy
    Command
    iscsiadm -m session --rescan 

Permission Errors in SANsymphony

Problem: Storage operations (create, delete, resize) fail with permission errors.

Cause: The SANsymphony user account used by Proxmox lacks the required permissions.

Solution: Grant the user sufficient privileges in SANsymphony to create, modify, and delete virtual disks.

General Error Diagnosis

Problem: Errors occur when working with the plugin or storage, but the cause is unclear.

Cause: Proxmox service or storage logs were not reviewed.

Solution: Check for error messages related to Proxmox services, storage, or the plugin. Logs are typically located under /var/log/pve.

    Copy
    Command
    journalctl -xe

Virtual Disk Creation Fails Due to Inactive iSCSI Sessions

Problem: When attempting to create a virtual disk using the SANsymphony Storage Plugin for Proxmox, the operation may fail.

Cause: One or more iSCSI sessions between Proxmox VE and SANsymphony are inactive or not properly connected.

Resolution: Verify that all required iSCSI sessions are active before creating a virtual disk from the plugin.

Plugin Removed or Fails After Proxmox VE Upgrade

Problem: After upgrading Proxmox VE (PVE) to a version supported by the SANsymphony Storage Plugin for Proxmox, the plugin may be removed from the repository or may fail to function correctly after the upgrade.

Solution: Uninstall the existing plugin and reinstall the latest compatible version of the plugin.

Learn More