[02:17] <ruben23> hi guys i have two user on my ubuntu server nick and vincent, nick has a default ssh keys setup already and i wanted to add for new user vincent also, how do i do that two user with there respective ssh keys.? any idea guys
[02:18] <ruben23> coz im confused either i put the public key on authorized_key or i will create a separate file for vincent also.? any idea.?
[02:19] <ruben23> anyone can help please
[04:41] <cpaelzer> coreycb: that is a change to python libvirt
[04:41] <cpaelzer> I added to my todo that I need to re-sync the new version after the new libvirt is in
[07:38] <olivier[m]7> Good morning
[09:14] <tobasco> coreycb: was something just changed in bionic-rocky packages
[09:14] <tobasco> Failed to start sahara-api.service: Unit sahara-api.service not found.
[09:14] <tobasco> was eventlet sahara-api removed?
[09:15] <tobasco> if so, would be good with a heads up if something like this changes since all deployment tools usually break
[09:35] <yossarianuk> hi - just trying out ubuntu server 18.04.1 - I was unable to use a KVM bridge with netplan - so I installed ifupdown and configured /etc/network/interfaces - config is here : https://pastebin.com/smQYsvgu
[09:35] <yossarianuk> However on boot I have no networking
[09:35] <yossarianuk> unless I use the command
[09:35] <yossarianuk> ifup br0
[09:36] <yossarianuk> Can anyone suggest how to get br0 to start on boot ?
[09:36] <yossarianuk> also
[09:36] <yossarianuk> if I use
[09:36] <yossarianuk> # systemctl restart networking
[09:36] <yossarianuk> That also removes br0
[09:37] <yossarianuk> 18.04 + KVM don't seem to mix very well...
[09:37] <yossarianuk> It works 100% fine if I just use # ifup br0 thouh - thinking about removing 18.04 and using debain/centos...
[09:42] <tobasco> coreycb: assume this caused it https://launchpad.net/ubuntu/+source/sahara/1:9.0.0~b2-0ubuntu1
[09:43] <tobasco> is sahara-api systemd unit file not supplied anymore? is wsgi in for example apache forced?
[09:44] <tobasco> oh and there is a 9.0.0~b3 available btw
[09:44] <tobasco> saw it now on releases.openstack.org
[09:49] <yossarianuk> is anyone able to make ubuntu 18.04 work with a kvm bridge (and the bridge starts on boot)
[09:53] <rbasak> yossarianuk: you've not said "auto br0".
[09:58] <yossarianuk> basak: i.e I should add the line before the iface line ?
[10:00] <tobasco> coreycb: https://bugs.launchpad.net/ubuntu/+source/sahara/+bug/1786214
[11:51] <coreycb> tobasco: yes it's switched to run under apache as of b2
[11:51] <coreycb> tobasco: sorry will include that in the release notes
[11:51] <coreycb> tobasco: i'm working through b3/rc1 this week
[11:53] <tobasco> coreycb: aight, pretty close to rocky release, it's impossible to add it back in?
[11:53] <tobasco> we need to build in wsgi support asap otherwise for puppet stuff
[11:56] <coreycb> tobasco: i believe it had something to do with eventlet and py3. we've been adding py3 support this cycle.
[11:59] <tobasco> so we cant? :(
[12:00] <coreycb> tobasco: i think it would be a move backwards to switch it back anyway
[12:00] <cpaelzer> hi coreycb, did you catch the bug I opened and subscribed you to?
[12:01] <cpaelzer> TL;DR - hit rebuild after my libvirt merge is complete
[12:01] <cpaelzer> I'll do that then
[12:02] <coreycb> cpaelzer: i did not but i'll look
[12:03] <coreycb> cpaelzer: ok so it'll be fixed soon is what it sounds like :)
[12:04] <cpaelzer> yeah, libvirt keeps on giving issues on testing as usual on a merge
[12:04] <cpaelzer> but once that is resolved it will start to move
[12:04] <coreycb> cpaelzer: great, thanks
[12:04] <cpaelzer> also there is no other fix than getting a new libvirt in, so the build dependency is fulfilled
[12:05] <cpaelzer> so there would be no alternative fast-path to this
[12:05] <coreycb> ok
[12:05] <cpaelzer> other than pushing a broken libvirt faster - no that won't make it better :-)
[12:06] <coreycb> cpaelzer: fyi we have 3 weeks until rocky releases
[13:31] <ahasenack> I connceted to an autopkgtest vm with "socat - UNIX-CONNECT:/tmp/autopkgtest-qemu.fmuv1ubd/ttyS0",
[13:31] <ahasenack> and inside that I did a tail -f on a log file
[13:31] <ahasenack> problem is that I can't ctrl-c that, because that will kill the socat, not the tail
[13:31] <ahasenack> so I'm stuck
[13:31] <ahasenack> any ideas?
[13:32] <cpaelzer> ahasenack: it has also ssh up
[13:32] <ahasenack> cpaelzer: any ideas? ^
[13:32] <ahasenack> well, that's the reason I used socat
[13:32] <cpaelzer> connect via that and kill the cat process
[13:32] <ahasenack> ssh wasn't letting me in
[13:32] <cpaelzer> arr
[13:32] <ahasenack> Aug  9 10:32:14 autopkgtest sshd[3315]: error: maximum authentication attempts exceeded for ubuntu from 10.0.2.2 port 53548 ssh2 [preauth]
[13:32] <ahasenack> I don't know what failed in the ssh setup
[13:33] <ahasenack> with socat I was able to login with ubuntu/ubuntu
[13:33] <cpaelzer> does it has a ttyS1 as well
[13:33] <cpaelzer> ?
[13:33] <ahasenack> oh, it does, and immediate root
[13:33] <cpaelzer> I think on autpkgtest S0 is supposed be normal and S1 is auto-root
[13:33] <ahasenack> thanks :)
[13:44] <ahasenack> interesting, this doesn't fail:
[13:45] <ahasenack> $ sudo aa-enforce /etc/apparmor.d/usr.sbin.squid3
[13:45] <ahasenack> when the file doesn't exist, I mean
[13:45] <ahasenack> Profile for /etc/apparmor.d/usr.sbin.squid3 not found, skipping
[13:45] <ahasenack> $ echo $?
[13:45] <ahasenack> 0
[13:45] <ahasenack>         # Verify it loads ok
[13:45] <ahasenack>         ret, report = cmd(['aa-enforce', self.aa_abs_profile])
[13:45] <ahasenack>         expected = 0
[13:45] <ahasenack> heh
[13:45] <ahasenack> "you were fooled!"
[14:04] <ahasenack> Ran 7 tests in 267.713s
[14:04] <ahasenack> allright, progress
[18:38] <wendico> hello there. Im trying to install my first ubuntu server. i donwloaded and want to install on a motherboard with an array of disk in raid1.  i downloaded the last ubuntu server, burnt to my pendrive, i boot i go install i walla, my ubuntu server detects my drives alone an not my raid groups, why? what i must do so i can install on my array and not on just an alone disk
[18:43] <teward> wendico: how did you create the RAID groups to begin with?  does your system have a standalone RAID card for the array, or does the BIOS see individual drives rather than a disk array?
[18:45] <wendico> i set up my arrays on my BIOS, i have an integrated Intel Matrix Storage Manager (rom v5.6.2.1002 ich7r) wich i access with a set of commands on boot. There i set up 2 arrays
[18:46] <wendico> I have 2 disk in raid1 where i want to install my server and 2 disk in raid0 for nas storage
[18:47] <wendico> i dont know how to boot my ubuntu server to see those arrays and then install on the first one
[18:47] <ChmEarl> wendico, append `dmraid` to the cmdline
[18:47] <wendico> just for example "live dmraid" ?
[18:48] <ChmEarl> https://help.ubuntu.com/community/FakeRaidHowto
[18:48] <ChmEarl> dmraid=fakeraid
[18:51] <ChmEarl> wendico, that howto above will give you an idea of how the Intel raid devices might be named... its not obvious
[18:52] <wendico> i am reading and so far assuming i dont even need to use that since anyways is a "fakeraid"
[18:52] <wendico> they faked me
[18:52] <wendico> if is not real hardware raid, should not just disable it and use ubuntu software raid?
[18:55] <ChmEarl> wendico, it might be fun to launch the installer, drop to the shell, run `dmraid -ay`, then look for the devices
[18:55] <ChmEarl> isw_aabbcc
[18:56] <wendico> im on it
[19:01] <wendico> ChmEarl: ty, getting closer, dmraid was not in live, i sudo installed, then sudo dmraid -ay shows my 2 arrays not activated
[19:01] <wendico> how can activate them to proceed installation on my array?
[19:05] <ChmEarl> wendico, not sure what to tell you, but from shell: `ls /dev/mapper/isw_*` might be of interest
[19:06] <ChmEarl> whatever the prefix is nv_ or pdc_
[19:08] <ChmEarl> looks like Intel isw* raid uses this driver: dm_raid45
[19:15] <wendico> puf, this ubuntu thing is frustrating
[19:16] <wendico> im about to give up
[19:46] <tomreyn> wendico: yes you should dsable the fakeraid and install with software raid
[19:46] <wendico> tomreyn: thank you, going on
[19:51] <wendico> one last question, since im so tired of probing today, may i install server in one disk disabling all others and enable the raid functions later so i can have my server running soon, all day and still not have a server running
[19:52] <wendico> i pretend to disconnect all drives, disable sata fake raid, and install ubuntu server on my only drive, afterwards and after playing with the sever, may i add the second disk to mirror my server for tolerance?
[19:52] <sarnold> I've never tried converting but I have to imagine that's a lot more work than doing the install with raid from the start
[19:53] <sarnold> just skip the "I want to boot to either drive when the array is degraded" work until later
[19:53] <wendico> ok, so is better to use both disk and define the software raid group on the instalation menus
[19:54] <wendico> ok i go ahead, see if i finally got my server running in some minutes
[20:07] <wendico> stuck again with the mesage if i use all my disk in arrays there is no place to put the boot partition
[20:07] <wendico> lol
[20:07] <wendico> i really dont understand, the boot partition cannot be mirrored?
[20:08] <wendico> this raid thing is getting on my nerves
[20:11] <wendico> Ok, i have 2 identical disk 128gb and another 2 identical 250. i Want raid mirrored on my  128 disk to install server and raid stripped on the other two disk, how the heck do i do this on ubuntu. My set up is ready, my machine boots server live, im on the define software raid but i cant define those 2 arrays because says then i dont have a partition to install my boot. but if i dont even defined partitions im only setting arra
[20:15] <tomreyn> wendico: your message was cut off after "but if i dont even defined partitions im only setting arra" due to the maximum line length on this IRC network.
[20:16] <tomreyn> wendico: what you need to know about setting up software raid is that depending on how you'll boot (uefi vs csm / legacy bios) you may need a separate ESP partition (you need this with any OS if you use uefi)
[20:17] <tomreyn> ESP can't be on a software raid, OS independant.
[20:18] <wendico> tomrey, i understand, so in what boot mode do i not need a separate partition?
[20:18] <tomreyn> wendico: also, it is recommended to have /boot on nothing but software raid (no further intermediate block device layers, such as LVM or full disk encryption), since it complicates the setup + booting.
[20:20] <tomreyn> for 128 GB disks you, can boot in legacy mode without ESP partitions, and with everything on msdos / MBR partitoned disks (instead of GPT, so you don't require a biosgrub partition)
[20:20] <tomreyn> is this what you want to do? probably not
[20:21] <wendico> yes i think i want that to start,
[20:21] <wendico> if not is to complex to learn
[20:21] <tomreyn> there should be an option for automatic partitioning with RAID and LVM. that's the easiest option really.
[20:22] <wendico> so im gonna set my sata on "ide" mode, set all to legacy, disable anything about uefi
[20:23] <wendico> and see if ubuntu dont complaint for not having a partition outside a raid group
[20:24] <tomreyn> you most likely want ahci, not ide
[20:24] <tomreyn> that's if you're refrring to the bios setting
[20:25] <tomreyn> note that ths is hardware specific configuration, it has nothing to do with ubuntu
[20:26] <wendico> ok, so im there, no uefi and set to ahci
[20:26] <wendico> booted ubuntu server live install
[20:26] <wendico> im on the disk setup
[20:28] <wendico> so now you sugest to use auto LVM and install on my first 128 disk?
[20:31] <tomreyn> wendico: what does the option say exactly?
[20:32] <wendico> tomreyn, give me a min since i clicked install anyways, but it only ommited the word RAID. i had 4 options: use entire disk, use auto lvm, manual and someting else
[20:33] <wendico> clicked auto lvm on my first 128 disk and parted for /boot and / (leaving bunch of free space)
[20:34] <tomreyn> wendico: this installer is pretty new and i'm not so much into it, yet, so i'm not certain what the LVM option actually does. if it doesn't say "RAID" my guess is it doesn't do RAID.
[20:35] <tomreyn> wendico: but i'm doing it in a VM now, so i see the options you discussed
[20:35] <tomreyn> no mention of RAID there, so i dont think you're getting any
[20:36] <tomreyn> so with the server-live-installer i think you need to use manual partitioning indeed
[20:36] <tomreyn> if you want to go back to this point, i can guide you
[20:37] <tomreyn> this is shown as installation step 7 of 11 here
[20:37] <wendico> yes please
[20:37] <wendico> let me start over so u can guide me
[20:37] <tomreyn> ok
[20:37] <tomreyn> keep hilighting me since i keep switching channels
[20:37] <wendico> my server is booting on hd, need few seconds to reboot live
[20:37] <wendico> tomreyn:ok
[20:38] <tomreyn> sure, np
[20:41] <wendico> tomreyn: ok, im there on step 7
[20:42] <tomreyn> wendico: okay, do manual, then take a screen shot
[20:42] <wendico> tomreyn: wherever u are ready to guide me i wait with patience
[20:42] <wendico> !pastebin
[20:42] <tomreyn> here's mine http://i.imgur.com/QRr24LF.png
[20:43] <tomreyn> !screenshots | wendico
[20:44] <tomreyn> i guess prtscr does not apply during the server installer
[20:44] <tomreyn> so use some smartphone if you have one
[20:44] <wendico> https://imgur.com/a/TFOis66
[20:45] <tomreyn> alternatively some form of out of band management from another computer can help, too
[20:45] <wendico> mobile and webwthatsapp is my faster trick hehe
[20:45] <tomreyn> okay, we only care bout your first two disks for now, right?
[20:45] <wendico> yes the others is for a stripped nas
[20:45] <wendico> the first two for raid ubuntu server
[20:46] <tomreyn> i think you mean 'striped', so RAID0
[20:46] <wendico> no, for first two i mean tolerance, mirrored
[20:46] <wendico> i want my server failsave
[20:46] <wendico> for the second 2 disk i want my data stripped
[20:47] <tomreyn> okay, i understood so much. just saying that it's correctly spelled (and spoken) striPed. but this doesn't matter now.
[20:47] <wendico> ah ok sorry, english bad for me hehe
[20:48] <wendico> the problem i encounter if use create software raid, i define raid1 on my first 2 disk but cannot define raid0 on the other 2 disk coz i get the error nowhere to install boot loader
[20:49] <tomreyn> we need to partition before we create the md raid
[20:49] <tomreyn> let me try this here quickly to make sure this can work
[20:50] <wendico> can be, even i probably have partitions and grubs and windows, and ubuntus on all those disks
[20:50] <wendico> they were used on machines that now is garbage
[20:50] <wendico> havent format or parted yet, i though it would do installing
[20:51] <tomreyn> hmm okay this installer insists on creating a bios_brub parttion, so i guess we can't get around this
[20:51] <tomreyn> it's only 1 MB, though, so you're not loosing too much.
[20:52] <tomreyn> so move the cursor to the upportmost disk
[20:52] <tomreyn> press enter, then add partition
[20:52] <wendico> done
[20:52] <wendico> size, file format?
[20:53] <tomreyn> full size, leave unformatted
[20:53] <tomreyn> this new partiton is now listed on top, and on the bottom you have a partiton 1: bios_grub
[20:54] <tomreyn> correct?
[20:54] <wendico> correct
[20:54] <tomreyn> now move to the second disk, make a parittion, 1 MB, leave unformatted
[20:55] <wendico> going
[20:55] <tomreyn> "1M"
[20:56] <wendico> tomreyn: done
[20:56] <tomreyn> then another partition on the second drive, ignore 'size', set formatting to leave unformatted
[20:57] <tomreyn> then take another screenie please
[20:58] <tomreyn> i forgot to ask: you don't want LVM there, or do you?
[20:59] <tomreyn> here's what it looks like for me now: http://i.imgur.com/NNyWo5s.png
[20:59] <wendico> https://imgur.com/a/YISDm8r
[20:59] <wendico> perfect, same for me
[21:00] <tomreyn> looks good, unless you want LVM
[21:00] <wendico> no i dont
[21:00] <wendico> i will plug a usb3 nas to my server
[21:00] <wendico> i dont care lvm
[21:00] <tomreyn> now select 'create software raid"
[21:01] <tomreyn> tick 'partition 2' on top and on bottom. to tick press space bar
[21:02] <tomreyn> on top is should say md0 for name and raid elevel 1
[21:02] <tomreyn> then go on and 'create'
[21:03] <tomreyn> http://i.imgur.com/HUGuNrn.png
[21:03] <tomreyn> http://i.imgur.com/bDjVRgu.png
[21:04] <tomreyn> wendico: still with me?
[21:04] <wendico> tomreyn: yes
[21:04] <tomreyn> wendico: okay, where are you now?
[21:04] <wendico> i did something wrong, repeating steps, give me a second
[21:05] <tomreyn> wendico: we didnt write any changes to disk, yet, so you can just "reset" on the bottom
[21:07] <wendico> that i did, i went over, i did all correcttly but
[21:08] <wendico> Done at the botton is grey out, let me screen shot where am i
[21:08] <tomreyn> it should be greyed out.
[21:08] <tomreyn> but a screen shot would be good, yes
[21:10] <wendico> https://imgur.com/a/0aVSUsa
[21:10] <wendico> here i am tomreyn: ^
[21:10] <tomreyn> lets see
[21:11] <tomreyn> looks good
[21:11] <wendico> seems correct, and seems i could follow ahead and set my second array
[21:11] <wendico> but why cant i continue?
[21:12] <wendico> guess should i define mount points
[21:12] <tomreyn> for some reason it says "md/server" for you when it says "md0" for me. but i dont care too much
[21:12] <tomreyn> oh did you name this md?
[21:12] <tomreyn> wendico: it seems like you set "md/server" as a name
[21:12] <wendico> ses
[21:13] <wendico> yes tomreyn, i used "server" as a name
[21:13] <wendico> is it wrong?
[21:13] <tomreyn> wendico: this may work, but i'm not sure it will. we can try
[21:13] <tomreyn> okay, that's probably fine
[21:13] <tomreyn> it will be /dev/md/server in the final system
[21:13] <tomreyn> let me change this here quickly
[21:13] <wendico> okey, np
[21:15] <tomreyn> now , under AVAILABLE DEVICES, select md/server, then Format, then ext4
[21:15] <tomreyn> mount should remain /
[21:15] <tomreyn> okay, i failed
[21:15] <tomreyn> lets reset, we must have a separate /boot
[21:16] <tomreyn> wendico: ^ sorry about that
[21:16] <wendico> perfect no problem
[21:16] <wendico> reset
[21:17] <tomreyn> okay, on the first disk, create partition, 2G, leave unformatted
[21:18] <tomreyn> on the first disk, create partition, do not set size, leave unformatted
[21:18] <tomreyn> on the second disk, create partition, 2G, leave unformatted
[21:18] <tomreyn> on the second disk, create partition, so not set size, leave unformatted
[21:19] <tomreyn> and wrong again
[21:19] <tomreyn> wendico: did you create partitons on the 2nd disk, yet?
[21:19] <wendico> nope
[21:19] <wendico> just first finished
[21:19] <wendico> need 2g+1m partition?
[21:20] <tomreyn> yes 1M, 2G, (blank) for sizes, all unformatted
[21:20] <tomreyn> in this order ^
[21:20] <wendico> okeys going
[21:22] <tomreyn> http://i.imgur.com/UDHsez7.png
[21:23] <wendico> perfect done
[21:23] <wendico> went ahead also and created my raid0
[21:23] <wendico> now im ready to set mount points
[21:23] <wendico> i think
[21:23] <wendico> let me screenshot in case
[21:24] <tomreyn> san i see it?
[21:24] <tomreyn> *can
[21:24] <tomreyn> thanks
[21:25] <wendico> https://imgur.com/a/rB5N5CN
[21:25] <wendico> note that my md0 is called server
[21:26] <wendico> and md0 is actually my data stripped array
[21:26] <wendico> i forgot to change name to my second array
[21:26] <wendico> im goona create again to name DataNAS
[21:26] <wendico> more clear for me
[21:26] <tomreyn> you can edit
[21:27] <tomreyn> you can select the 'md' device on top and select 'edit' to change the name
[21:27] <wendico> done
[21:27] <tomreyn> but you need to also create a raid-1 across theose partition 2
[21:27] <wendico> so now i format ext4 my first array
[21:28] <wendico> ok
[21:28] <wendico> for the /boot?
[21:28] <tomreyn> correct
[21:28] <wendico> ok going on
[21:29] <tomreyn> what you call md/Server is md/os_slash here and will be mounted at /. what you are just creating now is called os_boot here and will be mounted at /boot
[21:29] <tomreyn> but let me know what you named it so i can use the same names
[21:31] <wendico> ok all done, here is the final screen shot:
[21:31] <tomreyn> ah great, i didnt want to ask ;)
[21:32] <wendico> https://imgur.com/a/SYcewpE
[21:33] <tomreyn> great, i now have md/Boot and md/Server, too
[21:33] <tomreyn> so lets assign mount points
[21:33] <tomreyn> select md/Boot
[21:34] <tomreyn> format ext4, mount /boot
[21:34] <tomreyn> geez it doesnt allow that
[21:34] <wendico> lol
[21:34] <wendico> yeap, same problem
[21:34] <tomreyn> this installer is unfortunatley full of bugs
[21:35] <wendico> i can see
[21:35] <wendico> i guess it doesnt like a boot on a striped raid
[21:35] <tomreyn> it's mirror raid
[21:35] <wendico> yes sorry
[21:35] <tomreyn> but it doesn't seem to like it on raid at all
[21:35] <tomreyn> software raid
[21:36] <wendico> yep, i clicked other and writed /boot and get error, bott must be on a partition
[21:36] <tomreyn> well, i'm sorry. i think with this installer we may only have a non redundant /boot partition
[21:37] <mwhudson> https://bugs.launchpad.net/subiquity/+bug/1785332
[21:37] <tomreyn> the proper installer, i mean the legacy installer, would have accepted this setup
[21:37] <mwhudson> yeah, use d-i if you need this for now
[21:37] <tomreyn> mwhudson: thanks for the link
[21:37] <tomreyn> something tells me i should use debian in the future
[21:39] <tomreyn> wendico: now, i think our options are clear? you can downlaod the other installer and we can redo it there or we can have a non raid-1 /boot
[21:39] <tomreyn> wendico: what we can do is to install with boot on just one device now and fix it after installation
[21:39] <wendico> yes that last option i prefer
[21:39] <tomreyn> s/device/storage device/
[21:40] <tomreyn> i think it's the best, too
[21:40] <wendico> so i delete boot array
[21:40] <tomreyn> correct, delete md/Boot
[21:40] <wendico> done
[21:41] <tomreyn> on disk 1, partitoon 2, format as ext4
[21:41] <tomreyn> mount at /boot
[21:42] <wendico> done
[21:43] <tomreyn> wendico: so on top we now have two file systems:
[21:43] <tomreyn>  /, a software raid 1, ext4 format
[21:43] <tomreyn>  /boot, partition of local disk, ext4 format
[21:44] <tomreyn> maybe you have a 3rd across your nas
[21:44] <tomreyn> correct?
[21:44] <tomreyn> admit it, you're doing a screenie
[21:45] <wendico> yep hehe
[21:45] <wendico> https://imgur.com/a/yTQoyrS
[21:46] <wendico> now my "Done" is not grey out
[21:46] <wendico> is it all correct?
[21:47] <tomreyn> wendico: looks good
[21:47] <wendico> i mounted /home on my data raid0, /boot on primary ext4 first disk second partition and leaved 1m free space for grub
[21:47] <tomreyn> we're DONE with this
[21:47] <wendico> THANK YOU VERY MUCH!
[21:47] <tomreyn> well we're not done installing
[21:47] <wendico> I OWE YOU A BEER
[21:48] <tomreyn> let's hope it works out ;)
[21:48] <tomreyn> we also need to fix the /boot raid, yet
[21:48] <wendico> goonna click done lets see hehe
[21:50] <wendico> should i install the sugested popular snapsin¿
[21:50] <wendico> dont bother i just install all and later remove what not need
[21:50] <tomreyn> up to you, i would not
[21:50] <wendico> oh ok, then i uncheck all lol
[21:50] <tomreyn> installing snaps is quick later on, too
[21:51] <tomreyn> and i'm not a huge fan of snaps, but that's personal preference, i guess
[21:51] <wendico> i just want a firewall, proxy and nas
[21:51] <wendico> i dont think i need all that
[21:51] <wendico> i unchecked all
[21:52] <tomreyn> right, you dont
[21:52] <wendico> installing going on
[21:52] <tomreyn> mine's done ;)
[21:52] <wendico> hehe i got old machine
[21:54] <tomreyn> sweet - "fatal, no bootable medium found! System halted."
[21:54] <wendico> lol
[21:54] <tomreyn> i dont think i made a mistake, but i'll try again quickly
[21:54] <wendico> mines still on installing kernel
[21:55] <wendico> done installing, rebooting
[21:57] <wendico> so far i only see a blinking cursor hehe, gonna check if booting from proper hd
[21:59] <wendico> ok
[21:59] <wendico> try to boot from the second drive, seems thats our mistake
[22:00] <wendico> i switched to boot from drive 2 and ubuntu runned
[22:00] <tomreyn> maybe you had grub installed there already?
[22:01] <wendico> could be
[22:01] <tomreyn> like before we did th einstallation. or did you say these are new disks
[22:01] <wendico> no all used
[22:01] <wendico> used with ubuntu desktop and windows all them
[22:03] <wendico> nevertheless is taking ages to boot, seems is encountering problems, maybe arranging software raids for first time or something
[22:03] <tomreyn> yes, it's to the initial raid sync in the background
[22:03] <tomreyn> if these are old / slow disks, this can take a while
[22:03] <wendico> oh ok, i let it time then
[22:03] <wendico> no, ssd new
[22:04] <tomreyn> once it's booted and oyu're logged in you can see the progress with cat /proc/mdstat
[22:04] <wendico> is the only uptodate thing on this machine hehe
[22:04] <tomreyn> hehe, well ssds ought to be faster
[22:05] <wendico> i cant log in yet is halted on post
[22:05] <tomreyn> "fatal, no bootable medium found! System halted."
[22:05] <wendico> but i can hear hds work crazy
[22:05] <tomreyn> on post?
[22:05] <wendico> let me take screen shot
[22:06] <tomreyn> did it say loading kernel yet
[22:06] <tomreyn> oh maybe it wont says that. yes, screenie is good
[22:07] <wendico> https://imgur.com/a/LMnbKsT     The last line character is because i tiped a key to see if it was frozen
[22:08] <wendico> ok my bad
[22:08] <wendico> im logged on
[22:08] <tomreyn> omg, yes it installs grub to the wrong disk
[22:08] <tomreyn> aaaaaaaaaaaaaaaaah
[22:09] <wendico> haha
[22:09] <wendico> that did yes
[22:09] <wendico> installed grub to my second disk
[22:09] <tomreyn> i just booted off the second disk, tooo, and it boots up fine
[22:10] <wendico> so what would u do?
[22:10] <wendico> would u leave it like that
[22:10] <tomreyn> just the first, default diosk, which was also listed first in the installer, got no grub at all, at leats not anywhere where it'S triny gto boot it.
[22:10] <tomreyn> we can fix this quickly
[22:10] <wendico> i follow you if you are in the mood
[22:10] <tomreyn> but this is a results of insufficient QA, or almost none
[22:11] <wendico> what is QA?
[22:11] <tomreyn> which is inacceptable for minor release one of an LTS relase
[22:11] <tomreyn> quality assurance
[22:11] <wendico> lol yes you are right
[22:12] <tomreyn> anyways, we got them both booted, and are loggedin, right?
[22:12] <wendico> yep
[22:12] <tomreyn> first, install pending updates: become root or use sudo: apt update && apt dist-upgrade
[22:12] <wendico> go for
[22:15] <wendico> updating,
[22:15] <tomreyn> here's my partition tables http://i.imgur.com/ojDxgOT.png
[22:15] <tomreyn> ...
[22:18] <tomreyn> at leats it did write grub to the bios_grub partition
[22:20] <tomreyn> tell me when you're done
[22:20] <wendico> done
[22:20] <wendico> looks the same
[22:20] <tomreyn> so updating worked, you have internet access, right?
[22:21] <wendico> yep
[22:21] <wendico> updated working
[22:21] <wendico> but my devices not same as yours
[22:21] <wendico> i have sda, sdb, sdc
[22:21] <tomreyn> of course, you have sda, sdb, sdc, sdd
[22:22] <tomreyn> 4 physical disks
[22:22] <tomreyn> those remain visible to linux, since we'Re doing software raid, not hardware raid
[22:22] <wendico> ahhh of course
[22:22] <tomreyn> also we do software raid on partitions, not whole disks
[22:22] <tomreyn> please : apt install pastebinit
[22:23] <tomreyn> oh thats already installed
[22:23] <wendico> yep
[22:23] <tomreyn> are you still physically working on the server?
[22:23] <wendico> yep
[22:24] <wendico> got the server online on a pc and a laptop beside with ubuntu desktop talking to u
[22:24] <tomreyn> shall we install ssh there first so you can connect form a different computer and do easier copy and paste and screenies?
[22:24] <wendico> ok
[22:24] <wendico> please show me how
[22:24] <tomreyn> oh i got ssh already installe,d ok
[22:24] <tomreyn> so you just ssh to it form the other computer
[22:25] <tomreyn> do you know its ip address?
[22:25] <tomreyn> if not, ip a
[22:25] <tomreyn> it is also listed when you log out and login again
[22:25] <wendico> got it
[22:26] <tomreyn> so you ssh to it form the other computer, where you should also chat from
[22:26] <tomreyn> i guess you're doing this already
[22:26] <tomreyn> you ssh using the user you created during installation and its password
[22:27] <wendico> i try but only ask me password, not user
[22:28] <tomreyn> you specify the username when connecting
[22:28] <wendico> lol ok
[22:28] <tomreyn> either using -l username
[22:28] <tomreyn> or user@serverip
[22:29] <wendico> conected
[22:30] <tomreyn> pastebint /proc/mdstat
[22:30] <tomreyn> pastebinit /proc/mdstat
[22:30] <tomreyn> the latter
[22:30] <tomreyn> and tell me the http address, please
[22:30] <wendico> http://paste.ubuntu.com/p/3sVm5mzn5V/
[22:32] <tomreyn> okay, thats weird. i need to see your disks
[22:32] <tomreyn> are you working as your standard user or as root?
[22:32] <wendico> i think standar coz i always have to tipe sudo
[22:33] <tomreyn> ok, i mean what you prefer foir now: working as your restricted user using sudo, or as root?
[22:33] <wendico> for now better as root
[22:33] <tomreyn> i think sudo is good, especially for beginners
[22:33] <wendico> oh then sudo
[22:33] <tomreyn> but its your choice
[22:33] <wendico> im very begginer
[22:33] <wendico> hehe
[22:33] <tomreyn> ok, we do sudo
[22:34] <tomreyn> sudo parted -ls | pastebinit
[22:34] <wendico> http://paste.ubuntu.com/p/rgQft7dNyH/
[22:36] <tomreyn> and mine is http://paste.ubuntu.com/p/c4Gn8c7hdD/
[22:37] <tomreyn> so that is interesting in that your disks now show up in a different order than they used to. look at the capacities
[22:37] <tomreyn>  /dev/sda is the first disk, its 120 GB, that's fine, just ntfs is wrong of course.
[22:37] <wendico> thats coz i had to change order in bios to boot
[22:38] <tomreyn> oh you changed that permanently there, ok
[22:38] <wendico> coz grub wasnt on first disk
[22:38] <tomreyn> right
[22:38] <sarnold> Partition Table: unknown
[22:38] <tomreyn> that's actually correct since you created the NAS md across the entire disks
[22:39] <tomreyn> so on the raw disks, like hardware raid, so therE's no partition tables there
[22:39] <wendico> yes i did and i did not format or created partitions yet there
[22:39] <wendico> just set it them as array
[22:39] <wendico> o yes i did
[22:39] <tomreyn> you did create an ext4 file system on top
[22:39] <wendico> coz /home is mounted there
[22:39] <tomreyn> but we can change this if you want to, np
[22:39] <wendico> right
[22:40] <tomreyn> but first lets concentrate on fixing the installer bugs
[22:40] <wendico> yes
[22:41] <tomreyn> we want to create a /boot raid1 across what is currently /dev/sda2 and /dev/sdc2
[22:41] <wendico> yes
[22:41] <tomreyn> to do so, we need to umommunt /boot first, which is /dev/sdc2, since we want to reuse it
[22:42] <tomreyn> but before we do this, let's confirm what is mounted where using "mount"
[22:42] <tomreyn> mount | pastebinit
[22:42] <wendico> http://paste.ubuntu.com/p/83yTrJR2tv/
[22:43] <tomreyn> line 33 of this confirms what i just claimed
[22:43] <tomreyn> we need to umommunt /boot first, which is /dev/sdc2, since we want to reuse it
[22:43] <tomreyn> sudo umount /boot
[22:44] <wendico> done^^  no echo
[22:44] <tomreyn> which means it succeeded
[22:45] <tomreyn> just to confirm things, and for a better overview: sudo lsblk -o NAME,SIZE,FSTYPE,TYPE,MOUNTPOINT | pastebinit
[22:45] <wendico> http://paste.ubuntu.com/p/2cW9CCsc7k/
[22:46] <tomreyn> now prepare the raid devices: sudo mdadm --zero-superblock /dev/sdc2
[22:46] <tomreyn> sudo mdadm --zero-superblock /dev/sda2
[22:47] <wendico> mdadm: Unrecognised md component device
[22:47] <tomreyn> oh right
[22:47] <tomreyn> so we can just skip this
[22:49] <tomreyn> sudo mdadm --create --verbose /dev/md/Boot --level=0 --raid-devices=2 /dev/sda2 /dev/sdc2
[22:49] <tomreyn> wait
[22:49] <tomreyn> wrong raid level
[22:49] <tomreyn> sudo mdadm --create --verbose /dev/md/Boot --level=1 --raid-devices=2 /dev/sda2 /dev/sdc2
[22:49] <tomreyn> wendico: ^
[22:49] <tomreyn> then do "cat /proc/mdstat" and see it building / initially synching
[22:50] <tomreyn> (if you're fast enough)
[22:50] <wendico> done
[22:50] <tomreyn> then, if there are no errors: sudo mkfs.ext4 -F /dev/md/Boot
[22:50] <wendico> on first command i get this note:Note: this array has metadata at the start and
[22:50] <wendico>     may not be suitable as a boot device.
[22:51] <wendico> by i clicked yes
[22:51] <wendico> then i runned second command with no echo
[22:52] <wendico> so my console look like this https://paste.ubuntu.com/p/wjrmwrd5kW/
[22:52] <tomreyn> it went on to say "If you plan to store '/boot' on this device please ensure that your boot-loader understands md/v1.x metadata, or use --metadata=0.90"
[22:52] <wendico> yep
[22:52] <tomreyn> our bootloader, grub 2, AKA grub 1.99,  understands this newer md metadata, so this is of no concern
[22:53] <wendico> awesome
[22:53] <tomreyn> you were meant to just run this in the end: cat /proc/mdstat
[22:53] <tomreyn> nothe the text i wrote: " and see it building / initially synching
[22:53] <tomreyn> :)
[22:54] <tomreyn> just ctrl-c if you're still hanging there
[22:54] <tomreyn> but i guess it's not waitring for input, but you have a prompt
[22:55] <tomreyn> does it look like you can enter new commands right now?
[22:55] <wendico> yep done
[22:55] <wendico> and cat proc shows now 3 raids
[22:55] <wendico> seems worked
[22:56] <tomreyn> cat /proc/mdstat | pastebinit
[22:56] <tomreyn> i'm so curious
[22:56] <wendico> http://paste.ubuntu.com/p/7CnF3kHPXZ/
[22:57] <tomreyn> loooks fine
[22:57] <tomreyn> and its already in sync
[22:58] <tomreyn> now we need to update /etc/fstab, the file which configured which file systems are part of this ubuntu installation and how they should eb treated on boot
[22:58] <wendico> ok
[22:58] <tomreyn> before we do, we need to get the UUIDs of those partitions we have
[22:58] <tomreyn> blkid | pastebinit
[22:58] <wendico> http://paste.ubuntu.com/p/jS6gM4ZfBC/
[22:59] <tomreyn> do you have a preferred console text editor, such as vim, nano, jed, pico
[22:59] <wendico> no
[22:59] <wendico> im learning on it
[22:59] <wendico> im just on default terminal
[22:59] <tomreyn> are oyu into vim basics, yet?
[23:00] <wendico> yes a bit
[23:00] <wendico> i edited a file sometime
[23:00] <tomreyn> so you know you need to type :q to quit, unless you made exits, then you need to user :x or :wq
[23:00] <tomreyn> *use, not useR
[23:01] <tomreyn> well, lets use nano for now, it's easier
[23:01] <tomreyn> sudo nano /etc/fstab
[23:02] <tomreyn> wait, this is missing one, because... we didnt create a file system, yet
[23:02] <tomreyn> exit nano if you started it already
[23:03] <tomreyn> wendico: sudo mkfs.ext4 /dev/md/Boot
[23:03] <wendico> lol, i can go out vim
[23:03] <wendico> q doesnt work
[23:03] <tomreyn> it's colon q
[23:03] <wendico> im about to close terminal an open ssh again
[23:03] <tomreyn> :q
[23:03] <wendico> done
[23:03] <wendico> ty
[23:03] <tomreyn> and before that, in case you are editing, you need to hit escape
[23:03] <tomreyn> ok
[23:04] <tomreyn> so do the mkfs
[23:04] <wendico> done^^ with normal echo no errors
[23:04] <tomreyn> then, once again (my fault): blkid | pastebinit
[23:04] <wendico> http://paste.ubuntu.com/p/PJTbdzFy72/
[23:04] <tomreyn> this should not like the file system we just created on the /boot raid
[23:05] <tomreyn> but it doesnt
[23:07] <tomreyn> wendico: are you sure you ran the "mkfs.ext4" command?
[23:08] <wendico> http://paste.ubuntu.com/p/VddpVf2PNj/
[23:08] <tomreyn> okay this looks liek the output of this
[23:09] <tomreyn> oh, sudo helps
[23:10] <tomreyn> sudo blkid /dev/md/Boot
[23:10] <tomreyn> says what?
[23:10] <wendico> /dev/md/Boot: UUID="c6603bb0-a540-4060-9b1d-14f665169137" TYPE="ext4"
[23:11] <tomreyn> wendico: okay, now: sudo nano /etc/fstab
[23:11] <wendico> im there
[23:11] <tomreyn> actually quit it again, the pastebinit /etc/fstab
[23:11] <tomreyn> then edit again
[23:12] <tomreyn> now look for the line which has "/boot" in it, and replace UUID=... by: UUID=c6603bb0-a540-4060-9b1d-14f665169137
[23:15] <wendico> replaced and saved file
[23:15] <tomreyn> to explain this a little: each file syytem has a 'universally uniquie ID' assigned to it, that's one of these garbled strings. they can be used for mounting at boot. it's an alternative to using these /dev/sd... device IDs, which, as we learnt during this boot where you changed the order of disks on the bios, can vary.
[23:15] <tomreyn> but the UUIDs always point to 'the right thing'
[23:16] <wendico> i understand
[23:16] <tomreyn> so even when you change the bios boot order, as long as grub loads, it will know where to keep booting from
[23:16] <tomreyn> i dont think you posted /etc/fstab
[23:16] <wendico> i see
[23:16] <tomreyn> could you do it now?
[23:17] <tomreyn> to exit nano, press ctrl-x
[23:19] <wendico> http://paste.ubuntu.com/p/Xjhbp6wHzq/
[23:19] <wendico> soz had some problems hehe
[23:19] <tomreyn> 'soz'?
[23:19] <wendico> file opened by root and by user, then tryint to paste an empty document to pastebin
[23:19] <wendico> thats why took so long for last paste
[23:19] <wendico> soz=sorry
[23:20] <tomreyn> oh ok, glad it worked, let me proof read this quicklky
[23:20] <wendico> ok np
[23:20] <tomreyn> i'm comparing to http://paste.ubuntu.com/p/PJTbdzFy72/
[23:20] <tomreyn>  / in fstab has UUID 08d55fa0-9c1e-11e8-82c0-001a92eb6f5c
[23:21] <tomreyn> uui in your "blkid" output is /dev/md126
[23:21] <tomreyn> which is the raid-1 across sda3[0] sdc3[1]
[23:22] <tomreyn> so this should be the md/Server
[23:22] <tomreyn> which is then fine
[23:23] <wendico> ok so we fixed the raid1 /boot partitions
[23:23] <wendico> should we now move grub to the proper drive?
[23:23] <tomreyn> fstab says /boot is UUID c6603bb0-a540-4060-9b1d-14f665169137
[23:23] <tomreyn> you said above that this UUID is /dev/md/Boot
[23:23] <tomreyn> so thats fine
[23:24] <tomreyn> fstab says /home is UUID 11799c98-9c1e-11e8-82c0-001a92eb6f5c
[23:24] <tomreyn> and "sudo blkid" and http://paste.ubuntu.com/p/jS6gM4ZfBC/ say that this is /dev/md127
[23:25] <tomreyn> and according to "cat /proc/mdstat" and http://paste.ubuntu.com/p/7CnF3kHPXZ/ md127 is the raid-0 spun across sdb and sdd, so the NAS storage
[23:26] <tomreyn> wendico: so, yes, this looks good.
[23:26] <tomreyn> there is another change we need to make to /etc/fstab thanks to another installer bug
[23:26] <wendico> awesome, you are the master hehe
[23:26] <tomreyn> so "sudo nano /etc/fstab" it again
[23:26] <wendico> go ahead, im all ears (eyes)
[23:27] <tomreyn> in the line which is about the / munt point, change the trailing 0 into 1
[23:27] <wendico> im on nano
[23:28] <tomreyn> in the lines which are about the /boo and /home mount points, change the trailing 0 to 2
[23:28] <tomreyn> then ctrl-x  and save
[23:28] <tomreyn> then: pastebinit /etc/fstab
[23:28] <wendico> there are two 0 in each line
[23:29] <wendico> all line ends with double 0
[23:29] <wendico> wich one of those 0 have to switch to 1
[23:29] <tomreyn> you only edit those in the last column
[23:30] <wendico> perfect
[23:30] <tomreyn> i can confirem this once it's on pastebin
[23:31] <wendico> http://paste.ubuntu.com/p/kFbfNGsJkN/
[23:31] <tomreyn> and while you're at it: pastebinit /etc/mdadm/mdadm.conf
[23:31] <wendico> http://paste.ubuntu.com/p/XTnfbJZrrP/
[23:31] <tomreyn> okay fstab looks fine
[23:32] <tomreyn> mdadm.conf is the main mdadm configuration file, which tells the system which raid arrays there are.
[23:33] <tomreyn> does it look good to you?
[23:33] <wendico> no, no /boot array
[23:33] <tomreyn> i agree
[23:34] <tomreyn> run: sudo mdadm --detail --scan
[23:34] <tomreyn> do you know what to do next?
[23:34] <wendico> http://paste.ubuntu.com/p/7CnF3kHPXZ/  this showed we had 3 arrays
[23:35] <wendico> reboot?
[23:35] <tomreyn> nonno.
[23:35] <wendico> mdadm scan show 3 arrays
[23:35] <tomreyn> sudo mdadm --detail --scan | pastebinit
[23:35] <wendico> the boot uuid array dows not match
[23:35] <tomreyn> okay it shows three arrays NOW, but the system may not know about this at boot
[23:35] <wendico> ?
[23:36] <tomreyn> does not match waht?
[23:36] <tomreyn> also if you would boot now you would not have a kernel to boot. since this needs to be on /boot, which is currently an empty new file system
[23:37] <wendico> ARRAY /dev/md/Boot metadata=1.2 name=servertronica:Boot UUID=d5b6fc5c:9a7dfc93:dd6e08a9:eac5746e
[23:37] <tomreyn> this was returned by "sudo mdadm --detail --scan"?
[23:37] <wendico> yes
[23:37] <tomreyn> okay then addi it to mdadm.conf
[23:38] <tomreyn> and tell me when you're done
[23:39] <tomreyn> so we got mdadm prepared for booting, we got fstab prepared for booting, but we need yet to re-populate /boot. /boot needs to contain our kernel image and initrd, without it linux (the kernel) cant boot
[23:40] <tomreyn> wendico: how are you coming
[23:40] <tomreyn> i'll brb, 3 minutes
[23:41] <wendico> http://paste.ubuntu.com/p/BfPfQGkMcx/
[23:41] <wendico> added
[23:41] <wendico> is that ok^?
[23:44] <tomreyn> i dont know your "sudo mdadm --detail --scan" output, but so i cant guarantee
[23:44] <tomreyn> but it seems to be in the right format
[23:45] <wendico> http://paste.ubuntu.com/p/JjTG9WX7Qc/
[23:45] <wendico> i see a problem there though
[23:46] <wendico> the lines i have not added i can read "Ubuntu-server" but my server name is correct only in the line i added "servertronica"
[23:46] <wendico> why is it that? should i edit the other first 2 line to match my server name?
[23:46] <tomreyn> this is fine, as long as it matches the mdadm --detail --scan output
[23:47] <tomreyn> this information is not only stored in mdadm.conf but also written to the raid arrays themselves
[23:47] <wendico> ok i understand
[23:47] <tomreyn> so the hostname you see there is the one which was valid by the time the raid array was created
[23:47] <tomreyn> two of these arrays we created from the installer
[23:48] <wendico> exactly
[23:48] <tomreyn> which had this "ubuntu-server" hostname
[23:48] <tomreyn> okay, now lets fix /boot
[23:48] <wendico> perfect
[23:48] <tomreyn> sudo mount /boot
[23:48] <wendico> done
[23:49] <tomreyn> now we need to getthe kernel and initrd installed there again
[23:49] <tomreyn> forst of all we need to find out which kernel should be installed / was installed on /boot before we deleted it
[23:49] <tomreyn> dpkg -l linux\*
[23:49] <tomreyn> those lines which start with ii are packages which are currently installed
[23:50] <tomreyn> we only care about those linux-image-4.15... packages for now
[23:50] <tomreyn> which ones do you have there=?
[23:51] <tomreyn> wendico: meep meep
[23:51] <wendico> 4.15.0linux-image-4. 4.15.0-29.31
[23:52] <tomreyn> oh this is cut off
[23:52] <wendico> also 30.32
[23:52] <tomreyn> you'd need to increase the size of your terminal or use something like
[23:52] <wendico> let me pastebin better, many lines there
[23:52] <tomreyn> COLUMNS=200 dpkg -l linux\*
[23:52] <wendico> http://paste.ubuntu.com/p/Rwy7xwd5xz/
[23:53] <tomreyn> okay, great, so we only care about the 'Name' column for now
[23:53] <tomreyn> and there only about those linux-image-4... packages
[23:54] <tomreyn> those are the ones which were on /boot previously and which we eradicated
[23:54] <wendico> i see
[23:54] <tomreyn> and which we now need to reinstall
[23:54] <tomreyn> so which packages is this?
[23:55] <tomreyn> i'm tryin got make you understand and learn things a bit,. if you'd prefer to be done soon we can do it a little faster
[23:55] <wendico> no i prefer this way
[23:55] <wendico> im learning
[23:55] <tomreyn> cool
[23:56] <wendico> linux generic 4.15.0.30.32  ??
[23:56] <tomreyn> just look at package names
[23:56] <tomreyn> you loolked at the Version column as well
[23:57] <sarnold> btw rather than COLUMNS=... stuff, I prefer dpkg -l whatever | cat
[23:57] <sarnold> that's enough to get dpkg to just show the output
[23:57] <wendico> so only linux-generic
[23:57] <tomreyn> thanks sarnold, good hint
[23:57] <tomreyn> so we're looking for the linux-image-4.... something packages
[23:57] <tomreyn> those with a veriosn number in the package name
[23:58] <tomreyn> i know it's a bit itrritating thatthose have version numbers in their name
[23:58] <wendico> but i have many of those lines
[23:59] <wendico> linux-image-generic
[23:59] <tomreyn> wendico: you don't . in the first column, there are those 'ii' and 'un'. we only want those which are 'ii'
[23:59] <tomreyn> in the second column, yuo have the package names.