![](https://aussie.zone/pictrs/image/36bb602f-fa88-462c-886c-437bcb769a43.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
Nope. You do not need physical access for it, just root access. and you HW is compromised with only means to recover it is SPI flashing of CPU.
Nope. You do not need physical access for it, just root access. and you HW is compromised with only means to recover it is SPI flashing of CPU.
3600 was released in 2019. And it they was making it for at least 2 years.
You need to be a root to exploit it, but if it get exploited any way to get rid of it is to throw MB to trash.
Why use SSD OS (unless he is using windows ). System can do to USB stick and rest od data to disk, and SSD may be a good option.
Does not really matter what wording they will put in. It is clear that project will go to pay or get nothing way. So just start working on decommissioning it. Free software really need better ways to pay developers, that will allow to avoid crap like that.
I would add LVM to the list of software raids, and remove btrfs as poorly engineered.
couple of old 2.5 HDD + usb to SATA converter. But Pi5 is hardly suitable to host anything. May just get old PC (which gives you HDD too). There are plenty for < $100 or even free. But you are going to pay more for power.
I do not see why it will cause any problems with exception of stacking mapping layer. I wonder can LVM do it natively without adding intermediate block device of 2 x 2G?
Stay with TP-Link. Ubiquity done some strange things recently.
Many sells, some just wipe them, some just contains encrypted data. If you happy with just used drive eBay is full of surprises.
Some diagram would help. Are you trying to use your server as a switch?
Why create yourself a headache and still get substandard and no-warranty drive. If you want cheaper drives go for reconditioned/refurbished/used drives. Same risks, better product. Old enterprise SAS drives are cheap and many still have plenty of heath in them.
Do you plan to compress video ( which generally already compressed format) when saving to remote location? I do not see use case for it, as you ether use lossless compression and not compressing it in any meaningful way, or just re-encode to different format and loose quality. Second option is simpler to achieve by re-encoding before sending out.
Yes, it will. Will it make any difference for you, depends of what are you doing. I would not use surveillance drive in to server, they are way too specific. Outside of that prices is pretty much same per TB/(Warranty Year) accross the board.
I done some excessive research couple of years back on the topic. you can find it here https://blog.holms.place/2022/05/01/hdd-storage-cost-comparation-may-2022.html. I do not think situation have changed match since than. Price per TB/Year is nearly constant past 8GB size.
Also consider looking to re-certified drives, or even refurbished drives. you may save hips on them. But it depends on how much you value your data, how much redundancy in you storage pool and how good your backup strategy.
I have only one question. Why mission to Hubble need to be manned? Dragon should be capable to dock to the ring even without guidance assist from Hubble.
Syncthing sync files, it is all does.
Look to other orchestrations solution too, like SALT. If you need to manage a lot of servers it is live saver. Setting up is only first step.
Usually just plug/unplug couple of times is enough. No fancy chemicals.
Run long smart test on the disk and check smart data after that. Other possibility is ZFS pool is nearly full.
Usually it can be solved by talking to hotel stuff. you are paying for that service and can expect it be suitable for any legal use.