the problem here does not originate in zfs, this is a hardware failure due to a poorly supported SoC (vendor says PCIe works ‘normally’ since kernel 7.1, this system ran 6.19) and bad electricity supply

do you ever get a new shiny thing and it looks like it works very nice and coherently and then you dig a bit deeper and realize that it is just a bunch of semi-broken shit held together by glue and duct tape? that’s the state of android, that is nicely obscured on pixels by google customizations

haha, no, depending on your use case zfs is mostly set and forget, you just have to get a set of sane defaults, which, at least for me, is way easier and saner than stuff like btrfs. Arch wiki is a good source for that.

scrub is a command that reads data from disks and verifies checksums, it can automatically heal the corrupt data if some redundancy is available. 0 bytes repaired means nothing was repaired, 5 errors mean that there are 5 instances where the recalculated checksums of data did not match the expected values that were calculated when initially written. Normally the command would output ‘scrub repaired 0B with 0 errors’, that’s how you know that the pool is healthy.

shprutzling the cache vdevs sideways is generally required only for obscure optimizations, I’ve never seen a case where a wrong setting would lead to data loss.

The gotchas come from a single thing: the stupid CDDL licence, which is not compatible with GPL. That means that zfs is not included in linux kernel and most of the normal linux userspace filesystem stuff do not work with zfs.

Also, keep in mind that zfs is generally almost impossible to fuck up, what I’ve done here is a result of extreme dedication and like 8 years of experience.

I’ve seen a calculation somewhere for drive speed, size and scrub frequency where optimal number of extra drives was calculated. On fast storage and with weekly scrubs one extra drive should be mostly fine.

My philosophy is any raid is not really a data contingency solution - it just saves some time when the drive fails.

that’s no fun. also, it turned out that this is not a disk error, the zfs metadata got corrupted and now I get a panic when trying to mount this.

This is raidz1. Three 4TB NVME drives. I’ve built this machine as the primary server for services like immich as a fun project that enables me to say that my photo service runs faster than all the commercial stuff and is on ARM64. The downside is that the SoC is not supported by upstream very well so vendor patches had to be applied and there was some instability between that and my shitty electricity supply.

I feel very sorry for you. I have the same problem (panic on mount) with this one, but at least it works when mounting read-only. I’ve been moving data with zfs send the entire day

my achievement here is that this is a proper raidz setup with multiple disks and ecc ram

also, machines wipe themselves at each boot! service state data is distributed via zfs send! zfs that actually works!

I have a fucking thinkpad that does not follow the USB PD spec!

The thing has only type-c ports, the thing is relatively recent (2023), the thing accepts 140W via type-c, I never bothered to check the actual specs and assumed PD 3.1

Turned out that no, this is not PD, this works only via proprietary power brick that outputs 20v@6.75A, that I didn’t get as I already have a bajilion of PD 3.0/3.1 power supplies at home.

I’ve been hosting grist for a while and it is quite nice. Wasn’t able to move all the stuff from classic spreadsheets though

After about a thousand commits in my config I no longer know how to do stuff the normal way. A few days ago I spent 20 minutes trying to figure out how to run python with modules without resorting to shell.nix

But are you truly using nixos, if you don’t have a swarm of 10+ machines that do distributed builds?Can you really say that your system is deployable, if you never tested it on an obscure ARM board and a laptop from 2005?

That’s strange - vanilla gnome should start in overview mode and dash is populated with gnome apps by default. Aside from that, there’s a button in the upper left corner that goes into overview if you press it.

Maybe your install did get corrupted, because literally my grandma could figure it out. On the other hand, most mainstream distros ship with dash to dock and discoverability must be the reason.

deleted by creator

Complex things that someone has already done are infinitely easier in nixos - stuff like having zfs as root filesystem is literally two lines in the config (and the magic is that it is very, very hard to break).

Complex things that are your own edge case will make you want to pull your hair out - I wanted to run immich on a raspberry pi 5 with native 16k page size, long story short, I still don’t have immich.

On the other hand, if by “normie” you mean “running a browser and some flatpaks”, nixos is likely the best distro that will work right out of the box - the graphical installer will generate a good config, the out of the box hardware support is the best in my experience, breakage is almost impossible. Automatic updates will not work though and there’s no gui that will prompt you to do so at all.

Who cares if it breaks? You can always just boot a previous generation! Need to rebuild without the breakage? You surely must now how to add a package from an earlier commit via flakes by now, right?

I distinctly remember seeing sprites about 10 years ago, where the enemies were eco protesters. The biters were protesters with signs, the spitters were protesters with Molotov cocktails, the nests were tent encampments.

I think I did not imagine that and it seems to me that the enemies’ mechanics make a lot more sense if they were people protesting.

Does anyone know what I’m talking about? Was this in the early builds or was that a mod?

P.S: the goal of Factorio is clearly to build a large enough factory to cripple your hardware, then apply the gained skills in a real factory to be able to buy new hardware, then get fired due to your addiction, freeing up time to build further

Well, if you can’t figure out how to integrate the flake in 30 seconds by month 6, you clearly have a skill issue. Or a “sleeping at night instead of writing nix” issue. Better use a noob-friendly distro like arch.

Seriously though, despite all the flaws, there is no other packaging system where I can as painlessly use random forks of packages. I absolutely love how I’m able to run gnome-mobile on my x64 tablet. True to the NixOS way, I found the overlay on someone’s GitHub, there were only the files, no further instructions.

I also have a USB with live debian at all times, because you never know when you stumble upon a thing that just can’t work with NixOS

Who needs documentation? The code is self-documenting! The entire thing’s on GitHub, just check the issues to figure out what’s going on! Didn’t work? Sorry, the thing got broke a few months ago. Just go through the commit history and I’m sure you’ll be up and running in no time!

I’ve also made a module that fixes your specific issue and uploaded it to my self hosted gitlab instance. The server is down right now? Well, isn’t that better? Now you can make the thing yourself! Remember to upload your thing to your GitHub, name it something like “nixos” and never mention it anywhere.