[01:13] <yoink> Is there a preferred way to image a server I don't have easy physical access to (IE I don't want to make a datacenter appointment) so that I can test moving from 14.04 to 16.04 before actually doing it on the production machine? Or does rsync remain my best friend?
[01:15] <RoyK> rsync
[01:16] <RoyK> unless your server is on snapshotttable storage
[01:16] <RoyK> is it virtual?
[01:21] <yoink> No it's a physical machine colo'ed.
[01:22] <yoink> one of several. the datacenter is, thankfully a 10 minute walk from home so maybe I just bite the bullet and go in with a drive to take a snapshop of the volume. Would be quicker and not chew up any network resources.
[01:26] <yoink> on a totally different note, is there any way to speedup 16.04 reboots? it seems that on EC2 instances running 16.04 the systems wait quit a while on the network interfaces, though on my local KVM setup they're quicker (but nowhere near as quick as 14.04 was for reboots on any platform)
[01:42] <sarnold> yoink: the discussions in these bugs may be helpful https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774 https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1457400 https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1551415
[01:43] <yoink> sarnold: many thanks reading now
[12:18] <DexterF> greetings
[12:19] <DexterF> 16.04.1 installation. I'd like to install remotely via ssh. possible? machine is on a dhcp network
[12:37] <DexterF> quite another issue is that the installer sees only 2 of 3 hard disks and thus won't let me create a raid5. in /proc/partitions they are perfectly listed as sda sdb sdc
[12:38] <DexterF> to check a general installer bug I spawned a VM with 3 vdisks in Virtualbox and ran a 16.04.1 server installation. that saw the 3 disks but reveleaed quite another problem: once the raid was created I could not create partitions in md0
[12:38] <DexterF> is there a general problem with that?
[16:26] <ejat> conjure-up error : http://paste.ubuntu.com/23160160/