My server unable to boot after resizing
[ 0.100000] ffff881811ef7ddb ffffffff810f1edb 0000000000000000 ffff881811ef8
[ 0.100000] ffffffff81036f77 ccffffffff0a0005 d3e47c6016e06514 ffffffff810fa
[ 0.100000] Call Trace:
[ 0.100000] [<ffffffff810f1eda>] ? set_freezable+0x2a/0xa0
[ 0.100000] [<ffffffff810f1edb>] ? set_freezable+0x2b/0xa0
[ 0.100000] [<ffffffff81036f77>] text_poke_bp+0x57/0xf0
[ 0.100000] [<ffffffff810f1eda>] ? set_freezable+0x2a/0xa0
[ 0.100000] [<ffffffff81033bab>] arch_jump_label_transform+0x9b/0x120
[ 0.100000] [<ffffffff81f83430>] ? kvm_smp_prepare_boot_cpu+0x15/0x15
[ 0.100000] [<ffffffff81197226>] __jump_label_update+0x76/0x90
[ 0.100000] [<ffffffff811972c8>] jump_label_update+0x88/0x90
[ 0.100000] [<ffffffff81197525>] static_key_slow_inc+0x95/0xa0
[ 0.100000] [<ffffffff81f83466>] kvm_spinlock_init_jump+0x36/0x46
[ 0.100000] [<ffffffff81002135>] do_one_initcall+0xb5/0x200
[ 0.100000] [<ffffffff81420b55>] ? find_next_bit+0x15/0x20
[ 0.100000] [<ffffffff81039789>] ? speculative_store_bypass_ht_init+0x79/0x0
[ 0.100000] [<ffffffff81f680a7>] kernel_init_freeable+0xcc/0x218
[ 0.100000] [<ffffffff8185ed70>] ? rest_init+0x80/0x80
[ 0.100000] [<ffffffff8185ed7e>] kernel_init+0xe/0xe0
[ 0.100000] [<ffffffff8186bfd2>] ret_from_fork+0x42/0x80
[ 0.100000] [<ffffffff8185ed70>] ? rest_init+0x80/0x80
[ 0.100000] Code: 00 00 0f a2 4d 85 ed 74 4a 41 0f b6 04 24 41 38 06 75 18 3
[ 0.100000] RIP [<ffffffff81036b43>] text_poke+0x1a3/0x240
[ 0.100000] RSP <ffff881811ef7d50>
[ 0.100000] ---[ end trace 701027c1e71c2b1b ]---
[ 0.100007] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0b
[ 0.100007]
[ 0.101326] ---[ end Kernel panic - not syncing: Attempted to kill init! exib
[ 0.101326]</ffff881811ef7d50></ffffffff81036b43></ffffffff8185ed70></ffffffff8186bfd2></ffffffff8185ed7e></ffffffff8185ed70></ffffffff81f680a7></ffffffff81039789></ffffffff81420b55></ffffffff81002135></ffffffff81f83466></ffffffff81197525></ffffffff811972c8></ffffffff81197226></ffffffff81f83430></ffffffff81033bab></ffffffff810f1eda></ffffffff81036f77></ffffffff810f1edb></ffffffff810f1eda>
1 Reply
tlambert
Linode Staff
Hey @grouprint!
Your best bet when you've got a server down is to open a Support Ticket so the Linode Support team can address the issue quickly.
In situations where your server is experiencing a kernel panic, the first thing I suggest is to boot into Rescue Mode and run a file system check. This will examine your disk and repair errors if possible.
If the issue is not resolved after that process completes, the next step would be to boot your Linode with a different kernel. If you have been using GRUB2, boot using the Latest Linode kernel. Similarly, boot using GRUB2 if you've been using the Latest Linode kernel.
I hope this helps!