It’s a BE (backend) bug. Our instance admins need to update the BE to version 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 😒.