MySQL Forums
Forum List  »  Newbie

Re: .\ibdata1 can't be opened in read-write mode
Posted by: Dan Godoy
Date: January 10, 2015 09:18PM

Barry,

Thanks a ton for your help. I'm getting somewhere.

Running Command Prompt as Administrator, I was able to get the MySQL service to start (mysqld --console output is at the bottom. It includes logging information about the database not being shut down properly, which is consistent with my suspicion that this all started when my laptop battery died).

I fired up another instance of Command Prompt as Administrator to launch mysql.exe, and see if I could access my databases.

I got this:

C:\Program Files\MySQL\MySQL Server 5.6\bin>mysql "--defaults-file=C:\ProgramDa
ta\MySQL\MySQL Server 5.6\my.ini" "-uroot" "-p" "--default-character-set=utf8"
Enter password: *******
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: Y
ES)

As you said, it looks like permissions. But this is all very strange. Prior to my battery dying, I was able to log into this database without any escalation.

Should I try a fresh install of MySQL? If I did that, would I somehow be able to recover data from my existing data stores?

Thanks in advance for any more advice.

Dan


C:\Program Files\MySQL\MySQL Server 5.6\bin>mysqld --console
2015-01-10 21:09:54 0 [Warning] TIMESTAMP with implicit DEFAULT value is depreca
ted. Please use --explicit_defaults_for_timestamp server option (see documentati
on for more details).
2015-01-10 21:09:54 2916 [Note] Plugin 'FEDERATED' is disabled.
2015-01-10 21:09:54 2916 [Note] InnoDB: Using atomics to ref count buffer pool p
ages
2015-01-10 21:09:54 2916 [Note] InnoDB: The InnoDB memory heap is disabled
2015-01-10 21:09:54 2916 [Note] InnoDB: Mutexes and rw_locks use Windows interlo
cked functions
2015-01-10 21:09:54 2916 [Note] InnoDB: Memory barrier is not used
2015-01-10 21:09:54 2916 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-01-10 21:09:54 2916 [Note] InnoDB: Not using CPU crc32 instructions
2015-01-10 21:09:54 2916 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2015-01-10 21:09:54 2916 [Note] InnoDB: Completed initialization of buffer pool
2015-01-10 21:09:54 2916 [Note] InnoDB: Highest supported file format is Barracu
da.
2015-01-10 21:09:54 2916 [Note] InnoDB: The log sequence numbers 1625997 and 162
5997 in ibdata files do not match the log sequence number 1626007 in the ib_logf
iles!
2015-01-10 21:09:54 2916 [Note] InnoDB: Database was not shutdown normally!
2015-01-10 21:09:54 2916 [Note] InnoDB: Starting crash recovery.
2015-01-10 21:09:54 2916 [Note] InnoDB: Reading tablespace information from the
.ibd files...
2015-01-10 21:09:54 2916 [Note] InnoDB: Restoring possible half-written data pag
es
2015-01-10 21:09:54 2916 [Note] InnoDB: from the doublewrite buffer...
2015-01-10 21:09:54 2916 [Note] InnoDB: 128 rollback segment(s) are active.
2015-01-10 21:09:54 2916 [Note] InnoDB: Waiting for purge to start
2015-01-10 21:09:54 2916 [Note] InnoDB: 5.6.21 started; log sequence number 1626
007
2015-01-10 21:09:54 2916 [Note] Server hostname (bind-address): '*'; port: 3306
2015-01-10 21:09:54 2916 [Note] IPv6 is available.
2015-01-10 21:09:54 2916 [Note] - '::' resolves to '::';
2015-01-10 21:09:54 2916 [Note] Server socket created on IP: '::'.
2015-01-10 21:09:54 2916 [Note] Event Scheduler: Loaded 0 events
2015-01-10 21:09:54 2916 [Note] mysqld: ready for connections.
Version: '5.6.21' socket: '' port: 3306 MySQL Community Server (GPL)

Options: ReplyQuote




Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.