I was looking at doing something similar with my Asustor NAS. That is, supply the voltage, battery, charging circuit myself, and add one of those CH347 USB boards to provide I2C/GPIO etc and just have the charging circuit also provide a voltage good signal that software on the NAS could poll and use to shut down.
r00ty
joined 2 years ago
My understanding is that the only issues were the write hole on power loss for raid 5/6 and rebuild failures due to un-seen damage to surviving drives.
Issues with single drive rebuild failures should be largely mitigated by regular drive surface checks and scrubbing if the filesystem supports it. This should ensure that any single drive errors that might have been masked by raid are removed and all drives contain the correct data.
The write hole itself could be entirely mitigated since the OP is building their own system. What I mean by that is that they could include a "mini UPS" to keep 12v/5v up long enough to shut down gracefully in a power loss scenario (use a GPIO for "power good" signal). Now, back in the day we had raid controllers with battery backup to hold the cache memory contents and flush it to disk on regaining power. But, those became super rare quite some time ago now. Also, hardware raid was always a problem with getting a compatible replacement if the actual controller died.
Is there another issue with raid 5/6 that I'm not aware of?
Trinitycore has a guide https://trinitycore.info/ if you follow it properly it will result in a working server. Any time I've seen someone have a problem following it, they either missed a step by mistake, or tried to go off on a tangent, configuring it for their own needs during install/setup.
First make it work with the instructions, and once it is working, then tinker with it :P
It's more likely trinitycore (which forked from mangos quite some time ago). https://github.com/TrinityCore/TrinityCore/
Mangos do still have a Wrath server branch. But specifically for 3.3.5 trinitycore is more often used.
This was actually the story I had in mind when I wrote my comment. In my case, I'm using cloudflare for this mbin instance, another unrelated low traffic site, and R2 for the media on the instance. It's so small that it will never really escape their free tier.
But yeah, if you're doing something that is scaling up this is definitely something you need to be aware of.
There seems to be a line, so far as I can tell. If everything you need sits on the free tier, they're really good (well tbh their R2 storage is reasonably priced too). But once you stray into needing a paid tier, it apparently (I'm not there) quickly gets expensive as you're lured into every higher tiers.
But yes, in general I don't mind cloudflare so much and do use their free (and R2 paid) services.
It's good to see. The UK one is still ticking upward too (133.5k/100k). It's been an impressive last minute push.
Now, we wait and see I guess. I expect nothing useful to come from the UK one, but at least we force them to respond again. Even if it is the same response.
The EU one, I really do hope something comes of it.
This is my assumption too. It's disabled for me. I have no plans to change that.
I was going to say. The fediverse isn't an echo chamber. It's a series of echo chambers, some of which even talk to eachother. :P
Aha, I see. So you mean there should be a community for anonymous posts. I think it's not inherently supported with ActivityPub. But I guess someone could create a bot that all posts went through. However for very obvious reasons the community would need to be moderated VERY efficiently.
I think so. I would consider perhaps allowing a short time without power before doing that. To handle short cuts and brownouts.
So perhaps poll once per minute, if no power for more than 5 polls trigger a shutdown. Make sure you can provide power for at least twice as long as the grace period. You could be a bit more flash and measure the battery voltage and if it drops below a certain threshold send a more urgent shutdown on another gpio. But really if the batteries are good for 20mins+ then it should be quite safe to do it on a timer.
The logic could be a bit more nuanced, to handle multiple short power cuts in succession to shorten the grace period (since the batteries could be drained somewhat). But this is all icing on the cake I would say.