I was importing some dumps when presumably a bug caused MySQL to crash and damage the InnoDB data file (two bugs in one?). Now MySQL won't start. Is there any to have it bypass it just so that I can get it started? Since I'm populating this database fresh, I can stand to lose the InnoDB databases. But I want to avoid having to repopulate the system tables.
This is MySQL 5.5.19 on Solaris Express 11.
InnoDB: Log scan progressed past the checkpoint lsn 1595675
111222 0:23:48 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1733055
InnoDB: Error: tried to read 16384 bytes at offset 0 5128192.
InnoDB: Was only able to read -1.
111222 0:23:49 InnoDB: Operating system error number 5 in a file operation.
This is MySQL 5.5.19 on Solaris Express 11.
InnoDB: Log scan progressed past the checkpoint lsn 1595675
111222 0:23:48 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 1733055
InnoDB: Error: tried to read 16384 bytes at offset 0 5128192.
InnoDB: Was only able to read -1.
111222 0:23:49 InnoDB: Operating system error number 5 in a file operation.