=== cpaelzer_ is now known as cpaelzer === alucardromer0-l2 is now known as alucardromero-l2 [12:57] hi, i try to install ubuntu 22.04 and i receive this error "Size in not a multiple of 512 error" when it try to create a LVM partition. [12:58] the disk size it is 1.9T and i try to create a 1.73T RAID1 disk [12:59] what can i do? :) === drkokandy_ is now known as drkokandy [16:01] try 1.72 or 1.74, or whatever math is closest to 1.73T while being a multiple of 512 [16:01] you'd think the ubuntu installer would round it for you though [17:05] Hello all. So, I have a couple of odd issues with 18.04 FIPS to 20.04 FIPS. On 18.04 we installed Dovecot Ubuntu package from upstream as the 18.04 version was older and didn't have certain functionality we needed. When we did a do-release-upgrade, it apparently did not find an update and kept dovecot at the old version "dovecot-core/now 2:2.3.19-2+ubuntu18.04 amd64 [installed,local] [17:05] We manually ran apt-update on the dovecot packages and it then updated it to latest from the repos. dovecot-core/focal,now 2:2.3.19.1-2+ubuntu20.04 amd64 [installed] [17:06] so that's the first odd thing. [17:07] We found this out when we paniced Dovecot when enabling quotas. [17:07] Next, we found libgcrypt20 and libgcrypt20-hmac were not updated [17:07] apt list --upgradeable [17:07] Listing... Done [17:07] libgcrypt20-hmac/focal 1.8.5-5ubuntu1.fips.1.4 amd64 [upgradable from: 1.8.1-4ubuntu1.fips.2.5] [17:07] libgcrypt20/focal 1.8.5-5ubuntu1.fips.1.4 amd64 [upgradable from: 1.8.1-4ubuntu1.fips.2.5] [17:08] attempting to upgrade libgcrypt then threw this error "libgcrypt selftest: binary (0): No such file or directory (/lib/x86_64-linux-gnu/.libgcrypt.so.20.hmac)" [17:09] and then somehow libgcrypt20 and libgcrypt20-hmac files were removed and the initramfs script was removed also. [17:09] I manually copied the relevant package files from another 18.04FIPS>20.04FIPS system and got libgcrypt working again. [17:10] I saw something similar related to libgcrypt in 18.04>20.04 upgrades in this bug report but I am unable to access Bug 1944403. https://www.mail-archive.com/ubuntu-bugs@lists.ubuntu.com/msg5956327.html [17:10] any ideas? [17:26] samy1028b: it's probably worth a bug report against ubuntu-release-upgrader ; I don't understand the whole usrmerge end of things here :( but this feels like something the tooling should know how to handle [17:27] samy1028b: re: dovecot, I *think* third-party repos are disabled as part of the upgrade process. (I might be remebering something else, or something similar, etc. I don't do upgrades all that often and don't use third-party repos at all, so it's not something I see much) -- so that might be working as expected [17:46] sarnold: I'll open up a bug report on it. [17:47] Also, do you know why I can't seem to access Bug 1944403? Is it restricted from public view? [18:08] samy1028b: it is, and I don't know why; I've added a comment bugging the folks who set it private :) [18:08] sarnold: thank you.