Jump to content

Enver

Members
  • Content Count

    65
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Enver

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Hello, Has anyone installed the ARECA driver for unRAID 8.6.3? You can download the latest driver here: http://www.areca.us/support/s_unRAID/driver/unRAID-6.8.3.zip ARECA does provide instructions but for me they don't make sense. They refer to zip files that don't exist and want you create a bootable USB for some reason? I would have thought booting into unRAID via USB as normal would be the way to go, to skip the USB bootable key creation part and skip to step 5 in the following instructions. The problem is the ARCMSR driver is in use when I attempt "rmmod arcmsr" via cmdline. Can someone please provide some guidance how to do this? I have an ARECA 1883ix-12 card the temperatures and SMART info has never worked for me, the card in in JBOD mode; my current theory is whatever driver version is in the vanilla version of unRAID 8.6.3 doesn't understand this card; hence my attempt to upgrade to the latest OEM driver. Update device driver for Raid controllers that were not supported by build-in driver ======================================================================================== 1. Extract unRAIDServer-6.8.x-x86_64.zip to an USB flash drive with volume label 'UNRAID'. 2. Extract arcmsr-1.50.0X.00-20200310-unRAID-6.8.x.zip to UNRAID USB flash drive /. 3. Right-click on the file °•make_bootable°¶ and select °•Run as administrator°¶. The °•syslinux°¶ utility will write the Master Boot Record and create a small hidden file named °•ldlinux.sys°¶ on the Flash device, making it bootable. 4. Boot from unRAID USB flash drive. 5. After boot up, login as root. type following commands to update device driver. # rmmod arcmsr # insmod /boot/arcmsr.ko.xz 6. To make new arcmsr.ko.xz driver take effect for next boot, type following command to rebuild bzmodules. # cp /boot/buildbzmod /root # chmod +x buildbzmod # ./buildbzmod # reboot
  2. @SSD Can you please parachute in here and advise as to why triggering udevadm via the below script makes my cache SSD disappear from the drop down list? I am in maintenance mode and am running these lines manually and after executing "udevadm trigger" my cache Samsung NVME SSD disappears from the drop down list; it is however available to the system if I enumerate the SCSCI devices list. cp /boot/60-persistent-storage.rules /lib/udev/rules.d udevadm control --reload-rules udevadm trigger Diagnostics attached; it seems that the host is unable to determine the ID of the /dev/nvme01 Can someone please advise / help with this problem. tower-diagnostics-20200508-0921.zip
  3. Hello Everyone, I have been trying to get my unRAID server to expose the temperature and SMART capabilities of my ARECA 1883 12 port card by following this thread: I followed this guide and included the following in my Go file: #cp /boot/scripts/60-persistent-storage.rules /lib/udev/rules.d #udevadm control --reload-rules #udevadm trigger Upon reboot after having added the above to my Go file the array had stopped because the disks had to be reassigned, no problem and expected as all the SATA and Areca SCSI disks have their serial numbers documented in the GUI and via the Disk Locations plugin. I was able to reassign those no problem. Now the problem: I have two by NVME SSD's one mounted in an M.2 slot on the motherboard for my pass-through disk for my VM and another NVME disk mounted in a PCIE to M.2 board for my unRAID cache. After the reboot after the UDEV utility ran the NVME cards disappeared in the drop down list of available disks and I was unable to reassign the cache drive as it no longer appeared?! They both appear in the SCSI devices list so are still available to the system but are nowhere to be found in the available drop down list. I found this forum article below that describes a similar problem related to the number of pass-through disks for an ARECA card but I am not experiencing this issue as all my pass-through disks are present. This is unexpected behaviour; has anyone experienced this problem? Thanks, Enver
  4. Hello Everyone, I have been trying to get my unRAID server to expose the temperature and SMART capabilities of my ARECA 1883 12 port card by following this thread: I followed this guide and included the following in my Go file: #cp /boot/scripts/60-persistent-storage.rules /lib/udev/rules.d #udevadm control --reload-rules #udevadm trigger Upon reboot after having added the above to my Go file the array had stopped because the disks had to be reassigned, no problem and expected as all the SATA and Areca SCSI disks have their serial numbers documented in the GUI and via the Disk Locations plugin. I was able to reassign those no problem. Now the problem: I have two by NVME SSD's one mounted in an M.2 slot on the motherboard for my pass-through disk for my VM and another NVME disk mounted in a PCIE to M.2 board for my unRAID cache. After the reboot after the UDEV utility ran the NVME cards disappeared in the drop down list of available disks and I was unable to reassign the cache drive as it no longer appeared?! They both appear in the SCSI devices list so are still available to the system but are nowhere to be found in the available drop down list. I found this forum article below that describes a similar problem related to the number of pass-through disks for an ARECA card but I am not experiencing this issue as all my pass-through disks are present. This is unexpected behaviour; has anyone experienced this problem? Thanks, Enver
  5. Hello, I am trying to install Telegraf; I have downloaded the telegraf.conf file from the following location unmodified. https://github.com/influxdata/telegraf/blob/master/etc/telegraf.conf When I copy the DEFAULT configuration file to the following location usr/appdata/telegraf/ and then start the docker I receive the following error in the docker log. 2019-07-27T12:03:58Z I! Starting Telegraf 1.11.3 2019-07-27T12:03:58Z I! Using config file: /etc/telegraf/telegraf.conf 2019-07-27T12:03:58Z E! [telegraf] Error running agent: Error parsing /etc/telegraf/telegraf.conf, line 7: invalid TOML syntax It seems that the default configuration file cannot be parsed?
  6. Brilliant that worked! Thanks so much.
  7. @binhex Thanks for the clarification. I guess I was hoping to elevate privileges when required; I am supposing that isn't possible through the docker container? What about adding 'nobody' user to the Wheel Group and un-commenting the "%wheel ALL=(ALL) ALL" line using visudo? Is the 'nobody' user group completely isolated from the host or is there a way to do what I am suggesting?
  8. Appreciate the advice but in my instance this isn't a contributing factor. I ran permissions the "Docker Safe Fix Permission" operation in tools with no change. To put it into context I have reinstalled Krusader a number of times over the years......different versions of Krusader and unRAID; also deleted the Krusader folder under appdata to be sure and I have never been able to get this feature to work. Is there any prerequisite binaries that is required? I read on another forum that I need the kdesu binary installed?
  9. Hello Everyone, I seem to be unable to load Krusader in Root Mode using the GUI. I have searched over this forum and others but can't seem to find the answer to this. I am sure there is a simple explanation; can someone please advise. Docker is running as PUID 99 / PGID 100. Please see the error below: Thanks, Enver
  10. Hello @gridrunner For simplicity sake I have added back the hash tags for the auth and password lines. Yes, both dockers are running on the same logical network as the NGINX docker. I have restarted, Letsencrypt, Sonarr and Radarr but the behaviour is the same..... How do I check that DNS resolution between dockers is working? <- Its the only thing I can think of that may be contributing to the problem. I would have assumed the default behavior for unRAID was for the host to manage the DNS resolution between docker containers? Let me know your thoughts. Thanks, Enver
  11. Hello @Gridrunner. I have successfully port forwarded the services, mapped the CNAME's to the DNS record in DuckDNS and also verified the certificates are working as per logs. I get the NGINX landing page for both Binhex-Sonarr and Binhex-radarr when I attempt browse to the CNAME's. So quite obviously DNS, CNAME and port fowarding are working. I have double check both config (sonarr.subdomain.conf and radarr.subdomain.conf) files, they appear to be OK. See below extract: # make sure that your dns has a cname set for sonarr and that your sonarr container is not using a base url # to enable password access, uncomment the two auth_basic lines server { listen 443 ssl; server_name sonarr.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_sonarr binhex-sonarr; proxy_pass http://$upstream_sonarr:8989; } } Please advise. Enver
  12. @limetech Hello, Could we please have this error suppressed in 6.4. This is superfluous error with no downsides that I have experienced. It seems to be temperature sensor related; my Areca RAID 6 card is watercooled so its not an issue for me. The error seems to be related to the fact unRAID can't interpret the temperature sensor messages.
  13. Array fails to stop manually through the GUI. It seems the array is waiting for the LibVirt.img file on the cache pool and never exits. Any ideas?
  14. Is there a resolution to this? I have upgraded to 6.4 and every single time I perform a reboot the server claims the last shutdown was unclean. I have increased the shutdown timeout to 120 seconds but am still experiencing the issue.