- Newest
- Most votes
- Most comments
Hello.
Have you checked the OS system log?
Also, is it possible to restore EC2 from a snapshot?
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/troubleshoot-unreachable-instance.html
Hi,
The simplest way to understand what's going is to use InstanceConnect (before trying ssh from your laptop)
So, follow this KC article to do it: https://repost.aws/knowledge-center/ec2-instance-connect-troubleshooting
Best,
Didier
this is my system logs....
[ 2.991133] md: ... autorun DONE. [ 2.994607] /dev/root: Can't open blockdev [ 2.998785] VFS: Cannot open root device "UUID=86f13586-c516-4493-81ea-e6f07cf45644" or unknown-block(0,0): error -6 [ 3.010102] Please append a correct "root=" boot option; here are the available partitions: [ 3.019045] ca00 104857600 xvda [ 3.019046] driver: vbd [ 3.027490] ca01 62912495 xvda1 8a4bbb4c-b20b-4757-94b8-2cec5fe5fe7b [ 3.027491] [ 3.038944] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 3.047659] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.218-208.862.amzn2.x86_64 #1 [ 3.055811] Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006 [ 3.062506] Call Trace: [ 3.065232] dump_stack+0x57/0x70 [ 3.069167] panic+0x10e/0x2f1 [ 3.072981] mount_block_root+0x221/0x29f [ 3.078070] prepare_namespace+0x13b/0x16a [ 3.083473] kernel_init_freeable+0x172/0x198 [ 3.088703] ? rest_init+0xb4/0xb4 [ 3.092255] kernel_init+0xa/0x11c [ 3.096442] ret_from_fork+0x22/0x30 [ 3.100700] Kernel Offset: disabled
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked 2 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 5 months ago
this are my system logs. If you could suggest something after analysing this...
[ 2.991133] md: ... autorun DONE. [ 2.994607] /dev/root: Can't open blockdev [ 2.998785] VFS: Cannot open root device "UUID=86f13586-c516-4493-81ea-e6f07cf45644" or unknown-block(0,0): error -6 [ 3.010102] Please append a correct "root=" boot option; here are the available partitions: [ 3.019045] ca00 104857600 xvda [ 3.019046] driver: vbd [ 3.027490] ca01 62912495 xvda1 8a4bbb4c-b20b-4757-94b8-2cec5fe5fe7b [ 3.027491] [ 3.038944] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 3.047659] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.218-208.862.amzn2.x86_64 #1 [ 3.055811] Hardware name: Xen HVM domU, BIOS 4.11.amazon 08/24/2006 [ 3.062506] Call Trace: [ 3.065232] dump_stack+0x57/0x70 [ 3.069167] panic+0x10e/0x2f1 [ 3.072981] mount_block_root+0x221/0x29f [ 3.078070] prepare_namespace+0x13b/0x16a [ 3.083473] kernel_init_freeable+0x172/0x198 [ 3.088703] ? rest_init+0xb4/0xb4 [ 3.092255] kernel_init+0xa/0x11c [ 3.096442] ret_from_fork+0x22/0x30 [ 3.100700] Kernel Offset: disabled