[Win 7] Mysql shutdown unexpectedly (O.S. error 238)

[keea]

Hello, im having this issue with mysql:

this is what control panel says when i try to start mysql

1:47:12 [mysql] Checking default ports...
1:47:12 [mysql] Attempting to start MySQL app...
1:47:12 [mysql] Executing ""c:\xampp\mysql\bin\mysqld.exe" --defaults-file="c:\xampp\mysql\bin\my.ini" --standalone --console"
1:47:12 [mysql] Return code: 0
1:47:13 [mysql] Status change detected: running
1:47:13 [mysql] Status change detected: stopped
1:47:13 [mysql] Error: MySQL shutdown unexpectedly.
1:47:13 [mysql] This may be due to a blocked port, missing dependencies,
1:47:13 [mysql] improper privileges, a crash, or a shutdown by another method.
1:47:13 [mysql] Press the Logs button to view error logs and check
1:47:13 [mysql] the Windows Event Viewer for more clues
1:47:13 [mysql] If you need more help, copy and post this
1:47:13 [mysql] entire log window on the forums

and this is the error log:

2016-06-21 01:47:13 a3c 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.
2016-06-21 1:47:13 2620 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2016-06-21 1:47:13 2620 [Note] InnoDB: The InnoDB memory heap is disabled
2016-06-21 1:47:13 2620 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-06-21 1:47:13 2620 [Note] InnoDB: Memory barrier is not used
2016-06-21 1:47:13 2620 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-06-21 1:47:13 2620 [Note] InnoDB: Using generic crc32 instructions
2016-06-21 1:47:13 2620 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2016-06-21 1:47:13 2620 [Note] InnoDB: Completed initialization of buffer pool
2016-06-21 1:47:13 2620 [Note] InnoDB: Highest supported file format is Barracuda.
2016-06-21 01:47:13 a3c InnoDB: Operating system error number 38 in a file operation.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
InnoDB: Operation read to file os\os0file.cc and at line 3158
2016-06-21 1:47:13 2620 [ERROR] InnoDB: File (unknown): 'read' returned OS error 238. Cannot continue operation

I think this can easily be fixed, but i don't know how to.
This is the story: i backed up my old "xampp" folder and installed xampp again, so i have all the files from my old databases, and all the information that i need to work with, so i tried deleting the default xampp "mysql/data/" folder and i replaced it with my old "data" folder.

Im not an expert with databases, so i dont think this is the correct way to "backup", but i couldn't find the way to do it. i guess someone here can help me.

[Nobbie]

I think this can easily be fixed

Why do you think so? It is far from easy.

This is the story: i backed up my old "xampp" folder and installed xampp again, so i have all the files from my old databases, and all the information that i need to work with, so i tried deleting the default xampp "mysql/data/" folder and i replaced it with my old "data" folder.

Aha - this does not work in any case, if there is a "large" release step between old and new Xampp (especially between old MySQL and new MySQL), you cannot simply copy the whole data folder. Instead run a an export of your databases in the old Xampp and import the resulting file into the new Xampp, that is the way how it should work in any case.

If you are lucky, this is only a question of permissions, maybe MySQL cannot open the files in the data folder due to missing rights. How do you run/start MySQL? Try to run NOT as a service, run it directly from the Xampp Control DIalog (a mouse click). If you run it as a service, MySQL is executed by the "SYSTEM" User, which has restricted rights. If you run it directly via mouse click, it is executed by your own UserID, probably the same UserID you used to copy the data folder. Maybe the problem disappears when starting MySQL directly.

If it does not help, you have to do the export/import instead.

[keea]

if there is a "large" release step between old and new Xampp

that is a good point, i will try to fix it installing the same version i used to work with.

If you are lucky, this is only a question of permissions

It is not, i can start mysql perfectly when i try using the new data folder, the problem is in my old mysql folder

If it does not help, you have to do the export/import instead.

i can't start mysql, so i can't export my databases.


___________________________________________________________________

EDIT: I installed the same version of xampp, and it doesn't work, actually, i still have the old xampp folder, and i tried to start mysql from there, and the same error shows off, i also tried starting mysql from the clean installation and it started normally, but when i replaced the "mysql/data" folder, the error appears. Help me please

I just want my databases structure (Tables, and columns). i dont need any data from the tables.