I particularly enjoyed the title of this video "Why Scrubbing ZFS Without ECC RAM Probably Won't Corrupt Everything". The only way available to normal end users to eliminate such errors is to reload the pool from backup. Once bad data is injected into a pool, hopefully it can be deleted if it is within a file, but if it is metadata then there is a good chance that there is no way to delete it, and the error is permanently introduced into the pool. It should be pointed out that the big argument for ECC is that ZFS contains no "fsck" or "chkdsk" ZFS is entirely reliant on the correctness of the code and the ability of the pool to faithfully store and retrieve data. I will need to hear by tomorrow of course. I am curious to hear from others who are using truenas without ECC, who have maybe had catastrophic issues. If I wanted it would be much more expensive and are not keen to spend much at all. It is regularly backup up to truenas and the media machine share. My main machine has important files on there. It is not tied to my livelyhood, mainly my entertainment. So if I lose a data on a truenas, it will be annoying. With a BIOS update can boot headless it seems. VMs will be allocated more memory and cores. So it seems tempting to get some slow cheap memory 64GB - maybe tomorrow as it is black Friday. So I have an MSI B450 tomahawk and a 3600X CPU not being used. Oh and backup weekly to external drives - 4 of them. A few old hard drives in raid Z1 is in it with samba shares. I left XMP turned off so the memory runs cooler and hopefully less errors.Įverything important is regularly backup up to another machine. I have had broken drives, so replaced.Īny memory issues have been due to lack of it, but apparently not due to using non ECC. I passthrough the onboard intel sata controller to ttuenas. I have been using it for a few years It had freenas, then truenas.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |