EC2 启动期间发生内核恐慌
在使用 AMI 映像模板在新 EC2 上部署新应用程序版本期间,我收到以下错误:
[ 1.670047] No filesystem could mount root, tried:
[ 1.670048]
[ 1.677170] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 1.685026] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.14.181-140.257.amzn2.x86_64 #1
[ 1.692532] Hardware name: Amazon EC2 t3a.nano/, BIOS 1.0 10/16/2017
以前它工作得像魅力 - 我没有更改任何 AMI 或模板设置 - 只是向 nginx 添加了新的 SSL 证书
我找到了这篇故障排除文章,但是由于我无法访问实例终端,因此无法移动它。
我尝试通过添加不同的内核 ID 来启动新实例,但收到此错误:
You cannot launch multiple AMIs with different virtualization styles at the same time.
我相信在 AMI 期间内核已发生某种变化并导致问题 - 这可能吗?
什么可能导致该问题以及如何解决?
During deployment of new app version on new EC2 with template from AMI image I got following error:
[ 1.670047] No filesystem could mount root, tried:
[ 1.670048]
[ 1.677170] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 1.685026] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.14.181-140.257.amzn2.x86_64 #1
[ 1.692532] Hardware name: Amazon EC2 t3a.nano/, BIOS 1.0 10/16/2017
previously it was working like charm - I haven't change any AMI or template setting - just added new SSL certs to nginx
I found this troubleshooting article but cannot move with it since I cannot access instance terminal.
I've tried to boo new instance with add different kernel ID but got this error:
You cannot launch multiple AMIs with different virtualization styles at the same time.
I believed during AMI kernel has somehow changed and it causes problem - is it possible?
What can cause that issue and how to solve?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论