/srv/irclogs.ubuntu.com/2014/09/19/#ubuntu-installer.txt

psivaacjwatson: curious if you'd be able to take a look at: https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1359712 please?08:15
ubot2Launchpad bug 1359712 in base-installer (Ubuntu) ""base-installer: error: /cdrom/install/filesystem.squashfs has failed to be mounted as squashfs." is seen on trusty server instalaltions" [Undecided,New]08:15
psivaacjwatson: plars mentioned someone was asking for trusty server install failures08:15
psivaas/for/about08:15
cjwatsonpsivaa: ack10:37
fish_re10:53
fish_cjwatson: not directly installer related but just saw you were involved in 'biosdevname on poweredge'. so I just installed trusty (sucessfuly this time ;)) but now my 2nd interface sometimes is called eth1, sometimes em210:54
fish_so well, there is this problem now and I'm wondering whether I should care to fix it or jsut disable biosdevname10:55
cjwatsonI would just disable it if it is causing trouble11:01
fish_franky, given that dell 'invented' this doesn't make me more confident in using it - even on dell boxes.11:01
cjwatsonit ... wasn't really my idea to enable it by default11:01
fish_what should it solve anyway? it's not very clear to me.. the device ordering should be the same across all my systems if the hw is the same. and if I change the hw, I reinstall the systems anyways11:02
fish_cjwatson: ok, all the discussion sounded like that :) thanks for confirming, I'll just disable it11:02
cjwatsonnetwork device enumeration isn't necessarily stable across reboots even with the same hardware11:02
cjwatsoncan depend on such things as which order the PCI bus happens to respond in11:03
fish_cjwatson: I've heard about that but I never saw that happen across reboots11:03
fish_IIRC the order gets encoded as udev rules during install anyway, right? but I never saw it during reinstalls either11:04
fish_well, actually a few years ago I had such issue once when bootstrapping debian but it was somehow caused by odd kernel parameters (aka me)11:05
cjwatsonmy understanding is that the udev rule approach is not in fact reliable and can e.g. result in interfaces getting stuck with renamed_foo names11:09
fish_hrm well, I see how it makes sense to have something like biosdevname.. well, but since I was thinking 'I need to reinstall those systems, let's just install trusty now' and this already took me longer than I hoped I'll stick with the good ol' eth naming for now11:11
fish_but things are really odd with trusty. why on earth does it run dhcp even though /etc/network/interfaces doesn't set that up?11:47
fish_ah never mind, that's my fault11:56
cjwatsonpsivaa: ah, just a d-i kernel abi bump needed, I'll do that13:27
psivaacjwatson: ack, thanks.13:27
=== DalekSec_ is now known as DalekSec
=== Laney is now known as Guest37661
=== DalekSec_ is now known as DalekSec
=== lan3y is now known as Laney
fish__now I hoped I've fixed the lvm volume creation in my late script but now the ubuntu-vg vg can't be found15:29
fish__is it possible to set the default lvm volume group name? it defaults to the hostname which I don't want (and don't think is a good idea in general)15:39
fish__I can't even find the sources for whatever is defining the volume group name16:19
fish__could someone point me to that?16:20
fish__finally I found it: partman-auto-lvm/new_vg_name - would be great of those things are documented somewhere. it's not in here for example: https://help.ubuntu.com/lts/installation-guide/example-preseed.txt16:28
fish__so now my last problem with this install: somehow it didn't install ifenslave even though I specified it in my preseed: d-i pkgsel/include string openssh-server lxc-docker btrfs-tools apparmor ifenslave16:40
fish__the log shows that it's installing apparmor but not ifenslave16:40
fish__I'll reinstall this machine again to make sure. it sounds so unlikely that even I can't believe it ;)16:59
=== superm1_ is now known as superm1

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!