This thread is to be used to provide feedback, suggestions etc to anything within the More Information Thread (https://forums.unraid.net/topic/120220-fix-common-problems-more-information)

 

This thread should not be used for getting help on any given issue, but only suggestions, wording changes etc to the more information posts

 

As usual, if you are creating a new topic to get assistance with any problem in Fix Common Problems, always include your diagnostics

 

Docker image file is getting full (currently xxx % used)

Is confusing if you don't use a Docker Image File, but have defined folder based.

 

Can you @Squid add a separate Error for this or extended the naming/description of the actual Error.

 

For example Docker Directory/Cache/Device/Path ... is getting full. (currently xxx % used)

Edited November 27, 20223 yr by Revan335

@Squid She have ignored the ignored and can added multiple times.

Hey everyone - came home to a unclean shutdown.  Rebooted and am getting this error - 

 

Jun 9 15:25:09 Skynet root: mcelog: ERROR: AMD Processor family 23: mcelog does not support this processor. Please use the edac_mce_amd module instead. Jun 9 15:25:09 Skynet root: CPU is unsupported

 

I haven't changed the CPU in months so its weird.  Just running a AMD Ryzen 5 3600 6-Core @ 3600 MHz.  Should I be worried?  That's the only MCE error I'm seeing in the syslog. 

 

 

Is /mnt/system/ excluded automatic by the Permission Fix?

 No  Only Appdata. 

 

Additionally, if you are running a docker folder instead of a docker image you should NEVER run the new permissions tool against it's share (and this includes Docker Safe New Perms) as it's a guarantee that you will need to recreate the docker image afterwards.

14 hours ago, Squid said:

 No  Only Appdata. 

 

Additionally, if you are running a docker folder instead of a docker image you should NEVER run the new permissions tool against it's share (and this includes Docker Safe New Perms) as it's a guarantee that you will need to recreate the docker image afterwards.

Can you add a Warning and exclude of the Default Docker/Folder Path /mnt/system/docker/?

 

Libvirt the same?

Hi, I am getting this message:

var/log is getting full 

Either your server has an extremely long uptime, or your syslog could be potentially being spammed with error messages.

 

My current runtime is 11 days.  This is the second time I am getting this warning. Before I could run my server for 60+ days without issues. 

 

Thanks

backupserver-diagnostics-20240112-2318.zip

3 hours ago, Smily said:

var/log is getting full 

Either your server has an extremely long uptime, or your syslog could be potentially being spammed with error messages.

And you can't see many Errors or other Spam in the log?

No, not many errors. I don't know what is meant by 'other spam.' My server runs fine, so I don't check the log very often. It was suggested in 'Fix Common Problems' that I should restart the server and post diagnostics here, so that is what I did. Maybe someone knows exactly what to look for?

You need to look at the syslog BEFORE restarting the server (which clears the syslog) which is in RAM so does not survive a reboot.

Out of memmory in common fix, Can't seem to find what it is, been like that since upgrade 6.12.6 and and cache upgrade to zfs 2 1 terabyte ssd raid mirror please help

conwayserver-diagnostics-20240120-1650.zip

Started getting this error today. From research it seems like an AMD thing. The server has been up for year running on AMD.

Quote

Machine Check Events detected on your server

 

tortuga-diagnostics-20240125-1026.zip

Under 6.12.8:

Event: Fix Common Problems
Subject: Warnings have been found with your server.
Description: Investigate at Settings / User Utilities / Fix Common Problems
Importance: warning

* Docker Patch Not Installed 

Is this a new Patch or a false positive from the past? The Docker Patch are included in earlier Version.

Ah, OK. A new Patch.

 

Hi,

 

FCP gives me the following warning: "Share appdata set to cache-only, but files / folders exist on the array". I changed the settings so appdata is only using the cache pool. How can I find out which files and folders are causing this?

 

AlsoI can't find the settings mentioned here:

Any guidance is much appreciated.

Thanks

 

 

tower-diagnostics-20240225-1601.zip

appdata                           shareUseCache="only"    # Share exists on cache, disk1
a-----e                           shareUseCache="no"      # Share does not exist
b-----s                           shareUseCache="no"      # Share exists on disk1
c------e                          shareUseCache="no"      # Share does not exist
d--a                              shareUseCache="yes"     # Share exists on cache, disk1, disk2
d-z                               shareUseCache="no"      # Share exists on disk1
domains                           shareUseCache="prefer"  # Share exists on cache
isos                              shareUseCache="yes"     # Share exists on disk1
l--s                              shareUseCache="no"      # Share exists on disk1
m---a                             shareUseCache="no"      # Share does not exist
n-------d                         shareUseCache="no"      # Share exists on disk1
p------l                          shareUseCache="yes"     # Share exists on cache, disk1
system                            shareUseCache="prefer"  # Share exists on cache

You need to stop the docker service (Settings, Docker)

 

Then from shares change appdata to have the primary storage to be cache, secondary storage to be array, and mover action to be array -> cache

 

After applying, from Main, Array Operations hit Move.

 

After mover is finished (may take a bit) then you can re-enable the docker service in Settings, Docker.  The share settings are probably what you want anyways.

@Squidthis worked! Thanks a lot

Hi All,

 

I was wondering if someone could help me with a "Machine Check Events detected on your server - Your server has detected hardware errors. The output of mcelog has been loggeg. Post your diagnostics and ask for assistance on the Unraid forums" error that came up in Fix Common Problems.  I've attached the diagnostic file.

unraid-1-diagnostics-20250331-1711.zip

The first post in https://forums.unraid.net/topic/120220-fix-common-problems-more-information/ has a dead link to the old diagnostics docs. I think the new link should probably be https://docs.unraid.net/unraid-os/troubleshooting/diagnostics/capture-diagnostics-and-logs/

Also, I was experiencing DNS resolution problems as described in https://forums.unraid.net/topic/120220-fix-common-problems-more-information/page/2/?tab=comments#comment-1101084 after moving my server to a new physical network. I already had those as my DNS servers. I ended up resolving it by updating my "IPv4 default gateway" in my Network Settings, since I am using static IPv4 address assignment. It was previously 192.168.1.1 on the old network and had to be 192.168.1.254 on the new one. Not sure if that is worth mentioning as a potential fix.

Edited January 2Jan 2 by Robb04