Good advice. One should always test, for correctness, not just infer.

I would watch it.

My guess as a Linux admin in IT.

I understand the fix takes ~5 minutes per system, must be done in person, and cannot be farmed out to users.

There are likely conversations about alternatives or mitigations to/for crowdstrike.

Most things were likely fixed yesterday. (Depending on staffing levels.) Complications could go on for a week. Fallout of various sorts for a month.

Lawsuits, disaster planning, cyberattacks (targeting crowdstrike companies and those that hastily stopped using it) will go on for months and years.

The next crowdstrike mistake could happen at any time…

With 20 TB drives, I would have concerns about a drive failure during a rebuild. I suggest at least 3 drives and a config that can handle 2 failures.

Unless everything is replaceable.

“Easier” and “simpler” are in the eye of the beholder.

A different way to approach it is to limit the failure domains. If this breaks how sad are you?

I would separate storage from the rest. Networking stuff together may be fine. Home assistant depends on how dependent on it your household is.

I have not had an issue mixing and matching drives in a hardware or software RAID. Just needs to be at least as big as the previous.

I have had issues with non-vendor drives in Dell and/or HP systems.

(I am a pro, but not your pro.)

Zombie processes are hilarious. They are the unkillable package delivery person of the Linux system. They have some data that must be delivered before they can die. Before they are allowed to die.

Sometimes just listening to them is all they want. (Strace or redirect their output anywhere.)

Sometimes, the whole village has to burn. (Reboot)

Yes! It is great.

Any more I reencode for local streaming to my TV.

This is great! No better way to demonstrate how perfect Debian is! Debian for the win!

Also do it on 4/20.

… Not a drop of water?

The slowness is on purpose.

(OP may know, but I don’t know if everyone does.)

Edit: /u/getaway@lemmynsfw.com is picking up what I was putting down.

There is a fork of Debian without SystemD. https://www.devuan.org/

From the prequel with his first wife. Really informs the character’s backstory.

Have you tried a restore? A non-differential smap snapshot should be fine, but differential snapshots would make a restore difficult to impossible.

A zfssend and zfsrestore with a differential snapshot would be more traditional. If one put mbuffer in the middle, it would even be fast.

Kinda related: what if I install something like Debian/Ubuntu on it? Can I still use the NAS hardware in the same way?

This question confuses me. Debian and Ubuntu can be setup to be NASes.

NAS is a description of a mid-level function that various software provide a part of.

Various file systems and volume managers can provide snapshots and rollbacks. To aid your research LVM, ZFS, and many others support snapshots.

There are various ways to then expose the formatted space to the network. To aid research NFS, SMB, and iSCSI are options.

Anyway, I hope this is helpful to someone.

I wonder if the specifics of the hack would make backing up elsewhere fail. Possibly by spreading the hack to new machines.

In any case, testing backups is important.

Also consider rubber feet.

Any chance of finding the source of the water and redirecting it?

Does the sound correspond to the power draw?