libera/#devuan/ Wednesday, 2022-07-13

systemdletestill having fun here.  I wonder if the bad memory caused some permanent disk issues.04:51
systemdleteat any rate, I am getting a ton of hash mismatches now.04:51
systemdleteI created a brand new VM and running update/upgrade.  But it is complaining about all these hash mismatches.04:51
systemdletePlus, comcast seems to be having a bad day or something.  It's been up and down several times now.04:52
systemdletere-running apt upgrade seems to help, but I am not sure if this should go unchecked.  I mean, isn't a hash mismatch a problem?  Why am I getting those?  How do I diagnose the problem?04:59
systemdletethe two packages with the hash mismatch were linux-image and firefox-esr05:00
systemdletethey downloaded cleanly this time05:00
gnarfacewell, with or without bad ram there are several cases where you can plausibly get filesystem corruption05:06
gnarfacenot to mention just having a bad harddrive too...05:06
systemdleteI've checked the logs and see no indicators of bad drives05:07
systemdleteI do have some spare drives on hand just in case05:07
gnarfaceone way to test; tar the entire contents of the filesystem up to some other known-good (freshly formatted with the current kernel) backup drive, then freshly format the current suspect drive (with the current kernel; in some cases this part may be important) then untar the backup back to it... if the errors go away then your filesystem was corrupt and the drive is physically fine05:08
systemdleteI am looking at memory (my original order did not go through)05:08
systemdleteIt seems that ECC memory is not generally available for consumer mainboards05:09
gnarfaceseen ext4 corruption based on switching kernels/tools unluckily05:09
systemdleteon switching kernels?05:09
systemdletereally?05:09
gnarfaceyea, ext4 known issue sometime around the wheezy/jessie or jessie/ascii changeover, i forget which05:09
systemdleteoh05:09
systemdletenot recently though?05:09
gnarfacei don't think so, but i kinda stopped using ext4 after that05:10
systemdleteEverything seemed to be ok until I rebooted from the -14 to the -16 kernel05:10
gnarfacesomewhat after it, it was corrupting regularly on a slow crappy SD card i had, and i was told since that bug had been fixed it MUST be a bad SD card, but then i switched the filesystem on the SD card to something else and the problem stopped happening, so i'm still blaming ext4 for that too05:11
systemdletesure05:11
gnarfacebut that was also not recently05:11
systemdleteI'd almost pay for a mainboard supporting ECC if I could find one05:11
systemdleteI think that would obviate some of these problems, though not entirely of course05:11
systemdletebut that's only if someone can convince me it is really worth it05:12
systemdleteIf this is too theoretical, we can skip this, but if there is a decent chance of heading off a good deal of problems, I might be interested.05:14
systemdletegnarface:  What about the CPU?05:14
systemdleteI've got a fx8350 (8 cores) and I've got some spares in case that part breaks.05:14
systemdleteI know that some time soon, I will need to "ryzen up" but for now these have been satisfactory05:15
gnarfaceyou're wondering if a bad cpu could corrupt the filesystem? i suppose so, but if you just found bad ram i'd blame that first05:52
gnarfaceif you're on a AMD board it should already support ECC, afaik all the AMD boards do stock, that's something only Intel charges extra fo05:53
gnarfacefor*05:53
gnarfacei'm not sure what the price on ECC ram is these days though, has been a while since i bought it but i think then it was something like 250% of the price of regular ram?05:54
gnarfacei would just first start by pulling the bad ram stick from the machine and doing a drive re-format05:56
___usedAre we updated? X.org? https://www.theregister.com/2022/07/13/xorg_servers_updated/19:54
___usedI see nothing in aptitude.19:55
ltsNot yet19:55

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!