Squazz

Ok, I guess I'll try enabling C-states again then

With these changes, won't my Ryzen CPU then always be at a fixed clock, and consume a lot of electricity under idle?

I found "Power Supply Idle Control" and set it to "typical current idle" I also disabled "Global C-States" and "AMD Cool N Quiet" I also changed "Load-Line Calibration (LLC)" from auto to 4 (based on recommendation here: (https://www.reddit.com/r/AMDHelp/comments/pcp4fs/comment/hakelm3/?utm_source=share&utm_medium=web2x&context=3) I know I changed many things at once. But all changes should make the system more stable

I've had this problem with several versions unraid, but it's also present here in 6.12.6 Suddenly UnRaid just stops responding. - Shares are unavailable - display output is no more - I lose access to my running containers / they stop responding Hardware: MSI X370 SLI PLUS (MS-7A33) , Version 2.0 American Megatrends Inc., Version 3.JR BIOS dated: Friday, 29-11-2019 AMD Ryzen 7 1700 Eight-Core 16 GiB DDR4 I've attached the logs I could find from just after the first boot after the last time it happened. Every time it happens I run a full parity, finding 0 errors each time nas-syslog-20231230-1833.zip nas-syslog-20231230-1036.zip nas-diagnostics-20231230-1932.zip

That could very much be it, thanks! So long since I've set up my unRaid box, totally forgot that CA Backup was a thing

I have this same problem, where the binhex-plexpass container stops with "WARN received SIGTERM indicating exit request" as the message in the log. But, I haven't asked it to shut down, for some reason it just does that by itself.

I was thinking the same thing. But, when looking up excactly that series, I found this reddit post: https://www.reddit.com/r/DataHoarder/comments/2vxboz/comment/cp6umlc/?utm_source=share&utm_medium=web2x&context=3 As soon as sustained writes gets past 30GBs the write speed tanks (people say it flattens out at 27MB/s. Which it always will when it is introduced to Unraid. So, I am still curious what the actual experience is by the people who are using these Archive drives. And, wonder if anyone has ever replaced an existing drive with a archive drive?

So, I've seen that quite a few people are running Seagate Archive drives, and seem to be happy with the drives. But, that is confusing me. Won't the fact that they are SMR drives be quite a problem when replacing a dead drive, or just introducing them to the array? Right now I have 40Tb (8x5TB ST5000AS0001) worth of drives sitting on a shelf, as I don't want to introduce them to my UnRaid array if they turn out to be quite a hassle to work with. I tried to replace a 3Tb WD RED (WD30EFRX) with one of my Archive drives, and it quickly went from acceptable to 10MB/s. For a 5TB drive, 10MB/s is never gonna cut it. At that speed, they are probably never gonna get introduced to the array before another drive dies. So, in the end my question might be. What am I doing wrong? If people are happy with their 8Tb Seagate Archive drives, then why does it seem that I am getting speeds as 10MB/s?

Buying new harddrives just for the reduction in power, seems to not really be worth it. At least here in Denmark We are talking a payback time of at least a decade, when looking at powerdraw exclusively It's a nice bonus. But not something I'd buy new drive for

That's a fair point! Which is also what is making me consider if I should just go with 8Tb 7E8 drives instead. My signature is updated now Good to hear about your experience, and a fair point about the 2hr/day is also viable, as long as it is done.

I feel there's beginning to be a consensus. I'm propably gonna end up with buying 2x Seagate Exos X16 ST16000NM001G 16TB drives, that's where I get most space for the money. And it also seems that parity checks is not that big of a problem with drives in the sizes of above 10Tb

I guess I'll go with the 16Tb drives then I'm considering removing one of my two parity drives, and then just go with a single 16Tb parity drive Sounds interresting, I'll give it a look Interresting that you only see 26 hours for a parity check on the 16Tb drives. If one doesn't feel the impact of the parity check, a monthly check might be OK. @DMills could the reason you don't see an impact be that you have a big cache? Personally I don't have that big a cache as I'm only running SSDs as my cache

Hi I have a bunch of WD Green 3Tb drives. And I'm beginning to run out of space (both physical in the computer case, and on the shares) I'm considering buying new Seagate Exos X16 16 or 14 Tb drives. But, are they gonna be too big? I'm considering the parity checks. Right now it takes me about 8 hours for my 3Tb drives. If it's gonna tke me 5,5 times as much time with 16Tb drives, we are talking 40+ hours of parity checking. That's almost two days where I will see degraded performance on my shares. Right now I do parity checks every month. That doesn't seam feasable with a 2 days parity check. What is the experience from other people? Are 16Tb drives too big? How often do you do parity checks with so large drives? How long does it take to take to do parity checks of drives of this size? My main fear is data degradation through bitrot or the like.

Noted, hereby uploaded

I have 2 5Tb disks as parity, and duing a parity-sync they both ended in an error-state. I've attached SMART reports for both. On of the drives I understand if is dying/dead. It seems it has some errors, and they are probably worsening. The other drive on the other hand, I don't understand why ended in an error-state. I'm hoping someone can help me figure out why my drives ended in an error state. Crossing fingers that I'll be better to read the reports after I've gotten some help on this event. nas-smart-20220309-1900.zip nas-smart-20220309-1853.zip nas-diagnostics-20220309-2042.zip