Jump to content

dlandon

Community Developer
  • Posts

    10,399
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by dlandon

  1. I need more information. Post a system diagnostics and I'll take a look. Open files is helpful when shutting down the server is troublesome. Open files shows files opened that might cause the shutdown to hang. Files Activity can catch file activity that potentially spins up a disk.
  2. The ease of implementing a feature is not the issue. I don't add a feature that only has value for one user or solves a problem that should be solved in another way, especially when the UD page real estate is at a premium.
  3. You shouldn't be having the problem with UD hanging up when a SMB or NFS share goes away.
  4. And then it would spin back up. Figure out why it is spinning up to keep it from doing that.
  5. I don't see any value in this. UD issues a 15 minute standby/sleep command to a drive and a drive will spin up as needed when accessed. There is no need to do a manual spin up/down from the GUI.
  6. On two occasions of shutting down my main server and test server I've gotten a message on the console. stopping_svcs ca.turbo line 14 unknown... I didn't get the message exactly right because it flew by so fast, but you get the idea. There wasn't anything in the log that indicated any issue. I don't think it's necessarily a big deal, but might be an indication of a gremlin in hiding.
  7. I would uninstall UD and delete the /flash/config/plugins/unassigned.devices directory and then re-install and start over. Your disk configuration is missing.
  8. I don't see in the log where UD mounted any drives. The nvme disk does not have the '+' and the drive says it's mounted, but it doesn't show a Temp, or FS; Look at the smart report on the drive and see if there are any issues. Download the uD log and post it. Also post your /flash/config/plugins/unassigned.devices/unassigned.devices.cfg file. It looks like the UD configuration for that drive is corrupted.
  9. I found this in the syslog: Mar 22 16:26:28 Excelsior inotifywait[11860]: Failed to watch /mnt/disk11; upper limit on inotify watches reached! Mar 22 16:26:28 Excelsior inotifywait[11860]: Please increase the amount of inotify watches allowed per user via `/proc/sys/fs/inotify/max_user_watches'. Install the Tips & Tweaks plugin and increase the 'Max user Watches'. I need to look into this further though because File Activity should not show as running.
  10. Your drive arrangement is not the problem. Without any error information I don't know how to fix the problem either.
  11. How about some more information. What version of unRAID? What version of UD? That problem should have been fixed in UD.
  12. His vars shows 24 disks, so I just assumed that's what he had in his system. Strange setup but File Activity should work fine.
  13. You have a problem not related to File Activity. Your diagnostics shows 24 disks, but they are not all mounted. Sort that out and File Activity should work.
  14. File Activity is not including all of your disks. Please post the result of this command 'ls /mnt/'.
  15. Got a minor typo in one of the FCP log messages: Mar 20 18:39:29 Tower root: Fix Common Problems: Error: Probable 32 Big package ntfs-3g-2010.3.6-i486-1.txz found on the flash drive in the packages folder I think you meant to say "32 Bit package..." not "32 Big package...". I'm not sure a "Big" package is necessarily a problem.
  16. I see several things. Clean these up and then see if UD will mount the disk. You have unmenu in the /boot/config/plugins. I'd remove that. It is not necessary and may have some incompatibilities with the latest unRAID version. drwxrwxrwx 2 root root 16384 Mar 8 07:29 unmenu_install1371 -rwxrwxrwx 1 root root 3864 Mar 8 07:30 unmenu_install1371.zip You are installing a wrong version of ntfs-3g. Remove it. The proper version is already installed in unRAID. Mar 20 18:39:29 Tower root: Fix Common Problems: Error: Probable 32 Big package ntfs-3g-2010.3.6-i486-1.txz found on the flash drive in the packages folder Mar 20 18:39:30 Tower root: Fix Common Problems: Warning: The plugin ntfs-3g.plg is not known to Community Applications and is possibly incompatible with You have a browser open to unRAID when you booted and it's generating errors. Close all when rebooting. This keeps UD from working properly. Mar 20 18:25:38 Tower root: error: plugins/preclear.disk/Preclear.php: wrong csrf_token Mar 20 18:25:40 Tower root: error: plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Why do you have the array autostart disabled? Mar 20 18:25:29 Tower emhttp: autostart disabled You need to pay attention to the Fix Common Problems messages and fix anything it tells you is a problem. Mar 20 18:39:25 Tower root: Fix Common Problems Version 2017.03.19 Mar 20 18:39:27 Tower root: Fix Common Problems: Error: Array is not started Mar 20 18:39:27 Tower root: Fix Common Problems: Error: Plugin Update Check not enabled Mar 20 18:39:29 Tower root: Fix Common Problems: Error: Probable 32 Big package ntfs-3g-2010.3.6-i486-1.txz found on the flash drive in the packages folder Mar 20 18:39:30 Tower root: Fix Common Problems: Warning: The plugin ntfs-3g.plg is not known to Community Applications and is possibly incompatible with Fix these and then try to mount your disk. If it still doesn't mount, download and post the UD log.
  17. Please post your diagnostics and the /tmp/file.activity/file.activity.disks file.
  18. This is the right place to post your issue. You have not provided enough information. Please post your diagnostics. The ntfs3g drivers are now included in unRAID.
  19. File Activity is not starting and I can't see why. Be sure you have the latest version of the plugin installed. Go to a command line and run this command: /usr/local/emhttp/plugins/file.activity/scripts/inotify.file.activity See if you get any errors. If it looks like the program is hanging, then it is running. Ctrl-C to stop the program. Let me know the results.
  20. It looks like File Activity is assuming the Unassigned Devices plugin is installed and you are not using it. I will have to make an update to fix this.
  21. The version of UD you were running is not compatible with unRAID 6.3 because of some security changes made to unRAID. If you look at your syslog you will see some errors concerning "csrf_token". Before asking for help on any plugins, be sure you have updated to the latest version of the plugin. This saves you some headaches and time from everyone on supporting an incompatibility solved by a plugin update.
×
×
  • Create New...