It’s a BE (backend) bug, so it’s not Jerboa related. Our instance admins have to update the BE to 0.18.4.
It’s a BE (backend) bug, so it’s not Jerboa related. Our instance admins have to update the BE to 0.18.4.
No need to create an issue, it’s a BE (backend) bug, fixed in 0.18.4, but our instance admins haven’t update to the latest BE version 🤷.
It’s not a Jerboa bug, it’s a BE bug, confirmed a few posts below. Lemmy.ml should be on 0.18.4, so should lemmy.dbzer0.com.
Yeah, that should be super easy, since In don’t speak any German 😒.
Nevertheless, I’ll try and see if they reply.
BE of my instance: 0.18.3.
0.0.42… that’s the version in the About section.
BE of my instance?
I’ll create one 👍. Just need more confirmations, a few more replies should do it.
Might be a SAS driver issue. Have you checked if the drives show up on a live distro, something more current, like let’s say Void or anything that has a 6.x kernel?
I’ve had issues like this with older Marvel SCSI controllers, some of them don’t have open source drivers for Linux, and the ones provided by the manufacturer (if there are any) are so old that you’d have to be runnig kernel 2.x in order for them to work. I just gave up in the end, disabled the SCSI controller in BIOS and just used the rigs on IDE/SATA.
I was not about to RCE the binary if I can get a working solution from googling 😒.
Discovery is never gonna work on the fediverse. Info is too scattered. Sure, large servers will get discovered, but not smaller ones. They come and go, URLs change… it’s a mess.
You delete comments here as well?
Sometimes, there is no documentation for the problem you’re having, especially if you’re dealing with proprietery solutions.
Oh, yeah, makes sence in that case. Thought it was some other general information, like troubleshooting info.
I can get behind stuff like this, sure, but not with stuff like I posted 😒. There was valuable info there that could’ve solved my problem in an instant, but I just had to go the long way around 😒.
I told the 2 ladies “please move away, I need to leave” and they said “do you mind, we’re talking 🤨”… to which I just pulled out my phone, dialed 911 and started explaining how 2 women aren’t letting me leave the market… they got pissed as hell and other people shoved them over to the side, said not to make a fuss. I left and told the operator that the problem has been resolved, to not send units over.
I really have no idea what’s wrong with some people…
Yet they still need to catch up on the latest gossip about their kids or the new newigbour who someone saw naked doing OF stuff in front of a camera 😒… like who gives AF, it’s their business, not mine, why would would anyone care about someone else’s business is beyond me.
Could I ask why you would delete your own comments after a week of two?
I managed to get pointed in the right direction, but no thanks to that user 😒.
Doesn’t matter, I have no idea who the user is.
I did… zero replies 😒. And I asked on reddit as well. Didn’t get an exact answer, but at least I got pointed in the right direction.
It’s a BE (backend) bug. Our instance admins need to update the BE to version 0.18.4.