MySQL Bugs: #50001: mysqld instant crash if InnoDB on D:

Bug #50001	mysqld instant crash if InnoDB on D:
Submitted:	30 Dec 2009 17:01	Modified:	30 May 2012 12:25
Reporter:	Alec Cawley	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: InnoDB storage engine	Severity:	S3 (Non-critical)
Version:	5.1.41	OS:	Windows (Win XP SP 3)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
In clean install with InnoDB assigned to D:, MySQL fails to run because mysqld crashes at once, whether run as Service or at command prompt.

How to repeat:
Clean install from mysql-5.1.41-win32.msi downloaded from MySQL site. Everything as default except put InnoDB table in default position on D: (NTFS, 110GB free) and don't setup security. Service fails to start, mysqld run from console quits immediately.

Suggested fix:
Keep InnoDB on C:. (Only used D: because it had more free space).

Thank you for the bug report. With clean install you meant never was installed a MySQL server on that machine so there is not chance to exist older my.ini files, older InnoDB files and so on?. Thanks in advance.

Sorry, no. MySQL 5.0 had previously been installed on the computer. I tried to upgrade to 5.1, but the installer would not work while 5.0 present. I removed 5.0 by deletion (the Add/Remove programs did not have an uninstall link) and hunted through the registry for anything with "MySQL" in it to remove. However, I did not delete any files not under C:\Program Files\MySQL, so there might have been InnoDB files left in other places.

Alec,

It looks like the InnoDB tried to open an old (and maybe corrupted) data file. Could you please check whether there is any MySQL configuration file (my.ini or my.cnf) under c:\windows, or c:\?

Thanks,
Calvin

Apologies for delay in replying - I only have access to the failing system at weekends.

No, the only files called my.* on c: are my.ini in the MySQL Server 5.1 directory (plus others in the recycle bin). There is a my.png deep down in another application on D:, but I cannot see this affecting the system. I uninstalled 5.1, deleted the Program Files/MySQL directory and tried again, with the same result. Specifically, there is no my.ini in C:\ or C:\Windows.

Alec

Hi Alec,

Please, try this standalone test as follows, if you still have D: that caused problems.

1.  download and exact mysql-noinstall-5.1.62-win32.zip  to the D: drive:
http://dev.mysql.com/downloads/mirror.php?id=406810#mirrors

2.  then run it directly like this:
cd d:\mysql-5.1.62-win32\bin

3.  mysqld.exe --no-defaults --port=3333 --console --core-file --tmpdir=. 

Does the above crash?  If so what kind of filesystem/disk is D: ?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".