Sorry, I really haven’t a clue. I just know once in awhile it does work, but usually it fails for me.

Shouldn’t this all be handled automatically by the Debian installer though? It seems weird that I would ever have to run other tools just to install a brand new system.

I’m on Debian, they’ve been providing UEFI images for a number of years so everything should “just work”. In fact I have one server where things did just work and that’s the only system using UEFI. Two other servers of the same model and BIOS version completely failed after numerous attempts so I finally said screw it and just did a normal install.

I associate it with the fight I’ve had every single time I tried to use it. It’s never been a smooth process on any server I attempted to use it on. Usually I either run into problems with a system not wanting to properly boot the memory stick even with a full UEFI image flashed to it, or if I do get that to work I go through the whole installation process only to find the system unbootable for whatever reason. Eventually I just give up and do a standard installation because why should I have to work this hard to put an OS on a machine?

Ah thank you, that DOES make more sense.

I’m having a hard time understanding this article. They say the Teslas have the highest rating of deadly accidents, but then go on to say Tesla ranked #6 on the list of fatalities, then once again stated Tesla was the worst. So what happened to the other five vehicles that had a higher fatality rating?

If they switched to linux the ice cream would be colder and even smoother.

Sounds like a great sales pitch… “PoS machines, but unlike Windows-based devices ours continue to work after the first six months!”

Funny, when I think of Windows, reliability and stability are the last things on my mind. I mean, if they could build a reliable release then why isn’t that shipped with all computers? You know, like with linux, the stable version is also the current release. Basically your description makes it sound like what’s really making Windows so unreliable is all the crapware that Microsoft forces down your throat.

Hard to say for sure. He’s on Facebook so I don’t have a way to see what he posts, but my wife still has an account there and said he’s in some of the same groups as her. She’s pretty aware of what he’s posting and they’ve actually had conversations in person about the whole immigration thing. The rest… yeah I just don’t know.

This started on Wednesday, almost immediately after Trump’s victory was announced. By Friday it was already being reported in grade schools because asshole parents enjoy raising asshole sons, and Trump tells people that it’s ok to be the absolute worst human being they can be.

I have a friend who is a hard Republican. We generally don’t talk politics, but after this started last week he was posting things online being offensive towards women and POC (and the whole “illegals took my job and healthcare”) so I finally had to call him out. His response was basically that he wasn’t aware of any increased discrimination happening against women, therefore he didn’t believe it was happening. I’ve known the guy for 40 years but this may be the thing that breaks our friendship. He claims to be an advocate for people’s rights yet he is painfully unaware of the world around him.

Quite interesting advocating from 1st Amendment rights, while also also deleting content that he personally doesn’t like.

That’s a shame since literally everyone should distrust Edge, given Microsoft’s history with browsers (and everything else). I don’t think anyone matches Microsoft’s caviler attitude of “We know there are hundreds of gaping security holes that allow attackers to take full admin control of your computer, but we’re just going to mark those bugs as will-not-fix and blame the users when something goes wrong.”

Yeah I figured there would be multiple answers for you. Just keep in mind that you DO want to get it fixed at some point to use the disk id instead of the local device name. That will allow you to change hardware or move the whole array to another computer.

Are you sure about that? Ever hear about this supposed predictable network names in recent linux versions? Yeah those can change too. I was trying to set up a new firewall with two internal NICs plus a 4-port card, and they kept moving around. I finally figured out that if I cold-booted the NICs would come up in one order, and if I warm-booted they would come up in a completely different order (like the ports on the card would reverse which order they were detected). This was completely the fault of systemd because when I installed an older linux and used udev to map the ports, it worked exactly as predicted. These days I trust nothing.

OP – if your array is in good condition (and it looks like it is) you have an option to replace drives one by one, but this will take some time (probably over a period of days). The idea is to remove a disk from the pool by its old name, then re-add the disk under the corrected name, wait for the pool to rebuild, then do the process again with the next drive. Double-check, but I think this is the proper procedure…

zpool offline poolname /dev/nvme1n1p1

zpool replace poolname /dev/nvme1n1p1 /dev/disk/by-id/drivename

Check zpool status to confirm when the drive is done rebuilding under the new name, then move on to the next drive. This is the process I use when replacing a failed drive in a pool, and since that one drive is technically in a failed state right now, this same process should work for you to transfer over to the safe names. Keep in mind that this will probably put a lot of strain on your drives since the contents have to be rebuilt (although there is a small possibility zfs may recognize the drive contents and just start working immediately?), so be prepared in case a drive does actually fail during the process.

That is definitely true of zfs as well. In fact I have never seen a guide which suggests anything other than using the names found under /dev/disk/by-id/ or /dev/disk/by-id/uuid and that is to prevent this very problem. If the proper convention is used then you can plug the drives in through any available interface, in any order, and zfs will easily re-assemble the pool at boot.

So now this begs the question… is proxmox using some insane configuration to create drive clusters using the name they happen to boot up with???

One promising item I found are some json files from Reuters…

This one provides info on the candidates and the key for state ID’s: https://graphics.thomsonreuters.com/data/2024/us-elections/production/events/20241105/metadata.json

This one seems like it will provide the ballot counts(0) and possibly any declared winners(1): https://graphics.thomsonreuters.com/data/2024/us-elections/production/events/20241105/summary-votes/president.json

Of course I won’t know anything for sure until tomorrow evening when states start releasing their counts, but I went ahead and wrote up some code to use the files. It’s something at least, and the Reuters data should be fairly timely. I hope to play around with the collected info in real time, then maybe next election I can re-use the same code.

Yeah I found the same on the AP data. I also found that reddit thread, but haven’t been able to find a valid URL for this year’s election. Maybe they don’t make it available until voting starts?

Hmm good idea, I’ll take a look into that!