EC2 instance failing status check due to full disk

0

I have an Ubuntu instance created from a marketplace AMI, and it's failing status checks after a reboot. System logs show this:

[ 99.747391] cloud-init[864]: OSError: [Errno 28] No space left on device [FAILED] Failed to start Initial cloud-init job (metadata service crawler). See 'systemctl status cloud-init.service' for details.

I increased the volume size, but it seems to be failing before it gets to the point where it's able to extend the filesystem. I don't have a password-enabled user, so I can't use the serial console. I spun up a temporary instance and tried to mount the root volume as a secondary volume, but got an error because it's from a marketplace AMI. I launched a new instance from the same AMI, but am still unable to mount it. Do I have any other options?

질문됨 일 년 전283회 조회
1개 답변
0

The instance you are attaching the full volume must be in stopped state according to Attach an Amazon EBS volume to an instance.

profile pictureAWS
전문가
kentrad
답변함 일 년 전

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