FYI, if you go to "Account Settings" and uncheck "Show Read Posts", this should automatically hide all posts that you open, up vote, or down vote.

I understand and agree though that having the ability to split that into separate options would be nice. But this might help you until they possibly add that option later. This is also tied to your account and not just the app, which is nice if you use Lemmy from multiple devices.

Currently though, I and several others are having issues where the last update appears to have broken that feature. I'm not sure if the issue is instance specific, (lemm.ee) or more broad.

Thank you for responding and providing the link and info. The top comment in that reddit post has the same link I posted above.

For the

zpool import // find the ID of the NVME pool

How did you find the ID of the NVME pool? I think is part of the problem I have where I see multiple partitions and not entirely sure which is the "boot" partition I should be pointing to. I think in your case, you're pointing to the "data" partition, but this might help me eliminate one of my options.

I'm also not sure how the raid1 plays into things since it seems like both physical drives seem to have the same partitions. Not sure if I can just point to one of the "boot" partitions on one of the drives and it'll find it's partner when it starts booting?

What were the issues you had with Clover in particular? I'd be interested to hear since I'm trying to head down that path myself.

For your "remap" can you explain what you did/have an example? I think this might give me the knowledge I'm lacking since I think part of my problem is not understanding which partition/PARTUUID is the Proxmox boot/what I should point Clover at.

Prior to doing the Proxmox install, and prior to the PCIe bifurcation, I still was unable to see the drives directly in iDRAC/bios. What I've read online is Dell does this for "reasons" and they happen to sell an add-on card to let you directly access NVMe from PCIe.

While I'm not ruling out the ZFS mirror issue, I don't think it's the cause of my problem considering both Clover and the Proxmox install debug can see the drives/partitions. I just don't understand partition/device/boot structures and processes enough to make sense of what I'm seeing in the blkid/preboot results.

Trying to find information about it online just gets me bad guides about making partitions. The Linux docs for blkid and fdisk also don't seem to have the explanation of the results, just the arguments for the commands.

The server has 24x 2.5" bays. I have an old SSD drive that I figure I could use as a last resort to be the Proxmox boot drive and then just use the NVMe's as storage.

I was just hoping to have the Proxmox install/configuration in the NVMe RAID1 just for some minor safety in case a drive dies. From what I've read, this should be possible. I'm just lacking the knowledge to know what I've done wrong. (Mostly my lack of understanding the blkid results.)

The original plan is to use an SD card with Clover in read-only mode to bootload Proxmox running on the NVMe drives. (Read-only to prevent frying the SD card) This server has a built in SD Card slot Dell calls "vFlash" that you can actually remotely partition and configure. That's where I was going to put the final configuration of Clover.

How fast/often is Proxmox writing logging? It's concerning that you say you had this fry some NVMes since that's what I'm trying to do here. Is this a setting that you can adjust?

From what I've read online, Dell does something similar. There's some sort of card/add-on that can enable directly seeing and booting from PCIe but they are costly.

This server has the internal USB and a build in SD slot accessible from the rear. (There's also a dual card option like you mention for redundancy.)

My plan was to get Clover working with USB, then use the vFlash SD slot to hold the Clover bootloader in read-only mode. This would hopefully prevent the SD card from dying quickly.

Any way you could update/create your own drawing with what you mean? (Bad paint drawings are acceptable!)

I ask because I am curious if I am subject to the same problem. I'm not the most networking savvy so I need the extra help/explanation and maybe the drawing will help others.

Yeah, for anyone that gets the 502 gateway error. That means the instance was down when it tried to login/didn't respond. I'm going to revisit this part of the code later and see if I can fix/handle that happening so it at least goes through with the rest of the accounts. If it happens to you, just run it again and hopefully you'll get through at least once.

Subsequent runs actually hit the servers with less requests since you can pull most of the info you need with the initial site response and I check that before making any needed requests.

Also, someone else mentioned they had a problem with the none type thing. I'm using Python 3.11 and forgot to specify that. I'll add it to the readme when I get a chance.