# Help with node optimizations / best practices

**URL:** <https://forum.storj.io/t/help-with-node-optimizations-best-practices/25279>\
**Category:** Node Operators\
**Tags:** windows-gui, proxmox-vm, hardware\
**Created:** [February 20, 2024, 2:10am UTC](https://forum.storj.io/t/help-with-node-optimizations-best-practices/25279 "2024-02-20T02:10:24Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [February 24, 2024, 1:29pm UTC](https://forum.storj.io/t/help-with-node-optimizations-best-practices/25279/26 "2024-02-24T13:29:57Z")

</div>

Check the backblaze stat

> [@Raid 5 failed. 3TB node dead. Recovered partially and going through GE thanks to forum](https://forum.storj.io/t/raid-5-failed-3tb-node-dead-recovered-partially-and-going-through-ge-thanks-to-forum/6914/42):
>
> @Sasha often people won’t know that their array has failed and only become aware of it when a drive finally dies… but drives are most often bad long before they die, so people trust their system to keep everything working and then when it breaks its like 1 disk dead and a ½ disk bad, or worn down so much that when the rebuild is started that kicks it over the edge. raid arrays aren’t backups, they aren’t they are mitigation of the 2% or so odds that a data drive fails… mirror / raid1 is a tan…

The greater disk and lower the quality - the bitrot is the inevitable event.  
In the RAID setup it’s - fatality, unless you use ZFS and in the any pool with a redundancy.  
Otherwise you have a lower risk for a single drive setup with a plain ext4 for Linux and NTFS for Windows (please, DO NOT MIX the OS and FS).

---

_[View the full topic](https://forum.storj.io/t/help-with-node-optimizations-best-practices/25279)._