Server Disk crashed while migrating it using VMWare Storage VMotion in Vsphere.

Issue

The server Disk crashed during the migration it using VMWare Storage VMotion in Vsphere. After migration, the mysql database is not starting and giving the following errors.

InnoDB: Doing recovery: scanned up to log sequence number 597 3573664768
InnoDB: Doing recovery: scanned up to log sequence number 597 3578907648
InnoDB: Doing recovery: scanned up to log sequence number 597 3584150528
InnoDB: Doing recovery: scanned up to log sequence number 597 3589393408
InnoDB: Doing recovery: scanned up to log sequence number 597 3594636288
InnoDB: Doing recovery: scanned up to log sequence number 597 3599879168
InnoDB: Doing recovery: scanned up to log sequence number 597 3605122048
InnoDB: Doing recovery: scanned up to log sequence number 597 3610364928
InnoDB: Doing recovery: scanned up to log sequence number 597 3615607808
InnoDB: Doing recovery: scanned up to log sequence number 597 3620850688
InnoDB: Doing recovery: scanned up to log sequence number 597 3626093568
InnoDB: Doing recovery: scanned up to log sequence number 597 3631336448
InnoDB: Doing recovery: scanned up to log sequence number 597 3636579328
InnoDB: Doing recovery: scanned up to log sequence number 597 3641822208
InnoDB: Doing recovery: scanned up to log sequence number 597 3642608891
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 120614 10:36:39InnoDB: Assertion failure in thread 1120643392 in file log0recv.c line 793
InnoDB: Failing assertion: !page || (ibool)!!page_is_comp(page)==index->table->comp
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to <a class="make_room_for_kcs" href="http://bugs.mysql.com." target="_blank">http://bugs.mysql.com.</a>
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: <a class="make_room_for_kcs" href="http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html" target="_blank">http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html</a>
InnoDB: about forcing recovery.
mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

Is there any issues from Red Hat Enterprise Linux server side?