I'm experiencing strange problem. I have downloaded latest version of xampp 1.7.7. extracted from zip on my local hard drive.
After doing setup_xampp.bat I have run xampp_control.exe and both apache and mysql started without any problems.
I have decided to copy this xampp to my USB hard drive (3 terabytes), I have again run setup_xampp.bat and xampp_control.exe but this time mysql didn't start. Apache is running nicely but mysql won't budge.
I have checked mysql log for USB drive:
120102 9:38:30 [Note] Plugin 'FEDERATED' is disabled.
120102 9:38:30 InnoDB: The InnoDB memory heap is disabled
120102 9:38:30 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120102 9:38:30 InnoDB: Compressed tables use zlib 1.2.3
120102 9:38:30 InnoDB: Initializing buffer pool, size = 16.0M
120102 9:38:30 InnoDB: Completed initialization of buffer pool
120102 9:38:30 InnoDB: highest supported file format is Barracuda.
120102 9:38:30 InnoDB: Operating system error number 87 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: File name F:\xampp 1.7.7\mysql\data\ib_logfile0
InnoDB: File operation call: 'aio read'.
InnoDB: Cannot continue operation.
I have checked local hard drive log as well:
120102 9:41:46 [Note] Plugin 'FEDERATED' is disabled.
120102 9:41:46 InnoDB: The InnoDB memory heap is disabled
120102 9:41:46 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120102 9:41:46 InnoDB: Compressed tables use zlib 1.2.3
120102 9:41:46 InnoDB: Initializing buffer pool, size = 16.0M
120102 9:41:46 InnoDB: Completed initialization of buffer pool
120102 9:41:46 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!
120102 9:41:46 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
120102 9:41:47 InnoDB: Waiting for the background threads to start
120102 9:41:48 InnoDB: 1.1.8 started; log sequence number 1595675
120102 9:41:48 [Note] Event Scheduler: Loaded 0 events
120102 9:41:48 [Note] mysql\bin\mysqld.exe: ready for connections.
Version: '5.5.16' socket: '' port: 3306 MySQL Community Server (GPL)
It runs but It looks like it found same problems "starting crash recovery". I have also used USB drive with 1 terabyte capacity and I have no such problems.
Do You tink 3 terabytes might have caused this problem? Did anyone came across something like that?