Leaderboard
Popular Content
Showing content with the highest reputation on 07/10/20 in all areas
-
Remove that line altogether from the docker.cfg file It's winding up overriding the system (and it's not present on my system at all) Probably @limetech / @bonienl should update the OS to ignore that2 points
-
This is the support thread for multiple Plugins like: AMD Vendor Reset Plugin Coral TPU Driver Plugin hpsahba Driver Plugin Please always include for which plugin that you need help also the Diagnostics from your server and a screenshots from your container template if your issue is related to a container. If you like my work, please consider making a donation
1 point -
This container needs a ConbeeII usb zigbee stick to work This container is for the deCONZ software from Dresden Elektronik. It is used to control a conbee zigbee usb stick and can be used with home assistant. Setup. 1. Without conbee usb stick plugged into the server run the following command in a terminal window ls /dev/ 2. Plug your conbee usb stick into the unraid server. Then run the above again. You will now see an extra device here. This is your conbee zigbee stick. Most likely ttyACM0 (unless you have maybe a zwave stick plugged in aswell then it might not be) 3. Now add the name of the stick to the template. (default is already ttyACM0) Add it to both usb conbee: and usb device name: 4. I think it best to set a static ip for the container. You can then access the container from http://xxx.xxx.xxx.xxx (the ip you set) 5. Now you can add your zigbee devices in the webui and connect deconz to home assistant for it to be able to access you zigbee devices.
1 point -
I didn't see a thread like this, but I'm always interested in hearing the types of things people are doing with their unRAID servers. When I first started with mine 5+ years ago, it was simply to store my movies and to be able to serve them to different client devices throughout my house. I have expanded quite a bit since then, and lots of that is due to reading and contributing to different threads on these forums where members discuss things they're doing with their own servers. Here's a rundown of what my server does. Hopefully others will post their own server jobs so other readers of this forum can be inspired to try out some new things they may not have thought of! Data storage - Your standard parity protected storage of data. Mine includes movies, tv shows, music, pictures, and other documents and files. Syncronized databases - Through the use of dockers such as MariaDB, I have my unRAID server hosting a database which all my client devices such as Chromeboxes and Raspberry Pi's throughout my home can read from and share data when accessing and displaying media. Virtualization - After upgrading my server, I decided to better utilize it's power by now virtualizing instances of Kodi with LibreELEC. Now, rather than running off of Raspberry Pi's, a couple of my TVs are connected directly to video cards on my server which are running virtual instances of LibreELEC. I plan to create another workstation, likely Windows 10, through the use of a VM on unRAID. Dockers for media - Through the use of a stack including Radarr/Sonarr/Headphones downloading torrents and nzb files and sending them over to Deluge/NZBGet, I have a pretty automated system for keeping my media in check and up to date. I'm running Plex and Kodi Headless to organize and distribute this media locally and remotely. Dockers for home automation & security - I'm running other dockers such as Zoneminder & Home Assistant in an effort to centralize the pieces working together to provide a secure & automated home environment. Other Dockers - I'm also running other dockers like NextCloud, OpenVPN, MQTT and others which provide more specific tasks for my needs. With that said, how are you using YOUR unRAID server?1 point
-
https://www.presse-citron.net/tutoriel-comment-creer-un-nas-maison-avec-des-composants-pc-et-unraid-partie-1/1 point
-
6.9.0-beta24 vs. -beta22 Summary: fixed several bugs added some out-of-tree drivers added ability to use xfs-formatted loopbacks or not use loopback at all for docker image layers. Refer to Docker section below for more details (-beta23 was an internal release) Important: Beta code is not fully tested and not feature-complete. We recommend running on test servers only! Multiple Pools This features permits you to define up to 35 named pools, of up to 30 storage devices/pool. The current "cache pool" is now simply a pool named "cache". Pools are created and managed via the Main page. Note: When you upgrade a server which has a cache pool defined, a backup of config/disk.cfg will be saved to config/disk.cfg.bak, and then cache device assignment settings are moved out of disk.cfg and into a new file, config/pools/cache.cfg. If later you revert back to a pre-6.9 Unraid OS release you will lose your cache device assignments and you will have to manually re-assign devices to cache. As long as you reassign the correct devices, data should remain intact. When you create a user share, or edit an existing user share, you can specify which pool should be associated with that share. The assigned pool functions identically to current cache pool operation. Something to be aware of: when a directory listing is obtained for a share, the unRAID array disk volumes and all pools which contain that share are merged in this order: pool assigned to share disk1 : disk28 all the other pools in strverscmp() order. As with the current "cache pool", a single-device pool may be formatted with either xfs, btrfs, or reiserfs. A multiple-device pool may only be formatted with btrfs. A future release will include support for multiple "unRAID array" pools. We are also considering zfs support. Something else to be aware of: Let's say you have a 2-device btrfs pool. This will be what btrfs calls "raid1" and what most people would understand to be "mirrored disks". Well this is mostly true in that the same data exists on both disks but not necessarily at the block-level. Now let's say you create another pool, and what you do is unassign one of the devices from the existing 2-device btrfs pool and assign it to this pool. Now you have x2 1-device btrfs pools. Upon array Start user might understandably assume there are now x2 pools with exactly the same data. However this is not the case. Instead, when Unraid OS sees that a btrfs device has been removed from an existing multi-device pool, upon array Start it will do a 'wipefs' on that device so that upon mount it will not be included in the old pool. This of course effectively deletes all the data on the moved device. Language Translation A huge amount of work and effort has been implemented by @bonienl to provide multiple-language support in the Unraid OS Management Utility, aka, webGUI. There are several language packs now available, and several more in the works. Thanks to @Squid, language packs are installed via the Community Applications plugin - look for a new category entitled Language. Note: Community Applications must be up to date to install languages. See also here. Each language pack exists in public Unraid organization github repos. Interested users are encouraged to clone and issue Pull Requests to correct translations errors. Language translations and PR merging is managed by @SpencerJ. Linux Kernel Upgraded to 5.7. These out-of-tree drivers are currently included: QLogic QLGE 10Gb Ethernet Driver Support (from staging) RealTek r8125: version 9.003.05 (included for newer r8125) HighPoint rr272x_1x: version v1.10.6-19_12_05 (per user request) Note that as we update Linux kernel, if an out-of-tree driver no longer builds, it will be omitted. These drivers are currently omitted: Highpoint RocketRaid r750 (does not build) Highpoint RocketRaid rr3740a (does not build) Tehuti Networks tn40xx (does not build) If you require one of these drivers, please create a Bug Report and we'll spend some time looking for alternatives. Better yet, pester the manufacturer of the controller and get them to update their drivers. Base Packages All updated to latest versions. In addition, Linux PAM has been integrated. This will permit us to install 2-factor authentication packages in a future release. Docker Updated to version 19.03.11 We also made some changes to add flexibility in assigning storage for the Docker engine. First, 'rc.docker' will detect the filesystem type of /var/lib/docker. We now support either btrfs or xfs and the docker storage driver is set appropriately. Next, 'mount_image' is modifed to support loopback formatted either with btrfs or xfs depending on the suffix of the loopback file name. For example, the file name ends with ".img", as in "docker.img" then we use mkfs.btrfs. If file name ends with "-xfs.img", as in "docker-xfs.img" then we use mkfs.xfs. We also added the ability to bind-mount a directory instead of using a loopback. If file name does not end with ".img" then code assumes this is the name of directory (presumably on a share) which is bind-mounted onto /var/lib/docker. For example, if "/mnt/user/system/docker/docker" then we first create, if necessary the directory "/mnt/user/system/docker/docker". If this path is on a user share we then "dereference" the path to get the disk path which is then bind-mounted onto /var/lib/docker. For exmaple, if "/mnt/user/system/docker/docker" is on "disk1", then we would bind-mount "/mnt/disk1/system/docker/docker". Caution: the share should be cache-only or cache-no so that 'mover' will not attempt to move the directory, but the script does not check this. In this release however, you must edit the 'config/docker.cfg' file directly to specify a directory, for example: DOCKER_IMAGE_FILE="/mnt/user/system/docker/docker" Finally, it's now possible to select different icons for multiple containers of the same type. This change necessitates a re-download of the icons for all your installed docker applications. A delay when initially loading either the dashboard or the docker tab while this happens is to be expected prior to the containers showing up. Virtualization libvirt updated to version 6.4.0 qemu updated to version 5.0.0 In addition, integrated changes to System Devices page by user @Skitals with modifications by user @ljm42. You can now select PCI devices to isolate from Linux upon boot simply by checking some boxes. This makes it easier to reserve those devices for assignment to VM's. Note: If you had the VFIO-PCI Config plugin installed, you should remove it as that functionality is now built-in to Unraid OS 6.9. Refer also @ljm42's excellent guide. In a future release we will include the NVIDIA and AMD GPU drivers natively into Unraid OS. The primary use case is to facilitate accelerated transcoding in docker containers. For this we require Linux to detect and auto-install the appropriate driver. However, in order to reliably pass through an NVIDIA or AMD GPU to a VM, it's necessary to prevent Linux from auto-installing a GPU driver for those devices upon boot, which can be easily done now through System Devices page. Users passing GPU's to VM's are encouraged to set this up now. "unexpected GSO errors" If your system log is being flooded with errors such as: Jun 20 09:09:21 Tower kernel: tun: unexpected GSO type: 0x0, gso_size 31, hdr_len 66 You need to edit each VM and change the model type for the Ethernet bridge from "virtio" to "virtio-net". In most cases this can be accomplished simply by clicking Update in "Form View" on the VM Edit page. For other network configs it may be necessary to directly edit the xml. Example: <interface type='bridge'> <mac address='xx:xx:xx:xx:xx:xx'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> Other AFP support has been removed. Numerous other Unraid OS and webGUI bug fixes and improvements. Version 6.9.0-beta24 2020-07-08 Bug fixes: fix emhttpd crash expanding number of slots for an existing pool fix share protected/not protected status fix btrfs free space reporting fix pool spinning state incorrect Base distro: curl: version 7.71.0 fuse3: version 3.9.2 file: version 5.39 gnutls: version 3.6.14 harfbuzz: version 2.6.8 haveged: version 1.9.12 kernel-firmware: version 20200619_3890db3 libarchive: version 3.4.3 libjpeg-turbo: version 2.0.5 lcms2: version 2.11 libzip: version 1.7.1 nginx: version 1.19.0 (CVE-2019-9511, CVE-2019-9513, CVE-2019-9516) ntp: version 4.2.8p15 openssh: version 8.3p1 pam: version 1.4.0 rsync: version 3.2.1 samba: version 4.12.5 (CVE-2020-10730, CVE-2020-10745, CVE-2020-10760, CVE-2020-14303) shadow: version 4.8.1 sqlite: version 3.32.3 sudo: version 1.9.1 sysvinit-scripts: version 2.1 ttyd: version 20200624 util-linux: version 2.35.2 xinit: version 1.4.1 zstd: version 1.4.5 Linux kernel: version 5.7.7 out-of-tree driver: QLogic QLGE 10Gb Ethernet Driver Support (from staging) out-of-tree driver: RealTek r8125: version 9.003.05 out-of-tree driver: HighPoint rr272x_1x: version v1.10.6-19_12_05 Management: cleanup passwd, shadow docker: support both btrfs and xfs backing filesystems loopbacks: permit xfs or btrfs based on filename mount_image: suppport bind-mount mount all btrfs volumes using 'space_cache=v2' option mount loopbacks with 'noatime' option; enable 'direct-io' non-rotational device partitions aligned on 1MiB boundary by default ssh: require passwords, disable non-root tunneling web terminal: inhibit warning pop-up when closing window webgui: Add log viewer for vfio-pci webgui: Allow different image types to upload with 512K max webgui: other misc. improvements webgui: vm manager: Preserve VNC port settings1 point
-
6.9 beta 22 its integrated1 point
-
That's normal when the router isn't set to reflect outside addresses accessed from the inside to the appropriate internal resources. Search for your router model plus the terms "nat loopback reflection hairpinning"1 point
-
Those files are supposed to be there, was wondering if you had specifically file named "sshd_config" - if so you need to delete that one. Another possibility is maybe you have a line in 'go' file or a script somewhere that is replacing the 'stock' /etc/ssh/sshd_config ?1 point
-
Version 2020.07.10b is available1 point
-
This is listed in the manual: Clear CMOS - 1 (short pin), but I don't see it in their diagram. Pulling the battery should work.1 point
-
I'm going to say that the cause for my lockups seemed to be the log filling up. Since I fixed the ACPI error I've gotten tons of uptime with no issues. Thanks for the help!1 point
-
Next release, it will be filtered out, to prevent issues like this.1 point
-
Wireguard not reporting handshake properly: 6.9 Beta 24 6.8.3 These two servers are connected and the VPN is working, but 6.9 does not show handshake activity.1 point
-
You absolutely magnificent person. Thank you so much! This worked like a charm. I had to use the 'Intel' version despite on AMD but no complaints here. The HBA is a stop gap anyway until I get a large LSI HBA. I must have taken the diags after re-enabling HVM (SVM) but IOMMU was on from the start. In anycase, thanks again. This just saved me from the madhouse. I owe you a bottle of Scotch.1 point
-
@mutabear, why don't you start by reading here: https://wiki.unraid.net/index.php/UnRAID_Manual_6#Parity-Protected_Array The first thing you need to do is to completely forget about RAID. If you have a Dell RAID card, most of them can be crossflashed into the LSI IT-Mode. (LSI actually made the Dell cards under an OEM contract.)1 point
-
Unraid is not RAID so you can't think of it that way. Also parity is not a backup - protection against a single drive failure is not a backup. You should provide some details as to what you are using the server for + what other hardware is available so we can give you better suggestions.1 point
-
The device added to the pool will be added automatically and the pool converted to raid1, this is default behavior for a 2 device pool, after the balance finishes you can convert to raid0.1 point
-
ooops didn't notice all of them were grouped!sorry1 point
-
What Ghost82 said in general is true, but all these devices are in the same group and have to be passed through to make it work. In your case that will break a lot of things. You have a couple options to separate the GPU in it's own group. You can try to use a different PCIE slot and check if the groupings are better or you use the ACS Override Option to split the groups. Most modern motherboard BIOS also have an option to enable IOMMU, which can help to split up the groups. Don't try to pass all these devices to a VM, or unraid will loose access to all these devices (network, USB, sata controller). You can even break it by only trying to use one device in a VM and the rest can lag out, crash or completely dissapear from unraid.1 point
-
i was going to jam a fresh install on an old AMD 8 core box i have kicking around and then we will know for sure I also have to add I love your work most of the stuff I use is yours1 point
-
Hi - I just want to participate to this channel on the huge work and say a huge thank you for this container. I've used this container to build a kernel with a new version of r8152 driver. I searched for days to find a way to do it and with this container - it was really easy to do it.1 point
-
Parity check completed without errors, and drive no longer disabled and working. Will keep an eye on it - Would be good to know what caused it to become disabled!! Thanks for everyones help!1 point
-
Corrected in next version. Thanks.1 point
-
In the 6.8.3 announcement thread, theres a link you can paste into install plugin to update (And, that link posted for the Nvidia plugin is not the actual link for the plugin itself which is why it didn't work)1 point
-
Not yet. I haven't had time to do so yet. Personal time on the PC has been limited of late. I'll post an update when it is.1 point
-
I want to provide a vanilla experience of ZFS on unRAID until it’s natively supported [emoji16] I don’t want to add some some functions that might or might not benefit user use-cases. If you want the pool to automatically import export it’s a great idea to add zpool export -a and zpool import -a on stopping/starting the array via the awesome user scripts plugin. Considering this is a plug-in for advanced users I don’t think the target audience for this will have a problem adding these commands if preferred. Now we just wait and see if native zfs support comes in the next betas Ps I have built Sanoid/Syncoid for myself and was wondering if there was any demand for a plug-in?1 point
-
IT WORKS!!!!!!!! The main difference: The PCI bridge in this card. 1c:00.0 PCI bridge: ASMedia Technology Inc. Device 1806 (rev 01) 1d:00.0 PCI bridge: ASMedia Technology Inc. Device 1806 (rev 01) 1d:02.0 PCI bridge: ASMedia Technology Inc. Device 1806 (rev 01) 1d:06.0 PCI bridge: ASMedia Technology Inc. Device 1806 (rev 01) 1d:0e.0 PCI bridge: ASMedia Technology Inc. Device 1806 (rev 01) 1e:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02) 1f:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02) 20:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02) 21:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02) https://www.aliexpress.com/item/32947768312.html One year trying to make this happen.
1 point -
You could have used Unraid for 30 days with the trial license to test it. That was the "right thing" to do. If you actually read PayPal's user agreement, you can easily learn that an item may not be considered Significantly Not as Described if the item was properly described but did not meet your expectations. I'm pretty sure LT will refund you, but not because you are right. LT likes to keep their customers satisfied.1 point
-
Plug and Play here -Unraid 6.8.3 -Dell R710 II w/Dell H200 in IT Mode -LSI 9200-8e in IT Mode -NetApp DS4246 24-Bay IOM61 point
-
@jonathanm Yes. This was the first to pop up on google for me though. After posting here I saw the new thread and posted there as well. I wanted to make sure people can find a solution. I've had unRaid since 2016 but I'm new to posting on the forms, so I'm open to advice. Thanks!1 point
-
You should also be able to change it per drive by going to MAIN then clicking the drive and changing the values Click Disk Change Value
1 point -
Hi, new to unraid and nextcloud and I want to share a fix for a problem I had a couple of days ago. I looked for a fix in the forums but only 2 people reported it and one of them moved to owncloud after giving up on it, I hope this will help other people who had the same issue. After I setup nextcloud (followed SpaceinvaderOne's video) I had a problem each time I tried to upload a large file (11.2 GB). After the upload, while processing, an error message showed up - "Error when assembling chunks, status code 504". If I refresh the page the file is there and its ok (compared checksum to source). Tested it a couple of times and only one time the file didn't show up (can't really explain it). The message is pretty annoying so I had to look it up. Found the following issue: https://github.com/nextcloud/server/issues/17992 To fix I had to open the nginx config - appdata/nextcloud/nginx/site-confs/default Searched for 'fastcgi' and inside the brackets I added these lines: fastcgi_connect_timeout 60; fastcgi_send_timeout 1800; fastcgi_read_timeout 1800; That fixed those error messages and I hope it will help you. For more info you can check the issue on nextcloud's github. Have a good day1 point
-
Hi, After searching around I found a blog here which listed the steps to get System Temp Running. I'll place a bit more instructions here though for anyone else looking: Install Nerd Tools following the post here Install Perl by opening the Nerd Tools plugin and selecting the slider Open the System Temp Plugin The detect button should be active now, so press it and save Select the applicable sensors Press Apply Press Done You can uninstall Perl by going back to the Nerd Tools plugin Grab a drink and stay cool P.S. Also found author's instructions here ?1 point
-
Cause is probably from a docker mapping: one container is referencing a share named music, and another container is referencing a share named Music Easiest solution would be to install and set up the Krusader app, then navigate to /UNRAID/user on both display panes, then cut and paste from one to the other to combine the files all into the same share. Then double check your mappings in your various docker apps and make sure they are all using the same one (otherwise it will just get created again) Set up Krusader something like this:
1 point
