May 25 17:01:00 esnode17 SM: Raising exception ]
May 25 17:00:54 esnode17 SM: SCSI_DEV_CTRL: Failure, Invalid argument As Xen will throw below exception, if LUN ID (being discovered via Hardware HBA is greater than 256), see below SMlog: One liner: ' Asssign LUN ID between 0-256 OR Don't assign LUN ID greater than 256 to XEN SR (via FC SAN Backend)'. May 25 10:55:03 esnode17 SM: FAILED in util.pread: (rc 1) stdout: '', stderr: 'scsi_id: invalid option -Įdit#01: All the multipaths are healthy (verified via xen as well as backend) May 25 10:55:03 esnode17 SM: pread SUCCESS May 25 10:55:03 esnode17 SM: failed with ('Operation not permitted',)
I have also tried to safely move (LUNs) from one XENserver to another (in which case, it reattaches the LUNs and 'we move them from backend storage Views) but still fails to detect that and gives same General IO error. We have been using Hardware HBA to probe new LUNs (from FC SAN am also checking SAN logs for any issues (so far none) and it is only affecting new probes. Alan: Xenserver version is 6.5, we have also tried this with xen 7.0 also.
