Realize how how much they are supporting and storing.

Come back to the comments after.

Yes. This isn’t something you want your own machines to be doing if something else is already doing it.

So you think it just checks the target when you want?

It really shouldn’t have. It doesn’t make sense that all your other drives were still addressed except for this one.

Nvidia drivers work the same now as a few years ago.

If you don’t like it, migrate.

If you don’t mind it, keep it.

Your uplink capabilities are way different than your actuality. Get the service first, do some measurements, then start planning.

You seem pretty focused on reverse proxies for some reason, but that isn’t security. An alternative is a VPN into your network. Simple solution that solves all of your asks if you don’t need many people accessing your services.

The device names and aliases in /dev don’t just simply change between reboots. Something else happened here.

What are the path or IDs of the drives that are in there now under /dev/nvme*?

When you say “the drives were renamed”, do you mean you renamed them while the array was online? That sounds like what this means.

In that case, you can find out which drive is the problem, clear it, and repair the array. Should be pretty quick.

There are tons and tons. This is called “deduplication” or “dedupe”. Just so a quick search and find one that looks good to you.

Came here to say this.

WOW, you must be super special. Everyone else has issues: https://www.reddit.com/r/linuxquestions/comments/13k5xc6/why_does_ntfs_corrupt_so_much_more_on_linux/

It’s also a known tagged issue with that driver in the kernel mainttnotes, and a warning on every single distro I’ve ever used when attempting to format something with NTFS.

Lucky you.

NTFS will 100% get corrupted under Linux, and 150% with Samba involved.

What you’re talking about is a software solution, but the solutions you mention are not standalone software in the way you’re thinking.

Honestly, it sounds like you don’t want a NAS, you just want shared network storage. If that’s the case, make a Fat partition, share it windows, then go configure samba under the Linux side similarly, paying attention to map a user with a matching uid. There will be some wonk happening here and there with file permissions perhaps, but it will work for the most part.

The other options you mentioned are meant to control the entire host, but you may be ready to make that leap yet.

For minimal money, you could also try and get your hands on an older RPi (possibly for free, people just have them laying around), and attach your disks via USB to that, and then you have a basic, but dedicated NAS you can setup the way you like.

Settings

Your goal isn’t super clear from the post.

Are you asking how to host an OS on an NFS share?

Some states have open data. Unsure if it’s in Json though.

Also, this answer.

Yeah, so if you’re running rootless containers, they aren’t run by root, and for added security, you don’t want them run by your normal user because if they get broken, then they’d have access to what your user has access to. Just create another user that only runs containers, and doesn’t have access to your things or root.

Wireguard is a VPN, so that’s not going to help you much here unless you’re forwarding all your traffic through a remote server, in which case anyone gets in there will still be able to get your local machines. It’s another hop in the chain, but that’s about it.

If you want to be more on guard about reacting to attacks, or just bad traffic, you probably want something like Crowdsec. You’ll at least be able to detect and ban IPs probing your services. If that’s too much work, leverage OoenWRT reporting and some scripting to ban bad actors that probe your firewall and open ports. That’s a good first step.

If you’re concerned about the containers, consider using something more secure than dockerd. Podman rootless with a dedicated service user is a good start. Then maybe look at something more complex: Kata, gvisor, lxc…etc. The goal being sandboxing the containers more to prevent jailbreaks.