[00:30] <Roey> I have a Dell Inspiron 14z nv11 laptop from 2009-2012 time frame. I've just installed Covid 22.10 on it.  When I try to boot it, it says "Operating system not found".  How can I make my ship go?
[00:30] <Roey> Kubuntu 22.10 *
[00:32] <Roey> (yeah sorry bout that, am listening to a news report in the background)
[00:32] <Roey> anyway, how can I ascertain if the booting issue is due to bad MBR/GPE or something else?
[00:47] <tomreyn> Roey: disable intel rst in bios
[00:47] <arraybolt3> Roey: Check your drive boot order and enabled bootable devices, too.
[01:30] <Roey> tomreyn: I'm not sure this was even a setting like that available in bios
[01:30] <Roey> arraybolt3: the boot drive order has the ssd as first boot device, wich is what i wan
[01:30] <Roey> want*
[01:30] <arraybolt3> Roey: Hmm, do you know if this is a BIOS or a UEFI system?
[01:30] <Roey> BIOS
[01:31] <Roey> not UEFI.
[01:31] <Roey> it's too old to be uefi
[01:31] <Roey> there's no UEFI setting in BIOS at all
[01:31] <Roey> it's a dell inspiron 14z nv11, circa 2009-2012
[01:32] <arraybolt3> Hmm. OK, boot from the live USB, run "sudo fdisk -l | nc termbin.com 9999" and send the link that spits out. That should give us clues as to why it's not working.
[01:32] <arraybolt3> Also, did you try to install this standalone or dual-boot?
[01:32] <Roey> ok, I'll try that.
[01:32] <Roey> installed it standalone
[02:15] <Roey> hi all again
[02:15] <Roey> arraybolt3: so I've finally booted it and it's been booting from the DVD for like half an hour so far
[02:15] <Roey> maybe the dvd lens is dirty or something
[02:15] <Roey> gosh
[02:15] <Roey> anyway, so I'm at a knosole prompt now
[02:15] <Roey> lsblk
[02:16] <Roey> shows a partitioned /dev/sda
[02:16] <Roey> into four partitions
[02:23] <arraybolt3> Hmm. OK, boot from the live USB, run "sudo fdisk -l | nc termbin.com 9999" and send the link that spits out. That should give us clues as to why it's not working.
[02:23] <arraybolt3> (fdisk, not lsblk.)
[02:23] <Roey> arraybolt3: https://termbin.com/r5vy
[02:24] <arraybolt3> hmm... I see the bios boot partition, so this should work, but maybe GPT has confused it.
[02:24] <Roey> ok
[02:24] <Roey> there shouldn't be any EFI partition, right?
[02:24] <arraybolt3> I'd try reinstalling with manual partitioning, formatting the disk as MBR this time instead.
[02:24] <Roey> ok
[02:24] <Roey> hrm.
[02:24] <Roey> then I need to manually set up LVM encryption
[02:24] <arraybolt3> The EFI partition is made automatically even on BIOS systems confusingly.
[02:24] <Roey> that's why I chose full-disk + LVM + encryption
[02:25] <arraybolt3> Roey: No need for LVM for encryption to work if you're manual partitioning.
[02:25] <arraybolt3> Just make a LUKS-encrypted ext4 partition.
[02:25] <Roey> well
[02:25] <Roey> I want / + /boot + /home + swap  on all of it
[02:26] <Roey> arraybolt3: so how can I do that?
[02:26] <arraybolt3> Encrypt / and /home, put a swapfile on /, and leave /boot unencrypted?
[02:27] <Roey> swapfile I can do
[02:27] <Roey> /boot unencrypted though
[02:27] <Roey> hrm.
[02:27] <arraybolt3> That's what you get with LVM+encryption anyway.
[02:27] <Roey> I mean with the guided setup, /boot is encrypted too, right?
[02:27] <Roey> oh
[02:27] <Roey> ok
[02:27] <arraybolt3> You might be able to set /boot encrypted too, though I've not tried it with Kubuntu. I know it Just Works on Lubuntu, but Lubuntu uses a different installer.
[02:27] <Roey> ah
[02:27] <Roey> now
[02:28] <Roey> I /am/ installing stock 22.10
[02:28] <Roey> without any updates over the network
[02:28] <Roey> has this thing issue been fixed since october 2022?
[02:28] <arraybolt3> I don't think /boot being unencrypted is considered a bug.
[02:28] <Roey> ok
[02:28] <Roey> plus I wonder how much more effort this takes
[02:28] <arraybolt3> I don't know if it will fail if you try to encrypt /boot, I've never tried it on Kubuntu. It's worth a shot, and I would expect it to work.
[02:29] <Roey> ok
[02:29] <Roey> ewll if the default method doesn't encrypt /boot
[02:29] <Roey> then why should I do it myself
[02:29] <Roey> so how do I go about doing all this?
[02:29] <arraybolt3> Manual partitioning, MBR partition table, make a 4 GB /boot encrypted, then a <however big you want plus room for swap> root encrypted, then everything else /home encrypted, and install the bootloader to the main disk directly. Or you can make /boot unencrypted, your choice.
[02:30] <Roey> how would I install the bootloader to hte main disk directly, what, with grub you mean?
[02:30] <Roey> *to the main partition on the main disk
[02:32] <Roey> also, arraybolt3, so in taking your advice above, i'd be using a swap partition and not a swap file, why your switch in tactics?
[02:33] <arraybolt3> Roey: The way above is still with a swap file.
[02:33] <Roey> oh
[02:33] <arraybolt3> Also installing the bootloader to the main disk directly should be easy, just select whatever your main disk is (probably /dev/sda) in the "Boot loader location" box or whatever it's called.
[02:34] <arraybolt3> (With EFI I think you do things slightly differently but this isn't EFI.)
[02:34] <arraybolt3> Roey: The way above has you make a root partition with extra room so that you can fit a swapfile on the root partition. I mean you *could* store the swapfile in /home but that would be weird :P
[02:34] <Roey> soparition-wise: MBR | 4 GB /boot encrypted (ext4? btrfs?) | swap partition?, encrypted | / encrypted, btrfs? | /home encrypted, btrfs?
[02:35] <Roey> arraybolt3: oh ok
[02:35] <Roey> I thought you meant to make swap a separate partition
[02:35] <arraybolt3> I would avoid using btrfs on root if the swapfile is going there, that could be tricky.
[02:36] <Roey> maybe I'll just make a swap partition
[02:36] <Roey> thne.
[02:36] <Roey> but I'd like to put btrfs over a LUKS/lvm thing
[02:36] <Roey> yeah
[02:36] <lee> hello
[02:37] <Roey> o/
[02:37] <lee> i have a problem with my hardware (keyboard)
[02:37] <lee> button presses are hit or miss
[02:38] <Roey> also--
[02:38] <lee> sometimes numbers dont work
[02:38] <Roey> for some reason, arraybolt3, it doesn't appear to respond when I click "New Partition Table..."
[02:38] <Roey> or "Delete"
[02:38] <lee> i have to keep pressing the key(s)
[02:38] <Roey> or clicking on any of the checkboxes in the "Format?" column
[02:38] <Roey> arraybolt3: ^
[02:38] <arraybolt3> That's weird.
[02:40] <Roey> ok nevermind
[02:40] <Roey> I managed to delete them all
[02:40] <Roey> manually
[02:40] <Roey> by clicking on the partition entry and clicking "Delete"
[02:41] <Roey> lee: sorry for ignoring you, I'm just knee-deep in this installation
[02:41] <arraybolt3> lee: I don't think that can be resolved by Kubuntu, if your keyboard is requiring that you hit stuff multiple times, that sounds like you need a new keyboard.
[02:43] <Roey> how big a size for root, arraybolt3?
[02:43] <Roey> I've got a 1 TB ssd here.
[02:43] <Roey> 100GB?
[02:43] <Roey> 200GB?
[02:43] <Roey> and the rest for /home?
[02:43] <Roey> I'll use a swap file instead of a partition.
[02:44] <Roey> or maybei t doesn't matter since it's btrfs anyway
[02:44] <arraybolt3> Roey: I'd personally use between 64-128 GB for /root, but that's just me, if you use a lot of apps (especially big apps) you might need more.
[02:44] <arraybolt3> Er, not /root, but /.
[02:44] <Roey> *ahh* ok
[02:44] <arraybolt3> (There's actually a /root folder but that's a very differernt thing)
[02:44] <Roey> yeah old-school unix folks used to put /root on a separate partition
[02:45] <Roey> if I make a swapfile on a BTRFS filesystem on an SSD
[02:46] <Roey> will btrfs's COW muck things up?
[02:46] <arraybolt3> Possibly. When you try to "swapon" the file, it may say "swapfile has holes" and refuse to let it work.
[02:46] <arraybolt3> I think there's a way to make it work though.
[02:46] <Roey> eek.
[02:46] <Roey> ok
[02:46] <Roey> swap partition it is, then.
[02:46] <arraybolt3> Also, how many partitions are you about to have?
[02:47] <arraybolt3> If you're going to use more than 4, you'll need to make an "extended partition" and then make further "logical partitions" inside that one.
[02:47] <arraybolt3> (MBR only supports four primary partitions, or three primary and one extended. Then the extended one can hold as many logical partitions as you want.)
[02:47] <Roey> /boot | /swap | / | /home
[02:47] <arraybolt3> Ah, nice.
[02:47] <Roey> thanks.also, how do I set these up as encryptd?
[02:50] <arraybolt3> There should be an "Encrypt" checkbox when you go to make each partition, I believe.
[02:51] <Roey> so I have:  /boot - 8,  GB swap - 16 GB, / - 150 GB, /home - 825 GB or so
[02:51] <Roey> arraybolt3: I see no such option
[02:52] <arraybolt3> Tar, lemme look at the actual installer...
[02:52] <arraybolt3> (I'd be very surprised if Ubiquity, the installer used by Kubuntu, doesn't have this option...)
[02:53] <Roey> ok
[02:53] <Roey> and this is for 22.10
[02:53] <arraybolt3> OH wow. I got the installer to crash >_<
[02:54] <arraybolt3> Hold on, I'll do some experimenting, give me a bit...
[02:54] <Roey> :-)
[02:54] <Roey> thank you :)
[03:05] <arraybolt3> Roey: Wow. So I underestimated how limited this installer was.
[03:05] <Roey> `hahaha
[03:05] <Roey> :)
[03:05] <arraybolt3> Roey: It looks like you can make a "physical volume for encryption", but then how you set a filesystem...?
[03:05] <Roey> I've found https://www.tangibleabstraction.com/2020/05/21/full-disk-encryption-on-ubuntu-with-manual-partitioning/  <- and this involves dropping to a Konsole instead of using Ubiquity's paritioner
[03:06] <arraybolt3> Yeah. That might work.
[03:06] <Roey> gosh this looks so complimicated
[03:06] <arraybolt3> Hmm. Lemme try an installation like that and report back the results.
[03:07] <Roey> ok
[03:07] <Roey> oh wow you're so flexible, thanks so much
[03:11] <arraybolt3> Might take a bit, thanks for your patience.
[03:11] <Roey> aye
[03:16] <arraybolt3> OK well the installer threw a *fit* over what I just did, but it's installing :P
[03:16] <arraybolt3> If this works, then encrypted /boot should be possible.
[03:16] <arraybolt3> As well as BTRFS and whatnot.
[03:20] <Roey> oooh ok
[03:21] <Roey> so what exactly did you do?
[03:27] <arraybolt3> Well, hold on, lemme see if this works first :P
[03:27] <Roey> sure :) :)
[03:27] <arraybolt3> (My connection is slow and I failed to tell it to not install updates so it might be a few more minutes.)
[03:28] <Roey> ok
[03:29] <Roey> I'm just impressed that you did an installation just to help me out
[03:29] <arraybolt3> I use virtualization software, so it's super easy to do stuff like that.
[03:29] <Roey> ha, aye
[03:29] <arraybolt3> (Basically it lets me run a whole "computer" as an application, so I can do an OS installation in a virtual machine and be able to figure out how to make things happen.)
[03:30] <Roey> yeah I know
[03:30] <Roey> it's just the amount of effort
[03:30] <Roey> wow, like I said, I'm impressed, and thank you
[03:30] <Roey> :)
[03:30] <arraybolt3> If this works, I'll make a second VM but with a much larger disk, and then we'll walk through making identical installations at the same time. That way if something blows up, I'll know it on my end before it blows up on your end.
[03:30] <Roey> k
[03:31] <arraybolt3> Uh... crud. OK so things did blow up with the partition that /boot was on encrypted.
[03:32] <arraybolt3> (I didn't make a separate /boot and /, I just made them the same thing and encrypted / entirely, and it made GRUB mad.)
[03:32] <Roey> ok
[03:32] <Roey> hrm
[03:32] <arraybolt3> Sigh. It looked like it was going so well.
[03:32] <Roey> heh
[03:32] <Roey> it's ok
[03:33] <Roey> I mean I suppose I can live with unencrypted /boot
[03:33] <arraybolt3> K. Well, let's try it. The installer was able to cope with my shenanigans, so hopefully having /boot unencrypted will do the trick.
[03:33] <Roey> hey I wonder... if I use btrfs on (unencrypted) /boot, (encrypted) / and (encrypted) /home,  will BTRFS play nice with all that, since it sits a layer above LUKS?
[03:34] <arraybolt3> BTRFS and LUKS technically function together, but I have heard of it possibly making SSDs fail in the past.
[03:34] <arraybolt3> (LUKS just makes an encrypted container that you can put theoretically any filesystem inside.)
[03:35] <Roey> aye
[03:35] <arraybolt3> Then again, my mentor runs LUKS+BTRFS on his main rig and it works just fine :P
[03:35] <Roey> :)
[03:35] <arraybolt3> OK, are you at the Kubuntu desktop?
[03:35] <Roey> yes I am
[03:35] <arraybolt3> Alright, let's launch Konsole.
[03:35] <Roey> currently at the partitioner screen of the installer
[03:35] <Roey> sure
[03:35] <Roey> I'm there
[03:35] <arraybolt3> Close the installer, we need to do this part first and then launch the installer.
[03:36] <arraybolt3> It will ask if you want to abort the installation, tell it yes.
[03:36] <Roey> done
[03:36] <arraybolt3> OK, do "lsblk" and tell me what your main disk is.
[03:36] <arraybolt3> (I assume it's going to be /dev/sda.)
[03:36] <Roey> .dev.sda
[03:36] <Roey> /dev/sda, right
[03:36] <arraybolt3> K.
[03:36] <arraybolt3> sudo fdisk /dev/sda
[03:36] <Roey> Command (m for help):
[03:37] <arraybolt3> At the fdisk prompt, type a single "o" and press Enter. This will wipe the disk.
[03:38] <Roey> it bitches about "the device contains 'gpt' signaure and it will be removed by a write command.  See fdisk(8) man page and --wipe option for more details", but also says "Created a new DOS disklabel with disk (identifier 0x73f9703)
[03:38] <arraybolt3> (hold on, I'll be right back, I have to go afk for just a sec)
[03:38] <Roey> k
[03:38] <Roey> probably because the installer before it made a gpt partition
[03:38] <arraybolt3> Probably.
[03:38] <Roey> thinking that this is a UEFI system
[03:38] <Roey> excuse my language, sory
[03:39] <Roey> but now I am back at the Command (m for help): prompt
[03:41] <arraybolt3> OK back.
[03:41] <arraybolt3> Alright, type a single "n" and press Enter.
[03:41] <arraybolt3> Then "p", Enter.
[03:42] <arraybolt3> Then Enter again.
[03:43] <arraybolt3> It should say something like First sector (2048-99999999, default 2048): (but that 999999999 will almost certainly be different)
[03:43] <Roey> Parition nuumber (1-4, default 1):
[03:44] <arraybolt3> Yeah, press Enter there.
[03:44] <Roey> ok
[03:45] <Roey> NOW it says "First sector (2048-1953525167, default 2048):
[03:45] <arraybolt3> Alright, good. Now just "Enter" again.
[03:45] <arraybolt3> Next prompt should be "Last sector" and then a bunch after that.
[03:46] <Roey> Last sector, +/- sectors or +/-size{K,M,G,T,P} (2048-1953525167, default 1953525167):
[03:46] <arraybolt3> Type "+4G" and then press Enter.
[03:46] <Roey> ok
[03:46] <Roey> (is 4 G good enough for /boot? without it getting full?)
[03:46] <arraybolt3> Should be more than necessary. All /boot has to hold is the kernels and whatnot.
[03:46] <Roey> Created a new partition 1 of type 'Linux' and of size 4 GiB.
[03:46] <Roey> Command (m for elp):
[03:46] <arraybolt3> 2G might be a bit thin, 4G should work.
[03:46] <Roey> k
[03:47] <Roey> saying this b/c I've encountered a too-small /boot before
[03:47] <arraybolt3> OK, "n", Enter.
[03:47] <Roey> at like 350 mb
[03:47] <Roey> ok
[03:47] <Roey> Parition type
[03:47] <arraybolt3> (My system is currently using a <2G /boot made by the installer and it works.)
[03:47] <Roey> p primary (1 primary, 0 extended, 3 free)
[03:47] <arraybolt3> "p", Enter.
[03:47] <Roey> e extended (container for logical partitions)
[03:47] <Roey> ok
[03:47] <Roey> Partition number (2-4, default 2):
[03:47] <arraybolt3> Enter.
[03:48] <Roey> First sector (8390656-1953525167, deault 8390656):
[03:48] <arraybolt3> Enter.
[03:48] <arraybolt3> OK, how much RAM is in your system?
[03:48] <Roey> 8GB
[03:48] <arraybolt3> OK, so do "+8GB", Enter.
[03:49] <arraybolt3> (You could get away with less, but that should work well.)
[03:49] <Roey> Last sector, +/- sectors or +/-size{K,M,G,T,P} (28390656-1953525167, default 1953525167):  +8GB
[03:49] <Roey> er
[03:49] <Roey> I thought 16 GB
[03:49] <Roey> ?
[03:49] <Roey> twice the size of RAM, right?
[03:49] <arraybolt3> It used to be recommended that you have twice as much swap as RAM, that is no longer.
[03:49] <Roey> for systems with smaller amounts of ram
[03:49] <Roey> ok
[03:49] <arraybolt3> You can do 16G if you want, but 8G should be plenty enough.
[03:49] <Roey> I'm not gamin on this old laptop after all
[03:49] <Roey> ok, 8GB it is.
[03:50] <Roey> compromise: 12G
[03:50] <arraybolt3> Sure.
[03:50] <arraybolt3> +12G, Enter.
[03:50] <Roey> Created a new partition 2 of type 'Linux' and of size 12 GiB.
[03:50] <Roey> Command (m for help):
[03:50] <arraybolt3> Nice. OK, and you wanted / to be how big?
[03:51] <Roey> 150GB, say
[03:51] <arraybolt3> OK. "n", Enter again.
[03:51] <Roey> (like with BTRFS it shouldn't matter, right, since it glomps them all together?)
[03:51] <arraybolt3> ...I don't think that quite works that way.
[03:51] <Roey> ok, again it asks me for "p" primary or "e" extended
[03:51] <arraybolt3> You *can* glomp them together, but it's not automatic.
[03:51] <Roey> arraybolt3: well with my desktop, I see that the free space on / and /home and /boot are all the same
[03:52] <arraybolt3> That's because they're all on the same partition.
[03:52] <arraybolt3> Separate partitions will change that.
[03:52] <Roey> pj/ upi
[03:52] <Roey> er
[03:52] <Roey> oph, you're right.
[03:52] <Roey> they're all on /dev/sda1
[03:52] <Roey> even though they show up as separate entries in "df"
[03:52] <arraybolt3> True.
[03:53] <arraybolt3> Er... wait what?
[03:53] <Roey> hrm. I wonder how that happened.
[03:53] <arraybolt3> I got "df" and "du" mixed up.
[03:53] <arraybolt3> Oh... you probably are using mutliple BTRFS *subvolumes*.
[03:53] <arraybolt3> That's likely how that happened.
[03:53] <Roey> yeah, / /home and /arch are all on /dev/sda1
[03:53] <Roey> yeahhh I think so
[03:53] <Roey> I installed it with btrfs through ubiquity
[03:53] <Roey> this is how it installed it, I guess.
[03:54] <arraybolt3> Hmm... ok we might be able to make that happen.
[03:54] <Roey> and yes, they are subvolumes, I'm certain of that
[03:54] <Roey> oh good!!
[03:54] <arraybolt3> If you want the separate subvolumes.
[03:54] <Roey> I would like that to be the case since then I don't care so much about the free space on any individual partition
[03:54] <Roey> er
[03:54] <Roey> subvolume
[03:54] <arraybolt3> Nice. In that instance, we should probably make the next partition eat the whole disk.
[03:54] <Roey> ok
[03:54] <Roey> for what it's worth--
[03:54] <arraybolt3> And hope Ubiquity figures out how to make the subvolumes right :P
[03:55] <Roey> I do not have a /boot on my desktop as a separate partition
[03:55] <Roey> just /, /home and /arch (for media and such)
[03:55] <Roey> arraybolt3: :)
[03:55] <arraybolt3> If you want encryption to work with Ubiquity, I'd definitely make a separate /boot like we just did, since it really blew up a bit ago trying to encrypt it.
[03:55] <Roey> ah ok
[03:55] <Roey> yes yes
[03:55] <Roey> understood
[03:55] <arraybolt3> So I think we're on the right track.
[03:55] <oerheks>  /arch ?
[03:55] <oerheks> lolz
[03:55] <Roey> that's for po
[03:55] <Roey> *media*
[03:55] <Roey> yes
[03:55] <arraybolt3> Ack...
[03:56] <arraybolt3> Roey: You may be using Enter a bit too much. An anti-flood bot just mistakenly muted you....
[03:56] <arraybolt3> It stops after 60 seconds, so just hang on a sec.
[03:56] <arraybolt3> (Sorry about that.)
[03:56] <oerheks> do not copy paste mutiple channesl
[03:56] <oerheks> hahaha'
[03:57] <arraybolt3> OK, fixed.
[03:57] <Roey> \o/
[03:57] <arraybolt3> Roey: OK, so "p", Enter.
[03:57] <Roey> Partition number (3,4, default 3):
[03:57] <arraybolt3> Then just keep pressing "Enter" until you get to the "Last sector" line.
[03:57] <Roey> ok, there.
[03:58] <arraybolt3> If we're going to have Ubiquity do the subvolumes thing, I think just hit Enter again and that will make the last partition take up the rest of the disk.
[03:58] <Roey> ok
[03:58] <Roey> size 915.5 GiB
[03:58] <Roey> good.
[03:58] <arraybolt3> Alright. "w", Enter.
[03:58] <arraybolt3> We are now done with partitioning.
[03:58] <Roey> ok good
[03:58] <Roey> it synced disk, ok.
[03:58] <mmikowski> Hey Roey, I see you are undertaking LUKS + BTRFS on kubuntu? (hi arraybolt3!)
[03:59] <arraybolt3> Alright, the next step is to make our filesystems. We want /boot on /dev/sda1, which will be ext4 since we don't really care what FS /boot uses, I don't think.
[03:59] <arraybolt3> mmikowski: o/
[03:59] <Roey> mmikowski: indeed!!
[03:59] <Roey> arraybolt3: any chance of using btrfs on /boot?
[03:59] <mmikowski> I can still send that file. It would be good for reference.
[03:59] <arraybolt3> Then swap will be, well, a swap-formatted partition. Then we'll leave the last one *unformatted* so Ubiquity takes care of it.
[03:59] <Roey> arraybolt3: ok
[03:59] <Roey> mmikowski: which one?
[03:59] <arraybolt3> Roey: Depends on if GRUB can understand btrfs or not.
[03:59] <mmikowski> You can use btrfs on boot, but it starts getting complicated.
[04:00] <Roey> well it can boot / as btrfs
[04:00] <Roey> which includes /boot
[04:00] <mmikowski> Grub sorta can understand btrfs
[04:00] <Roey> on my desktop
[04:00] <arraybolt3> Ah, nice, then yes, we can do btrfs on /boot, I believe.
[04:00] <mmikowski> Depends on the version; there are caveats
[04:00] <Roey> latest & greatest
[04:00] <arraybolt3> mmikowski: Well we're using the latest interim release, so it should work.
[04:00] <arraybolt3> Roey: OK, so, lemme figure out the mkfs.btrfs command...
[04:00] <Roey> aye
[04:00] <Roey> mkfs.btrfs /dev/sda1 I'd think
[04:01] <mmikowski> well, let me see if I used it on our test build. That was tested a lot. I think we did.
[04:01] <Roey> ok
[04:01] <mmikowski> But you need to make it big to allow for snapshot.
[04:01] <mmikowski> ^s
[04:01] <Roey> erm 4 GB enough?
[04:01] <arraybolt3> Oh tar. I didn't take snapshotting into account.
[04:01] <mmikowski> yeah, that's probably a good size
[04:01] <Roey> I've run into disk space issues on /boot before
[04:01] <arraybolt3> Ah, OK.
[04:01] <Roey> when it was like 200 MB
[04:02] <Roey> sometimes when i'm ruinning low on disk space, I delete previous snapshots
[04:02] <Roey> I made a script to do that
[04:02] <Roey> ok so,
[04:02] <arraybolt3> Roey: I think "sudo mkfs.btrfs /dev/sda1" should work.
[04:02] <mmikowski> I ran /boot as a BTRFS subvolume; no separate partition.
[04:03] <Roey> that worked
[04:03] <Roey> also "performing full device TRIM /dev/sda1 (4.0GiB) <- btrfs plays well with ssd trim, yeah?
[04:03] <arraybolt3> mmikowski: Ubiqiuty really blew up on me when I tried to encrypt the partition containing /boot, so something about that didn't work.
[04:03] <Roey> mmikowski: yeah that'swhat I do on my desktop.
[04:03] <arraybolt3> Roey: I believe so.
[04:03] <Roey> I mean I read about it playing nice with ssd trim aye
[04:03] <Roey> ok, next up:
[04:03] <Roey> swap
[04:04] <arraybolt3> sudo mkswap /dev/sda2
[04:04] <Roey> mkswap /dev/sda2
[04:04] <Roey> yeah
[04:04] <mmikowski> Yes, there are conditions there too.
[04:04] <Roey> ok
[04:04] <Roey> btw we wnat this encrypted too
[04:04] <mmikowski> Ah, luks2 is not full supported for grub as of 2022.04
[04:04] <arraybolt3> Oh. I forgot about that.
[04:04] <mmikowski> have to use grub v1
[04:04] <arraybolt3> OK, lemme check something...
[04:04] <mmikowski> That may have been updated, but those are in my notes.
[04:05] <mmikowski> So this is the full-encryption image I'm looking at, and we discarded that.
[04:05] <Roey> ok
[04:05] <mmikowski> luks1 is not as secure.
[04:05] <arraybolt3> Thankfully we're using /boot unencrypted so we won't need to use luks1.
[04:05] <Roey> aye
[04:06] <mmikowski> Yeah, that's the other image that I actually used. Let me bring that up.
[04:06] <arraybolt3> OK, I can make the swap partition LUKS-encrypted.
[04:06] <oerheks> https://answers.launchpad.net/ubuntu/+question/703288
[04:07] <arraybolt3> oerheks: Hmm... spam comment in there.
[04:07] <arraybolt3> Might wanna report that.
[04:07] <arraybolt3> Roey: OK, so to make the encrypted swap, do "sudo cryptsetup luksFormat /dev/sda2".
[04:08] <mmikowski> I ran 512M boot/efi, 4GB swap, 4GB /boot BTRFS, rest LUKS; subvolumes of @ / and @home /home
[04:08] <arraybolt3> Roey: It will warn about the wiping of data, type "YES" (in capitals) and press Enter.
[04:08] <arraybolt3> Then type your intended passphrase twice.
[04:08] <Roey> k
[04:09] <Roey> ok
[04:09] <Roey> it's crunching away
[04:09] <Roey> now it finished.
[04:09] <mmikowski> kk, off to dinner. Good luck guys. If you get stuck and want the script, I can send it along in a pastebin.
[04:10] <Roey> thanks mmikowski
[04:10] <Roey> enjoy dinner!
[04:10] <Roey> arraybolt3: next step,
[04:10] <mmikowski> one sec, I'll add to paste bin.
[04:10] <Roey> thanks
[04:10] <mmikowski> Ignore the reference to a recovery partition, you don't need that.
[04:11] <Roey> arraybolt3: next step is / and /home on /dev/sda3
[04:11] <Roey> as btrfs, on a luksFormat
[04:11] <Roey> mmikowski: ok
[04:11] <mmikowski> what's the recommended pastebin these days?
[04:11] <Roey> paste.ubuntu.com
[04:13] <mmikowski> https://pastebin.ubuntu.com/p/mTQ4XyrbdN/
[04:13]  * Roey clicks
[04:13] <arraybolt3> OK, back, sorry for the delay.
[04:14] <Roey> aye np
[04:14] <arraybolt3> Roey: OK, so *now* launch Ubiquity.
[04:14] <Roey> oh, so not even bother mkfs.brfs on /dev/sda3?
[04:14] <Roey> ok
[04:14] <arraybolt3> True. We'll let... tar, I missed a step, close Ubiquity :P
[04:14] <mmikowski> This script was run in live CD mode and partitioned everything before running install. Then the installer could use all existing partitions. I ran this setup for 4 months.
[04:14] <Roey> arraybolt3: ok done :)
[04:15] <mmikowski> So there you have it if you need it. IIRC, it just worked, although ymmc.
[04:15] <Roey> mmikowski: much appreciated
[04:15] <mmikowski> ^ymmv. Good luck!
[04:15] <arraybolt3> Roey: OK, so, we did cryptsetup on /dev/sda2, right?
[04:15] <arraybolt3> Yeah.
[04:15] <Roey> arraybolt3: correct, we did
[04:16] <arraybolt3> Alright, so next step is actually for me to facepalm because I missed an argument in the above cryptsetup command
[04:16] <Roey> \o/
[04:16] <Roey> I mean /o\ *
[04:16] <arraybolt3> Can you do "ls /dev/mapper" and tell me what is shows?
[04:16] <Roey> control
[04:17] <Roey> as a character device
[04:17] <Roey> er
[04:17] <arraybolt3> Oh, OK, I didn't forget, I'm just forgetting some of my commands.
[04:17] <Roey> crw----------
[04:17] <arraybolt3> We're fine.
[04:17] <Roey> phew \o/
[04:17] <arraybolt3> OK, "sudo cryptsetup open /dev/sda2 luksSwap"
[04:17] <mmikowski> https://pastebin.ubuntu.com/p/2zR45j8XKk/
[04:17] <arraybolt3> (I thought the "luksSwap" went in the above command, thus my confusion.)
[04:17] <arraybolt3> Er, you know what I mean.
[04:18] <mmikowski> ^^ That's the post-install script; it cleaned up a bunch of stuff after install but before reboot.
[04:18] <Roey> ok
[04:18] <Roey> arraybolt3: it took.
[04:18] <mmikowski> kk guys, hope that helps.
[04:18] <Roey> mmikowski: ^_^
[04:18] <mmikowski> peace out :)
[04:18] <arraybolt3> Roey: Nice. btw, if this fails miserably, we'll just go back and try mmikowski's script, which probably works better anyway.
[04:18] <Roey> ok
[04:18] <Roey> mmikowski: gnight :)
[04:18] <Roey> enjoy dinner :)
[04:19] <Roey> arraybolt3: so what now?
[04:21] <arraybolt3> Roey: I am so sorry, but I've suddenly run out of time to do this. I think your best bet may be to use mmikowski's scripts (especially since they worked for him and I am not entirely sure if my way is going to work or not).
[04:22] <Roey> !!
[04:22] <Roey> is there a wya we can continue tomorow?
[04:22] <arraybolt3> Maybe. I am so sorry this happened. I gotta go.
[04:22] <Roey> ok
[04:22] <Roey> well thank you
[04:55] <claudio> Bluetree
[13:29] <BluesKaj> Hi all
[16:17] <imperio-yhwh> ok
[21:35] <Guest62> hello
[21:36] <hasek> any1 here?
[21:37] <arraybolt3> hasek: o/
[21:37] <arraybolt3> There's plenty of people here usually, we just usually don't say alot until someone asks for help.
[21:37] <hasek> i need help
[21:37] <arraybolt3> What's gone wrong?
[21:37] <hasek> with my sources and discover
[21:38] <arraybolt3> OK. Can you explain in detail what's happening, and also tell us what error messages you're seeing, if any?
[21:38] <hasek> every time i lunch my discover i get a msg that the ubuntu server source is not longer there
[21:39] <hasek> so i cant sudo apt update or anything
[21:39] <hasek> can i post a pic?is that possible?
[21:40] <arraybolt3> Hmm, OK. In order to see what's gone wrong, I'll probably need to see what sources apt is using. Can you run in Konsole "cat /etc/apt/source.list | nc termbin.com 9999", and send the link that outputs? *Please do not paste the full contents of the file into the chat, just send the link and that will let me see it.*
[21:40] <arraybolt3> Also, sure, you can upload pictures to Imgur or ImgBB and send the link to them here.
[21:42] <hasek> it says no such file or directory
[21:45] <arraybolt3> Check your typing, you probablh mis-spelled something.
[21:45] <arraybolt3> The command you type should match the one above to the letter.
[21:45] <arraybolt3> Except that I made a typo.
[21:45] <arraybolt3> Facepalm...
[21:45] <hasek> i copied and pasted
[21:45] <arraybolt3> cat /etc/apt/sources.list | nc termbin.com 9999
[21:46] <hasek> oh
[21:46] <arraybolt3> (I wrote "source.list" rather than "sources.list" /o\)
[21:46] <hasek> i got this   https://termbin.com/4qqm
[21:47] <arraybolt3> Oh. You're using Kubuntu 21.04, which went EOL nine months after release.
[21:47] <arraybolt3> And strangely you don't have the updates or security repos?
[21:47] <hasek> ya .... what is eol?
[21:48] <hasek> b/c it wont
[21:48] <arraybolt3> EOL = End Of Life. Basically the OS no longer receives updates after it goes EOL.
[21:48] <hasek> everything is messed up
[21:48] <arraybolt3> The only solution is to upgrade to a newer version of Kubuntu.
[21:48] <arraybolt3> However, Kubuntu 21.04 is very far behind the current latest LTS of Kubuntu, and even further behind the most recent release.
[21:48] <hasek> can i do that without starting over
[21:48] <arraybolt3> You might be able to, but it's likely going to be a whole lot of work.
[21:49] <arraybolt3> Unless you have a specialized setup, it would almost certainly be easiest to back up your data and install Kubuntu 22.04 or 22.10 from scratch.
[21:49] <hasek> so i just need to erase and reinstall the new one/?
[21:49] <arraybolt3> Yep.
[21:49] <hasek> ok
[21:50] <arraybolt3> Hopefully it goes without saying, but make sure you save your data on an external drive before installing the newer version of Kubuntu. :)
[21:50] <hasek> ya is was working all good then all of the sudden one time when i went to go update i started to get all these errors. i was thinking i must have dont something worng
[21:51] <arraybolt3> Nah, the old repository probably just got archived.
[21:51] <hasek> ya i mean i plan to get a new hd anyway, i just wanted to see if i could somehow fix these errors
[21:52] <arraybolt3> If you don't like updating frequently, you should probably use Kubuntu 22.04, which is supported for 3 years. Kubuntu 22.10 only gets nine months of support, which means you'll have to upgrade soon after the next release comes out or this will probably happen again.
[21:53] <hasek> ya that what i was going to upgrade to, but i also thought this one was an lts. what happened to that?
[21:53] <arraybolt3> Kubuntu 20.04 was LTS. 21.04 is an interim.
[21:53] <arraybolt3> LTS releases are made every two years.
[21:53] <hasek> oh
[21:53] <hasek> cool beans
[21:53] <arraybolt3> So 20.04 and 22.04 are the current LTS releases. (20.04 goes EOL very soon, 22.04 should work for a good long while.)
[21:54] <hasek> welp ill be getting the new one then
[21:55] <hasek> ok well thank you for your help
[21:56] <arraybolt3> Glad to help!
 Here's a fun one, trying to use the  Game Controller calibration, but it doesnt work for PS5 pads because it wants the axis values of the R2 and L2 buttons, but pushing them counts as a button presss and moves on to the next calibration step.