File system error occurs when root volume of EC2 instance is reduced and reconnected.

Asked 1 weeks ago, Updated 1 weeks ago, 330 views

File system error occurs when root volume of EC2 instance is reduced and reconnected.
Instructions are provided in this article
I did the work with reference to .

Use this task to reattach the volume as the root volume and restart the EC2 instance, while some instances pass the status check at 2/2.

To eliminate this failure, image each successful instance to AMI and
I will use that AMI to restart the instance.
If you do that, the status check will fail 1/2 of the time.

If the status check fails, it is difficult to determine the cause because ssh cannot be performed and system logs cannot be retrieved.

What are the possible causes and countermeasures for this symptom?

aws amazon-ec2

2022-11-24 20:36

2 Answers

<Working instructions in this article > formatting xfs with ext4 may indicate that the file system is corrupted.

2022-11-24 21:44

At the beginning of the referenced article

Depending on your Linux and partition configuration, the method may vary.
This article provides an example procedure for the following environments:

  • Using LVM
  • The boot loader is GRUB2 (using Stage 1.5)
  • The operating system is Linux (RedHatEnterpriseLinux 7.5)
  • EC2 for work is t2 instance

It says.I understand that there is an error in the grub, but does the condition match that the boot loader is GRUB2 (using Stage 1.5)? I don't know because there is no information about the environment in the questionnaire, but if it doesn't match, I think we need to do something else.

The status check will fail 1/2 no matter what.

The status check may be considered a black box, but it is explained to some extent by the instance status check.There are two types of status checks:

  • Checking System Status
    Hardware health checks primarily responsible for AWS.
  • Check Instance Status
    Check if the network interface responds to ARP.Because the OS cannot respond to ARP without initializing the network interface and giving it an IP address, it acts as a check to see if the OS is able to initialize.

Strictly speaking, you need to look at the instance metrics, but I think it's 1/2 because the instance status check almost certainly failed from the background of the question.
The cause is clear, and the OS has not been able to boot to the point where it initializes the network interface.
As long as the network interface has not been initialized, it is natural that it cannot ssh.

2022-11-24 21:47

If you have any answers or tips

© 2022 OneMinuteCode. All rights reserved.