EC2 unresponsive ,status check failed , not reaching via ping/ssh

Question

Ec2 is not unresponsive after the force shut down and the normal start of ec2 instances. 
When starting, the Status check failing and the below logs are seen via Get system log option on aws console:
Now as there is no way to access to ec2, how can I resolve it?

```
----
[    3.766101] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 11
[    4.210518] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[    4.862401]  nvme0n1: p1 p2
[    4.876284] random: nonblocking pool is initialized
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... [    4.929843] device-mapper: uevent: version 1.0.3
[    4.931134] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.25.2
[/sbin/fsck.ext4 (1) -- /dev/nvme0n1p2] fsck.ext4 -a -C0 /dev/nvme0n1p2 
/dev/nvme0n1p2 contains a file system with errors, check forced.
/dev/nvme0n1p2: Inodes that were part of a corrupted orphan linked list found.

/dev/nvme0n1p2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
	(i.e., without -a or -p options)
fsck exited with status code 4
done.
Failure: File system check of the root filesystem failed
The root filesystem on /dev/nvme0n1p2 requires a manual fsck
[    5.052672] ACPI: bus type USB registered
[    5.053800] usbcore: registered new interface driver usbfs
[    5.055203] usbcore: registered new interface driver hub
[    5.056611] usbcore: registered new device driver usb
[    5.058820] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    5.060950] ehci-pci: EHCI PCI platform driver
[    5.065352] uhci_hcd: USB Universal Host Controller Interface driver
[    5.068489] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    5.071678] hidraw: raw HID events driver (C) Jiri Kosina
[    5.074091] usbcore: registered new interface driver usbhid
[    5.075511] usbhid: USB HID core driver
```

Answer

Yes, I am able to login using serial port , but no idea how to fix this thing. If I run the command manually on serial console then i get the same error.

```
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.25.2
[/sbin/fsck.ext4 (1) -- /dev/nvme0n1p2] fsck.ext4 -a -C0 /dev/nvme0n1p2 
/dev/nvme0n1p2 contains a file system with errors, check forced.
/dev/nvme0n1p2: Inodes that were part of a corrupted orphan linked list found.

/dev/nvme0n1p2: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., withou[   13.089321] ACPI: bus type USB registered
t -a or -p optio[   13.158239] usbcore: registered new interface driver usbfs
ns)
fsck exited[   13.160407] usbcore: registered new interface driver hub
 with status cod[   13.163360] usbcore: registered new device driver usb
e 4
done.
Failure: File system check of the root filesystem failed
The root filesystem on /dev/nvme0n1p2 requires a manual fsck
[   13.265290] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   13.357764] ehci-pci: EHCI PCI platform driver
[   13.364183] uhci_hcd: USB Universal Host Controller Interface driver
[   13.368666] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[   13.373432] hidraw: raw HID events driver (C) Jiri Kosina
[   13.458440] usbcore: registered new interface driver usbhid
[   13.460332] usbhid: USB HID core driver
(initramfs) Failure: File system check of the root filesystem failed
/bin/sh: 1: Failure:: not found
(initramfs) fsck -r -V
fsck from util-linux 2.25.2```

Answer

Are you able to use the EC2 Serial Console. This provides a way to troubleshoot boot and network connectivity issues by establishing a connection to the serial port of an instance. This access can be used for interactive troubleshooting.

The AWS article Why is my EC2 Linux instance unreachable and failing one or both of its status checks? may be of use

The AWS article [Why is my EC2 Linux instance unreachable and failing one or both of its status checks?](https://aws.amazon.com/premiumsupport/knowledge-center/ec2-linux-status-check-failure/) may be of use

EC2 unresponsive ,status check failed , not reaching via ping/ssh

Relevant content