)ScsiDeviceIO: 2369: Cmd(0x41364311b740) 0x16, CmdSN 0x198a4a from world 0 to dev "naa.ID failed H:0x8 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.
Lun state in doubt.
i had a problem with my storage array last week we had to replace one controller.
even i have rebooted everything the esxi hosts start loosing luns in couple of days.
and once esxi hosts start loosing luns it become "not responding" in the vcenter.
any advice other then re-creating the luns. or that is the only possible solution now. ?
Given that your storage needed a controller swap. I'm wondering if you don't do a fail over to the second controller assuming it is active/standby. Could just be some oddities that persisted through the controller swap.
When first time the controller fails it did not fail over nicely and we lost half of our luns, however, now both controllers are fine after the replacement( or at least looks fine).
we have PSP most recent with acitive/active ...
any suggestion?
Well, another thought is the time correlation of losing a LUN and logs on the storage array. Have you engaged the storage vendor further on this post issue?
I was not able to find any solution/ reason for this problem. so we migrated our vms on other Esxi hosts.