During the first online database command, after you execute load database across two platforms with different endian types, the hash partition is marked suspect.
Any global clustered index on a round-robin partition, which has an internally generated partition condition with a unichar or univarchar partition key, is marked suspect.
After the database is online, use sp_post_xpload to fix the suspect partitions and indexes.