a_p_
Leadership
Leadership

According to the log file, the LUNs have been detected as "Spanshot LUNs".

2023-09-25T16:16:16.289Z cpu31:1718527)LVM: 11764: Device naa.60014053b90ac9ddd622d463edae0dd1:1 detected to be a snapshot:
2023-09-25T16:16:16.289Z cpu31:1718527)LVM: 11770: queried disk ID: <type 2, len 22, lun 1, devType 0, scsi 0, h(id) 2259623917972509401>
2023-09-25T16:16:16.289Z cpu31:1718527)LVM: 11777: on-disk disk ID: <type 2, len 22, lun 2, devType 0, scsi 0, h(id) 10461069855284865661>
2023-09-25T16:16:16.289Z cpu31:1718527)LVM: 11794: If Device naa.60014053b90ac9ddd622d463edae0dd1:1 is OsData:0 status:Success
2023-09-25T16:16:16.290Z cpu31:1718527)LVM: 11764: Device naa.6001405aa947686d3ca2d481ed8c85d0:1 detected to be a snapshot:
2023-09-25T16:16:16.290Z cpu31:1718527)LVM: 11770: queried disk ID: <type 2, len 22, lun 2, devType 0, scsi 0, h(id) 9153303937128236436>
2023-09-25T16:16:16.290Z cpu31:1718527)LVM: 11777: on-disk disk ID: <type 2, len 22, lun 1, devType 0, scsi 0, h(id) 13470468055773502861>
2023-09-25T16:16:16.290Z cpu31:1718527)LVM: 11794: If Device naa.6001405aa947686d3ca2d481ed8c85d0:1 is OsData:0 status:Success

Please follow the steps (I recommend the command line approach) in https://kb.vmware.com/s/article/1011387 to verify this, and to possible mount the LUNs again.

André

View solution in original post