When you automount a drive in /etc/fstab even if it's not important like an external drive that you only use sometimes and is not required for booting, it will prevent a successfuly boot. If you disable quiet mode for booting you will see something like below "A start job is running for dev-disk ...." How do we fix an fstab entry from preventi........

The strange thing is that usually the first install or two will work on any new machine but then it suddenly won't. I had this experience on QEMU 2.13 on a different machine. There is something finicky or buggy about the CUCM installer even when choosing the same virtual hardware specs. qemu-kvm command: /usr/libexec/qemu-kvm -version QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2-2.506.el6_10.1), Copyright (c) 2003-2008 Fabrice Bellard ........

I messed up the bootloader by accident on a standard Centos 6.3 install because I turned the /dev/vda1 boot partition into an mdadm raid 1. This was all done correctly aside from one point Ididn't realize was an issue metadata=00.90 is the only thing that will allow you to boot (otherwise grub won't work and you won't boot). So the next step is rescue mode from a CD right? The problem you will find is that grub does not detect your hard drives, this is Ibelieve is be........

The best way I could figure out is to use another guest of some sort to do this, while assigning the disk that needs to be resized to the same guest. So say we have /dev/xvda as the guests drive and we've booted it up. We also have /dev/xvdb (this is going to be the image/disk to be resized). In this case it's based on an ext3/4 image. Run e2fsck on it to ensure there are no filesystem errors. e2fsck /dev/xvdb........