-
Posts
43882 -
Joined
-
Last visited
-
Days Won
137
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by trurl
-
-
Often the cause of docker image corruption is overfilling it. And filling docker.img is often caused by an application writing to a path that isn't mapped.
I have been using default 20G docker.img for years with no problem, but I have never ran more than 16 containers.
-
20 minutes ago, Stephan4711 said:
Settings/ManagementAccess
I see that setting now.
-
Quote
extra origins
What does this refer to? Doesn't seem to be anything related to the Unraid OS itself.
If you are asking about a docker container you should go to its support thread or page. You can usually get there by clicking its icon in your Unraid webUI and selecting Support.
For future reference
-
Diagnostics required for bug reports.
-
-
That is not Diagnostics.
-
-
2 minutes ago, trurl said:
What do you get from command line this?
ls -lah /boot
Actually, I can see this from diagnostics.
You have a lot of FSCK files on flash, which are the result of repairing corruption on flash.
Do you have a current backup of your flash drive?
You should probably reformat flash, reinstall, and copy your config from your flash backup.
-
The fact that settings are reset, and also unclean shutdown, makes me suspect flash drive corruption, since all of your settings are on flash, as well as the status that says the array was stopped.
If that status can't be written for some reason, unclean shutdown is the result.
And if any settings can't be read from flash, they go back to defaults.
What do you get from command line this?
ls -lah /boot
-
-
I see, you rebooted before getting diagnostics.
If it happens again try to get diagnostics before rebooting.
And setup syslog server.
-
Are you sure you posted to the right thread? Diagnostics shows you have /mnt/user.
-
Attach diagnostics to your NEXT post in this thread.
-
You have a large number of plugins, and for some reason checking plugin version is blocked or something, so can't easily tell if any are out-of-date. Updating all plugins was mentioned in the release notes.
In fact, booting in SAFE mode is mentioned in the Report Guidelines I linked above.
And, you have a lot of stuff in the extra folder on your flash drive, probably put there by NerdTools.
Not sure if extra folder will be loaded if you boot in SAFE mode or not.
-
Probably unrelated, but you were supposed to update all plugins.
-
1 hour ago, dopeytree said:
appdata folder as the default shares are creates for all user.
Default shares are not created until Docker and/or VM Manager are enabled. And those paths are actually determined by the Docker and VM Manager settings made.
So not everyone will have appdata.
Flash drive is the only persistent storage guaranteed to exist.
-
-
The link you posted is "legacy" as it says.
https://docs.unraid.net/unraid-os/getting-started/
2GB is probably bare minimum now, and may be too small in some circumstances.
Update can't be in RAM since it has to reboot.
-
4 minutes ago, David Grenon said:
putting logs elsewhere (not on boot drive) would give me more infos?
no
-
1 minute ago, David Grenon said:
How to trouble shoot this though.... No logs...
setup syslog server
-
48 minutes ago, David Grenon said:
Realtek network card bug
You don't have one according to your diagnostics and the list you posted above.
- 1
-
3 hours ago, David Grenon said:
other things I forgot to mention is my Hardware listing
We can see that in your diagnostics in system/lspci.txt
3 hours ago, David Grenon said:could run a mem test, but I doubt
If only to eliminate that. Better safe than sorry.
3 hours ago, David Grenon said:Do you think the network card bug applies to me ?
Which bug are you referring to?
-
Looks like you have some things mentioned here:
https://docs.unraid.net/unraid-os/release-notes/6.12.6/
Also
https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#comment-819173
-
Have you done memtest?
[6.12.9] Can't start, update or remove containers - ZFS issue?
in Stable Releases
Posted
Another possible cause of corruption is bad RAM.