NewDisplayName

is it fixed that you can set the driver version to a different , but the plugin will eventually switch back to "latest"? I guess that would be annoying, untested (i also got the error with my 1050ti)

Yeah, the problem is, who looks at their uptime? xD If you know something is looping, you find it this way, correct. Devs dont seem to invest anything in "useability". There are servial minimal tweaks which would help reduce support and make user exp better.

They wont add QoL or logic things...

Since 6.10 i had freezes without any logs - changed ram, cpu, mainboard, power over the years, but the freezes kept happening like every week or every month. Since 7.0.0 i had a freeze like every other day. Since 7 days i didnt had a freeze, in 23 days we know if its finally fixed. The only thing which was the same were the hdds and sdds ofc. Now some time ago (7 days) I just changed one SSD. (because it got smart errors) (sitting in raid 1 with another one as cache drive) Could it be that unraid is so unreliable that it freezes just because of an "bogus" ssd? @limetech Maybe unraid could be made immune to such problems, like maybe let docker crash, but dont unraid freeze...? Isnt that the whole idea of letting unraid sit in ram? Maybe you can recreate that scenario now...? I keep you guys updated if that fixes it for me. edit: i never had any errors before on that disk, just btw. eidt2: it was a Samsung_SSD_860_EVO_1TB

CAN ANYONE explain how to create "Syslog catch all"...? Maybe that way i can find out why my servers keep freezing / crashing what ever

i had these bugs starting with 6.10 and i6700k current 1 M/B:ASRock Z390 Taichi Ultimate BIOS:American Megatrends Inc. Version P4.30 Dated 11/26/2019 CPU:Intel® Core™ i9-9900K CPU @ 3.60GHz HVM:Enabled IOMMU:Enabled Cache:L1 Cache: 512 KiB, L2 Cache: 2 MiB, L3 Cache: 16 MiB Memory:64 GiB DDR4 (max. installable capacity 64 GiB) So i dont think its special to a specific hardware. if you make a backup of your stick youre very fast back to the old version... btw and all of my hardware is 1. fresh or 2. fresh from a working system.

yeah unraid also liked to create some random network.cfg check everything it also likes to add double like (inside cfg files) IP[1] IP[1] unraid is getting worse and worse. Thats all. But there are new candidates on the horizon.

if i look at the many threads about losing drives i strongly believe its unraid. So i wouldnt throw it out the window, maybe there comes a update. I also "lost" 2 drives, but i cant believe it, because in the last 10 years i didnt lost so many drives..

Unraid is for me also unreliable since 6.10. Different RAM, CPU and MB, new stick, different locations - its just bad - a nas which cant even stay online. Most importantly for me it freezes or crashes without any usefull log. (like just ending, without anything) Do you use fritzbox?

INTERESTING! How did you create those catchall logs? do you use fritzbox products?

its the same with some hardware errors (or corrupt errors or what ever there called) , youll just notice if you look into your logs... and it could be so easy like if more then 10mb log in x hours -> something is wrong?

i really liked it and used many of those scripts like htop and python or vim or iotop or screen (!!!) I also think it (a way to install those kind of scripts) should be included in unraid. writing own scripts to put it somewhere is a ok workaround, but nothing more. Maybe those scripts can be added to "apps" so not 2 differnt stores needs to be worked on?

in the end its always the same script, just change the directories accordingly... i dont stop dockers because i couldnt find a difference and had never problems with backimg them up live... (or restoring) but it could be enabled by removing # in front of the code

docker.img

appdata