[02:29] I don't suppose anyone here has had spinrite not launch on one of their servers, after it actually booted into freeods? Tangentially on topic, because it's an ubuntu server ;) [02:29] It just needs help [02:31] spinrite? wow there's a name I haven't heard in ten years, give or take.. (in the sense of, "wow, there's aname I haven't heard of in ten years", at the time :) [02:32] Yeah, some dumbass used a laptop drive when he got this r610 in his basement, because he was so excited to set it up, and put in an SSD a few weeks later. All the data was moved over, just not the boot. [02:32] * kyle__ really hates that guy sometimes [02:33] sounds like someone you ought not let near your computers :) [02:33] * sarnold nods [02:33] Sometimes it feels that way. [02:35] I guess I'll let it sit overnight and see if it (spinrite) starts up. [02:35] Otherwise I know what I'm doing tomorrow after work :P [02:38] btw what's the point of spinrite in 2020? [02:40] It's a spinny drive that I put in there. Also the bulk-storage drives in my NAS box are spinny, because that's still the best bang for the buck storage wise. [02:40] ddrescue should do the same job [02:40] Work only buys spinners reluctantly any more, and I'm almost at that point at home. [02:40] but when you need a few dozen TB of space, they really are the cheapest way there :) [02:40] Also, I really enjoy the security-now podcast, so it's kindof like giving the old guy a donation. [02:41] but, like, what's the point of sipnrite? heh [02:41] morning RoyK :) [02:41] OK, really going to bed this time o7 night [02:41] gnight kyle__ [03:06] I have pfsense running as a VM on ubuntu server, with a NIC passed through, but connected to the host over a bridge. host can ping guest. I have a laptop plugged into a port on the NIC, and for testing I have allowed all traffic in firewall rules. laptop cannot ping the ubuntu host. Might I be missing something? not sure if it's a pfsense issue, [03:06] ubuntu issue, or user issue. [03:07] originally I was thinking, maybe it has to do with ip_forward, but that didn't seem to do anything. [03:11] sarnold: morning :) [03:12] in-place fixing of drives isn't really my cup of tea [03:19] I always thought of spinrite as a DOS FAT consistency thingy, so I'm surprised to hear of it again [08:05] Good morning === zyga_ is now known as zyga-mbp [14:17] I have unattended-upgrades to install security updates automatically, when I got to work this morning one of our servers were shutdown. It was terminated at 04 which is the same time I run [14:17] my automatic updates on... can anyone explain what the heck happened? I looked in the logs and I did not see it actually installed anything at 04 so am wondering if someone was pending from aa previous upgrade. [14:17] something was pending* [15:23] martin__: I beleive I've seen that happen once or twice, which is why I generally don't restart servers automatically, but rather schedule downtime for that to be done. [15:50] is seems kernel -4.15.0-109 problem since upgrade to to this kernel system in panic error and yesterday it was not booting at all [15:51] how do block kerenel -109 block for some days or block tilll i manaully update [16:11] i try to hold [16:18] what is latest stable version with 18.04 ? [16:19] can some one please confirm ? === kierank_ is now known as kierank === mwhahaha_ is now known as mwhahaha === mnasiadka_ is now known as mnasiadka === Triffid_Hunter_ is now known as Triffid_Hunter [17:22] Very baffled, I keep getting timeouts on file operations on a server but I can't seem to actually find anything throttling the io, or any errors that would indicate why suddenly things are failing :/ [17:24] The btrfs pool being used has user directories on it, so the big issue is email; Dovecot in particular seems to be having a lot of trouble (Postfix weirdly less so), the service won't even shut down although the log claims its been killed with signal 15. [17:25] All started when I applied updates to this 18.04 install and rebooted two days ago. [17:34] `kill -9`ing doesn't even seem to be able to remove the lingering dovecot processes . . . arghh [17:51] Linux hc-vubuntutest 4.15.0-109-generic #110-Ubuntu SMP Tue Jun 23 02:39:32 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [17:51] on 18.04 [17:51] No issues here [17:53] keithzg: Maybe sudo lsof|grep dovecot shows it busy in the middle of file operations of some sort which can't be closed [18:26] genii: Good point, I should have thought of that! And I did see some indications that that was the case, buried in the logs, with Dovecot complaining about `cannot append message to file /home/username/mailmirror: unable to lock for exclusive access: Resource temporarily unavailable`. Have since just rebooted the damn server, and since then it has worked fine, but the same sequence of events happened yesterday, so I bet I'll get another chance for such [18:26] introspection tomorrow . . . [18:27] Hard to meaningfully troubleshoot when everyone is calling and texting saying "everything is broken!", really quite distracting lol [18:32] keithzg: Maybe keep us posted, seems an interesting issue [18:35] genii: Shall definitely do . . . === halvors1 is now known as halvors [18:46] jamespage: regression testing passed on ussuri-proposed. I didn't promote any of your SRU packages though, will leave that to you. === halvors1 is now known as halvors