[01:50] good morning [06:55] good morning [07:07] Morning! [07:10] hi marcoagpinto [07:10] :) [07:17] how are you doing? [07:20] ducasse: fine, thanks, and you? [07:20] (except for the brain toasted of the supermarket) [07:20] i'm ok, thanks, nice and quiet morning [07:20] having a vape and drinking cola [07:21] I am drinking cola too [07:21] :) [07:21] i'm sure you are :-) [07:24] :p === Awoobis is now known as `Awoobis` === `Awoobis` is now known as Awoobis [20:08] UWN: Issue704 is on the streets: https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue704 :D [20:10] yay [20:25] tomreyn: that quackgver has done this before; won't share reports, and turns out likely installed outside of the package system [20:25] TJ-: thanks. [20:26] I've asked what this "pm2" is since apt-file search bin/pm2 doesn't reveal it in any package, but not got a response [20:28] it'll be some third party package, i guess [20:29] probably https://pm2.keymetrics.io/ [20:31] there's "with debian, use the install script" at https://pm2.io/docs/runtime/guide/installation/ [20:32] got hit by a lovely bug in initramfs-tools/lvm2 last week. We were hit with a 9 hour power failure which took the server down. On reboot it couldn't mount 3 LVM mirror LVs, /var/ and /home/ being 2, so system couldn't boot, and couldn't get them to start manually from busybox either. both base devices (nvme and hdd) were LUKS > LVM and also the HDD's LVM LVs were orphaned (not parented to [20:32] the LUKS container the LVM is in) [20:33] uuh ugly [20:33] Eventually, after a lot of digging, figured it out. these 3 LV mirrors use dm-cache's writecache mode so the NVME caches writes [20:33] but the tooling doesn't figure out that dm-writecache.ko module needs including in the initrd [20:34] the weirdest part of was lsblk showing the meta and data component LVs orphaned from the LUKS container [20:37] tomreyn: that user has just asked the very same questions in Linode support channel on OFTC [20:38] well, i also lost interest in helping there, so that's fine with me. [20:38] the dm-writecache.ko not in initrd issue is probably because you're one of the very few who don't include=most [20:39] which is good pioneer work, kind of, but probably makes you run into such issues, i guess [20:39] no, that was with -most [20:39] I tested [20:39] oh weird [20:40] the problem is the module diving that figures out what is required doesn't determine that in the lvm2 /usr/share/initramfs-tools/hooks/ [20:40] :-/ [20:42] oof, my eyes keep shutting, i better head to bed early. ttyl. [20:42] after the event, the only way I could figure out how to know is "dmsetup targets" [20:42] night === not_phunyguy is now known as phunyguy