geonerdist

That's sort of what I was guessing, just surprised that I have not seen this warning until recently. Just sort of started happening.

I've recently started experiencing the following error. Does anyone know if this is a Cloudberry or Unraid issue? I have done a bit of Googling but cannot seem to find a resolution for this.

Windows is still running check disk on my new drive. I've got the old drive plugged in to a USB 2.0 port and ran several short SMART tests in unraid (this would cause UD to hang before) without issues and currently running my backup. Must be a USB 3.0 thing. Anyways thanks again!

Sounds like a plan. Thanks.

This and the last one were external USB disks. Last one was from Seagate and this one is from WD. I'm beginning to think maybe it's not the disks or cables (using different cables this time too). What are the chances it could be the USB ports? I was going to try one of my front USB ports on my server when I have some time later.

well isn't that some luck! probably explains why the Windows check disk I ran over night was stuck on 6% this morning. Thanks!

Well Unassigned Devices seems to have hung again. We previously thought that my external drive that is my local backup of the server was causing it to hang because of disk errors. Tonight I attached a new disk that passed a smart test and it looks like the whole thing is about to hang again. One core is maxing out and it's moving around until everything is locked up. tower-diagnostics-20200311-1750.zip

Well now the saga continues. I unmounted the disk and remembered it was plugged in with a USB extension. Got rid of that and plugged it directly in to the server. Tried both USB3.0 ports (and a USB 2.0 after downloading the attached diagnostics) and am unable to mount and it throws warnings in the log. I'm going to plug it in to my windows machine and see what happens. tower-diagnostics-20191215-0350.zip

It is one of these.

Thanks for making the clarification. Potentially there could be some issues with the drive enclosure and not the drive itself, previously there were smart errors. So now I’m confused. @dlandonand @Squid is there anything else I can do to help troubleshoot this? I’m considering tuning another full smart scan on this drive again and try to get diagnostics via terminal.

I managed to get UD to hang, tried downloading diagnostics before I rebooted but it would never download the zip file. Previously errors were found on my seagate external drive that seemed to be the culprit and I am just hoping we can confirm that the drive is indeed bad and I need to get rid of it. I started to do a full smart scan of that drive yesterday and let it run. This morning UD was hung up. So I think that's probably the issue but wanted to be sure. tower-diagnostics-20191213-1658.zip

Thanks! I updated UD and have not seen it hang yet.

Good catch, thanks....better brush up on my smart report skills. Would it matter if I pulled the diagnostics after I had rebooted and uninstalled -UD? I'm going to see if it'll hang again and get diagnostics downloaded before it becomes completely unresponsive. Thanks again!

Thought I attached it to my original response. tower-diagnostics-20191127-2342.zip

@mustava Did you ever find out what was the issue? I was running 6.5.3 for a long time and every time I tried to upgrade this would happen. I started with a new USB device to see if that was the issue and this started again but I was able to catch some signs that it was UD. I didn't see any replies or solutions to this. I have since uninstalled UD.

I am fighting with this issue again, hoping now that some time has passed that someone else may be experience weird permissions problems as I have described.

@SlrG Apologies for the lack of response. So far I have not seen this error lately. But it might being mask by some ACPI errors in the log that the Gen8 MicroServer is prone to, so that is my current project. But I'll be coming back to this soon. I'll give those a shot when I come back around to this.

I finally got around to testing this out...I use my FTP a lot more than I thought when I first set it up. Anyways I first disabled the server, then disabled ProFTPd, the uninstalled the plugin and still get this error when logging in to the UI. Baffling...but as you all have said I don't think it's a problem at all...just looks scary on the System Log with all that red.

@SlrG I haven't done any of the extra security stuff that's been enabled in 6.4. I have always had a password set for the root user. I only have two users root and mine, there is no ftpuser. Ftpuser is just a keyword added to my personal user account to enable that to login to my FTP share. I'm planning on removing the ProFTPd plugin this weekend to see what might happen.

After upgrading the issue persists. Prior to the upgrade I disabled mover logging and the server has only been up for less than 13 minutes when I downloaded my diags. The errors appeared at 19:19. Thanks for the reply @ljm42. I was thinking it was an issue with the plugin except for the fact that this error appears only when I log in/out of the web UI. tower-diagnostics-20180206-1920.zip

I did notice there was an update for the ProFTPd plug in so I installed that and logged out of the Web UI and logged back in and the log shows this now: Feb 5 18:19:59 Tower nginx: 2018/02/05 18:19:59 [error] 4714#4714: *257229 user "logout" was not found in "/etc/nginx/htpasswd", client: 192.168.1.144, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.3" Feb 5 18:19:59 Tower nginx: 2018/02/05 18:19:59 [error] 4714#4714: *257229 user "logout" was not found in "/etc/nginx/htpasswd", client: 192.168.1.144, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.3" Feb 5 18:19:59 Tower nginx: 2018/02/05 18:19:59 [error] 4714#4714: *257229 user "ftpuser" was not found in "/etc/nginx/htpasswd", client: 192.168.1.144, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.3" Feb 5 18:20:01 Tower nginx: 2018/02/05 18:20:01 [error] 4714#4714: *257229 user "ftpuser" was not found in "/etc/nginx/htpasswd", client: 192.168.1.144, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.3"

I upgraded to 6.4 recently and starting yesterday I noticed some weird entries in my log, shown below. They only appear in the log when I login to the web UI. the IP of 144 is the computer I'm on right now. I do have the ProFTPd plugin and various dockers, but nothing has changed since I started seeing this. I can pull diagnostics if needed but was mostly curious to see if any one has seen this or may know what it means. My search of the forum and internet revealed nothing that I thought was relevant. Feb 5 18:13:30 Tower nginx: 2018/02/05 18:13:30 [error] 4714#4714: *256266 user "ftpuser" was not found in "/etc/nginx/htpasswd", client: 192.168.1.144, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.3" Feb 5 18:13:32 Tower nginx: 2018/02/05 18:13:32 [error] 4714#4714: *256266 user "ftpuser" was not found in "/etc/nginx/htpasswd", client: 192.168.1.144, server: , request: "GET /Main HTTP/1.1", host: "192.168.1.3"

I did a quick search of the forum for this, has any one had this occur? I don't see an advanced parameter that can be updated like the memory allocation one. For searching purposes, "CrashPlan for Small Business is exceeding inotify's max watch limit." and "Real-time file watching cannot work properly. The inotify watch limit needs to be increased on the host."

I updated the docker without any issues today, just had to sign it and away it went. The new interface is terrible...but so far it's working.

Agreed, thanks to all those that have contributed to this. I suppose we shall just have to see how it unfolds.