So my instance was failing to boot with the following error in my console logs:

modprobe: FATAL: Module scsi_wait_scan not found.

modprobe: FATAL: Module scsi_wait_scan not found.

modprobe: FATAL: Module scsi_wait_scan not found.

modprobe: FATAL: Module scsi_wait_scan not found.

modprobe: FATAL: Module scsi_wait_scan not found.

modprobe: FATAL: Module scsi_wait_scan not found.

modprobe: FATAL: Module scsi_wait_scan not found.

[   67.206758] dracut Warning: No root device “block:/dev/disk/by-label/\x2f” found

[   67.213032] dracut Warning: Boot has failed. To debug this issue add “rdshell” to the kernel command line.

[   67.220871] dracut Warning: Signal caught!

[   67.224840] dracut Warning: Boot has failed. To debug this issue add “rdshell” to the kernel command line.

[   67.232101] Kernel panic – not syncing: Attempted to kill init! exitcode=0x00000100

[   67.232101]

[   67.239306] CPU: 0 PID: 1 Comm: init Not tainted 4.14.138-89.102.amzn1.x86_64 #1

[   67.244990] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006

[   67.249767] Call Trace:

[   67.252079]  dump_stack+0x5c/0x82

[   67.254990]  panic+0xd5/0x242

[   67.257618]  do_exit+0xb95/0xba0

[   67.260411]  do_group_exit+0x3a/0xa0

[   67.263465]  SyS_exit_group+0x10/0x10

[   67.267296]  do_syscall_64+0x67/0x110

[   67.270318]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2

[   67.274341] RIP: 0033:0x7fce6f87b249

[   67.277484] RSP: 002b:00007ffe2d6069a8 EFLAGS: 00000202 ORIG_RAX: 00000000000000e7

[   67.283245] RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007fce6f87b249

[   67.289874] RDX: 0000000000000001 RSI: 0000000000a43dd0 RDI: 0000000000000001

[   67.297033] RBP: 0000000000000000 R08: 000000000000003c R09: 00000000000000e7

[   67.305140] R10: ffffffffffffff70 R11: 0000000000000202 R12: 000000000040217c

[   67.313132] R13: 00007ffe2d606c80 R14: 0000000000000000 R15: 0000000000000000

[   67.320883] Kernel Offset: disabled

After spending some time on this I managed to replicate the error by changing the label on my disk. So if you are getting the error, just make sure you’re using the correct label.

You can easily replicate the error using the steps below:

[ec2-user@linuxbyimraan ~]$ sudo blkid

/dev/xvda1: LABEL=”/” UUID=”30bc2d31-3d87-4039-b63f-7b6acbff282d” TYPE=”ext4″ PARTLABEL=”Linux” PARTUUID=”fd0b0ede-242e-4abd-821c-a58f9d7af840″

[ec2-user@ linuxbyimraan ~]$ sudo e2label /dev/xvda1 test

Using the above commands, I changed the label from / to test. After rebooting the instance, you should get a Kernel Offset: disabled error.

Leave a Reply

Your email address will not be published. Required fields are marked *