[Plugin] CA Fix Common Problems

[diehard2k9]

On 8/20/2022 at 9:44 PM, wgstarks said:

Go to the docker tab and click the name of your plex docker. This will open the configuration window. Click the edit button for the path associated with the UD device and you will see a popup window similar to this-

 

Set the access mode to Read/Write - Slave and click "Save".

Hello, Yeah I found and understand what I needed to do but that didnt fix my problem!  I still cant see what on the drive so my plex server still isnt working. When conneccted threw the network all my file are not displaying. But unraid main page see the drive and that I have used up 2.4TB and have 1.5Tb free but under the unassign devices no files are showing up

[wgstarks]

1 hour ago, diehard2k9 said:

but under the unassign devices no files are showing up

I would suggest posting in the UD support thread then.

https://forums.unraid.net/topic/92462-unassigned-devices-managing-disk-drives-and-remote-shares-outside-of-the-unraid-array/

[dlandon]

On 8/20/2022 at 8:10 PM, diehard2k9 said:

Hello, just updateto the lastest unraid6.11.0-rc3 Now the plex server is broken. I have a link or share in unassigned device with the plexe data. Only problem is that unraid doesnt see my files on it. It doesnt need all the videos either.  It know that 2TB has been used and there is 1.4TB free but I cant see any of the files . "

 

I don't think this is the solution to your problem, but your log is being spammed with this:

