1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

I messed up! Deleted ibdata1...

Discussion in 'Troubleshooting and Problems' started by Kelso, Dec 10, 2012.

  1. Kelso

    Kelso Member

    I made the mistake of deleting ibdata1 from /var/lib/mysql, unforunately the service was restarted and the delete file is now gone.

    MySQL wont start now due to this, and Im in desprate desire to get my site back up and running.
    Code:
    121210 11:11:10 [Note] Plugin 'FEDERATED' is disabled.
    121210 11:11:10 InnoDB: The InnoDB memory heap is disabled
    121210 11:11:10 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    121210 11:11:10 InnoDB: Compressed tables use zlib 1.2.3.4
    121210 11:11:10 InnoDB: Initializing buffer pool, size = 128.0M
    121210 11:11:10 InnoDB: Completed initialization of buffer pool
    121210 11:11:10 InnoDB: highest supported file format is Barracuda.
    InnoDB: The log sequence number in ibdata files does not match
    InnoDB: the log sequence number in the ib_logfiles!
    121210 11:11:10  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...
    121210 11:11:10  InnoDB: Assertion failure in thread 140648100542272 in file fsp0fsp.c line 2102
    InnoDB: Failing assertion: inode
    InnoDB: We intentionally generate a memory trap.
    InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
    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: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
    InnoDB: about forcing recovery.
    16:11:10 UTC - mysqld got signal 6 ;
    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.
     
    key_buffer_size=16777216
    read_buffer_size=131072
    max_used_connections=0
    max_threads=151
    thread_count=0
    connection_count=0
    It is possible that mysqld could use up to
    key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346681 K  bytes of memory
    Hope that's ok; if not, decrease some variables in the equation.
     
    Thread pointer: 0x0
    Attempting backtrace. You can use the following information to find out
    where mysqld died. If you see no messages after this, something went
    terribly wrong...
    stack_bottom = 0 thread_stack 0x30000
    mysqld(my_print_stacktrace+0x29)[0x7feb3068d759]
    mysqld(handle_fatal_signal+0x483)[0x7feb30554ae3]
    /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7feb2f2a6cb0]
    /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7feb2e912425]
    /lib/x86_64-linux-gnu/libc.so.6(abort+0x17b)[0x7feb2e915b8b]
    mysqld(+0x65a400)[0x7feb30798400]
    mysqld(+0x65fd6f)[0x7feb3079dd6f]
    mysqld(+0x66c2be)[0x7feb307aa2be]
    mysqld(+0x637925)[0x7feb30775925]
    mysqld(+0x5e4a67)[0x7feb30722a67]
    mysqld(+0x5ae989)[0x7feb306ec989]
    mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7feb30557111]
    mysqld(+0x307cf1)[0x7feb30445cf1]
    mysqld(_Z11plugin_initPiPPci+0xa94)[0x7feb30449314]
    mysqld(+0x281a06)[0x7feb303bfa06]
    mysqld(_Z11mysqld_mainiPPc+0x59b)[0x7feb303c30eb]
    /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7feb2e8fd76d]
    mysqld(+0x27b845)[0x7feb303b9845]
    The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
    information that should help you find out what is causing the crash.
    
    this is what I get when attempting to start mysql.. start mysql just says job failed, so im manually starting using mysqld to see the errors. please help!
     
  2. Luke F

    Luke F Well-Known Member

    hard power off the box immediately (no graceful shutdowns)

    then grab an image of the disk (or just access it directly, I guess it doesn't matter) using another box and run some recovery tools
     
    Jake Bunce likes this.
  3. Kelso

    Kelso Member

    Since it appears all the data is in the tables, is there anyway to repopulate the innodb data? I was able to get mysql started again, and i essentially made a backup and have a fresh installation now. I copies the .frm/.myi/.myd data to the new folder, but it doesnt show up..

    will any of the rebuild functions in admin resolve this?
     
  4. Kelso

    Kelso Member

    man im ****ed.. :(
     
  5. Kelso

    Kelso Member

    attempting photorec using testdisk... /fingers crossed.. :|​
     
  6. Luke F

    Luke F Well-Known Member

    ibdata1 contains basically all of xenforo (and other innodb tables) when using the default setting for innodb table storage (as most people do)

    If you have no backup, your only option is to use recovery tools
     
    Jake Bunce likes this.

Share This Page