rtc_cmos 00:01: setting system clock to 2017-06-11 05:33:18 UTC (1497159198) Initalizing network drop monitor service input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input4 md: Waiting for all devices to be available before autodetect md: If you don't use raid, use raid=noautodetect md: Autodetecting RAID arrays. md: Scanned 0 and added 0 devices. md: autorun ... md: ... autorun DONE. RAMDISK: gzip image found at block 0 RAMDISK: incomplete write (4472 != 15380) write error VFS: Cannot open root device "UUID=bf4548e3-83c6-4661-9868-89e071376723" or unknown-block(0,0) Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Pid: 1, comm: swapper Tainted: G W --------------- 2.6.32-504.23.4.el6.x86_64 #1
What could be the problem here and how can I prevent this sort of problem during my migrations?
--
© 2017 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-discussion@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
---
You received this message because you are subscribed to the Google Groups "gce-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gce-discussion+unsubscribe@googlegroups.com.
To post to this group, send email to gce-discussion@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gce-discussion/12249667-8227-4518-a960-608a27de6276%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Found this post on how to fix the error “VFS: Unable to mount root fs on unknown-block” on CentOS Linux that might or might not help you to boot your instance. It says that running ‘sudo yum update kernel’ resolves the issue. Add a custom metadata on your Compute Engine VM instances with the key ‘startup-script’ and value ‘sudo yum update kernel’. Save the changes and restart the instance.