为毛我的MySQl5.5无法启动？

我的存储空间占满了，导致mysql自动停了，然后我删除部分文件，腾出了2g左右空间后，mysql就无法启动了，刚换到宝塔就出这种问题，什么个情况

1. InnoDB: Database physically writes the file full: wait...
   
2. 171124 13:24:28  InnoDB: Log file /www/server/data/ib_logfile0 did not exist: new to be created
   
3. InnoDB: Setting log file /www/server/data/ib_logfile0 size to 5 MB
   
4. InnoDB: Database physically writes the file full: wait...
   
5. 171124 13:24:28  InnoDB: Log file /www/server/data/ib_logfile1 did not exist: new to be created
   
6. InnoDB: Setting log file /www/server/data/ib_logfile1 size to 5 MB
   
7. InnoDB: Database physically writes the file full: wait...
   
8. InnoDB: Doublewrite buffer not found: creating new
   
9. InnoDB: Doublewrite buffer created
   
10. InnoDB: 127 rollback segment(s) active.
    
11. InnoDB: Creating foreign key constraint system tables
    
12. InnoDB: Foreign key constraint system tables created
    
13. 171124 13:24:28  InnoDB: Waiting for the background threads to start
    
14. 171124 13:24:29 InnoDB: 5.5.58 started; log sequence number 0
    
15. 171124 13:24:29 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
    
16. 171124 13:24:29 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
    
17. 171124 13:24:29 [Note] Server socket created on IP: '0.0.0.0'.
    
18. 171124 13:24:29 [Note] Event Scheduler: Loaded 0 events
    
19. 171124 13:24:29 [Note] /www/server/mysql/bin/mysqld: ready for connections.
    
20. Version: '5.5.58-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
    
21. 171124 13:24:30 [Note] /www/server/mysql/bin/mysqld: Normal shutdown
    
22. 
    
23. 171124 13:24:30 [Note] Event Scheduler: Purging the queue. 0 events
    
24. 171124 13:24:30  InnoDB: Starting shutdown...
    
25. 171124 13:24:31  InnoDB: Shutdown completed; log sequence number 1595675
    
26. 171124 13:24:31 [Note] /www/server/mysql/bin/mysqld: Shutdown complete
    
27. 
    
28. 171124 13:24:31 [Note] Plugin 'FEDERATED' is disabled.
    
29. 171124 13:24:31 InnoDB: The InnoDB memory heap is disabled
    
30. 171124 13:24:31 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    
31. 171124 13:24:31 InnoDB: Compressed tables use zlib 1.2.7
    
32. 171124 13:24:31 InnoDB: Using Linux native AIO
    
33. 171124 13:24:31 InnoDB: Initializing buffer pool, size = 16.0M
    
34. 171124 13:24:31 InnoDB: Completed initialization of buffer pool
    
35. 171124 13:24:31 InnoDB: highest supported file format is Barracuda.
    
36. 171124 13:24:31  InnoDB: Waiting for the background threads to start
    
37. 171124 13:24:32 InnoDB: 5.5.58 started; log sequence number 1595675
    
38. 171124 13:24:32 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
    
39. 171124 13:24:32 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
    
40. 171124 13:24:32 [Note] Server socket created on IP: '0.0.0.0'.
    
41. 171124 13:24:32 [Note] /www/server/mysql/bin/mysqld: ready for connections.
    
42. Version: '5.5.58-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
    
43. 171124 13:24:41 [Note] Plugin 'FEDERATED' is disabled.
    
44. 171124 13:24:41 InnoDB: The InnoDB memory heap is disabled
    
45. 171124 13:24:41 InnoDB: Mutexes and rw_locks use GCC atomic builtins
    
46. 171124 13:24:41 InnoDB: Compressed tables use zlib 1.2.7
    
47. 171124 13:24:41 InnoDB: Using Linux native AIO
    
48. 171124 13:24:41 InnoDB: Initializing buffer pool, size = 16.0M
    
49. 171124 13:24:41 InnoDB: Completed initialization of buffer pool
    
50. 171124 13:24:41 InnoDB: highest supported file format is Barracuda.
    
51. 171124 13:24:41  InnoDB: Waiting for the background threads to start
    
52. 171124 13:24:42 InnoDB: 5.5.58 started; log sequence number 1595675
    
53. 171124 13:24:42 [Note] Recovering after a crash using mysql-bin
    
54. 171124 13:24:42 [Note] Starting crash recovery...
    
55. 171124 13:24:42 [Note] Crash recovery finished.
    
56. 171124 13:24:42 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
    
57. 171124 13:24:42 [Note]   - '0.0.0.0' resolves to '0.0.0.0';
    
58. 171124 13:24:42 [Note] Server socket created on IP: '0.0.0.0'.
    
59. 171124 13:24:42 [Note] Event Scheduler: Loaded 0 events
    
60. 171124 13:24:42 [Note] /www/server/mysql/bin/mysqld: ready for connections.
    
61. Version: '5.5.58-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
    
62. 171124 16:23:56 [Note] /www/server/mysql/bin/mysqld: Normal shutdown
    
63. 
    
64. 171124 16:23:56 [Note] Event Scheduler: Purging the queue. 0 events
    
65. 171124 16:23:56  InnoDB: Starting shutdown...
    
66. 171124 16:23:58  InnoDB: Shutdown completed; log sequence number 51210707
    
67. 171124 16:23:58 [Note] /www/server/mysql/bin/mysqld: Shutdown complete
    

复制代码

你删的什么文件

河妖 发表于 2017-12-23 11:28
你删的什么文件

删的www/wwwroot下面的网站文件和回收站的文件

你私信我ssh信息看看吧 我给你启动看看 私信完回复一下

河妖 发表于 2017-12-23 15:06
你私信我ssh信息看看吧 我给你启动看看 私信完回复一下

好的 谢谢，私信你了

数据表损坏了 无法启动

河妖 发表于 2017-12-23 15:36
数据表损坏了 无法启动

什么东东？数据表自己也会坏？我都好几年了都没出过问题，弄过来表就坏了，没搞错吧

河妖 发表于 2017-12-23 15:36
数据表损坏了 无法启动

还好我有备份，这要是没备份不直接over了

河妖 发表于 2017-12-23 15:36
数据表损坏了 无法启动

以后遇到这种情况一般怎么处理？

taobao 发表于 2017-12-23 15:48
以后遇到这种情况一般怎么处理？

可能是你数据库在读写过程中 因硬盘满了mysql自动停止导致损坏了数据表

河妖 发表于 2017-12-23 16:39
可能是你数据库在读写过程中 因硬盘满了mysql自动停止导致损坏了数据表

像这种情况数据表有什么办法可以修复吗？