[Solved] Anyone having troubles with Ubuntu Server 14.04.1 amd64 on KVM?

Posted On // Leave a Comment


Solved


Ubuntu is stupid, and generates boot configuration files in /boot during installation, thus needing more than 256 inodes (the default partitioning scheme for /boot was somehow ext4 largefile, creating only one inode per MB on the disk.) It's worth noting that no other distribution does this out of: Debian 7.6.0, CentOS 6.5, CentOS 7.0, or ArchiLinux Dual.




Hello LowEndTalk,


While we were attempting to create templates for our customers with Ubuntu Server, we ran into (yet another) problem that we have never seen before with any other distribution (it goes without saying that I am not surprised at this point.)


The specific steps to reproduce, and materials used are listed below.




Materials


1) ubuntu-14.04.1-server-amd64.iso obtained from an official mirror, then tested (verifying the checksums, as well as the on-boot media self-check) to make sure it is authentic and not corrupt. We attached the CDROM using the hd/hda bus and target, with readonly set, and no cache.


http://ift.tt/1AMbMO2


2) A 5120M qcow2 format disk image, created with the qemu-img create command. We attached the VHD using the vd/vda bus and target, with no cache (we also tried writethrough.) The qemu-img info confirms that the disk was created successfully, shown below for confirmation purposes:



image: disk.0
file format: qcow2
virtual size: 5.0G (5368709120 bytes)
disk size: 196K
cluster_size: 65536



Method


We then VNC into the machine after it's created, and follow the normal setup prompts to install the system. We check the media, then continue with the installation. We choose English, United States, English (US), English (US) as they come up as options (and do not do a keyboard layout detection, as there's no point.)


We then choose the following settings per the prompts as they come up, in order:




  • Hostname: localhost.localdomain




  • Full Name: toor




  • Username: toor




  • Password: toorPassw0rd! (test password)




  • Encrypt Home Directory: [no]




  • Timezone: Vancouver




  • Partitioning: Manual (Pretty standard really, 256M /boot EXT4, MAX / LVM2/EXT4)




Partitioning




  • Then wait ~ 30 seconds for the installation to complete.




  • Proxy: No Proxy




  • Wait for "Configuring Apt..." to retrieve 61 files... then retrieve 32 more... then 1 more...




  • Configuring Tasksel: No Automatic Updates




  • Software Selection: OpenSSH Server only




Software Selection




  • Wait for the system to retrieve 191 more files... (and prepare/configure them all)




  • Wait for the system to retrieve and install a language pack (en_base)...




  • Install Grub Boot Loader: [yes]




Install GRUB2 on MBR



  • Get shown this very shiny error message, that contains zero useful information


grub-install /dev/vda failed




Solution


So, how do we got about fixing what Canonical appears to have screwed up this time?


Is anyone else experiencing a problem given the above very common install procedure?


http://ift.tt/1dvHQ0Z

0 comments:

Post a Comment