[07:03] <eugenio_> hi during the ubuntu server 18.04 installation I setup two raid1. one for sda1+sdb1 = md0 as / and the second sda2+sdb2 = md1 as /home. However, I was not able to setup md0 as bootable partition, and then I got busybox-initramfs error, can you help me?
[09:34] <jamespage> morning cpaelzer
[09:35] <jamespage> I was going to drop the 32 bit archs from ceph for cosmic; however I then realized how may reverse-depends there are of librados and librdb
[09:35] <jamespage> so putting them back but it will take me a while to sort out the 32 bit builds...
[09:52] <cpaelzer> hi jamespage
[09:53] <cpaelzer> thanks for the FYI
[09:53] <cpaelzer> is there anything on this you need me to do?
[09:57] <cpaelzer> jamespage: you reming me that I wanted to ask you if you think https://mail.openvswitch.org/pipermail/ovs-dev/2018-August/350437.html is a problem or if we can just wait for things to get into the usual released versions
[09:57] <cpaelzer> actually I just checked the latest packaging branch and we don't have the broken code
[09:57] <cpaelzer> so it might only be an issue if merging a newer upstream which has the bad code but not yet the fix
[09:57] <cpaelzer> what are the openvswitch current plans for now jamespage?
[09:58] <jamespage> cpaelzer: I was working on 2.9.2 but having trouble with testsuite reliablility
[09:58] <jamespage> oh no I did upload that already
[09:59] <cpaelzer> the offending patch of the issue I mentioned is of a few days ago
[09:59] <cpaelzer> and not yet released
[09:59] <cpaelzer> so it would be resolved on 2.9.3 or any other new versison I'd think
[09:59] <cpaelzer> yeah I see 2.9.2 in proposed
[10:00] <cpaelzer> is it hanging on said testsuite issues?
[10:13] <mwhudson> jamespage: hey, do you know anything about ceph not building extensions for python3.7?
[10:18] <mwhudson> huh uh forcing use of gcc-7 on arm because of bugs in gcc-6 seems out of date :)
[10:32] <jamespage> mwhudson: hmm
[10:32] <jamespage> mwhudson: I do not
[10:33] <jamespage> mwhudson: we can probably drop the gcc-7 bits for arm64 now
[10:33] <jamespage> that was more for the auto-backports to xenial
[10:33] <jamespage> which for mimic (as in cosmic) is not a concern
[10:47] <mwhudson> jamespage: maybe it should just not depend on python3-all-dev then :)
[10:47] <mwhudson> would be the easiest way to get it off http://people.canonical.com/~ubuntu-archive/transitions/html/python3.7-add.html
[14:11] <cryptodan> nacc: whislock I just read something interesting: https://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverId=X3P75 look at D703 referencing drive taken offline under certain circumstances.  I have D703 drives in my server
[14:38] <cryptodan> nacc: whislock and yup my drives are listed under that firmware fix for the drives.  So I will create a bootable cd in windows and update the firmware on all my drives then do a test of ubuntu 16.04 this weekend and see if I have the same issues
[16:15] <nacc> cryptodan_mobile: seems reasonalbe
[16:16] <leftyfb> I'm trying to run a PXE install on a UEFI client. I've got the PXE install working fine on BIOS clients, but the furthest I can get with UEFI is booting using the grubnetx64.efi.signed and being dumped to a GRUB prompt. Do I really need to rewrite my pxelinux.cfg in grub for this to all work for UEFI clients?
[16:16] <leftyfb> hi nacc :)
[16:19] <genii> leftyfb: Maybe look at https://www.syslinux.org/wiki/index.php?title=PXELINUX#UEFI for ideas
[16:20] <nacc> leftyfb: does that imply it's simply not loading a config file?
[16:20] <leftyfb> nacc: yeah, it's looking for grub/grub.cfg among some other grub files
[16:21] <leftyfb> I don't even have a grub at all. Up until now it hasn't been necessary
[16:23] <nacc> leftyfb: can you describe the config of your BIOS clients?
[16:25] <leftyfb> nacc: https://pastebin.ubuntu.com/p/szs9xYNvMT/
[16:25] <leftyfb> that's my pxelinux.0/default
[16:25] <leftyfb> not sure what other config you're looking for
[16:26] <leftyfb> sorry, pxelinux.cfg/default
[16:27] <nacc> leftyfb: so direct boot of kernel?
[16:28] <leftyfb> yep, not need for interaction. It's all done headless
[16:28] <leftyfb> not/no
[16:28] <nacc> leftyfb: and what file is being serv ed over dhcp?
[16:28] <leftyfb> pxelinux.0 for BIOS clients
[16:31] <nacc> leftyfb: i think you need to server out some efi file, iirc
[16:31] <nacc> syslinux.efi ?
[16:31] <nacc> and then can do the same config file, iirc
[16:31] <leftyfb> I'm trying that now
[16:32] <leftyfb> from genii's link
[16:32] <nacc> ah yeah, that's what i'm remembering
[16:32] <leftyfb> I HATE EFI btw
[16:32] <leftyfb> until now I've always had the option of disabling it
[16:38] <nacc> other than this, what is particularly different?
[16:39] <leftyfb> are you kidding?
[16:40] <nacc> leftyfb: I mean, in practice, I don't know why you "hate EFI"
[16:40] <leftyfb> it's a massive mess working out how to do different installations with EFI
[16:40] <leftyfb> it's always a mess every time I attempt it
[16:40] <nacc> is that because folks aren't spec compliant?
[16:41] <leftyfb> no idea
[16:42] <leftyfb> And if that's the case, then it's still a mess. The blame might not be on EFI, but on the vendor. But in the grand scheme of things, that doesn't make my stuff work :)
[16:43] <nacc> right
[16:43] <nacc> i just recall seeing the same thing with BIOS before
[16:45] <cryptodan> I have 2 machines with EFI and it was painless to setup.  one machine is dual boot with windows 10 and linux mint
[16:46] <leftyfb> "works for me" doesn't help people who have issues
[16:48] <cryptodan> on my lap top I had to change it from booting the windows efi boot manager to booting the ubuntu efi manager in the bios
[17:02] <eugenio_> hi, I'installing ubuntu-server18.04, the installation hangs at update-grub, do you know why?
[17:02] <leftyfb> EFI problems? ;)
[17:05] <eugenio_> leftyfb, did you answer to me?
[17:08] <moffa> Anyone know why http_proxy variable isn't used unless its run on the command as apt? (ubuntu 18.04) It makes no sense
[17:16] <nacc> moffa: evidence?
[17:17] <moffa> Well, just experience. When I run sudo echo $http_proxy, the variable is shown. But apt will hang.  If I run http_proxy=http://proxyinfo apt-get update it works
[18:36] <moffa> blah it was the sudoers file, I didn't a space between http_proxy and https_proxy not sure why it still echo'd the variable but its fixed.
[21:59] <pztrick> Any word on when http://changelogs.ubuntu.com/meta-release-lts will point to 18.04 point release?
[22:00] <pztrick> This file is used by server installs to check for next LTS release.
[22:00] <pztrick> AFAIK
[22:05] <tomreyn> pztrick: that's right, and no, not known, but 'soon'
[22:06] <hehehe> hi sarnold
[22:06] <hehehe> are u here?
[22:06] <hehehe> i was playing with that abandonware more :D
[22:06] <hehehe> hehe
[22:06] <hehehe> it uses a lot of outdated packages