hoxbox382

Members
  • Posts

    23
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

hoxbox382's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Hello. One of my hard drives had a read error. I've attached diagnostics and ran extended SMART test below. Should I replace the hard drive or just keep an eye on for now? Thank you. microserver-diagnostics-20200514-0257.zip microserver-smart-20200514-0254.zip
  2. Well I figured out my memory problem. Turns out when I was messing with Xen a while back I have the following in my syslinux.cfg label Xen/unRAID OS menu default kernel /syslinux/mboot.c32 append /xen dom0_mem=2097152 --- /bzimage --- /bzroot After changing the "menu default" to label unRAID OS menu default kernel /bzimage append initrd=/bzroot now Unraid can see all the RAM now! I guess I just lived with 2 gb of RAM for the last few years since and didn't notice it now since I run so little docker lol. As for the email problems I went ahead and cleaned out a lot of out of date plugins (that are now included with Unraid) I had before including ssmtp, apcupsd, and powerdown and now emails are now sending! Thank you all for the help.
  3. Ok I'm stumped. I pulled the 2 GB and tried the 8 GB in both Slot 1 and Slot 2 (I only have 2 slots). Both times Unraid still shows "Usable size: 1.8 GiB" even though it sees 8 GiB ram total. Not sure what's going on now. I attached another Diagnostics for what it's worth. microserver-diagnostics-20191117-0119.zip
  4. Yeah I actually have 10gig of RAM but only showing 1.7 usable? (see screenshot). Maybe my RAM went bad? I tried disabling docker and still cannot send any email out. EDIT: Added Output of "dmidecode -t 17" I have 2 GIG and and 8 GIG RAM. It looks like Unraid is only using the 2 GIG RAM. When I get home I will try to swap out the RAM into different slots and see. root@Microserver:~# dmidecode -t 17 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x1100, DMI type 17, 40 bytes Memory Device Array Handle: 0x1000 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 2048 MB Form Factor: DIMM Set: None Locator: PROC 1 DIMM 1 Bank Locator: Not Specified Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 1600 MT/s Manufacturer: HP Serial Number: Not Specified Asset Tag: Not Specified Part Number: 669237-071 Rank: 1 Configured Memory Speed: 1333 MT/s Minimum Voltage: 1.5 V Maximum Voltage: 1.5 V Configured Voltage: 1.5 V Handle 0x1101, DMI type 17, 40 bytes Memory Device Array Handle: 0x1000 Error Information Handle: Not Provided Total Width: 72 bits Data Width: 64 bits Size: 8192 MB Form Factor: DIMM Set: 1 Locator: PROC 1 DIMM 2 Bank Locator: Not Specified Type: DDR3 Type Detail: Synchronous Unbuffered (Unregistered) Speed: 1333 MT/s Manufacturer: HP Serial Number: Not Specified Asset Tag: Not Specified Part Number: 647658-081 Rank: 2 Configured Memory Speed: 1333 MT/s Minimum Voltage: 1.35 V Maximum Voltage: 1.5 V Configured Voltage: 1.5 V
  5. I have duplicati and PlexMediaSever and mapped to user and cache drives (see screenshot attached). I also did "df -h" and currently have 275M free on rootfs (screesshot 2)
  6. Hello All, I had email notifications set up with Unraid 6.6 and it was working flawlessly to my gmail. I had to manually upgrade to Unraid 6.7.2 because I only had 300 mb free in my /tmp folder (so the web update kept failing due to running out of space) using the manually copy all bz* files and a few other files method to USB memory drive. I also replaced my cache drive (to a bigger one) and converted my array hard drive from Reiserfs to XFS after the Unraid version upgrade. The 6.7.2 upgrade worked however now I discovered my email notifications stopped working. I triple checked my email settings (which were retained) and they are all correct. I even tried my yahoo mail and another gmail smtp server without success. When I send a test email Unraid gives me a message that says "Test Result." I looked in the logs and the last line is, "Nov 16 05:27:09 Microserver emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog" I have attached my diagnostic log as well. Thank you, Tom microserver-diagnostics-20191116-1129.zip
  7. UPDATE: Issue resolved on it's own and Crashplan Pro is now happily doing the backup. Must be a Crashplan maintenance issue... ORIGINAL POST: I just setup this Docker today, migrating from Home version I was able to log in and adopt however cannot connect to CrashPlan Central. It gives me "Destination unavailable - you have an older version." (screenshot attached). Anyone else see this? Does the CrashPlan Pro client need to be updated in the docker image? Code42 is doing an maintanence today so not sure if that has to do with anything: https://helpdesk.code42.com/hc/en-us/articles/115001877553 Thank you.
  8. Any idea of the current version of unraid 6 (v6.0-beta9) is affected by this bug? I'm still running 6.0-beta5a and it is affected.
  9. I managed to compile the 64 bit version of APCUPSD to 3.14.12 (see thread here). PLEASE NOTE: this is the 64 bit version and tested to work for Unraid 6 BETA and will not work for Unraid 5.x Edit: Since I don't have an Unraid 5 system any more if anyone is interested in trying to compile the 32bit version here are the instructions: To compile you need the APCUPSD source code and also the customized compilation file from SlackBuilds.org to tailor APCUPSD for Slackware. 1. Install Slackware version matching Unraid 5.x (?Is it still 13.1?). Do a full install including X-Windows. Apparently some dependencies in APCUPSD depends on libraries in X-windows. 2. Download the correct APCUPSD version of from http://slackbuilds.org/result/?search=Apcupsd&sv= 3. Download current source code for APCUPSD: http://www.apcupsd.com/ 4. Unzip the file you got from SlackGuilds ( tar xvfz {file name} ) 5. Copy the APUCUPSD source code into the apcupsd directory created by step 4. 6. Modify the apcupsd.SlackBuild to reflect the new APCUPSD version 7. run ./apcupsd.SlackBuild and hopefully it will compile without errors. If all goes well it will make a tgz package file If compile gives errors maybe try different versions of apcupsd from SlackBuilds Repository (I did not have to change anything for the Slackware 14.1 version [unraid 6])
  10. The powerdown plugin that Dynamix needs to turn off the computer if it over heats has a feature where it executes scripts upon "start array" or "stop array" which are located in rc.unRAID.d/ folder (named Kxx.sh and Sxx.sh). Details in the powerdown plugin post here. I tested this feature and it works fine with the default webGUI but it does not work with the Dynamix webGUI. Is there a way to put code in the Dynamix webGUI so it will execute these scripts upon hitting "start array" or "stop array" in Dynamix?
  11. Not sure if this is something I have to edit in Dynamix or Powerdown but I set up K00.sh / S00.sh scripts which worked fine when I hit "start array" or "stop array" with the standard webGUI. However after I installed the Dynamix enhanced webGUI the K00.sh / S00.sh scripts stopped being executed when I hit start/stop array on the Dynamix webGUI.
  12. I had the same problem when using autoFS (keep on getting error 13 when using sickbeard postprocessing script). Turns out a show folder created by SickBeard was under user sickbeard (which you can only tell if you look at the folder from the Unraid box and not the VM box) and when sabnzbd tried to copy to it sabnzbd did not have permission. My solution was using Samba (detailed in my post here)
  13. Thank you IronicBadger! I just got it installed yesterday and manage to install Crashplan (from the AUR repository using Yaourt, using headless crashplan guide here) and plex on it. I had a lot of trouble with autofs not mounting correctly and ended up using Samba. I couldn't get Samba to work with fstab: I think mainly due to delay between bootup and when ArchVM can find the Unraid server. I wound up hacking together a Systemd startup service mounting my drives using guide from: https://wiki.archlinux.org/index.php/Systemd_FAQ#Q:_How_can_I_make_a_script_start_during_the_boot_process.3F My service script (myscript.service in my case) is below: [unit] Description=My script [service] Type=oneshot ExecStart=/usr/bin/sleep 100 ExecStart=/usr/bin/mount -t cifs -o username={insert user name},password={insert password},rw,file_mode=0777,dir_mode=0777 //Tower/Data /mnt/Data ExecStart=/usr/bin/mount -t cifs -o username={insert user name},password={insert password},rw,file_mode=0777,dir_mode=0777 //Tower/apps /mnt/apps ExecStart=/usr/bin/systemctl restart crashplan [install] WantedBy=multi-user.target -Change {insert user name} and {inert password} to your username/password for the Unraid shares. -Change //Tower/*** to your share and /mnt/*** to where you want it to mount it on the archVM. -The sleep 100 is necessary because there's a delay between boot up and when ArchVM can find Unraid server. -It restarts the crashplan service so crashplan can find the newly mounted files. -You don't need to use a separate script file using this method since all the commands are in the service file itself. I found that the commands didn't run at all if I put it as a separate script file (?maybe because the commands need to be run as root?). This seems to work for me and I hope it helps others out there.