Recover Locally Hosted Site off Crashed HDD - XAMPP

Problems with the Windows version of XAMPP, questions, comments, and anything related.

Re: Recover Locally Hosted Site off Crashed HDD - XAMPP

Postby Micci101 » 20. May 2015 15:06

2015-05-20 10:48:47 5920 [Note] Plugin 'FEDERATED' is disabled.
2015-05-20 10:48:47 8dc InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-05-20 10:48:47 5920 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-20 10:48:47 5920 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-20 10:48:47 5920 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-20 10:48:47 5920 [Note] InnoDB: Memory barrier is not used
2015-05-20 10:48:47 5920 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-20 10:48:47 5920 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-20 10:48:47 5920 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-20 10:48:47 5920 [Note] InnoDB: Completed initialization of buffer pool
2015-05-20 10:48:47 5920 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-20 10:48:47 5920 [Note] InnoDB: 128 rollback segment(s) are active.
2015-05-20 10:48:48 5920 [Note] InnoDB: Waiting for purge to start
2015-05-20 10:48:48 5920 [Note] InnoDB: 5.6.21 started; log sequence number 1665234
2015-05-20 10:48:48 5920 [Note] Server hostname (bind-address): '*'; port: 3306
2015-05-20 10:48:48 5920 [Note] IPv6 is available.
2015-05-20 10:48:48 5920 [Note] - '::' resolves to '::';
2015-05-20 10:48:48 5920 [Note] Server socket created on IP: '::'.
2015-05-20 10:54:10 2708 [Note] Plugin 'FEDERATED' is disabled.
2015-05-20 10:54:10 3f8 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-05-20 10:54:10 2708 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-20 10:54:10 2708 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-20 10:54:10 2708 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-20 10:54:10 2708 [Note] InnoDB: Memory barrier is not used
2015-05-20 10:54:10 2708 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-20 10:54:10 2708 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-20 10:54:10 2708 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-20 10:54:10 2708 [Note] InnoDB: Completed initialization of buffer pool
2015-05-20 10:54:10 2708 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-20 10:54:10 2708 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665244 in the ib_logfiles!
2015-05-20 10:54:10 2708 [Note] InnoDB: Database was not shutdown normally!
2015-05-20 10:54:10 2708 [Note] InnoDB: Starting crash recovery.
2015-05-20 10:54:10 2708 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-20 10:54:10 2708 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace mysql/innodb_index_stats.Id_63049 which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
2015-05-20 16:05:02 128 [Note] Plugin 'FEDERATED' is disabled.
2015-05-20 16:05:02 d48 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-05-20 16:05:02 128 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-05-20 16:05:02 128 [Note] InnoDB: The InnoDB memory heap is disabled
2015-05-20 16:05:02 128 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2015-05-20 16:05:02 128 [Note] InnoDB: Memory barrier is not used
2015-05-20 16:05:02 128 [Note] InnoDB: Compressed tables use zlib 1.2.3
2015-05-20 16:05:02 128 [Note] InnoDB: Not using CPU crc32 instructions
2015-05-20 16:05:02 128 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2015-05-20 16:05:02 128 [Note] InnoDB: Completed initialization of buffer pool
2015-05-20 16:05:02 128 [Note] InnoDB: Highest supported file format is Barracuda.
2015-05-20 16:05:02 128 [Note] InnoDB: The log sequence numbers 1665234 and 1665234 in ibdata files do not match the log sequence number 1665244 in the ib_logfiles!
2015-05-20 16:05:02 128 [Note] InnoDB: Database was not shutdown normally!
2015-05-20 16:05:02 128 [Note] InnoDB: Starting crash recovery.
2015-05-20 16:05:02 128 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-05-20 16:05:02 128 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace mysql/innodb_index_stats.Id_63049 which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.
Micci101
 
Posts: 12
Joined: 18. May 2015 10:33
Operating System: Windows 8 Pro 64bit

Re: Recover Locally Hosted Site off Crashed HDD - XAMPP

Postby Micci101 » 20. May 2015 15:07

It also mentions upon install that because of the UAC on my system, there may be some functionality that could be restricted.
Micci101
 
Posts: 12
Joined: 18. May 2015 10:33
Operating System: Windows 8 Pro 64bit

Re: Recover Locally Hosted Site off Crashed HDD - XAMPP

Postby mark.mcdonald » 20. May 2015 15:30

Micci101 wrote:2015-05-20 10:54:10 2708 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysql/innodb_index_stats uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd. Cannot open tablespace mysql/innodb_index_stats.Id_63049 which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.id_63049.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

Have you tried steps 2 or 3?
It's normal for the message regarding UAC to come up. This won't be an issue.
mark.mcdonald
 
Posts: 160
Joined: 13. March 2015 15:48
Location: Edmonton
Operating System: Windows Server 2012 R2

Re: Recover Locally Hosted Site off Crashed HDD - XAMPP

Postby Micci101 » 20. May 2015 15:52

I have done all the steps listed.

It works without me copying the files, once I do copy them I get the errors that I posted below ...

Was hoping you could try on your side faster with the actual file?
As you never know what mistakes I could be making on this side as I am not a programmer.
Micci101
 
Posts: 12
Joined: 18. May 2015 10:33
Operating System: Windows 8 Pro 64bit

Re: Recover Locally Hosted Site off Crashed HDD - XAMPP

Postby Micci101 » 20. May 2015 15:54

I did not try any of the steps in the log files, I did not see those.

Will try those first thing tomorrow morning, unless you have any other suggestions?
Micci101
 
Posts: 12
Joined: 18. May 2015 10:33
Operating System: Windows 8 Pro 64bit

Re: Recover Locally Hosted Site off Crashed HDD - XAMPP

Postby mark.mcdonald » 20. May 2015 17:47

Your installation has lots of duplicated files and is a waste of space.
0) Rename your xampp installation to C:\xampp1 or C:\xampp-original (make sure this is not running when you change the name of the root folder)

1) Copy/Download my copy of xampp (5.6.3) from my Dropbox
https://www.dropbox.com/sh/xp7a32rqhgub ... A6nxa?dl=0

2) Run the control panel. Start Apache and MySQL fresh and make sure you can see the xampp screen come up on your localhost.
(There should be no problems running this, if there are please post any error logs)

3) Stop Xampp. Replace the files within: xampp\mysql\data\ folder with that of C:\xampp-original\mysql\data\
xampp\htdocs\ folder with that of C:\xampp-original\htdocs\
Start Xampp. Make sure both Apache and MySQL turn green. Hopefully this will fix your issue. Crossing my fingers for you that this works.
mark.mcdonald
 
Posts: 160
Joined: 13. March 2015 15:48
Location: Edmonton
Operating System: Windows Server 2012 R2

Previous

Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 61 guests