gistfile1.txt

core@vxxx-xxx-xxx-xxx ~ $ sudo coreos-install -d /dev/vda
Downloading and verifying coreos_production_image.bin.bz2...
gpg: Signature made Mon Feb 17 23:01:34 2014 UTC using RSA key ID xxxxxxxx
gpg: key xxxxxxxx marked as ultimately trusted
gpg: checking the trustdb
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: Good signature from "CoreOS Buildbot (Offical Builds) <[email protected]>"
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  164M  100  164M    0     0  21.3M      0  0:00:07  0:00:07 --:--:-- 23.8M
coreos_production_image.bin.bz2: OK
coreos_production_image.bin.bz2: OK
Writing coreos_production_image.bin.bz2 to /dev/vda...
  /tmp/coreos-install.xxeHszD0W1/coreos_production_image.bin.bz2: done
Warning: Unable to open /dev/sr0 read-write (Read-only file system).  /dev/sr0 has been opened read-only.
Warning: Unable to open /dev/sr0 read-write (Read-only file system).  /dev/sr0 has been opened read-only.
Error: Invalid partition table - recursive partition on /dev/sr0.
Error: The backup GPT table is not at the end of the disk, as it should be.  This might mean that another operating system believes the disk is smaller.  Fix, by moving the backup to the end (and removing the old backup)?
Warning: Not all of the space available to /dev/vda appears to be used, you can fix the GPT to use all of the space (an extra 413528064 blocks) or continue with the current setting?