3 added 20 characters in body
source | link

If you only see the .frm files, then there is a strong likelihood that the storage engine isin use was InnoDB and innodb_file_per_table must have been off by default.

If you transfertransferred everything from datadir on the crashed server onto another disk on another machine, you may be able to startup mysql with that folder as is.

SayFor example, suppose ServerA is your crashed server and ServerB is where you want it placed.

  • Install MySQL 5.5.8 on ServerB
  • net stop mysql on ServerB to make sure mysql is down on ServerB
  • md C:\MySQLData on ServerB
  • Drop everything from the data folder on ServerA into C:\MySQLData on ServerB
  • Make C:\MySQLData the new datadir

Add this to my.ini on ServerB

[mysql]
datadir=C:/MySQLData
  • C:\> del C:\MySQLData\ib_logfile* on ServerB
  • net start mysql on ServerB

Please try this and tell us what happened

UPDATE 2012-02-03 17:06 EDT

Since you were able to recover everything NOW DO THIS:

mysqldump -u... -p... -A -d --routines --triggers > C:\MySQLSchema.sql

This will give all table structures in the MySQL Instance.

If you only see the .frm files, then there is a strong likelihood that the storage engine is use was InnoDB and innodb_file_per_table must have been off by default.

If you transfer everything from datadir on the crashed server onto another disk on another machine, you may be able to startup mysql with that folder as is.

Say ServerA is your crashed server and ServerB is where you want it placed.

  • Install MySQL 5.5.8 on ServerB
  • net stop mysql on ServerB to make sure mysql is down on ServerB
  • md C:\MySQLData on ServerB
  • Drop everything from the data folder on ServerA into C:\MySQLData on ServerB
  • Make C:\MySQLData the new datadir

Add this to my.ini on ServerB

[mysql]
datadir=C:/MySQLData
  • C:\> del C:\MySQLData\ib_logfile* on ServerB
  • net start mysql on ServerB

Please try this and tell us what happened

UPDATE 2012-02-03 17:06 EDT

Since you were able to recover everything NOW DO THIS:

mysqldump -u... -p... -A -d --routines --triggers > C:\MySQLSchema.sql

This will give all table structures in the MySQL Instance.

If you only see the .frm files, then there is a strong likelihood that the storage engine in use was InnoDB and innodb_file_per_table must have been off by default.

If you transferred everything from datadir on the crashed server onto another disk on another machine, you may be able to startup mysql with that folder as is.

For example, suppose ServerA is your crashed server and ServerB is where you want it placed.

  • Install MySQL 5.5.8 on ServerB
  • net stop mysql on ServerB to make sure mysql is down on ServerB
  • md C:\MySQLData on ServerB
  • Drop everything from the data folder on ServerA into C:\MySQLData on ServerB
  • Make C:\MySQLData the new datadir

Add this to my.ini on ServerB

[mysql]
datadir=C:/MySQLData
  • C:\> del C:\MySQLData\ib_logfile* on ServerB
  • net start mysql on ServerB

Please try this and tell us what happened

UPDATE 2012-02-03 17:06 EDT

Since you were able to recover everything NOW DO THIS:

mysqldump -u... -p... -A -d --routines --triggers > C:\MySQLSchema.sql

This will give all table structures in the MySQL Instance.

2 deleted 1 characters in body
source | link

If you only see the .frm files, then there is a strong likelihood that the storage engine is use was InnoDB and innodb_file_per_table must have been off by default.

If you transfer everything from datadir on the crashed server onto another disk on another machine, you may be able to startup mysql with that folder as is.

Say ServerA is your crashed server and ServerB is where you want toit placed.

  • Install MySQL 5.5.8 on ServerB
  • net stop mysql on ServerB to make sure mysql is dopnwdown on ServerB
  • md C:\MySQLData on ServerB
  • Drop everything from the data folder on ServerA into C:\MySQLData on ServerB
  • Make C:\MySQLData the new datadir

Add this to my.ini on ServerB

[mysql]
datadir=C:/MySQLData
  • C:\> del C:\MySSQLData\ib_logfile*\MySQLData\ib_logfile* on ServerB
  • net start mysql on ServerB

Please try this and tell us what happened

UPDATE 2012-02-03 17:06 EDT

Since you were able to recover everything NOW DO THIS:

mysqldump -u... -p... -A -d --routines --triggers > C:\MySQLSchema.sql

This will give all table structures in the MySQL Instance.

If you only see the .frm files, then there is a strong likelihood that the storage engine is use was InnoDB and innodb_file_per_table must have been off by default.

If you transfer everything from datadir on the crashed server onto another disk on another machine, you may be able to startup mysql with that folder as is.

Say ServerA is your crashed server and ServerB is where you want to placed.

  • Install MySQL 5.5.8 on ServerB
  • net stop mysql on ServerB to make sure mysql is dopnw on ServerB
  • md C:\MySQLData on ServerB
  • Drop everything from the data folder on ServerA into C:\MySQLData on ServerB
  • Make C:\MySQLData the new datadir

Add this to my.ini on ServerB

[mysql]
datadir=C:/MySQLData
  • C:\> del C:\MySSQLData\ib_logfile* on ServerB
  • net start mysql on ServerB

Please try this and tell us what happened

If you only see the .frm files, then there is a strong likelihood that the storage engine is use was InnoDB and innodb_file_per_table must have been off by default.

If you transfer everything from datadir on the crashed server onto another disk on another machine, you may be able to startup mysql with that folder as is.

Say ServerA is your crashed server and ServerB is where you want it placed.

  • Install MySQL 5.5.8 on ServerB
  • net stop mysql on ServerB to make sure mysql is down on ServerB
  • md C:\MySQLData on ServerB
  • Drop everything from the data folder on ServerA into C:\MySQLData on ServerB
  • Make C:\MySQLData the new datadir

Add this to my.ini on ServerB

[mysql]
datadir=C:/MySQLData
  • C:\> del C:\MySQLData\ib_logfile* on ServerB
  • net start mysql on ServerB

Please try this and tell us what happened

UPDATE 2012-02-03 17:06 EDT

Since you were able to recover everything NOW DO THIS:

mysqldump -u... -p... -A -d --routines --triggers > C:\MySQLSchema.sql

This will give all table structures in the MySQL Instance.

1
source | link

If you only see the .frm files, then there is a strong likelihood that the storage engine is use was InnoDB and innodb_file_per_table must have been off by default.

If you transfer everything from datadir on the crashed server onto another disk on another machine, you may be able to startup mysql with that folder as is.

Say ServerA is your crashed server and ServerB is where you want to placed.

  • Install MySQL 5.5.8 on ServerB
  • net stop mysql on ServerB to make sure mysql is dopnw on ServerB
  • md C:\MySQLData on ServerB
  • Drop everything from the data folder on ServerA into C:\MySQLData on ServerB
  • Make C:\MySQLData the new datadir

Add this to my.ini on ServerB

[mysql]
datadir=C:/MySQLData
  • C:\> del C:\MySSQLData\ib_logfile* on ServerB
  • net start mysql on ServerB

Please try this and tell us what happened