[00:47] the Ubuntu Server 22.04 installer is just... terrible [00:47] The partitioning is... terrible [00:48] I have 6 disks, I want to slap 1 x 500MB for EFI and 1 x 100GB for a md0 [00:48] the installer won't let me add multiple EFIs [00:52] Yeah - the old Debian installer was a lot easier for partitioning. But I managed to get there eventually on the install I just did. (Didn't need EFI parts, though, because it was an older server.) [00:52] heh, are you using my old laptop too? :) [00:53] (I think that machine *can* do EFI, but I picked CSM back then Just Because) [00:57] I partitioned manually [00:57] I can't make it use the ESP partition [00:57] dear god [00:57] sarnold: No, I'm using your old HP Microserver Gen8, which was a sweet little box, and I wish they still made good servers like them. :-) [00:58] https://i.imgur.com/blH5Wpt.png [00:58] blahdeblah: ahh! yeah I keep hearing good things about those [00:58] znf: once it's installed, probably dpkg-reconfigure grub-pc or whatever it is will let you select all the EFIs you want to use [00:59] They took away a lot of cool things in the Gen10 to make them more enterprise so they could charge more money, which turned me off. I just use SFF desktops for my home servers now. [00:59] except: https://i.imgur.com/6JPYkOh.png [00:59] :) [00:59] argh :( [00:59] znf: lol [00:59] znf: oh man [01:00] znf: I think in the upper right corner there's a menu entry to file a bug report? it's been years since I've seen it.. [01:00] znf: if it feels like you ought to be able to proceed but can't, that's probably worth a report [01:00] I'm assuming it doesn't allow me to proceeed because I don't have a mounted EFI partition [01:01] but I can't tell how to use it [01:02] like nobody ever fucking tested this [01:02] do they just test this crap installer on "cloud" servers with 2 disks and call it a day [01:02] or wtf [01:03] can't even delete the partition https://i.imgur.com/piyCocZ.png [01:03] this is hilarious [01:04] OOOH! [01:04] I have to edit every disk [01:04] and tell it to "use as boot device" and then "add as another boot device" [01:05] And I end up with this: https://i.imgur.com/PdlfuLH.png [01:06] now let's see if it actually uses it as a "backup esp" and mirrors the contents [01:10] https://i.imgur.com/vxqA0OR.png [01:10] and it's taking 5+ minutes to... format 100GB? wtf [01:12] hmm, at 100 MB/s to usual hard drives, I think I'd expect around 17 minutes [01:12] they're 12G SAS drives, SSD [01:12] actually SAS, not SATA [01:13] https://i.imgur.com/QcKjBrv.png [01:13] is this thing actually waiting for the resync [01:13] wtf [01:14] no idae why it's 100MB/sec [01:49] oh, it failed the install [01:50] https://i.imgur.com/WizjI2n.png [01:50] \o/ [01:50] ;-( [01:51] it's a bit vague about what actually failed :( [01:51] yup [01:52] and it won't reboot lol === xispita_ is now known as xispita [11:47] I am currently running an Intel Atom-box (x86_64) in my basement and constantly look for possible arm64 replacements. Has anyone seen any small arm64 U1 boxes that work with Ubuntu Server for arm64? [11:48] sry, meant to say 1U rack mount [11:53] I ran across some of those when I was doing a few web searches for gear, but I can't remember who made them. Maybe Supermicro? [11:54] The one I currently have is a supermicro, but couldn't find any arm64 boxes from them. [11:58] I'll probably stick to the box I currently have. [12:44] derjanni: you might try gigabyte as well if you're looking for whitebox. you can check the certification site to see if the soc has been certified [12:44] dannf: awesome thanks [13:54] gigabyte just makings huge arm servers [13:54] the only small arm servers (under 200cores) I know of is by solid-run [15:36] paride: https://code.launchpad.net/~smoser/ubuntu/+source/sbuild-launchpad-chroot/+git/sbuild-launchpad-chroot/+merge/431224 [15:37] i pushed your suggested changes... now just curious on next steps. [15:37] a.) merge into master (~motu/ubuntu/+source/sbuild-launchpad-chroot:master) . [15:37] I just do that, right? I push to there ? [15:39] b.) then i upload ? I guess I should make a 'release' commit message before pushing, and then I just upload to lunar ? [15:48] smoser, yes I'd say so. What I'd do is: (1) merge to master (2) make "release version 0.20" pointing lunar in d/changelog (3) upload, wait for "Accepted" email (4) `git tag --signed 0.20` and push [15:49] make "release version 0.20" *commit* pointing lunar .. [15:49] ok. doing '1' and 2 now [15:50] I prefer to wait for the Accepted mail before pushing the release commit just in case the upload gets rejected for any reason [15:57] smoser, as we're speaking of that package, fyi I just filed https://bugs.launchpad.net/ubuntu/+source/sbuild-launchpad-chroot/+bug/1996205 [15:57] -ubottu:#ubuntu-server- Launchpad bug 1996205 in sbuild-launchpad-chroot (Ubuntu) "-proposed schroot not really using -proposed in >= Lunar" [Undecided, New] [16:00] did '3'. [16:06] paride: do you know how i make lintian aware of https://www.mit.edu/afs.new/sipb/project/debathena/lintian/www/tags/bad-distribution-in-changes-file.html [16:06] i'd have hoped it would reasd distro-info-data, but that has been updated. === scoobydoo_ is now known as scoobydoo