I resized(upgraded) a node. and now the node is not booting.
I resized(upgraded) a node. and now the node is not booting. The console says :
[ 0.467176] registered taskstats version 1
[ 0.468309] Key type trusted registered
[ 0.469175] Key type encrypted registered
[ 0.469859] IMA: No TPM chip found, activating TPM-bypass! (rc=-19)
[ 0.471022] Magic number: 8:149:339
[ 0.471706] rtc_cmos 00:00: setting system clock to 2020-06-01 17:20:29 UTC )
[ 0.473341] md: Waiting for all devices to be available before autodetect
[ 0.474447] md: If you don't use raid, use raid=noautodetect
[ 0.475550] md: Autodetecting RAID arrays.
[ 0.476203] md: autorun …
[ 0.476662] md: … autorun DONE.
[ 0.477251] List of all partitions:
[ 0.477816] No filesystem could mount root, tried:
[ 0.478641] Kernel panic - not syncing: VFS: Unable to mount root fs on unkn)
[ 0.479586] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 3.10.0-1062.9.1.el7.x81
[ 0.479586] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.14
[ 0.479586] Call Trace:
[ 0.479586] [<ffffffff8a17ac23>] dump_stack+0x19/0x1b
[ 0.479586] [<ffffffff8a174967>] panic+0xe8/0x21f
[ 0.479586] [<ffffffff8a789790>] mount_block_root+0x291/0x2a0
[ 0.479586] [<ffffffff8a7897f2>] mount_root+0x53/0x56
[ 0.479586] [<ffffffff8a789931>] prepare_namespace+0x13c/0x174
[ 0.479586] [<ffffffff8a78940e>] kernel_init_freeable+0x222/0x249
[ 0.479586] [<ffffffff8a788b1f>] ? initcall_blacklist+0xb0/0xb0
[ 0.479586] [<ffffffff8a169b80>] ? rest_init+0x80/0x80
[ 0.479586] [<ffffffff8a169b8e>] kernel_init+0xe/0x100
[ 0.479586] [<ffffffff8a18dd24>] ret_from_fork_nospec_begin+0xe/0x21
[ 0.479586] [<ffffffff8a169b80>] ? rest_init+0x80/0x80
[ 0.479586] Kernel Offset: 0x8a00000 from 0xffffffff81000000 (relocation ran)</ffffffff8a169b80></ffffffff8a18dd24></ffffffff8a169b8e></ffffffff8a169b80></ffffffff8a788b1f></ffffffff8a78940e></ffffffff8a789931></ffffffff8a7897f2></ffffffff8a789790></ffffffff8a174967></ffffffff8a17ac23>
any suggestions please.
3 Replies
Just guessing here but,
Kernel panic - not syncing: VFS: Unable to mount root fs on unkn)
Are your Linode’s disks configured to mount in the disk/config profile?
Have you tried using the rescue mode to examine/check your disks?
Full details in this article including how to check your disks.
I got the node working after executing following command in chroot environment
yum reinstall kernel
and rebooting.
:)
this link helped. https://www.digitalocean.com/community/questions/kernal-panic-not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block-0-0
Great, glad you got it sorted.
I wouldn’t have thought a resize would have impacted the software within your Linode, unless it had been migrated to different hardware that wasn’t compatible with your current kernel (Intel —> AMD?)
One to look out for I guess! Thanks for sharing your solution.