Bug #22300 MySQL fails to start on machine running Windows Server 2003(E) with AMD Proc.
Submitted: 13 Sep 2006 7:55 Modified: 13 Sep 2006 8:33
Reporter: Karaethon Cantando Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.0 OS:Microsoft Windows (Windows Server 2003)
Assigned to: CPU Architecture:Any

[13 Sep 2006 7:55] Karaethon Cantando
Description:
On a server machine running Windows Server 2003 on a nAMD proccesor I cannot get MySQL to start, I do not know why, it runs fine on any other(non-amd) machine I put the drive into. 

I dont get any specific error reason as to why, just when I attempt to start the service it fails, and If I run Mysql-nt or max-nt, from a command line, I get a warning 
"060913  2:26:29 [Warning] Changed limits: max_open_files: 2048  max_connections:
 511  table_cache: 763" 
then it shuts down.

I am using the default build download generally available release off the MySQL.com download section.

My err file is filled with copies of this:

060913  2:50:13  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...
060913  2:50:13  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 255009.
InnoDB: Doing recovery: scanned up to log sequence number 0 255009
InnoDB: Page directory corruption: supremum not pointed to
060913  2:50:13  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 00000000...00000;

;InnoDB: End of page dump
060913  2:50:13  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page directory corruption: supremum not pointed to
060913  2:50:13  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex 00000...0000;                                                                  

;InnoDB: End of page dump
060913  2:50:13  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
060913  2:50:13 [ERROR] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: Got signal 11. Aborting!

060913  2:50:13 [ERROR] Aborting

060913  2:50:13 [Note] C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt: Shutdown complete

System Specs:
Amd Athalon Proccesor 1.30 GHz
512MB Ram
Windows Server 2003 Enterprise Edition

How to repeat:
Install MySQL on a Windows Server 2003 machine with an AMD Athalon Proccesor
[13 Sep 2006 8:03] Valeriy Kravchuk
Thank you for a problem report. Please, specify exact MySQL version (5.0.x, with 5.0.24a being the latest released) or, even better, send URL used for download. Do you use 64-bit edition of Windows Server 2003 on Athlon? Please, send also your my.ini file content.
[13 Sep 2006 8:13] Karaethon Cantando
ok, I started with 5.0.18 when the problem surfaced, I then upgraded to 5.0.24 last week with no change, after submiting this report read another that the guy had install problems when upgrading, he deleted everything and reinstalled, I decided to try this. I now have 5.0.24, clean install, and it is now up and running.
I do appologize for the needless bug report... but maybe mine will help someone else some day.
[13 Sep 2006 8:33] Valeriy Kravchuk
Closed, as problem seems solved by clean re-installation of latest version.