-
Posts
3697 -
Joined
-
Last visited
-
Days Won
9
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by ChatNoir
-
-
This is not a bug, it's the way it is designed.
The configuration is stored in a cookie on your browser. So a different browser can be configured differently depending on your use case or resolution.
-
4 hours ago, carthis said:
+1
Are you still seeing the problem on 6.12.2 ?
Because nothing will be changed on 6.11.x
-
7 hours ago, philliphs said:
It's a weird placement for docker image size as it's RAM usage section
Not really, Flash is the used size of the flash drive, etc.
-
RAM usage is only the first line, the last line is about you docker image size if I am not mistaking.
-
6 hours ago, ch3vr0n5 said:
Syslog didn't capture anything from the crash. Not sure how I am supposed to get the full kernel panic.
did you
On 7/1/2023 at 1:31 PM, JorgeB said:Enable the syslog server and post that after a crash.
-
-
Not sure to see a significant improvement from 6.12.2.
It seems that some containers are more impacted than others (Plex, Jellyfin for example for me)
On the other end, I am wondering it is an actual RAM usage problem or an issue of reporting from docker and/or kernel interpretation. (my table above uses 'docker_container_mem' )
On the same time period than the image above (15 days), my system RAM usage does not seem to be fluctuating much while docker is supposed to have reached ~27GB from an average of 8-9GB on 6.11.
My total RAM is 64GB, so going from 9 to 27 should be clearly visible on the system.
The Unraid Dashboard is consistant with my Grafana dashboard.
-
Changed Status to Open
-
The question is :
- is it a Unraid problem ?
- or a linux+docker problem ? (ie new kernel + new docker version)
If it's the second, not much that can be done here.
-
-
I would guess that it is not a bug ?
The Dashboard settings are probably stored as a cookie and accessing from local or remote would not use the same cookie ?
-
7 hours ago, GG73 said:
how do you do that? when I download the diagnostics, if I drag and drop the folder. the above happens. All the individual files upload ?
it comes from Unraid as a zip file. Maybe you OS is 'helping' by automatically unziping archive ?
-
Changed Status to Closed
Changed Priority to Other
-
23 minutes ago, jimz011 said:
I presume I need to post diagnostics from after the update and not from my current running version right?
yes
23 minutes ago, jimz011 said:I also presume that diagnostics are found in the tools section?
yes
-
If Jorge's advice below does not fix your issue, then :
- Do not format
- Please create a new thread in prerelease so it is easier to assist than in the release thread
- attach your diagnostics in the new thread
-
As is, MACVLAN may or may not what is causing the crash.
You should setup a syslog server and post it after the next crash.
- 1
-
If you still need support, you should create a thread in https://forums.unraid.net/forum/55-general-support/
-
2 hours ago, Octalbush said:
This is the rc2 thread... Is there an rc3 thread I'm not seeing?
He means a thread about this specific issue like :
[6.12 RC2] ZFS default SPA slop space
Discussing many issues in the release thread is not the best way to have good follow up.
-
3 hours ago, mikeyosm said:
Is there a way to download the 6.12 rc2 manually (zip) instead of USB creator option?
https://unraid-dl.sfo2.cdn.digitaloceanspaces.com/next/unRAIDServer-6.12.0-rc2-x86_64.zip
- 1
-
What version of Unraid ?
Can you provide your diagnostics ?
Are you sure that no software or network appliance is accessing the drives ?
-
As stated in the first post :
QuotePlease create new topics here in this board to report Bugs or other Issues.
-
Could it be because vdisk1.img image already exists ?
-
Changed Priority to Other
-
Changed Status to Closed
Changed Priority to Other
UI Dashboard Tile
in Stable Releases
Posted
Changed Status to Closed
Changed Priority to Other