Mysql is not working....please help me

[Arshiya]

2018-03-26 13:35:18 5960 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-03-26 13:35:18 5960 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-26 13:35:18 5960 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-03-26 13:35:18 5960 [Note] InnoDB: Memory barrier is not used
2018-03-26 13:35:18 5960 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-26 13:35:18 5960 [Note] InnoDB: Using generic crc32 instructions
2018-03-26 13:35:18 5960 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-03-26 13:35:18 5960 [Note] InnoDB: Completed initialization of buffer pool
2018-03-26 13:35:19 5960 [Note] InnoDB: Highest supported file format is Barracuda.
2018-03-26 13:35:19 5960 [Note] InnoDB: The log sequence numbers 1948554 and 1948554 in ibdata files do not match the log sequence number 1986878 in the ib_logfiles!
2018-03-26 13:35:19 5960 [Note] InnoDB: Database was not shutdown normally!
2018-03-26 13:35:19 5960 [Note] InnoDB: Starting crash recovery.
2018-03-26 13:35:19 5960 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-03-26 13:35:19 5960 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace arsh_crm_db/arsh_crm uses space ID: 37 at filepath: .\arsh_crm_db\arsh_crm.ibd. Cannot open tablespace practice/crud which uses space ID: 37 at filepath: .\practice\crud.ibd
InnoDB: Error: could not open single-table tablespace file .\practice\crud.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.
2018-03-26 13:35:20 9b8 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.
2018-03-26 13:35:20 2488 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

2018-03-26 13:35:20 2488 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2018-03-26 13:35:21 2488 [Note] InnoDB: The InnoDB memory heap is disabled
2018-03-26 13:35:21 2488 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2018-03-26 13:35:21 2488 [Note] InnoDB: Memory barrier is not used
2018-03-26 13:35:21 2488 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-03-26 13:35:21 2488 [Note] InnoDB: Using generic crc32 instructions
2018-03-26 13:35:21 2488 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2018-03-26 13:35:21 2488 [Note] InnoDB: Completed initialization of buffer pool
2018-03-26 13:35:21 2488 [Note] InnoDB: Highest supported file format is Barracuda.
2018-03-26 13:35:21 2488 [Note] InnoDB: The log sequence numbers 1948554 and 1948554 in ibdata files do not match the log sequence number 1986878 in the ib_logfiles!
2018-03-26 13:35:21 2488 [Note] InnoDB: Database was not shutdown normally!
2018-03-26 13:35:21 2488 [Note] InnoDB: Starting crash recovery.
2018-03-26 13:35:21 2488 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-03-26 13:35:21 2488 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace arsh_crm_db/arsh_crm uses space ID: 37 at filepath: .\arsh_crm_db\arsh_crm.ibd. Cannot open tablespace practice/crud which uses space ID: 37 at filepath: .\practice\crud.ibd
InnoDB: Error: could not open single-table tablespace file .\practice\crud.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.