• Content Count

  • Joined

  • Last visited

Community Reputation

6 Neutral

About Progeny42

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. As of 7 hours ago, I'm getting the following alert pinged to me via email from Unraid: /bin/sh: line 1: 28292 Killed /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null This is occurring every 25-30 minutes or so. The Unraid GUI is broken a bit now too; I can navigate between pages, but the syslog won't load, sometimes the Main tab won't load areas, the Docker and VMs tab won't load at all, and I cannot update Plugins. The day before, Unraid became unresponsive around 1:00am, and was no longer displaying an output, so I had to hard reset it
  2. I am also having issues as of late as identifed by the File Activity tool, where Nextcloud is accessing an /appdata_{instanceId} directory and /files_encryption directory under /mnt/diskX/Nextcloud. This is causing a few of my disks to remain spun up. This did not use to be an issue. I use Nextcloud as a target for Backup, so I cannot change the share to use the cache. The Container is correctly configured using /data => /mnt/user/Nextcloud and /config => /mnt/user/appdata/nextcloud
  3. *Bump* If 9p is a bad way to mount a drive, then would anyone care to explain what the correct way is for best performance?
  4. I reseated the LSI card, the breakout SAS to SATA cable, and the SATA Power cable to the HDD. I'm still having the same issues as described, with the same behaviour shown in the log etc.
  5. Okay, I'll double check all the connections tomorrow. Apologies; Have attached them to this response if they are still necessary. I did some further investigation pending my hardware checks tomorrow; If when the drive is spun down (according to Unraid) I go to spin it up by selecting the grey circle on the Main tab, it "spins up" in 1 second. On the other hand, if I then spin it down, and then up again, each operation takes ~8 seconds. I've tried to demonstrate this in the Unraid terminal; If I issue a spindown command to a different disk that is spun
  6. My concern isn't the GUI so much as it is that the LSI card is keeping the drive spun up near constantly
  7. Unraid Version: 6.8.3 LSI SAS 2008: Firmware: Product ID: SAS9211-8i BIOS: NVDATA: I recently purchased the above LSI card to add additional SATA drives to my server. At the moment, it has 1 HDD and 1 SSD attached. For some reason, the HDD is being spun up, but Unraid does not know about it. Note I have 5 disks + 2 parity. The LSI attached drives are shown below: SCSI Devices: [9:0:0:0]disk ATA INTEL SSDSC2BF24 LH6i /dev/sdb 240GB [9:0:1:0]disk ATA WDC WD80EDAZ-11T 0A81 /dev/sdc 8.00TB I've at
  8. @santiman717 Can you post a screenshot of the Container's configuration? (Remove or blur any emails or sensitive info)
  9. I've been trialling Nextcloud as a cloud backup service for myself, and if successful, my family which live remotely. I'm using Duplicati to perform the backups, but that's not the point of this guide. The point is that when I backup files to Nextcloud, the Docker Image slowly fills up. I've never had it reach a point where the Image reaches 100%, but it's probably not a fun time. After searching the internet for hours trying to find anything, I eventually figured out what was required. For context, I'm running Nextcloud behind a Reverse Proxy, for which I'm
  10. Hmm not sure I can help you with that. It's not my software, I just made a template for it in unraid. Try contacting Snipe-IT directly about the issue
  11. That'll likely be your problem. That App Key is too long. Make sure you use this command to generate a key in the Unraid terminal: openssl rand -base64 32 Then in the Container Edit menu, put: base64:yourappkeyhere
  12. @Korshakov what is your App Key? This is the only time I've seen that issue.
  13. @Dimtar Hey glad you figured it out. Yes, you will experience an error if the App Key is not valid as far as the Container is concerned. There's also nothing the log file to indicate that the App Key is the cause of the problem, so it's mostly just a trial an error thing. I'll add it to the original post as an update to warn people.
  14. @argash Hey, glad to hear it helped someone! I've just checked CA, only saw my template in there, are you sure the second template isn't a previous install of yours? Out of interest, does your SMTP setup work?
  15. Snipe-IT is an Asset Management System. This guide will help you to install it and get it running. Database Backend Installing MariaDB Snipe-IT requires MySQL or MariaDB as its database backend. We’ll be using MariaDB. Head over to Community Applications and pull MariaDB. I left the Host Port as 3306, but ensure it doesn’t conflict with any existing containers. If you change it you will need to use the custom value in the Snipe-IT configuration later. You’ll need to setup a root password in Key 3, and it must be at least 4 characters long. Now