I’m not sure why SHR would require any file system, it’s an abstraction that sits below that layer.

I don’t have a Synology, but I implemented SHR manually using mdadm and LVM. If you have a RAID 1 array you can just add disks to it and “upgrade” it to the next tier of your choice. So with 3 disks you could just go to RAID 5 and that chunk would now become RAID 5.

It wouldn’t be merged with any additional chunks directly. Rather, you’d use LVM to create a volume group with each chunk added (each chunk world be formatted into a PV). From that you would carve out your volumes and then your file systems on top of that.

This is a pretty simple layout and I imagine Synology is pretty close to this.

The best way, I found to do this is to actually first partition your drives into 2-4TB chunks. Each of these partitions is then added to a RAID array, minimizing waste if you have mixed size drives. e.g. with three disks the first partitions are grouped into one raid array (chunk) and then the second partition of each disk is grouped into the next array, etc.

So, in your case, I suspect the Synology created a 1TB partition on each of your 1TB drives. If you replace 2 of those, Synology would create 1TB partitions on the new drives that match the existing raw disk size. It would then create a new RAID 1 array using the 3tb of additional space that’s sitting on new 3tb partitions. LVM would then add this chunk to your volume(s).

Of course, that’s just my guess based on research I did a while ago to build my own array. Check out the Synology RAID calculator. It’ll give you some ideas about this, too.

“But the breakthrough will come just as soon as the chips no one can make are delivered.”

Probably.

It’s about control. And monopolies love control (governments, too). If we let them, they’ll take it and then we’re screwed.

It’s probably going to move to hardware attestation similar to what Android and iOS are doing. This may or may not be a good thing.

Give me a free car and I’ll test it out with this “service”. I’m not buying a car that advertises to me.

They made metric paper. Time to make metric phones.

Poachers. Poachers are next.

Also check hardware support.

If the timeline is long enough then it’s always worth the refactor.

deleted by creator

Back of a cell phone won’t work because people put those into bulky cases.

Right. I forgot that browsers have the roots built in. Thanks!

Do they though? If you’re going to forge one cert why not forge the whole chain?

Aren’t they a MITM here? Can’t they easily forge certs for the domain name of their fake resolvers since they intercept and resolve your DNS requests?

Well, that’s the thing. I’ve seen many instances where the DoH field is required to be a FQDN, not an IP. This always struck me as strange, but I didn’t think much on it until recently.

With DoH, the first request to find the https DNS resolver itself is unencrypted rendering it subject to hijacking.

Correct me if I’m wrong, but that’s how I understand it.

Curious how UA is playing nicely with CN lately.

There are a few voices included with pied which is why I suggested it.

You don’t want random because that’s easy to detect. You want to fuck up the ML so you need to be more subtle like scrambling a few words or replacing certain nouns or logical connections in ways that are hard to differentiate from regular edits.