Why are existing LUNs not visible to VMware vSphere after updating to QTS 4.4.1 or later?
QTS 4.4.1 added support for Fibre Channel, which changed the way QTS handles LUN connections. Due to these changes, existing LUNs created in QTS version 4.4.0 or earlier might not be visible to VMware vSphere 6.x/5.x/4.x after updating QTS to version 4.4.1 or later. The LUNs are still visible in QTS and LUN data is unaffected.
For details on this issue, see: vSphere handling of LUNs detected as snapshot LUNs (1011387).
Solution:
ESXi 5.x and 6.x
To list the volumes detected as snapshots, run this command:
# esxcli storage vmfs snapshot list
You see output similar to:
5db64289-0d688636-6ebd-245ebe0aba0a
Volume Name: QTS436
VMFS UUID: 5db64289-0d688636-6ebd-245ebe0aba0a
Can mount: true
Reason for un-mountability:
Can resignature: true
Reason for non-resignaturability:
Unresolved Extent Count: 1
To mount a snapshot/replica LUN that is persistent across reboots, run this command:
# esxcli storage vmfs snapshot mount -l label
To resignature a snapshot/replica LUN (the volume is mounted immediately after the resignature), run this command:
# esxcli storage vmfs snapshot resignature -l label
To mount a volume without performing a resignaturing of the volume (the volume is mounted when the ESX host is rebooted), run this command:
# esxcfg-volume -M label
ESXi/ESX 4.x
To list the volumes that are detected as snapshots/replicas, run this command:
# esxcfg-volume -l
You see output similar to:
Scanning for VMFS-6 host activity (4096 bytes/HB, 1024 HBs).
VMFS UUID/label: 5db64289-0d688636-6ebd-245ebe0aba0a/QTS436
Can mount: Yes
Can resignature: Yes
Extent name: naa.6e843b656585cc0d5dcad4cb1da3bad6:1 range: 0 - 20223 (MB)
To mount a volume without performing a resignaturing of the volume (the volume is mounted when the ESX host is rebooted), run this command:
# esxcfg-volume -M label
To resignature a volume (the volume is mounted immediately after the resignature), run this command:
# esxcfg-volume -r label
For yderligere hjælp kan du spørge andre brugere og QNAP-eksperter i vores community. Gå til QNAP Community