EBS Snapshot of root device fails to start on new instance "Instance reachability check failed"

0

I have a linux server, went to update & upgrade, then on reboot it failed the 2nd check "Instance reachability check failed"

So I started a fresh EC2 linux (Ubuntu) instance and connected to it successfully on launch (i-058b3702fde1abd66) I then replaced the root device with a EBS snapshot of the initial server that failed. I get the same issue "Instance reachability check failed". I've now tried 3 snapshots (going back 3 days) all the same reachability check failed.

System log is below, seems to be some mount issue, so I reconnected root drive to a clean instance and edited /etc/fstab to be:

LABEL=cloudimg-rootfs / ext4 defaults,discard 0 1 LABEL=UEFI /boot/efi vfat umask=0077 0 1

Any ideas what next?

(this concerns me more because I thought my snapshots were my backups, and although I can access the files on the drive, the root drive not booting causes me concerns about my backup strategy)

Tks

[    3.523087] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[    3.532357] x86/mm: Checking user space page tables
[    3.586991] x86/mm: Checked W+X mappings: passed, no W+X pages found.
[    3.594864] Run /init as init process
Loading, please wait...
Starting version 245.4-4ubuntu3.22
[    3.842997] cryptd: max_cpu_qlen set to 1000
[    3.905239] FDC 0 is a S82078B
[    3.943483] AVX2 version of gcm_enc/dec engaged.
[    3.948912] AES CTR mode by8 optimization enabled
[    4.948350] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input4
Begin: Loading essential drivers ... [    5.326179] raid6: avx2x4   gen() 25672 MB/s
[    5.398181] raid6: avx2x4   xor()  8269 MB/s
[    5.470181] raid6: avx2x2   gen() 25398 MB/s
[    5.542180] raid6: avx2x2   xor() 15182 MB/s
[    5.614183] raid6: avx2x1   gen() 22721 MB/s
[    5.686179] raid6: avx2x1   xor() 12890 MB/s
[    5.754182] raid6: sse2x4   gen() 12825 MB/s
[    5.826180] raid6: sse2x4   xor()  7682 MB/s
[    5.898180] raid6: sse2x2   gen() 13219 MB/s
[    5.970180] raid6: sse2x2   xor()  8518 MB/s
[    6.042180] raid6: sse2x1   gen() 11670 MB/s
[    6.114178] raid6: sse2x1   xor()  7422 MB/s
[    6.118951] raid6: using algorithm avx2x4 gen() 25672 MB/s
[    6.122946] raid6: .... xor() 8269 MB/s, rmw enabled
[    6.127082] raid6: using avx2x2 recovery algorithm
[    6.132753] xor: automatically using best checksumming function   avx       
[    6.138696] async_tx: api initialized (async)
done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... [    6.221155] Btrfs loaded, crc32c=crc32c-intel, zoned=yes, fsverity=yes
Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.34
[/usr/sbin/fsck.ext4 (1) -- /dev/xvda1] fsck.ext4 -a -C0 /dev/xvda1 
cloudimg-rootfs: clean, 239778/1920000 files, 3112153/3931899 blocks
done.
[    6.325413] EXT4-fs (xvda1): Unrecognized mount option "uquota" or missing value
mount: mounting /dev/xvda1 on /root failed: Invalid argument
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /dev on /root/dev failed: No such file or directory
done.
mount: mounting /run on /root/run failed: No such file or directory
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.4) multi-call binary.

Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT [ARGS]

Free initramfs and switch to another root fs:
chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /,
execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint.

	-c DEV	Reopen stdio to DEV after switch
	-d CAPS	Drop capabilities
	-n	Dry run
Target filesystem doesn't have requested /sbin/init.
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.4) multi-call binary.

Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT [ARGS]

Free initramfs and switch to another root fs:
chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /,
execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint.

	-c DEV	Reopen stdio to DEV after switch
	-d CAPS	Drop capabilities
	-n	Dry run
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.4) multi-call binary.

Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT [ARGS]

Free initramfs and switch to another root fs:
chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /,
execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint.

	-c DEV	Reopen stdio to DEV after switch
	-d CAPS	Drop capabilities
	-n	Dry run
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.4) multi-call binary.

Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT [ARGS]

Free initramfs and switch to another root fs:
chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /,
execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint.

	-c DEV	Reopen stdio to DEV after switch
	-d CAPS	Drop capabilities
	-n	Dry run
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.4) multi-call binary.

Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT [ARGS]

Free initramfs and switch to another root fs:
chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /,
execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint.

	-c DEV	Reopen stdio to DEV after switch
	-d CAPS	Drop capabilities
	-n	Dry run
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.4) multi-call binary.

Usage: run-init [-d CAP,CAP...] [-n] [-c CONSOLE_DEV] NEW_ROOT NEW_INIT [ARGS]

Free initramfs and switch to another root fs:
chroot to NEW_ROOT, delete all in /, move NEW_ROOT to /,
execute NEW_INIT. PID must be 1. NEW_ROOT must be a mountpoint.

	-c DEV	Reopen stdio to DEV after switch
	-d CAPS	Drop capabilities
	-n	Dry run
No init found. Try passing init= bootarg.


BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.4) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) 
Rod
gefragt vor 6 Monaten255 Aufrufe
Keine Antworten

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen