June 18, 20233 yr Author 6 hours ago, CkChong said: Current version not compatible with Unraid latest version 6.12.0? When click on it just hanging on scanning screen without moving. 100% it is compatible. Does it show any scan in progress or just the popup not doing anything at all? If you give it a couple of minutes and then go back to FCP it will have the results.
June 19, 20233 yr 3 hours ago, Squid said: 100% it is compatible. Does it show any scan in progress or just the popup not doing anything at all? If you give it a couple of minutes and then go back to FCP it will have the results. After reboot Unraid again it back to work. Thank you.
June 19, 20233 yr 14 hours ago, CkChong said: When click on it just hanging on scanning screen without moving. Patience young Padawan! 🙂 Even on my rather fast box it takes MINUTES for the scan. Downloading the list of banned plugins and checking the versions of all installed apps takes a lot of time (the "Apps" window does it a lot faster). If you watch carefully, the last line of the text changes a bit now and then, but rarely and with loooong pauses between them. So, fire up the fix-scan, make yourself a coffee (slowly), wait until it got a bit cooler then sip it one by one... Then the scan should be finished and the results will be waiting for you. (And yes, this part needs some polishing and speedups)
June 23, 20233 yr I am getting the follow errors about cache pool but when checking the settings of the shares this is not the case (only one screenshot for brevity but have checked all of them) unraid-nas-diagnostics-20230609-0429.zip
June 23, 20233 yr 7 minutes ago, AngryPig said: I am getting the follow errors about cache pool but when checking the settings of the shares this is not the case (only one screenshot for brevity but have checked all of them) unraid-nas-diagnostics-20230609-0429.zip these screenshots do not agree with the share configuration files are that are in the diagnostics. The configuration files in the diagnostics for those shares all reference a pool called ‘cache’.
June 23, 20233 yr 2 hours ago, itimpi said: these screenshots do not agree with the share configuration files are that are in the diagnostics. The configuration files in the diagnostics for those shares all reference a pool called ‘cache’. Edit: In hindsight realized this is a question for the forum not for this thread. I will create a new post now that this issue has been discovered I took the screenshots today but they have been that way for many months. I do not even recall creating a pool by that name (unless I did and changed it in the first week of setup almost a year ago). How can the GUI show something different to the diagnostics and how can I fix it? Edited June 23, 20233 yr by AngryPig Moving question to new thread
June 23, 20233 yr Author 2 hours ago, itimpi said: these screenshots do not agree with the share configuration files are that are in the diagnostics. The configuration files in the diagnostics for those shares all reference a pool called ‘cache’. Something weird that I have to look at. The shares reference "cache-backup" which is non-existant, but the message says "cache"
June 24, 20233 yr 8 hours ago, Squid said: Something weird that I have to look at. The shares reference "cache-backup" which is non-existant, but the message says "cache" Fingers crossed it is a simple solution but I would doubt it - I created a thread here if you find the solution Edit: Solution provided in the thread. I just needed to re-apply the Share settings. I must have made a change when I set the server up and caused an issue Edited June 24, 20233 yr by AngryPig
June 27, 20233 yr I had a thought for a potential check that could be added although it may be too much work for the benefit. Given that it is recommended to keep a minimum free space equivalent to the largest intended file of a share, perhaps a warning that checks for the largest file on a share and checks if that is bigger than the minimum free space. Therefore if someone sets up the share too low and starts putting large files on it, they will have a warning suggesting to increase the size. Other than the time to implement this, I could also see this as possibly being too long to check for, especially on larger arrays with lots of files (unless there is a fast way to get all file sizes)
June 30, 20233 yr After update to 6.12.2 I have warning "Possibly out of inotify watches". Using Tips and tweaks plugin I changed setting, but the warning is still persist. Current settings: Max User Watches = 8388608 Current User Watches = 6085403 Available User Watches = 2303205 Also I never had this warning before. 6.12.2 bug? Edited June 30, 20233 yr by SuberSeb
July 3, 20233 yr Is it possible to have "FixCommonProblems" plug-in scan for any dmesg errors or warnings and if found, surface them? See this thread for reference. Or, if there is a better plug-in for that, feel free to enlighten me. Thanks!
July 3, 20233 yr Author Likely outside the scope of FCP and best to run a script to handle this. Things like SATA connection errors etc would already be handled via Unraid's own notification system.
July 19, 20232 yr 1 hour ago, accelaptd said: How do I actually get rid of these? They're not on my plugins list. I would expect them to be listed on your Plugins tab. If not, please upload your diagnostics.zip (from Tools -> Diagnostics) Note that is really not advised to run rc releases so long. You should upgrade to 6.11.5 or 6.12.3
July 20, 20232 yr Error (re)installing, tried to update to latest but it failed and in my haste I uninstalled and tried to reinstall but get the following error: plugin: downloading: fix.common.problems-2023.07.16-x86_64-1.txz ... plugin: fix.common.problems-2023.07.16-x86_64-1.txz download failure: Generic error Executing hook script: post_plugin_checks How to fix? nas-syslog-20230720-1744.zip
July 20, 20232 yr 2 hours ago, denzo said: Error (re)installing, tried to update to latest but it failed and in my haste I uninstalled and tried to reinstall but get the following error: plugin: downloading: fix.common.problems-2023.07.16-x86_64-1.txz ... plugin: fix.common.problems-2023.07.16-x86_64-1.txz download failure: Generic error Executing hook script: post_plugin_checks How to fix? Your flash drive has errors, looks like that is preventing the file from being written to it: Jul 19 13:01:31 NAS kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 400e4138) Jul 19 13:01:31 NAS kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 400e4138) Jul 19 13:01:31 NAS kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 400e4138) Jul 19 13:02:31 NAS kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 200e0e43) Jul 19 13:02:31 NAS kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 200e0e43) Jul 19 13:02:31 NAS kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 200e0e43) Jul 19 13:02:31 NAS kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 400e4138) I'd recommend putting the drive in a Windows computer and running chkdsk, It may work after that. You should also make a backup and get a new flash drive on order ASAP in case this fails completely, in which case see https://docs.unraid.net/unraid-os/manual/changing-the-flash-device
July 22, 20232 yr On 7/20/2023 at 2:11 PM, ljm42 said: Your flash drive has errors, looks like that is preventing the file from being written to it: Jul 19 13:01:31 NAS kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 400e4138) Jul 19 13:01:31 NAS kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 400e4138) Jul 19 13:01:31 NAS kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 400e4138) Jul 19 13:02:31 NAS kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 200e0e43) Jul 19 13:02:31 NAS kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 200e0e43) Jul 19 13:02:31 NAS kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 200e0e43) Jul 19 13:02:31 NAS kernel: FAT-fs (sda1): error, fat_get_cluster: invalid start cluster (i_pos 0, start 400e4138) I'd recommend putting the drive in a Windows computer and running chkdsk, It may work after that. You should also make a backup and get a new flash drive on order ASAP in case this fails completely, in which case see https://docs.unraid.net/unraid-os/manual/changing-the-flash-device Thanks for the reply. I followed your advice and CHKDSK appears to have fixed the issue with my USB drive. I went ahead and created a backup and a (new) USB drive just in case things go bad though. Appreciate you taking time to help me out, cheers!
July 28, 20232 yr The plugin does not scan, it stays on this screen indefinitely. Any solution ? Unraid 6.12.3
July 29, 20232 yr Author Works for me no problem. I'd suggest closing all browser tabs open to the server. But, after a couple of minutes even sitting on that Scanning popup, the scan would still continue in the background and the next time you load up FCP it should be populated.
July 30, 20232 yr Quick question: Any reason that FCP still tells me that I have multiple NICs on the same IP network? One of the cards is passed through to a VM. While I've got that warning set to "ignored", it's a valid configuration.
July 30, 20232 yr I just noticed this FCP notification and just wanted to check on it. I don't have any SSH ports open to the server I also don't have this machine in the DMZ.. On Jul 18 there were 17 invalid login attempts. This could either be yourself attempting to login to your server (SSH / Telnet) with the wrong user or password, or you could be actively be the victim of hack attacks. A common cause of this would be placing your server within your routers DMZ, or improperly forwarding ports. This is a major issue and needs to be addressed IMMEDIATELY NOTE: Because this check is done against the logged entries in the syslog, the only way to clear it is to either increase the number of allowed invalid logins per day (if determined that it is not a hack attempt) or to reset your server. It is not recommended under any circumstance to ignore this error tower-diagnostics-20230730-1336.zip
July 30, 20232 yr Author Jul 18 21:22:35 Tower sshd[19990]: Connection from 192.168.1.41 port 52386 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:35 Tower sshd[19990]: Received disconnect from 192.168.1.41 port 52386:11: [preauth] Jul 18 21:22:35 Tower sshd[19990]: Disconnected from 192.168.1.41 port 52386 [preauth] Jul 18 21:22:42 Tower sshd[20321]: Connection from 192.168.1.41 port 52441 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:42 Tower sshd[20321]: Invalid user from 192.168.1.41 port 52441 Jul 18 21:22:42 Tower sshd[20321]: Failed none for invalid user from 192.168.1.41 port 52441 ssh2 Jul 18 21:22:42 Tower sshd[20321]: Received disconnect from 192.168.1.41 port 52441:11: [preauth] Jul 18 21:22:42 Tower sshd[20321]: Disconnected from invalid user 192.168.1.41 port 52441 [preauth] Jul 18 21:22:42 Tower sshd[20325]: Connection from 192.168.1.41 port 52442 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:42 Tower sshd[20325]: Invalid user admin from 192.168.1.41 port 52442 Jul 18 21:22:42 Tower sshd[20325]: pam_unix(sshd:auth): check pass; user unknown Jul 18 21:22:42 Tower sshd[20325]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.41 Jul 18 21:22:45 Tower sshd[20325]: Failed password for invalid user admin from 192.168.1.41 port 52442 ssh2 Jul 18 21:22:46 Tower sshd[20325]: Received disconnect from 192.168.1.41 port 52442:11: [preauth] Jul 18 21:22:46 Tower sshd[20325]: Disconnected from invalid user admin 192.168.1.41 port 52442 [preauth] Jul 18 21:22:46 Tower sshd[20567]: Connection from 192.168.1.41 port 52474 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:46 Tower sshd[20567]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.41 user=root Jul 18 21:22:48 Tower sshd[20567]: Failed password for root from 192.168.1.41 port 52474 ssh2 Jul 18 21:22:48 Tower sshd[20567]: Received disconnect from 192.168.1.41 port 52474:11: [preauth] Jul 18 21:22:48 Tower sshd[20567]: Disconnected from authenticating user root 192.168.1.41 port 52474 [preauth] Jul 18 21:22:48 Tower sshd[20612]: Connection from 192.168.1.41 port 52518 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:48 Tower sshd[20612]: Invalid user user from 192.168.1.41 port 52518 Jul 18 21:22:48 Tower sshd[20612]: pam_unix(sshd:auth): check pass; user unknown Jul 18 21:22:48 Tower sshd[20612]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.41 Jul 18 21:22:51 Tower sshd[20612]: Failed password for invalid user user from 192.168.1.41 port 52518 ssh2 Jul 18 21:22:51 Tower sshd[20612]: Received disconnect from 192.168.1.41 port 52518:11: [preauth] Jul 18 21:22:51 Tower sshd[20612]: Disconnected from invalid user user 192.168.1.41 port 52518 [preauth] Jul 18 21:22:51 Tower sshd[20838]: Connection from 192.168.1.41 port 52567 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:51 Tower sshd[20838]: Invalid user admin from 192.168.1.41 port 52567 Jul 18 21:22:51 Tower sshd[20838]: Failed none for invalid user admin from 192.168.1.41 port 52567 ssh2 Jul 18 21:22:51 Tower sshd[20838]: Received disconnect from 192.168.1.41 port 52567:11: [preauth] Jul 18 21:22:51 Tower sshd[20838]: Disconnected from invalid user admin 192.168.1.41 port 52567 [preauth] Jul 18 21:22:51 Tower sshd[20843]: Connection from 192.168.1.41 port 52570 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:51 Tower sshd[20843]: Invalid user sysadm from 192.168.1.41 port 52570 Was this you? All from 192.168.1.41 What is that on your network?
July 30, 20232 yr 13 minutes ago, Squid said: Jul 18 21:22:35 Tower sshd[19990]: Connection from 192.168.1.41 port 52386 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:35 Tower sshd[19990]: Received disconnect from 192.168.1.41 port 52386:11: [preauth] Jul 18 21:22:35 Tower sshd[19990]: Disconnected from 192.168.1.41 port 52386 [preauth] Jul 18 21:22:42 Tower sshd[20321]: Connection from 192.168.1.41 port 52441 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:42 Tower sshd[20321]: Invalid user from 192.168.1.41 port 52441 Jul 18 21:22:42 Tower sshd[20321]: Failed none for invalid user from 192.168.1.41 port 52441 ssh2 Jul 18 21:22:42 Tower sshd[20321]: Received disconnect from 192.168.1.41 port 52441:11: [preauth] Jul 18 21:22:42 Tower sshd[20321]: Disconnected from invalid user 192.168.1.41 port 52441 [preauth] Jul 18 21:22:42 Tower sshd[20325]: Connection from 192.168.1.41 port 52442 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:42 Tower sshd[20325]: Invalid user admin from 192.168.1.41 port 52442 Jul 18 21:22:42 Tower sshd[20325]: pam_unix(sshd:auth): check pass; user unknown Jul 18 21:22:42 Tower sshd[20325]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.41 Jul 18 21:22:45 Tower sshd[20325]: Failed password for invalid user admin from 192.168.1.41 port 52442 ssh2 Jul 18 21:22:46 Tower sshd[20325]: Received disconnect from 192.168.1.41 port 52442:11: [preauth] Jul 18 21:22:46 Tower sshd[20325]: Disconnected from invalid user admin 192.168.1.41 port 52442 [preauth] Jul 18 21:22:46 Tower sshd[20567]: Connection from 192.168.1.41 port 52474 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:46 Tower sshd[20567]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.41 user=root Jul 18 21:22:48 Tower sshd[20567]: Failed password for root from 192.168.1.41 port 52474 ssh2 Jul 18 21:22:48 Tower sshd[20567]: Received disconnect from 192.168.1.41 port 52474:11: [preauth] Jul 18 21:22:48 Tower sshd[20567]: Disconnected from authenticating user root 192.168.1.41 port 52474 [preauth] Jul 18 21:22:48 Tower sshd[20612]: Connection from 192.168.1.41 port 52518 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:48 Tower sshd[20612]: Invalid user user from 192.168.1.41 port 52518 Jul 18 21:22:48 Tower sshd[20612]: pam_unix(sshd:auth): check pass; user unknown Jul 18 21:22:48 Tower sshd[20612]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.168.1.41 Jul 18 21:22:51 Tower sshd[20612]: Failed password for invalid user user from 192.168.1.41 port 52518 ssh2 Jul 18 21:22:51 Tower sshd[20612]: Received disconnect from 192.168.1.41 port 52518:11: [preauth] Jul 18 21:22:51 Tower sshd[20612]: Disconnected from invalid user user 192.168.1.41 port 52518 [preauth] Jul 18 21:22:51 Tower sshd[20838]: Connection from 192.168.1.41 port 52567 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:51 Tower sshd[20838]: Invalid user admin from 192.168.1.41 port 52567 Jul 18 21:22:51 Tower sshd[20838]: Failed none for invalid user admin from 192.168.1.41 port 52567 ssh2 Jul 18 21:22:51 Tower sshd[20838]: Received disconnect from 192.168.1.41 port 52567:11: [preauth] Jul 18 21:22:51 Tower sshd[20838]: Disconnected from invalid user admin 192.168.1.41 port 52567 [preauth] Jul 18 21:22:51 Tower sshd[20843]: Connection from 192.168.1.41 port 52570 on 192.168.1.5 port 22 rdomain "" Jul 18 21:22:51 Tower sshd[20843]: Invalid user sysadm from 192.168.1.41 port 52570 Was this you? All from 192.168.1.41 What is that on your network? Just checked, that is a machine on the network that I did copy files from UR. I don't recall getting auth failures to llogin from that machine. But, its good to know. I'll reboot it in case its still trying to reach out to UR. Thanks
July 31, 20232 yr On 6/18/2023 at 4:47 PM, Squid said: 100% it is compatible. Does it show any scan in progress or just the popup not doing anything at all? If you give it a couple of minutes and then go back to FCP it will have the results. I got this too. You get the "Now Scanning your system for common problems." popup, but it never goes away. Reloading later doesn't show any completed results either. Multiple computers, both with and without Incognito. Previous version worked fine. Edited July 31, 20232 yr by OverlordQ
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.