We have restored a database to SAN storage as part of a migration. A scheduled run of DBCC CHECKDB failed after the restore. Repeated runs of DBCC CHECKDB are returning different results. Each run returns consistency errors, but the consistency errors show up on different pages and allocation units. When the database is restored to local storage, DBCC CHECKDB comes back clean. That points me to an issue with the SAN, but I am very confused by the changing DBCC CHECKDB results. Has anyone seen behavior like this before?