[06:21] <lordievader> Good morning
[10:38] <mnms_> Hi guys. Do you think Pentium n4200 can candle 1Gb link?
[11:06] <sdeziel> mnms_: I would think so
[11:18] <tomreyn> https://pcengines.ch/apu2.htm comes with https://www.amd.com/en/product/7426 and they can do gigabit fine. your https://ark.intel.com/content/www/us/en/ark/products/95592/intel-pentium-processor-n4200-2m-cache-up-to-2-5-ghz.html looks more powerful in all aspects which would affect network data transfer.
[11:19] <tomreyn> (not counting performance degradation due to microcode updates / CPU bug counter measures)
[11:32] <mnms_> tomreyn: Im also worried little about nic chipsets Realtek 8111G
[11:57] <tomreyn> that's a better reason to be worried
[12:25] <mnms_> tomreyn: I see I can buy apu2c2, what workloads do you have?
[12:26] <mnms_> cpu is heavily loaded? Do you use it as a router :)?
[12:35] <tomreyn> mnms_: i don't have such hardware now, just used to play with it a little.
[12:36] <tomreyn> but they can be used as routers, yes.
[12:36] <patdk-lap> if it won't be doing tcp offload (routing) you need 1ghz per 1gbit
[12:36] <patdk-lap> if it's bidirection, that is 2gbit traffic per a 1gbit port
[12:37] <patdk-lap> that is only a 1.1ghz cpu
[12:37] <mnms_> yee its not much
[12:37] <patdk-lap> I would go with something with less cores and more ghz
[12:37] <mnms_> hard to find this kind of sbc
[12:37] <patdk-lap> cause drivers don't always irq balance between cores good
[12:38] <mnms_> understand
[12:39] <mnms_> up squared has realtek chipsets but Pentium n4200
[13:28] <friendlyguy> hi there! i am wondering if somebody has an idea: how could i "temporarily" extend the space of my /boot partition? i managed to maneuver myself in some unfortunate situation where i believe can get only out if i manage to increase the size of /boot
[13:30] <rbasak> friendlyguy: you could copy everything to somewhere bigger and bind mount that bigger place back to /boot
[13:30] <rbasak> friendlyguy: but perhaps easier to just move one probably-won't-be-touched thing out temporarily?
[13:31] <friendlyguy> nah, i think apt wants to install dozens of old kernels, that wont fit in the 250mb partition
[13:31] <rbasak> Why would apt want to do that?
[13:32] <friendlyguy> good question :) i managed to screw it up badly i guess
[13:33] <friendlyguy> i manually had to remove old kernels a bunch of times. i guess i just made an error
[13:53] <friendlyguy> okay, lets c if that works :) i attached another vhdx, created a partition and mounted that. ran rsync, unmounted /boot, mounted the temporary /boot and now running apt-get install -f
[13:54] <friendlyguy> might have been a good idea to create a snapshot first... but... already past that point#
[14:05] <friendlyguy> okay, i think that worked. now i am wondering why apt-get autoremove didnt remove the old kernels from there?
[14:28] <friendlyguy> okay... somehow things are screwed up even more: cant boot any more
[14:28] <friendlyguy> grub is entering rescue mode
[14:29] <friendlyguy> i think it "might" have used the uuid from the temporary disk or something
[14:31] <rbasak> Yes you'll need to run update-initramfs manually etc.
[14:31] <friendlyguy> ls in grub rescue only gives hd0, but no partitions?
[14:31] <rbasak> You seem to have inferred far more than just my suggestion.
[14:32] <friendlyguy> i moved the content of boot to another disk and mounted that as boot, isnt that what you suggested?
[14:34] <friendlyguy> cant i just tell grub to use /dev/sda1?
[14:34] <friendlyguy> because the content is there
[14:45] <muhaha> Is there a kickstart file for cloud-init ubuntu image?
[14:45] <friendlyguy> what a pain
[14:48] <friendlyguy> okay, ls in rescue mode gives me only hd0. if i try to ls hd0 i get unknown filesystem
[14:48] <friendlyguy> whats going wrong here?
[14:48] <friendlyguy> sda1 only has two partitions: boot and root
[14:48] <friendlyguy> so shouldnt grub display it as hd0,[1,2]?
[14:55] <friendlyguy> hello?
[14:59] <tomreyn> friendlyguy: hello.
[15:01] <tomreyn> did you mean to say "sda only has two partitions: boot and root" (not sda1)?
[15:01] <friendlyguy> :) thanks tomreyn, at least now i know my messages still go through.
[15:02] <friendlyguy> sda has two partitions, yes. sda1 and sda2. sda1 is /boot
[15:02] <friendlyguy> thats why i was trying to tell grub to use sda1
[15:03] <tomreyn> can you sum up what you're trying to do overall, and what has already been done?
[15:04] <friendlyguy> right now i try to unfuck it
[15:04] <friendlyguy> i had space issues with /boot (seperate partition, 250mb total). so i asked if somebody knows a good way to "temporarly" increase the size of /boot
[15:04] <tomreyn> so you have a system which does not boot; grub loads but cannot find its configuration file and thus does not show the menu
[15:05] <tomreyn> ok, go on
[15:05] <friendlyguy> its trying to boot of a disk with a uuid that is wrong... i guess
[15:05] <RoyK> friendlyguy: generally, you can't do that, since the boot partition is generally sandwiched between the start of the disk or EFI partition and the rest
[15:05] <friendlyguy> okay, going on...
[15:06] <friendlyguy> its legacy boto
[15:06] <friendlyguy> boot
[15:06] <friendlyguy> no efi partition
[15:06] <RoyK> friendlyguy: next time, don't use a dedicated boot partition ;)
[15:06] <friendlyguy> nevertheless its sandwitched
[15:06] <RoyK> ot was needed earlier, but that's quite some time ago
[15:06] <friendlyguy> so rbasak came up with the idea to copy the content somewhere else and mount it as /boot
[15:07] <friendlyguy> thats what i did: attached a second vhdx file to the vm, created partition and created fs on it, rsynced the content of boot to the temporary disk, mounted that disk
[15:07] <friendlyguy> than ran a apt-get install -f to fix the "initial" problem
[15:07] <RoyK> friendlyguy: just copy it to the rootfs and remove the boot partition - should work - some grub meddling may be needed, though
[15:08] <RoyK> modern versions of grub can boot from large partitions - earlier it couldn't
[15:08] <friendlyguy> i didnt want to move /boot permanently only temporary
[15:08] <RoyK> you don't need it
[15:08] <RoyK> really
[15:09] <friendlyguy> what do i dont need?
[15:09] <rbasak> friendlyguy: I did assume that you would put /boot back and weren't going to immediately reboot.
[15:09] <rbasak> Then it would fix itself on the next update.
[15:09] <RoyK> friendlyguy: a separate boot partition. I never use it anymore. it really isn't needed
[15:09] <rbasak> You can run (IIRC, check the manpage) "update-initramfs -u" to fix up the initramfs images in /boot when you have restored /boot to the real one that matches everything
[15:10] <friendlyguy> ah, yeah. but thats an very old system. so its in there, and it was done with setup defaults back then
[15:10] <nacc> -u -k all, iirc
[15:10] <friendlyguy> so i guess there was a time it was a good idea
[15:11] <tomreyn> i think /boot still goes to a separate partition with default paritioning on every current ubuntu installer
[15:11] <friendlyguy> okay, i now booted into the rescue system of some 16.04 iso
[15:12] <friendlyguy> mounted the root, mounted the boot partition
[15:13] <friendlyguy> so, only run "update-initramfs -u" now?
[15:13] <tomreyn> which ubuntu version do you have installed there?
[15:13] <friendlyguy> 16.04.5
[15:13] <tomreyn> you also need to mount virtual file systems
[15:14] <tomreyn> proc sys dev ...
[15:14] <friendlyguy> isnt that being taken from root?
[15:15] <tomreyn> hmm, i don't understand what you mean
[15:16] <friendlyguy> forget it. how do i mount the virtual file systems?
[15:16] <tomreyn> i'm saying that if you're going to run "update-initramfs" to update the initrd on your existing on-disk installation, you'll need to chroot into this installation and make sure the environment is similar enough to that of the booted system.
[15:17] <friendlyguy> i thought thats what the rescue-system did
[15:17] <friendlyguy> i took an 16.04.3 ios, booted it and selected repair a broken system (or something like that)
[15:17] <friendlyguy> i then told it which is my root partition and mounted /boot
[15:18] <friendlyguy> so i "guess" the rescue system chrooted me in there?
[15:18] <tomreyn> oh i see. i'm not sure how to work with this, always did it manually.
[15:18] <friendlyguy> jup, same here
[15:18] <friendlyguy> first try with the rescue system
[15:18] <tomreyn> https://help.ubuntu.com/community/LiveCdRecovery#Update_Failure is roughly the manal approach
[15:23] <tomreyn> so you'd mount / and any required fie systems of the standard system somewhere, say /target , then bind mount /proc /sys /dev /dev/pts onto the respective directories there and then chroot /target /bin/bash
[15:35] <friendlyguy> i think i found the issue: during the replacement of /boot with the temporary location my grub.cfg was modified
[15:35] <friendlyguy> the new grub config is pointing to the temporary disks uuid
[15:36] <friendlyguy> so i need to fix the grub config to point to the old disk again
[15:39] <friendlyguy> jup, that did the trick: the system is booting again
[15:40] <friendlyguy> it would be awesome if somebody could help me to figure out why there are still so many old kernels in boot
[15:42] <friendlyguy> kernel 4.4.0-154 is currently used. but there are still kernels in /boot ... 4.4.0-93, or an initrd.img... 3.13.0-70
[15:42] <friendlyguy> would be nice to remove those
[15:42] <friendlyguy> i *could* remove it manually, but i`d prefer that apt cleans it
[15:44] <rbasak> friendlyguy: try "apt --purge autoremove" - but check carefully when it prompts you
[15:45] <friendlyguy> didnt do anything
[15:45] <rbasak> I would remove them manually then.
[15:45] <rbasak> Be careful to avoid your currently booted kernel and also the latest kernel of course
[15:46] <friendlyguy> what i dont get: i have different number of files for abi, config, initrd and vmlinuz
[15:46] <friendlyguy> like there are two files starting with abi, 8 or nine files starting with initrd, 3 vmlinuz,3 system.map
[15:47] <rbasak> use "dpkg -S file" to see what package file comes from
[15:52] <friendlyguy> that doesnt work for those files
[15:52] <rbasak> Some may be generated
[15:53] <tomreyn> then they're not part of a package (or were generated during installation of a package and are not tracked)
[15:53] <rbasak> Yes one of those two
[15:53] <rbasak> Usually I "dpkg -l|grep linux" and manually return the ones I don't need.
[15:53] <rbasak> Anything that's obviously a kernel version that I don't need.
[15:54] <friendlyguy> wow
[15:54] <friendlyguy> i think thats the main problem
[15:55] <tomreyn> to make auto-removal of kernel images (all but the latest two and the currently active one) work, you'll need to ensure that linux-generic and linux-image-generic are installed and that all the packages which contain a kernel version number as returned by    dpkg -l linux-\* | awk '/^i/ {print $2}'    are automatically, not manually installed.
[15:55] <friendlyguy> let me show you something :)
[15:57] <friendlyguy> https://pastebin.com/LJ4vicss
[15:57] <friendlyguy> rbasak: i assume that command normally doesnt give you 240 lines back
[15:58] <tomreyn> the /etc/kernel/postinst.d/apt-auto-removal  hook script runs whenever you install a kernel image and tracks (in /etc/apt/apt.conf.d/01autoremove-kernels) which kernel images (and initrds, headers) should be kept / removed
[15:58] <tomreyn> those 3.13 packages must be remainders from before your release upgrade to 16.04
[15:59] <friendlyguy> entirely possible
[15:59] <friendlyguy> shall i just purge linux-image-extra-3*?
[15:59] <rbasak> Yeah that's rather large
[16:00] <friendlyguy> as well as linux-image-3*
[16:00] <tomreyn> i guess you can     sudo apt purge '^linux.*-3\.13\.0-.*'    but make sure you check the output before you confirm
[16:03] <friendlyguy> uuh:) down to 127
[16:03] <tomreyn> is this system booted from disk now, or still chrooted in recovery?
[16:03] <friendlyguy> booted from disk
[16:04] <tomreyn> which kernel is now running?
[16:04] <tomreyn> cat /proc/version or uname -r
[16:04] <friendlyguy> 4.4.0-154
[16:05] <tomreyn> good, that's not too far behind
[16:06] <tomreyn> so you can then purge all linux-* 4.4.0 packages which have a 2 digit patch level
[16:06] <friendlyguy> i`m horrible with regex
[16:06] <friendlyguy> :)
[16:06] <tomreyn> sudo apt purge '^linux.*-4\.4\.0-[0-9][0-9]-.*'
[16:06] <tomreyn> again, make sure you check the output before you confirm
[16:07] <friendlyguy> sure
[16:07] <nacc> bryce: how's it going?
[16:07] <friendlyguy> looking good to me, lets remove them
[16:08] <rbasak> I usually process the dpkg -l output by hand in an editor and then feed that to dpkg -P
[16:08] <rbasak> Saves doing regexes for a one off task and I get to confirm it's right
[16:08] <friendlyguy> interesting: errors occured with linux-image-extra-4.4.0-93-generic
[16:10] <tomreyn> probably some leftover files?
[16:10] <tomreyn> ah no that'd been a warning
[16:11] <friendlyguy> depmod: ERROR: could not open directory /lib/modules/4.4.0-93-generic: No such file or directory
[16:11] <friendlyguy> so i guess i can ignore that
[16:11] <tomreyn> if it prevents purging the package then you probably can't ignore it
[16:13] <friendlyguy> did it a second time: worked now
[16:16] <friendlyguy> thats how it looks now: https://pastebin.com/1Atr59u3
[16:16] <tomreyn> so you may want to get a fresh list of reamining installed (or leftover configuration files) linux-* packages and sort out which ones you want to keep / remove, or just mark all of them as automatically installed.
[16:16] <tomreyn> all of the versioned ones, that is.
[16:17] <friendlyguy> can you take a look at the link i posted, thats what is currently installed
[16:18] <tomreyn> i did :)
[16:19] <friendlyguy> looking much better to me :)
[16:19] <friendlyguy> thanks for your help so far!
[16:20] <friendlyguy> do you have an idea why it kept linux-headers-4.4.0-89 and 93?
[16:22] <friendlyguy> manually removing them worked
[16:23] <bryce> nacc, heya, was away on vacation friday; will pick back up on php this afternoon or tomorrow I think
[16:23] <friendlyguy> anyhow. need to get home. ill try to join back later
[16:23] <friendlyguy> thanks for the help of all of you!
[16:23] <friendlyguy> very kind
[16:23] <tomreyn> friendlyguy: i don't know why it kept these packages, no
[16:24] <friendlyguy> i was just wondering why they were not catched by your regex
[16:24] <tomreyn> friendlyguy: you haven't prevented this issue from occurring again, yet
[16:24] <friendlyguy> thought that they should have been catched
[16:24] <friendlyguy> tomreyn: exactly!!! i would love to though
[16:24] <friendlyguy> but i have to go home now
[16:24] <nacc> bryce: sounds good, thanks!
[16:24] <tomreyn> oh my regex had a dash behind those numbers
[16:25] <tomreyn> friendlyguy: see you
[16:25] <friendlyguy> aaah, i c
[16:25] <friendlyguy> :)
[17:51] <smoser> ahasenack: what is the process or is there one..
[17:51] <smoser> for me to request a push of a tag for merge of https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/cloud-utils/+git/cloud-utils/+merge/370194
[17:51] <smoser> i just uploaded rafael's b26a5aa7736d4e64c19f66fa563a12808b1c4ebd
[17:51] <smoser> as upload/0.31-0ubuntu1.1
[17:52] <smoser> but i can't push there.
[17:52] <smoser> (pinging you because you're the only member of usd-import-team that is in current timezone normal working hours)
[17:57] <Odd_Bloke> smoser: Andreas is at Debconf this week, so he may not be around.
[18:01] <smoser> fair enough
[18:03] <rafaeldtinoco> smoser: hey
[18:03]  * rafaeldtinoco reading
[18:04] <rafaeldtinoco> ahh its for andreas, ok, ill warn him (in front of me)
[18:04] <smoser> rafaeldtinoco: well, i think the ansewr is "there is no answer"
[18:05] <rafaeldtinoco> he is coming
[18:05] <rafaeldtinoco> =)
[18:06] <ahasenack> smoser: hi
[18:06] <ahasenack> smoser: there is none, let me look at that and push it for you, if there is still time to win the race
[18:08] <smoser> yeah, i'd guess you can win the race
[18:08] <smoser> as it is stuck waiting for approval
[18:08] <smoser> so i think you're racing a human
[18:08] <smoser> and they're slow
[18:09] <ahasenack> sru
[18:09] <ahasenack> ok
[18:13] <ahasenack> smoser: done
[18:13] <ahasenack> added info to the mp as well
[19:36] <catbadger> hi. i have a 55GB database dump i need to move. I'm aware that compressing it might not be an option. should I just rsync it to the other server?
[19:37] <lotuspsychje> !crosspost | catbadger