beginning this week’s reading:
You must log in or register to comment.
Comics… Equally enjoyable as they are frustrating (crossovers and reading orders make things unnecessarily complicated).
Other than that, pain and fatigue. Didn’t want this year to be like last year, but it seems many appointments are on the horizon.
Lots of Monster Hunter: Wilds. I’m at the point where I’m basically farming for dicerolls: Decorations, artian weapon materials.
I’m still only on chapter 3 I think? Haven’t played too much yet. Gotta go look up some tutorials on weapon combos and figure out how to organize my items and load outs.
I feel like I’m missing my attacks a lot more compared to MH World, but maybe I’m just really rusty haha
I’m missing a lot, too, but I chalked that up to the game being a little more lenient, thus giving me more room to freestyle instead of turtling.
I’ve played Gunlance since 4U, which has kept things relatively stable for me (aside from the occasional addition/removal of things like Blast Dash). I also picked up SnS this time around so I can take on group hunts with the Power of Friendship and Mushrooms.
Last week I released the blog post I mentioned previously. It’s now in Finnish and English.
I have an old netbook from 2011 that I have used as my home server since 2017. It has a 1 TB SSD, and for some time it had weird problems such as “Remounting filesystem read-only” and “EXT4-fs error”, usually leading to crashes. After rebooting, Ubuntu’s boot screen would not always appear. According to SMART, the drive was however all fine. At first I replaced the file system’s journal and ran fsck. That wasn’t enough, and the problems persisted. I was about to RMA the SSD, when I put Gparted Live on an USB stick and used that for fixing the file system. And it worked, now the home server has worked all fine for over three days!
Two thoughts in case unexplicable stuff happens again:
- SMART doesn’t detect all possible errors, especially not on SSDs. (It was originally designed as an early-warning system for mechanical failures on spinning rust drives, and later somewhat expanded.)
- A faulty RAM chip can cause all sorts of subtle (and not-so-subtle) mayhem but is often overlooked as a possible cause for disk troubles. If in doubt, MemTest86 is your friend!
I even ran MemTest86 and it showed things to be all fine. I recently bought new memory (2 GB) for the netbook.
