I'm not sure how to get the N from session history, nor how to check my session history..
journalctl --list-boots will list all sessions stored in the journal.
The output is from yesterday, when the device stopped working correctly.
I'm not familiar with linux kernel, but I can see there is definitely something wrong...
The HDD (old) is attached to a USB hub (new), I tried switching port of the hub but the same issue happened again, if I try to mount it with sudo mount /mnt/2tb, it says it is already mounted:
Those messages tell you what's happening, there's an unrecoverable error on the USB bus connecting the hard drive which is causing filesystem errors when writes fail. Diagnose that, lose the hub first and directly connect the drive to the pi, then try replacing the cable that attaches the drive if the error still occurs. I'd also check with people in the rpi community in case there are any known issues with USB on your model. There may be some pi specific USB firmware things you can do to increase reliability.
You can also try disabling UASP for the drive in case BOT transfer somehow stabilizes the connection. You'll lose performance but that helps with some USB storage bridges.
Some USB storage bridges are just unreliable under Linux and crash under load, your last option is to buy another drive enclosure that's tested and known to work correctly. I went through like 5 USB/NVMe enclosures looking for one that worked properly, that whole space is a compatibility mess.
Wow. It sure is a good thing we still have domestic products that can compete with all of the imported goods from these major trade partners ...right? Right?
Bluesky has exactly the same monetization and profitability issues twitter did, if anyone tries to tell you differently they're lying. Sooner or later Bluesky will fatten a sufficient crop of highly engaged users and run out of venture capital runway and be forced to look for someone to buy the platform. There's no way around this.
We need to start encouraging policies like reward bounties for exposing corruption. Know someone who's breaking the law to defraud the government? Expose them and get 5% of the money recovered after a successful conviction.
Manjaro manages to do just about everything wrong for one reason or another. They're trying to be the Canonical of the Arch ecosystem and they're not even close to competent enough to pull it off.
I'm sure they'll find some way to DDOS something with their own telemetry sooner or later.
The conservative media machine has been splitting wedges between groups basically forever, it's a convenient way to pit people against each other.
The DNC, in their infinite wisdom, took that political landscape and instead of bringing everyone together in a big tent decided to pick out specific identity groups to pander to and drove the original wedges clean through.
I'm almost convinced the DNC wants to lose at this point, they seem pretty content with the position of professional minority opposition - it's a convenient place to be if you want to fundraise endlessly.
It would be nice if instances automatically maintained a new and low connection count user feed so that people could browse it occasionally and help people find others to connect with.
That could be done either as part of the instance software or via a bot that runs through the instance user list and updates the feed every so often.
It's ridiculous that these things even need to be pointed out. The DNC is packed full of highly educated high income people who have no fucking idea what the average person's life is like and it shows in their priorities.
They need to drop their focus on identity pandering and neoliberal corporate blood sucking if they want any hope in hell of an EC win. All the slick consultants in the world won't convince middle America to vote for more business as usual.
journalctl --list-bootswill list all sessions stored in the journal.Those messages tell you what's happening, there's an unrecoverable error on the USB bus connecting the hard drive which is causing filesystem errors when writes fail. Diagnose that, lose the hub first and directly connect the drive to the pi, then try replacing the cable that attaches the drive if the error still occurs. I'd also check with people in the rpi community in case there are any known issues with USB on your model. There may be some pi specific USB firmware things you can do to increase reliability.
You can also try disabling UASP for the drive in case BOT transfer somehow stabilizes the connection. You'll lose performance but that helps with some USB storage bridges.
Some USB storage bridges are just unreliable under Linux and crash under load, your last option is to buy another drive enclosure that's tested and known to work correctly. I went through like 5 USB/NVMe enclosures looking for one that worked properly, that whole space is a compatibility mess.