Spyke

Replies

Comment on

fediverse soon

Reply in thread

Even more than defederating, it's in the hands of users. If people were to flood in from somewhere with bad intentions, it would likely be from one or two servers. At that point, just block those servers/communities from your view and continue about your day

Comment on

Determine shutdown cause in OPNSense

Reply in thread

Final Update: it's the hardware, I think it was overheating in general, but also the SSD seems to have been dying and the ram wasn't particularly reliable, possibly due to the heat.

Good lesson not to buy the cheapest thing from AliExpress! My new box is working great.

games

Comment on

Something about The Finals

Reply in thread

Possibly, but more likely the computer was just in need of some cleaning.

My friend plays Helldivers 2 on his laptop with integrated graphics on medium and hits 30fps. Any CPU from the last 8 years should be enough.

For the finals, yeah maybe you need something more powerful than that, but not by much. A 2070 is a fantastic GPU, it would be pretty weird to have a GPU from 2018 but a CPU from way earlier.

Comment on

Determine shutdown cause

UPDATE: It crashed again today, and I was able to pull some logs and check the temperature at the time of the crash. (91 degrees which dropped to 71 degrees right before crashing?

From system log

<13>1 2024-03-13T18:30:44-04:00 OPNsense.my.home opnsense 44846 - [meta sequenceId="1192"] /usr/local/etc/rc.newwanipv6: No IP change detected (current: IPV6ADDRESSREDACTED, interface: wan)
<13>1 2024-03-13T18:30:53-04:00 OPNsense.my.home opnsense 60522 - [meta sequenceId="1193"] /usr/local/etc/rc.newwanipv6: No IP change detected (current: IPV6ADDRESSREDACTED, interface: wan)
<45>1 2024-03-13T22:12:44-04:00 OPNsense.my.home syslog-ng 10182 - [meta sequenceId="1"] syslog-ng starting up; version='4.6.0'
<13>1 2024-03-13T22:12:45-04:00 OPNsense.my.home kernel - - [meta sequenceId="2"] ---<<BOOT>>---
<13>1 2024-03-13T22:12:45-04:00 OPNsense.my.home kernel - - [meta sequenceId="138"] WARNING: / was not properly dismounted

From dmesg

arp: 192.168.1.61 moved from someMAC to anotherMAC on igc1
arp: 192.168.1.61 moved from anotherMAC to someMAC on igc1
WARNING: / was not properly dismounted
WARNING: /: mount pending error: blocks 40 files 4

I mean, I'm not saying that errors on the drive are the CAUSE of the problem, more likely a symptom, but it does look like it just straight up crashed, right?