stack boot partition mismatch
I recently encountered a situation where a slot in a stack was clearly set to use a different boot partition to the remainder of its stack and upon stack reboot the slot in question was left stranded outside the stack topology on a dfferent firmware ...