Aug 20 20:53:54 KRAKEN  nmbd[74745]: [2022/08/20 20:53:54.152573,  0] ../../source3/nmbd/nmbd_incomingdgrams.c:303(process_local_master_announce)
Aug 20 20:53:54 KRAKEN  nmbd[74745]:   process_local_master_announce: Server GIGABYTE at IP 10.0.0.120 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
Aug 20 20:53:54 KRAKEN  nmbd[74745]: [2022/08/20 20:53:54.152691,  0] ../../source3/nmbd/nmbd_become_lmb.c:151(unbecome_local_master_success)
Aug 20 20:53:54 KRAKEN  nmbd[74745]:   *****
Aug 20 20:53:54 KRAKEN  nmbd[74745]:   
Aug 20 20:53:54 KRAKEN  nmbd[74745]:   Samba name server KRAKEN has stopped being a local master browser for workgroup WORKGROUP on subnet 10.0.0.17
Aug 20 20:53:54 KRAKEN  nmbd[74745]:   
Aug 20 20:53:54 KRAKEN  nmbd[74745]:   *****
Aug 20 20:54:12 KRAKEN  nmbd[74745]: [2022/08/20 20:54:12.727010,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
Aug 20 20:54:12 KRAKEN  nmbd[74745]:   *****
Aug 20 20:54:12 KRAKEN  nmbd[74745]:   
Aug 20 20:54:12 KRAKEN  nmbd[74745]:   Samba name server KRAKEN is now a local master browser for workgroup WORKGROUP on subnet 10.0.0.17
Aug 20 20:54:12 KRAKEN  nmbd[74745]:   
Aug 20 20:54:12 KRAKEN  nmbd[74745]:   *****

The local master browser election is bouncing back and forth causing a lot of log messages.  It makes it hard to analyze your log when it's filling with those messages.  Not sure what your LAN configuration is, but maybe install the local master plugin to make Unraid always win the election for master browser.

 

Once you've solved that, unmount and remount the UD drive you use for plex and post new diagnostics.

 

Also post a screen shot of the mapping of the drive to the plex docker container.

[diehard2k9]

8 hours ago, dlandon said:

 

I don't think this is the solution to your problem, but your log is being spammed with this:

Aug 20 20:53:54 KRAKEN  nmbd[74745]: [2022/08/20 20:53:54.152573,  0] ../../source3/nmbd/nmbd_incomingdgrams.c:303(process_local_master_announce)
Aug 20 20:53:54 KRAKEN  nmbd[74745]:   process_local_master_announce: Server GIGABYTE at IP 10.0.0.120 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
Aug 20 20:53:54 KRAKEN  nmbd[74745]: [2022/08/20 20:53:54.152691,  0] ../../source3/nmbd/nmbd_become_lmb.c:151(unbecome_local_master_success)
Aug 20 20:53:54 KRAKEN  nmbd[74745]:   *****
Aug 20 20:53:54 KRAKEN  nmbd[74745]:   
Aug 20 20:53:54 KRAKEN  nmbd[74745]:   Samba name server KRAKEN has stopped being a local master browser for workgroup WORKGROUP on subnet 10.0.0.17
Aug 20 20:53:54 KRAKEN  nmbd[74745]:   
Aug 20 20:53:54 KRAKEN  nmbd[74745]:   *****
Aug 20 20:54:12 KRAKEN  nmbd[74745]: [2022/08/20 20:54:12.727010,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
Aug 20 20:54:12 KRAKEN  nmbd[74745]:   *****
Aug 20 20:54:12 KRAKEN  nmbd[74745]:   
Aug 20 20:54:12 KRAKEN  nmbd[74745]:   Samba name server KRAKEN is now a local master browser for workgroup WORKGROUP on subnet 10.0.0.17
Aug 20 20:54:12 KRAKEN  nmbd[74745]:   
Aug 20 20:54:12 KRAKEN  nmbd[74745]:   *****

The local master browser election is bouncing back and forth causing a lot of log messages.  It makes it hard to analyze your log when it's filling with those messages.  Not sure what your LAN configuration is, but maybe install the local master plugin to make Unraid always win the election for master browser.

 

Once you've solved that, unmount and remount the UD drive you use for plex and post new diagnostics.

 

Also post a screen shot of the mapping of the drive to the plex docker container.

Hi I'm not very good with the whole linux thing. It's hard for me to understtand what to do.  I have the local master plug installed.

I am weeks away from upgrade and this happens.  I just know that the folders in the UD are not showiung up for the system to find what it need to run plex or show my files.  I reaally dont know what I need to do and I dont want to start from the beginning so any help would be great!

kraken-diagnostics-20220822-2157.zip

[dlandon]

You have the wrong mapping of the drive.  You're referring to the drive in the docker mounted at /mnt/disks/TEAM4TB, but the drive is actually mounted at:

Aug 22 21:57:10 KRAKEN unassigned.devices: Successfully mounted 'nvme0n1p1' on '/mnt/disks/112110050430099'

Do the following:

• Stop the plex docker container.
• Unmount the UD drive.
• Click on the UD mount point and change it to 'TEAM4TB'.
• Mount the UD drive.
• Start the plex docker container.

[randommonth]

Hi guys,

 

I've just discovered my server crashed again overnight and is displaying the same usual symptoms. Docker service failed to start and errors in unable to wrote to cache and unable to write to Docker image. Interestingly, this time both cache drives still appeared online under the Main tab. I tried to resolve this by moving the SATA cable from one port on the motherboard to another, but that created more issues with the Cache being unreadable, so I moved the cables back to the ports they were in originally and the system appears to have restarted ok. I can't help but assume that one or more SATA ports on my motherboard are faulty..?

 

bigdaddy-diagnostics-20220824-0613.zip

Edited August 24, 2022 by randommonth
More detail

[JorgeB]

10 hours ago, randommonth said:

I've just discovered my server crashed again overnight and is displaying the same usual symptoms.

 

Cache2 dropped offline:

 

Aug 23 21:49:46 BIGDADDY kernel: ata1: hard resetting link
Aug 23 21:49:51 BIGDADDY kernel: ata1: COMRESET failed (errno=-16)
Aug 23 21:49:51 BIGDADDY kernel: ata1: reset failed, giving up
Aug 23 21:49:51 BIGDADDY kernel: ata1.00: disabled
Aug 23 21:49:51 BIGDADDY kernel: ata1: EH complete

 

And it's not the first time, check/replace cables, then run a scrub and check all errors were corrected, see here for more info and better pool monitoring.

[diehard2k9]

On 8/22/2022 at 10:58 PM, dlandon said:

You have the wrong mapping of the drive.  You're referring to the drive in the docker mounted at /mnt/disks/TEAM4TB, but the drive is actually mounted at:

Aug 22 21:57:10 KRAKEN unassigned.devices: Successfully mounted 'nvme0n1p1' on '/mnt/disks/112110050430099'

Do the following:

• Stop the plex docker container.
• Unmount the UD drive.
• Click on the UD mount point and change it to 'TEAM4TB'.
• Mount the UD drive.
• Start the plex docker container.

Hello, thanks for all the help but I'm not sure what I';m doing anymore. You reply let me find that all my info is there.  I dont know why it all stoped working. I created a link to UD back when I installed the NVME for plex andd file. so when you say to do "Click on the UD mount point and change it to 'TEAM4TB'." not sure how this is done or where it is. I see now what the problem is my link that was create might have gotten changed after the upgrade that cchanged something.  I will try and see if I can change it back!

[dlandon]

1 hour ago, diehard2k9 said:

Hello, thanks for all the help but I'm not sure what I';m doing anymore. You reply let me find that all my info is there.  I dont know why it all stoped working. I created a link to UD back when I installed the NVME for plex andd file. so when you say to do "Click on the UD mount point and change it to 'TEAM4TB'." not sure how this is done or where it is. I see now what the problem is my link that was create might have gotten changed after the upgrade that cchanged something.  I will try and see if I can change it back!

 

In my case:

 

Click on the 'Testing' text when the drive is unmounted and change that to 'TEAM4TB'.

[randommonth]

14 hours ago, JorgeB said:

And it's not the first time, check/replace cables, then run a scrub and check all errors were corrected, see here for more info and better pool monitoring.

 

Hi @JorgeB, thanks for the advice but my server failed again overnight, 24 hours after the last failure (diagnostics attached). Interestingly these failures appear to happen at the same time, 4:40am. I've gone back through my notification emails and 4:40am is the time for about 80% of them. Could this be just the time that the plugin runs its checks or could there be another process triggering it?

 

When I restarted the server after the failure yesterday, the Docker service still appeared to be corrupted. So I deleted the Docker folder through the GUI and restarted the server, expecting to have to reload all my Dockers from templates. However upon restart, all my Docker containers were there and running fine??

 

I ran the scrub per your advice last night and got these results:

 

UUID: b22551d5-574f-45b3-a984-7648d094271c

Scrub started: Wed Aug 24 22:06:11 2022

Status: finished

Duration: 0:09:21

Total to scrub: 137.94GiB

Rate: 231.54MiB/s

Error summary: read=16457092 super=3

Corrected: 0

Uncorrectable: 16457092

Unverified: 0

 

All my cables are brand new so what else could be the problem? Your advice yesterday (besides cables) was to have better monitoring, but that doesn't appear to attack any root cause, just give me earlier warning before failure?

 

One of the SSDs (ADATA) is much older than the other. If it is the one failing, could I try removing it from the pool and reverting to a single cache drive for a while?

 

I'm very appreciative of all advice, just getting a bit frustrated here!!

 

Thanks

 

bigdaddy-diagnostics-20220825-0754.zip

Edited August 24, 2022 by randommonth

[JorgeB]

8 hours ago, randommonth said:

I'm very appreciative of all advice, just getting a bit frustrated here!!

Swap cables between both SSDs, if the Crucial keeps dropping replace it.

[randommonth]

1 minute ago, JorgeB said:

Swap cables between both SSDs, if the Crucial keeps dropping replace it.

 

Thanks. I thought the Adata SSD was the one failing? 

[hansolo77]

FCP has been running great with it's quick checks, but lately when I do an extended test I'm getting some errors.

 

The error "section" is labeled:

Quote

The following files / folders may not be accessible to the users allowed via each Share's SMB settings.  This is often caused by wrong permissions being used on new downloads / copies by CouchPotato, Sonarr, and the like:

 

I know this is kind of a generic section.  I do use Sonaar/Radaar, but many of the files that are in error are not in the paths those dockers use.  Some of them are, but not all.

 

For instance:

Quote

/mnt/user/Backups/F46B6190AFB842D7---  AARON-PC  ---20-20.mrimg  nobody/users (99/100)  0660
/mnt/user/Backups/F46B6190AFB842D7---  AARON-PC  ---21-21.mrimg  nobody/users (99/100)  0660
/mnt/user/Backups/F46B6190AFB842D7---  AARON-PC  ---22-22.mrimg  nobody/users (99/100)  0660
/mnt/user/Backups/F46B6190AFB842D7---  AARON-PC  ---23-23.mrimg  nobody/users (99/100)  0660
/mnt/user/Backups/F46B6190AFB842D7---  AARON-PC  ---24-24.mrimg  nobody/users (99/100)  0660
/mnt/user/Backups/F46B6190AFB842D7---  AARON-PC  ---25-25.mrimg  nobody/users (99/100)  0660
/mnt/user/Backups/F46B6190AFB842D7---  AARON-PC  ---26-26.mrimg  nobody/users (99/100)  0660
/mnt/user/Backups/F46B6190AFB842D7---  AARON-PC  ---27-27.mrimg  nobody/users (99/100)  0660
/mnt/user/Backups/F46B6190AFB842D7---  AARON-PC  ---28-28.mrimg  nobody/users (99/100)  0660

I have a computer that creates a daily backup using Macrium.  I created a network share for it to store the files in.  I thought I had the share set up right, but maybe not.  The Macrium software requires me to provide a username/password to access the share when I do a restore, the anonymous access doesn't work in the recovery environment.  I think this might be what's causing the problem here.  It writes with the ownership of the user that will be accessing it during restore.  So, I think these might be false/positives.

 

Another series of files I'm getting issues with, is the random Sonarr/Radarr finds.  Most of them are coming up as either "  nobody/users (99/100)  0640  " or "  nobody/users (99/100)  0660  "  Since it's saying that might be a permission problem on the new downloads, it bugs me why it's a "random" appearance.  What settings should I be using for those dockers?  For instance, in the docker config for Sonarr, it is set to use "Key 1 (PUID) = 99" and "Key 2 (PGID) = 100".  Then in the docker itself, under "Settings->Media Management", I have it set to NOT set permissions, the default setting says "755", and "chown group" is blank".  Should I be changing anything here?

 

Thanks guys!  Love Unraid, and this plugin! 

[writablevulture]

I am about to upgrade to Unraid 6.10.3 and have just run the Update Assistant which gives me this issue:

Quote

Issue Found: It appears that you have an ethernet adapter using the tg3 driver and IOMMU enabled. This combination has been found to potentially cause serious data corruption issues. Disable IOMMU in the BIOS

 

I am aware of the issue in other 6.10.x releases for certain machines including my HP Gen 8 Microserver, but I understand that the primary purpose of the 6.10.3 release was to fix that issue as described here in the official release post.

 

I am confused as to what to do here. The official release notes indicate that everything should be alright now because the Linux kernel default IOMMU operation mode has been changed from "DMA Translation" to "Pass-through"  but the Update Assistant says I need to disable IOMMU in the bios. Do I need to disable IOMMU or is the Update Assistant's advice out of date?

 

Thanks!

[JorgeB]

1 hour ago, writablevulture said:

but I understand that the primary purpose of the 6.10.3 release was to fix that issue as

Yes, perfectly to safe to upgrade now, @Squidis that warning still there or maybe is he using an old release?

[Squid]

Thanks @JorgeB  New version available.

[writablevulture]

6 hours ago, Squid said:

New version available.

I can confirm the issue is no longer present in latest. Thanks!

[deadnote]

On 8/21/2022 at 3:45 PM, Squid said:

Its your docker log that's spamming /var/log with something.  Unfortunately it appears that diagnostics doesn't include the rotated docker log files, some can't tell what's up with it.  You'll have to reboot, wait an hour or two and then post a new set of diagnostics

I updated to 6.10.3 and rebooted my server.

Here is a new diagnostics 3 hours after reboot

tower-diagnostics-20220829-2107.zip

[Dustiebin]

On 8/3/2022 at 4:50 PM, Dustiebin said:

I will check this later. Many thanks!

Update 

Eventually got a chance to look at this. 

Tried the edit method first and this stopped me seeing the server entirely.

So removed the flash, removed the network config, reinstated flash and booted up.

Server back 9nline with new IP and when I check no message telling me more than one IP 

Many thanks for your help. 

[diehard2k9]

On 8/24/2022 at 11:57 AM, dlandon said:

 

In my case:

 

Click on the 'Testing' text when the drive is unmounted and change that to 'TEAM4TB'.

I will try that but I have to upgrade the UNRAID server. I got new hard drives and I have to change the setup and move all the files and data to XFS raid10 if I can get it to work.  As for changing that label to "TEAM4TB"  I think I just tried to point it to the "unassigned.devices: Successfully mounted 'nvme0n1p1' on '/mnt/disks/112110050430099'" where I can see my files but PLEX would not show up. it was running but no metadata or my files was there.  I will have to do a teardown now that I got the new hard drives and am changing the filke system and putting it into a new box.

[diehard2k9]

On 8/24/2022 at 11:57 AM, dlandon said:

 

In my case:

 

Click on the 'Testing' text when the drive is unmounted and change that to 'TEAM4TB'.

OK DUDE YOU ROCK!

I was ok let me change this real quick just to say I did it and it didnt work.  Thanks alot man it's back up and running. Too bad I have to tear everything down now to add new file system and hard drives!

[trurl]

On 8/24/2022 at 6:05 PM, randommonth said:

4:40am

This is the default mover schedule.

[Shehan]

On 8/15/2022 at 4:51 PM, Squid said:

hmm.  I'd have to look into this.  Nothing super obviously corrupted, but FCP is finding something, so somewhere there is something....

so I made a new USB as it says in

https://unraid.net/buy-genuine-license
 

but still its giving me the error
Possible rootkit or malware detected Rootkits can introduce viruses / malware to your system. Post your diagnostics in the forum for more assistance or email [email protected]

sapphire-diagnostics-20220831-1642.zip

[JorgeB]

7 minutes ago, Shehan said:

but still its giving me the error

Delete key.key from the flash drive config folder and reboot.

[hansolo77]

On 8/28/2022 at 1:10 PM, hansolo77 said:

FCP has been running great with it's quick checks, but lately when I do an extended test I'm getting some errors.

 

The error "section" is labeled:

 

I know this is kind of a generic section.  I do use Sonaar/Radaar, but many of the files that are in error are not in the paths those dockers use.  Some of them are, but not all.

 

For instance:

I have a computer that creates a daily backup using Macrium.  I created a network share for it to store the files in.  I thought I had the share set up right, but maybe not.  The Macrium software requires me to provide a username/password to access the share when I do a restore, the anonymous access doesn't work in the recovery environment.  I think this might be what's causing the problem here.  It writes with the ownership of the user that will be accessing it during restore.  So, I think these might be false/positives.

 

Another series of files I'm getting issues with, is the random Sonarr/Radarr finds.  Most of them are coming up as either "  nobody/users (99/100)  0640  " or "  nobody/users (99/100)  0660  "  Since it's saying that might be a permission problem on the new downloads, it bugs me why it's a "random" appearance.  What settings should I be using for those dockers?  For instance, in the docker config for Sonarr, it is set to use "Key 1 (PUID) = 99" and "Key 2 (PGID) = 100".  Then in the docker itself, under "Settings->Media Management", I have it set to NOT set permissions, the default setting says "755", and "chown group" is blank".  Should I be changing anything here?

 

Thanks guys!  Love Unraid, and this plugin! 

 

While still waiting for a reply, I did a thing.  It's nothing new, I've done it many times before.  I went into the TOOLS tab and ran the "Docker Safe New Perms" tool.  After that I rebooted and ran another extended test.  Now it's saying "No problems found".  I wouldn't think much of this, except for that nothing has changed "setup-wise".  My dockers and shares still have the same permissions they did before, and new files are added daily.  My Macrium backups are daily with multiple types done through-out the week.  The "ARR" dockers are always grabbing things.  So I'm lost.  Why would it be throwing up alerts when I run a test every couple of months without making any changes and then again not have ANY problems for days?  Very confusing.