In order to tell in detail about the comments of Diomidis Spinellis in the accepted answer to the answer, it is important to check the file system label of the device that you are trying to include as a new root device. Although, to fix the problem with my own server migration, I had to do the following before my instance boots up:
Use the e2label command to change the label of the ext2 / ext3 / ext4 file system that you created for the new root device.
First check the file system label for the current root device.
$ sudo e2label /dev/xvda1 cloudimg-rootfs
Install the new device on the same file system label.
$ sudo e2label /dev/xvdg 'cloudimg-rootfs'
In my case, the label was cloudimg-rootfs . Sometimes it will be simple.
It is important to understand how e2label works; check man e2label on your computer or visit http://linux.die.net/man/8/e2label for more information.
Joey Jan 09 '15 at 3:58 2015-01-09 03:58
source share