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

would be cool ofc, but i dont think that should be high priority because you can archieve it very easy and fast... via user scripts... "some" directory:

i like

I suggested it to the Fix Common Problems author but no response for a year or so. Sometimes if a docker update breaks the container or you have some config fault it might happen that dockers restart over and over again, for ever, which is in 99,99% not the expected behaivor. (i know its because of restart unless stopped, but thats not the point) I would suggest to ATLEAST add some sort of NOTICE to unraid if unraid sees a container restarting 10 times in 5 minutes or something. A normal user would never notice that there is a loop...

What about a select/deselect all? What about maybe you can drag across and it marks it automatic. Like click, press and go over the cores to mark them. What about a do all dockers like this "..." Since its getting more and more cores ONLY this feature is getting more important over time.

Hi, thanks for your feedback. I never had gpu problems or crashes (gpu hang and inotify errors), these are new with unraid 7+. What i have since 6.10 is freezes and or crashes randomly between some hours and some weeks. And that with different mb, ram and cpu. 🙂 (and usb stick) All while not activly using igpu atall. --- To rule the gpu out, i tried removing my dgpu and this is where the new fun startet... ^^ --- now im back to dgpu, removed all dev dri and disabled VM. Edit: i saw that your igpu is using 1,1ghz and my is using 1,2ghz - maybe its just running stable with 1,1ghz edit2: If its a software problem (and im just using standard dockers like from linuxserver and so on) it should be a priority for the future for unraid and or limetech to implement some sort of debug mode or something WHERE we can get USEFULL logs.

Yeah, its hard to explain the odysee, the gpu hang thing is new (unraid 7+), also the inotify error others reported, and the idea that the other problems like freezes might come from that is a new idea. I saw gpu hangs in plex, frigate and tdarr. So unlikly a app thing, more a i915 thing. I know that it might be not much users or not much reporting about it because they are okay with it needign restart every XX days... If i would run some kind of special hardware i would understand but its pretty standard, yes youre right with my gaming rig i didnt used the igpu much, still i didnt had any crashes or freezes wihtout using it. I had the crashes while activly using it and also while actifly using a dgpu. So it happens in both cases. I removed dgpu to rule that out. my last straw was a new usb stick... Isnt it possible to get better logs? Like would it work if i run tail -f /var/log/* >> /boot/logs in screen? Where are docker logs?

Understand your customers, weve paid, yes its a one time, but it would work on standard hardware that was the deal for unraid. Since 2 years im plaqued by different problems but over all problem with freeezes and or reboots. Always using standard consumer hardware which was 100% working when used as a gaming pc. First with 6700k then with 9900k, there are either no logs or gpu hang or what other ppl are reporting. No extreme OC, plenty of w (1000w platinum) I tried to fix it myself, i tried everything suggested, it was on differnt usb sticks, ram, gpus, mainboards, cpus same problems, then this stops working, then th is is bugged, then this doesnt get saved or changes on itself... I dont know if its an hardware defect or a docker, but should unraid not try to find out where it is coming from? You always have to "feel" if the devs are aware of problems. In the end i had to put a dGPU into the unraid server, even its not really needed (save power), but the igpu doenst seem to work, maybe its a an intel issue? I dont know but how should i investigate such a thing?

No, its just a fresh usb install with you rinstaller. updated everything

I love the part where you get "attacked" for posting bugs. Testing new features would be a feature request. And yes its the first time ive used that feature, b ecause unraid isnt stable, because unraid dont work with (9900k) igpus. If you like you can move that post where you think its fitting. I gave up on that forum structure long ago.