Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation on 01/19/18 in all areas

  1. 1 point
    Application Name: davos Application Site: https://github.com/linuxserver/davos Docker Hub: https://hub.docker.com/r/linuxserver/davos/ Github: https://github.com/linuxserver/davos Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support
  2. 1 point
    I took a stab at writing a How-To based on the feedback in the release thread. If this looks helpful, maybe it could be added to the top post? Edit: this warrants it's own topic, thank you! -tom ----- Upgrading from 6.4.x to 6.5.0 Nothing to it really: Read the first post in the 6.4.1 and 6.5.0 release notes threads Consider disabling mover logging, it just adds noise to diagnostics. New 6.4.1 installs have it disabled by default. Go to Settings -> Scheduler -> Mover Settings Install/Update the Fix Common Problems plugin, then go to Tools -> Update Assistant and click "Run Tests". Whereas the normal FCP checks for potential problems with your *current* version of unRAID, the Update Assistant checks for incompatibilities with the version of unRAID you are *about* to install. It is highly recommended that you resolve any issues before proceeding. If you choose not to run the Update Assistant, you'll want to perform these steps manually: Ensure your server name does not include invalid characters, or you will have problems in 6.5.x. Only 'A-Z', 'a-z', '0-9', dashes ('-'), and dots ('.') are allowed, and the name must be 15 characters or less. To fix this, go to Settings -> Identification and change the "Server name". (see this) Upgrade all your plugins Uninstall the Advanced Buttons plugin, it was newly discovered to be incompatible (see this). You may want to review the next section for other plugins that are known to have problems, if you skipped that when going to 6.4.0. Note that the S3 Sleep plugin works again, feel free to install it if you removed it when going to 6.4.0 (see this). Stop the array (this step is optional, but I like to do it before starting the upgrade) Go to Tools -> Update OS and update the OS. You may need to switch from Next to Stable to see the update. Reboot! Then check out the "Setting Up New Features" section below. Upgrading from 6.3.5 (or earlier?) to 6.5.0 Before you upgrade from 6.3.5 Read the first post in the 6.4.0, 6.4.1 and 6.5.0 release notes threads Consider disabling mover logging, it just adds noise to diagnostics. New 6.4.1 installs have it disabled by default. Go to Settings -> Scheduler -> Mover Settings Install/Update the Fix Common Problems plugin, then go to Tools -> Update Assistant and click "Run Tests". Whereas the normal FCP checks for potential problems with your *current* version of unRAID, the Update Assistant checks for incompatibilities with the version of unRAID you are *about* to install. It is highly recommended that you resolve any issues before proceeding. If you choose not to run the Update Assistant, you'll want to perform these steps manually: Ensure your server name does not include invalid characters, or you will have problems in 6.5.x. Only 'A-Z', 'a-z', '0-9', dashes ('-'), and dots ('.') are allowed, and the name must be 15 characters or less. To fix this, go to Settings -> Identification and change the "Server name". (see this) If you have VMs, go to Settings -> VM Manager, switch to Advanced View, and make sure all of the paths are valid. Here are the default settings, but make sure the paths below actually exist on your system. Without these paths, your VMs will not load under 6.4.1. For more info see this default VM storage path -> /mnt/user/domains/ (this is DOMAINDIR in \\tower\flash\config\domain.cfg) default ISO storage path -> /mnt/user/isos/ (this is MEDIADIR in \\tower\flash\config\domain.cfg) Delete this file from your flash drive: \\tower\flash\config\plugins\dynamix.plg This is an old version of the dynamix webgui. Depending on how old it is, it can prevent the new webgui from loading. (see this, this) Upgrade all your plugins (other than the main unRAID OS plugin) You must uninstall Advanced Buttons (see this) and the Preclear plugin (see this, this, this, this, this, this). Consider uninstalling unmenu (see this), the Pipework docker (see this), and any other plugins you no longer use. Note that the S3 Sleep plugin works again, just make sure you have updated to the latest (see this) Consider installing the Fix Common Problems plugin and resolving any issues it highlights Additional cleanup you may want to perform: Consider deleting all files from the \\tower\flash\extra folder and install them using Nerd Tools instead Review your \\tower\flash\config\go script and use a good editor (like Notepad++, not Notepad) to remove as much as possible. For instance, remove any references to "cache_dirs" and use the Dynamix Cache Directories plugin instead. Consider moving other customizations to the User Scripts plugin Remove any port assignments added on the /usr/local/sbin/emhttp line FYI, a completely stock go script looks like this: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & Consider Installing any BIOS updates that are available for your motherboard If you made any substantial changes in this section, reboot and test to make sure any problems are not the result of these changes. Performing the upgrade from 6.3.5 Stop the array (If 6.3.5 or earlier) Go to Plugins and update the unRAID OS plugin (but don't reboot yet) (If on 6.4.0 or one of the 6.4 rc's) Go to Tools -> Update OS and update the OS (but don't reboot yet). You may need to switch from Next to Stable to see the update. By default, the webgui in unRAID 6.4.1 will use port 80 and any customization you made to the port in your go script will be ignored. If you need to change the port(s) before booting into 6.4.1 for the first time, use a good editor (like Notepad++, not Notepad) and edit \\tower\flash\config\ident.cfg Add the following lines to the end of the file, substituting the ports you want to use: USE_SSL="auto" PORT="80" PORTSSL="443" NOTE: If you need to change the defaults, be sure to pick high values over 1024. i.e. 81 and 43 are *not* good options. Try 8080 and 8443 Once you have booted in 6.4.0, you should no longer edit this file by hand. Better to use the webgui: Settings -> Identification -> Management Access If you are running Ryzen: Edit your \\tower\flash\config\go script (using a good editor like Notepad++ (not Notepad)) and add the "zenstates" command right before "emhttp", like this: /usr/local/sbin/zenstates --c6-disable /usr/local/sbin/emhttp & Also, go into your BIOS and disable "Global C-state control" Reboot It may be helpful to clear your browsers cache --- Setting Up New Features unRAID now supports SSL! unRAID will automatically provision and maintain a Lets Encrypt certificate for you, along with the necessary dynamic DNS entries. To enable this, go to Settings -> Identification -> Management Access and click Provision. If you get an error about rebinding protection, wait 10 minutes and try again. If you still get the error, click Help to read how to adjust your router. Using these certificates will change your url to <some long number>.unraid.net. No it can't be changed without disabling all of the automation and switching to your own certificates. You don't need to remember the number, when you connect via IP or servername it will automatically redirect. If you are concerned about a theoretical DNS outage, know that you can override your DNS by adding an entry to your PC's hosts file. Or in a pinch you can edit \\tower\boot\config\ident.cfg and set USE_SSL="no" If you prefer to not use the fully automated Lets Encrypt certificates, you can set your own domain name and supply your own certificates or use self-signed certificates. In this mode, you are responsible for managing DNS and ensuring the certificates do not expire. Click the Help icon on the SSL Certificate Settings page for more details. Want to check out the new themes? Navigate to Settings -> Display Settings -> Dynamix color theme. You may need to change your banner when you change the theme Note that you can now use the webgui to assign unique IP addresses to your dockers. If you manually customized your macvlans under 6.3.5 you'll need to set them up again using the webgui. You can now disable the insecure telnet protocol. Go to Settings -> Identification -> Management Access and set "Use TELNET" to "No" 6.4.1 adds docker support links to the docker page. Any dockers you install in 6.4.1 or later will automatically get this functionality, to update your existing dockers follow this one-time process Solutions to Common Problems Are you looking for the "edit XML" option for your VMs? First Edit the VM, then click the button in the upper right corner to switch from "Form View" to "XML View" If your system hangs at "loading /bzroot", you need to switch from "legacy" booting to UEFI. The ASRock C236 WSI motherboard in particular needs this, others may as well. (see this, this) To do this: (If needed) rename the "EFI-" folder on the flash drive to "EFI" Go into the bios and set the boot priority #1 to "UEFI: {flash drive}" Starting wth 6.4.1, unRAID now monitors SMART attribute 199 (UDMA CRC errors) for you. If you get an alert about this right after upgrading, you can just acknowledge it, as the error probably happened in the past. If you get an alert down the road, it is likely due to a loose SATA cable. Reseat both ends, or replace if needed. (see this) If your VMs will not start after upgrading, go to Settings -> VM Manager, switch to Advanced View, and make sure all of the paths are valid. Here are the default settings, but make sure the paths actually exist on your system: default VM storage path -> /mnt/user/domains/ (this is DOMAINDIR in \\tower\flash\config\domain.cfg) default ISO storage path -> /mnt/user/isos/ (this is MEDIADIR in \\tower\flash\config\domain.cfg) For more info see this. (the Update Assistant could have warned you of this in advance) If you can't access the webgui after upgrading to 6.5.0, your server name may include characters that are invalid for NETBIOS names. Only 'A-Z', 'a-z', '0-9', dashes ('-'), and dots ('.') are allowed, and it must be 15 characters or less. (see this) To fix this, edit \\tower\flash\config\ident.cfg using a good editor (like Notepad++, not Notepad) and remove those characters from the "NAME" parameter, then reboot. (the Update Assistant could have warned you of this in advance) If you are unable to access the webgui after upgrading, you may have a really old version of the dynamix webgui plugin on your system. Delete \\tower\flash\config\plugins\dynamix.plg and reboot. (see this, this) (the Update Assistant could have warned you of this in advance) If you have problems booting after applying the upgrade, move your flash drive to a Windows or Mac machine and run checkdisk, fixing any problems it finds. If your cache disk has an "incompatible partition" after upgrading, it was probably created in an older version of the Unassigned Devices plugin. UD has been updated so this won't happen again. (the Update Assistant could have warned you of this in advance) This is a one-time fix. You'll need to downgrade to 6.3.5 and move the data off the cache drive, re-format the disk and move the data back. The procedure is outlined here If you have on-board Aspeed IPMI you may find that IPMI loses video or changes color during the boot process. To resolve this, go to Main -> Boot Device -> Flash -> Syslinux Config and add "nomodeset" to your "append" line (and reboot). It should look something like this: label unRAID OS kernel /bzimage append initrd=/bzroot nomodeset You'll probably want to repeat that on each of the other append lines in this file. If you don't see CPU load statistics on the dashboard, or if you can't use the new web-based terminal, switch to Chrome or Firefox instead of Safari. This is a shortcoming in Safari, not a bug in unRAID. Doesn't apply in 6.5.0 Are you having problems with your Lets Encrypt docker? First, make sure the webgui and docker aren't both trying to use the same port. Beyond that, Lets Encrypt recently made some changes that break things. These issues are not related to the unRAID upgrade, refer to the LE docker thread for help Speedtest complaining about Python? The timing is coincidental, but it is not related to the unRAID upgrade, see the Speedtest thread If you are unable to update your dockers, or if you see this error in the syslog: Feb 3 12:08:59 Unraid-Nas [6503]: The command failed. Error: sh: /usr/local/emhttp/usr/bin/docker: No such file or directory then you need to uninstall the Advanced Buttons plugin. It is not currently compatible with 6.4.1+ See this (the Update Assistant could have warned you of this in advance) If you get this error message when trying to install the preclear plugin: unRAID version (6.4.1 - GCC 7.3.0) not supported. please re-read the "before you upgrade" section of this post. The preclear plugin is not compatible with 6.4.1+ If you see this error message in your logs, please re-read the "before you upgrade" section of this post. rc.diskinfo is part of the preclear plugin, which is not compatible with 6.4.1 (the Update Assistant could have warned you of this in advance) Feb 6 06:21:30 Tower rc.diskinfo[17255]: PHP Warning: file_put_contents(): Only 0 of 2584 bytes written, possibly out of free disk space in /etc/rc.d/rc.diskinfo on line 499 Are you seeing a "wrong csrf_token" token in your logs? Close all your browser tabs (on all computers) that were pointed at unRAID prior to the last reboot. More info If you have severe errors (no lan, array won't start, webgui won't start) try installing on a new flash drive. If it works, that means the problem is with one of your customizations. You can either try to find and fix the problem (if you skipped the "before you upgrade" section, that would be a good place to start), or move forward with the clean flash drive. To continue with the clean drive, copy just the basics (/config/super.dat and your key file) from the old drive to the new one and then reconfigure as needed. Are you still having problems? Review the expanded "Before you upgrade" section above. If that doesn't help, grab your diagnostics (Tools -> Diagnostics) if you can, and reboot into Safe Mode. If your problems go away, then the problem is likely with a plugin. If the problems persist, you'll need additional help. Either way, grab your diagnostics again while in safe mode and attach both sets to a forum post where you clearly explain the issue.
  3. 1 point
    Hi, I'm Clippy! I noticed you are asking our friendly volunteers for help, but you haven't included your diagnostics. Using the unRAID webgui, go to Tools -> Diagnostics, generate a diagnostics.zip file and attach it to your next post. If you can't access the webgui, this post explains how to generate one from the command line.
  4. 1 point
    I think people are concerned because there doesn't seem to be much track record for the PSU in question. General wisdom is to buy a high quality PSU from a well known manufacturer, so though this PSU looks great on paper (single rail, good warranty, modular, quiet), due to it being relatively unknown, it feels like a risk that could be easily avoided by purchasing a PSU from a well known, well reviewed manufacturer. As you say, warranties can be tricky, and even though this PSU does offer a great warranty (7 years), I'd rather buy a PSU that has a track record for not dying and taking a few components with it... This may be a fantastic PSU, but why be a trailblazer? Without an established record, you have no way of knowing how good or bad it is. Of course, that said, you've already bought it, so let's hope it works out! Who knows, perhaps you'll be one of the first buying a product that turns out to be on the recommended list in five years . EDIT: I just found a remarkably good review for this unit. Looks like the internals are all substantially better quality then they have used in the past. Personally, I would still not have bought it until it has been around for enough time to establish itself as a solid PSU, but it's promising that they've used great parts to build it.
  5. 1 point
    Ugh! I have done this to myself before. The VMDK boot works just fine with 6.4.0, as along as there is a passthrough USB key. My issue was I had a label on the VMDK called "UNRAID". I know better. You cant have two devices labeled "UNRAID". I renamed it to "UNRAIDBOOT" and it works as expected. Now I can start playing with Zeron's script to get vmware tools working.
  6. 1 point
    WD completed the extended test without a read failure, this means the current pending sectors are "false positives" and the disk is fine for know and you should be able to copy all data from it without issues, though IMO that disk should be replaced when possible as double digits raw read errors are never a good sign on WD disks. For the Seagate you only did a shot test, long test would be much better since there are some reported uncorrected errors, but they are quite old.
  7. 1 point
    Tip: use the browser zoom function to enlarge the map
  8. 1 point
    There is a short list of potentially problematic plugins here:
  9. 1 point
    OK, I softened the language around uninstalling preclear, and tried to find links that backed up the suggestion. If anyone has better ones let me know. I also added the suggestion to remove Pipework (thanks @Vaseer ) I had forgotten about that one.
  10. 1 point
    Today I was upgrading from 6.3.5 to 6.4.0. Upgrade went fine, but when 6.4.0 boot up, it stuck on Array Starting... Starting services... I find out that culprit was Pipework (Docker container) which I was using for setting Transmission's IP. Solution: Disable Array auto start on boot and then disable Docker. Delete docker.img. Start unRAID normally and reinstall Dockers (except Pipework). Alternative would be to revert to 6.3.5 and remove Pipework and then upgrade to 6.4.0. Prior to upgrade I turned off auto start on all Dockers, but Pipework auto started non the less. Hope it helps to someone.
  11. 1 point
    Agreed, I didn't mean nor want to make the Update Notes longer than necessary; however, was curious about clarification as I believe folks would want a quick and simple guide instead of having to read through multiple threads for the info they need. I reviewed the thread for preclear before posting and didn't see any specific evidence that it was a hard and fast rule that preclear needed to be removed by all. Seemed like a few instances where removing it helped. I guess I'm looking at it as instead of saying it needs to be removed, that it might need to be removed if a user sees XYZ issue.
  12. 1 point
    I still prefer the white theme. Just not sure why the padding was removed.
  13. 1 point
    Problem: Cache disk shows as having an incompatible partition after upgrading to 6.4. Reason: The cache disk was formatted by UD with an incompatible format. Until 6.4, unRAID would accept the incompatible format for the cache disk and mount it. unRAID now refuses to accept a disk with incompatible partitioning. UD has been updated so this won't happen again. Fix: You will have to downgrade to 6.3 and move the data off the cache, re-format the cache disk, and move the cache data back. The procedure is outlined here:
  14. 1 point
    Just a quick mention to all of you using this patch, it's probably reasonable to let you all know that @Jcloud contacted me to discuss compiling this for the community and to ask for a little advice and made a very generous donation from his own pocket to linuxserver.io which is very much appreciated and will go towards our server and hosting costs. So a big thanks to him from everyone is well deserved (although I would like to point out I would have provided any help for free! )
  15. 1 point
    I do have a unifi switch and by default it trunks all vlans to all ports. I'll take some screenshots to illustrate where i'm at **edit** I basically nuked all the routes and started from scratch and now, at least the containers, seem to work. It's possible that my USG didn't get all the config changes as it sometimes starts to provision before finishing the changes. I forced a provision which may have helped also. Anyway, this is a super cool feature and i'm glad to have it working. Now I just need to work backwards to open up all the ports I need for my containers then slap a big DENY ALL at the end of the list to limit the docker vlan from accessing my main LAN. I ended up taking all those screenshots anyway so I might compile a unifi specific guide for users looking to do this and how to harden the stack as all vlans are wide open by default. Thanks!
  16. 1 point
    HAHA I knew the community would beat me! Bah. Good learning experience though. I just successfully compiled and booted 6.4.0 with Ugly patch. VM's are up and running. Currently in my testing-paranoia mode
  17. 1 point
    Got the java version running on my unraid box right now! root@raid:/boot/custom # /usr/lib64/java/bin/java ZenBridgeBaconRecovery ------------------------------------------- Zen PCIe-Bridge BAR/Config Recovery Tool, rev 1, 2018, HyenaCheeseHeads ------------------------------------------- Tue Jan 16 06:41:14 CET 2018: Detecting VFIO-PCI devices Tue Jan 16 06:41:14 CET 2018: Device: /sys/devices/pci0000:00/0000:00:03.1/0000:09:00.1 Tue Jan 16 06:41:14 CET 2018: Bridge: /sys/devices/pci0000:00/0000:00:03.1 Tue Jan 16 06:41:14 CET 2018: Device: /sys/devices/pci0000:00/0000:00:03.1/0000:09:00.0 Tue Jan 16 06:41:14 CET 2018: Bridge: /sys/devices/pci0000:00/0000:00:03.1 Tue Jan 16 06:41:14 CET 2018: Monitoring 2 device(s)... Tue Jan 16 06:41:14 CET 2018: Lost contact with /sys/devices/pci0000:00/0000:00:03.1/0000:09:00.1 Tue Jan 16 06:41:14 CET 2018: Recovering 512 bytes Tue Jan 16 06:41:14 CET 2018: Bridge config write complete Tue Jan 16 06:41:14 CET 2018: Recovered bridge secondary bus Tue Jan 16 06:41:14 CET 2018: Re-acquired contact with /sys/devices/pci0000:00/0000:00:03.1/0000:09:00.1
  18. 1 point
    +1 I would like to see vbios passthrough in the vm template.
  19. 1 point
    SSH into the server or use the console and type: mover stop
  20. 1 point