matt15k

After updating to 7.2.0, every click to another section of the WebUI refreshes the entire page and makes the entire dashbar section across the top flash and reload. Happens in Firefox and Chrome. No installed plugins that should be related. Before the update (and on my other server that is not updated yet), every click to other sections (Dashboard, Main, Settings, Tools, etc.) does not refresh the whole page and the top portion of the WebUI does not flash or visually reload, just the bottom section changed, which was normal. This new bug (?) is a minor UI annoyance but it feels a lot less polished this way. I noticed it immediately and it's annoying when doing a lot in the WebUI at night. Hope it gets noticed and fixed. Other than that, the update was fast and working well so far. Thank you Unraid team!

My Unraid box has 2x16GB DDR5 sticks right now and I'm looking to add more RAM. I have the opportunity to add another matching 2x16GB kit for a total of 4x16GB (64GB), or to make a local trade and replace the existing RAM with 2x24GB (48GB). I read that with DDR5 using all 4 RAM slots can cause stability issues. Current RAM usage is about 80% so the 48GB should be enough of an upgrade for now... and I don't want to introduce any problems to the server. My main concern is stability and I don't mind setting the RAM at a lower 4800MHz speed in the BIOS if that would help with this 4 DIMM "problem". I could shell out twice the cost for a 2x32GB kit but if it works okay to use 4x16GB I'd prefer that. What do you think? It's from the i9-12900K (Thank God) / ASUS Z790-V Prime AX / 2x16GB G.Skill Ripjaws S5 DDR5-6000 bundle from Microcenter. The 2x24GB kit is from a friend who has the similar bundle and looks like those are DDR5-5200.

Thanks for the reply. Where can I read more about this? Everything I have read about data integrity in Unraid has said the parity protection is only for emulating a failed disk, not restoring incorrect or corrupted data, so I'd love to learn more details about how parity drives in the Unraid array protect against disk read errors. I have been considering moving my XFS array over to a ZFS pool and wondering if its stronger data integrity protections would help avoid similar issues in the future.

Hello, I understand similar questions have been asked, but I am still uncertain about this after hours and hours of research. I recently added another refurbished server grade 18TB HDD to my Unraid array, and it passed the initial preclear successfully (1 round of pre-read, clear, and post-read), followed by a successful extended smart test. Then I moved ~8TB of files from another full disk to the new disk using Krusader. After this move, the new disk is showing "Reallocated sector count: 2", "Current pending sector: 42" and "Offline uncorrectable: 20", and a new extended smart test shows "Completed: read failure". This looks to be a bad HDD, so I am going to return it for another one under the seller warranty, but I am mainly concerned about file integrity of the data I copied to the new disk. Some of the files were backed up outside the array so I am restoring them back to the original disk on the array from the backup. The other files were new downloads (online videos), and I am not finding any way to locate which files (if any) may have been damaged by this disk failure. For the meantime I plan to copy those video files back to another disk, and scan them with CorruptVideoFileInspector from a Windows VM. My hope is that if everything passes, I can assume no files were damaged. Any other suggestions are welcome. Overall, what is the best practice when these type of drive errors happen? The array has dual parity which I know is only for total disk failure, but it seems strange there are no protections available for the situation I have encountered here. I back up my important files, but the media files are too large unless I built a second Unraid array. If this suddenly happens to another disk in the future within the array, or to a parity disk, it does not seem practical to restore everything from backup over a few failed disk sectors. That is why I am wondering if there is a way to know if any files got affected by this (to put my mind at ease instead of manually redownloading TBs of files), and how to treat situations like this in the future. Thanks in advance.