• Content Count

  • Joined

  • Last visited

Community Reputation

71 Good

About FreeMan

  • Rank
    Advanced Member


  • Gender
  • Location

Recent Profile Visitors

2068 profile views
  1. Just for fun, today, the Cache Utilized Percentage is almost right, but the actual amount used is off. 175GB out of 360 is 48.61%. 147GB out of 360 is 40.83%. So either the math is wrong or it's not finding all 360GB of available cache space.
  2. This had, initially, fixed the display issue. However, it's back. These were from yesterday: And this is from this morning: No amount of adjusting the time frame will cause the Grafana reported utilization to get back in sync with the WebGUI. To address the other issues noted in your original response: * The mover is running at 01:10. It is currently 06:56, it's long since completed its task, the first shots were from sometime after noon yesterday * As noted previously, the query is pulling `"path" = '/mnt/cache'`. If you ha
  3. If the plugin was ever updated (I'm guessing not since the newest version I see is 2.0.0 and my plugin is dated 2018.02.11), your changes don't seem to have worked for me. I have auto updates turned on, but don't recall having seen the change come through (doesn't mean it didn't, just that I don't recall). My speed tests have been reliably failing before & since your post. I appreciate your efforts and hope that it does get updated! The V0.3.4 change appears to be working for me as well. A manual test functions, now to wait for my regularly scheduled test to ensure all is
  4. Have you notified whoever asked you to post diagnostics that they are up here? Maybe describe the issues you're having in more detail and someone else may be able to take a look. Most modern CPUs will throttle back if they get too hot, and will probably shut the computer down if temps continue to go up. You'd probably need to look at the docs for your mother board to determine if it has that feature and where in the BIOS settings it may be. The Parity Check Tuning plugin can be set to pause a parity check or disk rebuild if disk temps get too hot, but it won't shut down
  5. That is one. I wasn't aware of any, but figured they'd have a report somewhere. It is decidedly inconclusive. The first thing I noted was their extremely cool temps - the min temps any of my drives report in SMART history is about 30°C (86°F). Right now my "server room" is about 25°C (77F) and I've got drives spinning between 36-44°C. My SSDs are always reporting either 30 or 33C (1 @ 30, 2 @33). They never change (makes me a bit suspicious, but they're cool enough I'm not concerned). In general, it seems that occasionally hitting 50°C isn't quite the "instant death" I was initiall
  6. Interesting, I set the time frame to 1 hour and it sync'd the numbers. I set it back to 24 hr and it remained correct. I'm not sure where in the query I would need to make modifications, since it's selecting on "path" = '/mnt/cache'. I do have all 3 drives in the pool specified in the Cache Drive(s) drop down at the top of the page. And I don't care about the multiple images enough to be bothered, but thanks for the tip!
  7. I've just noticed an interesting inconsistency. As reported by the WebGUI: As reported by UUD: I know that the UUD is only refreshing every 30 seconds, but trust me, my system is NOT capable of writing 62GB to the cache drives in 30 seconds. Forgive this second image. I've tried deleting it twice, but it persists...
  8. After a brief DuckDuckGo search... Here's an undated PDF from Icy Dock with scary warnings about how heat kills drives. Of course, they want to sell you their docks to keep your drives cool, so one should take it with a grain of salt. Here's a 2020 page from ACKP claiming that "prolonged operation at temperatures under 20°C (68°F) or above 50°C (122°F)" will shorten a drive's lifespan. Of course, they want to sell you cooling solutions for your NOC, so there's a grain of salt with this one, too. Both of those actually reference the same white paper from National In
  9. This is more on line with what I believed and understood, but I've certainly got no proof one way or the other. Thank you for your input. I wonder if anybody has done /can find some research on what effect temp really has on drive lifespan. Sounds like something BackBlaze might have. I may see if they've got something. Sent from my moto g(7) using Tapatalk
  10. Interesting, and thanks for the feedback @Hoopster. I just don't think I'd ever seen a drive hit above about 40-41°C before, even during a parity check. I've got 5-in-3 cages, and this is the first time in quite a while that I've actually had 4 drives in any one cage. I've seen some comments about the IronWolf running hot, so maybe with it running hot and 4 drives (even though it was next to a drive that wasn't part of the array and spun down), the whole mess was just hotter than I'm used to. I'd still welcome other's input, feedback, comments.
  11. How hot is too hot for hard drives? I just finished rebuilding a drive in my array, and the brand new Seagate Iron Wolf was consistently hitting 46°C. I was using Parity Check Tuning to pause the rebuild, so that's about as hot as it got, but it spent 3 days bouncing between about 42-46°. I understand that different drives may have different operating conditions spec'd by the manufacturer (Seagate says up to 65° for the IronWolf), but what's a "reasonable" and "sensible" number? At what point should I worry about shutting things down to prevent drive damage?
  12. Thanks. Since it's not part of the array now, I either need to Preclear or rebuild parity. Since both this disk and parity are SMR (I know, what was I thinking), it's probably 6 of one, half dozen of the other in terms of time to live. Sigh... Sent from my moto g(7) using Tapatalk
  13. I ended up replacing the drive with the new Iron Wolf. With all the associated heat issues, it only took about forever to rebuild data onto the new drive. I now have the Barracuda with reported uncorrect errors still in the server and listed as an Unassigned Device. Would it be reasonable to try to run a preclear on it and see if it survives? If so, would more than 1 preclear cycle be suggested? If it survives one or more preclears, would you feel confident putting data on it? (running single parity, would ensure it's excluded from shares that might have critica
  14. As a general point of reference for any future issues you may come across, it's always helpful to go to the "Tools" menu, then click on "Diagnostics" and download the zip file. The page there tells you exactly what is being collected, but in general, it includes all the configuration info that the experts here would need to help diagnose setup issues like this. Glad you got this resolved so quickly and welcome to the Unraid family!
  15. In UNRAID, go to the "Tools" menu, then select "New Config". That should wipe out all previous disk assignments and allow you to reassign drives. It should also tell the OS that these are not UNRAID prepared disks, so it should do a clear on them. Of course, you can also do a preclear on the disks to ensure they get wiped, but when you start the system after doing a "New Config", that should do the trick.