Leaderboard

My co-workers wondered why I was taking off my shirt. They are still baffled why I have to show my belly button to a squid. 😁

Because not every here speaks English, a foreign language translation follows. This thread just hit a milestone and now has over 500,000 views 😁 (It however is not the most viewed topic here. That distinction belongs to Simple Features which formed the basis of Dynamix, unRaid's GUI) But nonetheless a celebration is in order. I think that I'll be doing something like this tonight But, thank you to everyone in these forums who've made CA what it is today... (along with Larry Page and Sergei Brin as their web scraping probably accounts for some of the views) To commemorate this very special day, 500 randomly selected unRaid users will find a piece of pocket fluff. (As a special bonus, 1 of those 500 winners will also find some navel fluff) 50 randomly selected unRaid users will find a perfectly usable USB flash drive on the street that may or may not be virus infected (but does have a unique GUID). 5 randomly selected unRaid users will discover that their once cherished tip 'n strip nude pen has been sitting in their miscellaneous kitchen drawer for the last 40 years. And the randomly selected grand prize winner will never again be asked by their spouse "does this outfit make me look fat?" Winners will be selected by a random number generator, but since it is technically impossible to create any random number generator that isn't pseudo-random, bribes may also wind up influencing the decision without drawing any attention to yourself. Good luck to everyone! Because of Schrödinger's Cat, any announcement of the winners will obviously affect the outcome and as such there will be no announcement made. ------------------------------------------- Isthay eadthray ustjay ithay away ilestonemay andway ownay ashay overway 500,000 iewsvay 😁 (Itway oweverhay isway otnay ethay ostmay iewedvay opictay erehay. Atthay istinctionday elongsbay otay Implesay Eaturesfay ichwhay ormedfay ethay asisbay fway Ynamixday, unRaid'sway UIGAY) Utbay onethelessnay away elebrationcay isway inway orderway. Iway inkthay atthay I'llway ebay oingday omethingsay ikelay isthay onighttay Utbay, ankthay ouyay otay everyoneway inway esethay orumsfay o'vewhay ademay ACAY atwhay itway isway odaytay... (alongway ithway Arrylay Agepay andway Ergeisay Inbray asway eirthay ebway apingscray obablypray accountsway orfay omesay ofway ethay iewsvay) Otay ommemoratecay isthay eryvay ecialspay ayday, 500 andomlyray electedsay unRaidway usersway illway indfay away iecepay ofway ocketpay uffflay. (Asway away ecialspay onusbay, 1 ofway osethay 500 innersway illway alsoway indfay omesay avelnay uffflay) 50 andomlyray electedsay unRaidway usersway illway indfay away erfectlypay usableway USBWAY ashflay ivedray onway ethay eetstray atthay aymay orway aymay otnay ebay irusvay infectedway (utbay oesday avehay away uniqueway UIDGAY). 5 andomlyray electedsay unRaidway usersway illway iscoverday atthay eirthay onceway erishedchay iptay 'nay ipstray udenay enpay ashay eenbay ittingsay inway eirthay iscellaneousmay itchenkay awerdray orfay ethay astlay 40 earsyay. Andway ethay andomlyray electedsay andgray izepray innerway illway evernay againway ebay askedway ybay eirthay ousespay "oesday isthay outfitway akemay emay ooklay atfay?" Innersway illway ebay electedsay ybay away andomray umbernay eneratorgay, utbay incesay itway isway echnicallytay impossibleway otay eatecray anyway andomray umbernay eneratorgay atthay isn'tway eudopsay-andomray, ibesbray aymay alsoway indway upway influencingway ethay ecisionday ithoutway awingdray anyway attentionway otay ourselfyay. Oodgay ucklay otay everyoneway! Ecausebay ofway Schrayöinger'sday Atcay, anyway announcementway ofway ethay innersway illway obviouslyway affectway ethay outcomeway andway asway uchsay erethay illway ebay onay announcementway ademay.

Was weird that it worked with all the other dockers and only rtorrent crashing it, but i found the problem. It was a 16Gb ram stick that threw errors.

Found this the other day. This might be related, it might not be. Take a look:

For planned outages of any length, it's easy to just temporarily stand up your current router for the duration of the maintenance. Hopefully there are no unplanned array stops, I've never had my pfSense VM stop or my array crash, but I am running server grade hardware.

then i would recommend a Mikrotik products, like https://mikrotik.com/product/hap_ac2, much cheaper than your budget. it can do about 1Gbit WAN, have at least 200Mbit Hardware accelerated Ipsec VPN, some wifi - for me i have a cable on all devices that required more than 50Mbit traffic, so not a big deal.. and if you are familiar with Mikrotik ROS, you have so many configuration options..

I made a capture of my system. Issues start at the line "BUG: unable to handle kernel NULL pointer..." Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6faa Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6fab Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6fab Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6fac Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6fac Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6fad Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6fad Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6f68 Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6f79 Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6f6a Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6f6b Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6f6c Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6f6d Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6ffc Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6ffc Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6ffd Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6ffd Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6faf Jan 23 18:19:58 vesta kernel: EDAC sbridge: Seeking for: PCI ID 8086:6faf Jan 23 18:19:58 vesta kernel: EDAC MC0: Giving out device to module sb_edac controller Broadwell SrcID#0_Ha#0: DEV 0000:ff:12.0 (INTERRUPT) Jan 23 18:19:58 vesta kernel: EDAC sbridge: Ver: 1.1.2 Jan 23 18:19:58 vesta kernel: BTRFS: device fsid 15cea296-4aa8-4a45-b03f-1d4bd2587221 devid 4 transid 37220822 /dev/sdg1 Jan 23 18:19:58 vesta kernel: BTRFS: device fsid 15cea296-4aa8-4a45-b03f-1d4bd2587221 devid 3 transid 37220822 /dev/sdf1 Jan 23 18:19:58 vesta kernel: BTRFS: device fsid 15cea296-4aa8-4a45-b03f-1d4bd2587221 devid 1 transid 37220822 /dev/sdh1 Jan 23 18:19:58 vesta kernel: BTRFS: device fsid 15cea296-4aa8-4a45-b03f-1d4bd2587221 devid 2 transid 37220822 /dev/sdk1 Jan 23 18:19:58 vesta kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000000 Jan 23 18:19:58 vesta kernel: PGD 1ff7e0d067 P4D 1ff7e0d067 PUD 1fbaaff067 PMD 0 Jan 23 18:19:58 vesta kernel: Oops: 0000 [#1] SMP NOPTI Jan 23 18:19:58 vesta kernel: CPU: 2 PID: 2532 Comm: modprobe Not tainted 4.19.94-Unraid #1 Jan 23 18:19:58 vesta kernel: Hardware name: Supermicro X10SRA-F/X10SRA-F, BIOS 2.1a 10/24/2018 Jan 23 18:19:58 vesta kernel: RIP: 0010:kernfs_name_hash+0x9/0x6d Jan 23 18:19:58 vesta kernel: Code: 48 33 04 25 28 00 00 00 74 05 e8 c3 3d ea ff 48 83 c4 60 4c 89 f0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 48 83 c9 ff 31 c0 49 89 f8 <f2> ae 48 f7 d1 8d 79 ff 31 c9 48 39 cf 74 1f 49 0f be 04 08 48 ff Jan 23 18:19:58 vesta kernel: RSP: 0018:ffffc90006b27cb8 EFLAGS: 00010246 Jan 23 18:19:58 vesta kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffffffffffff Jan 23 18:19:58 vesta kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 Jan 23 18:19:58 vesta kernel: RBP: ffff889fcab65198 R08: 0000000000000000 R09: ffffffff811ac100 Jan 23 18:19:58 vesta kernel: R10: ffffea007f2ad900 R11: ffff889fff075001 R12: ffff889fcab65348 Jan 23 18:19:58 vesta kernel: R13: 0000000000000000 R14: ffff889ff3a6c190 R15: 0000000000000000 Jan 23 18:19:58 vesta kernel: FS: 0000150ae6c37b80(0000) GS:ffff889fff680000(0000) knlGS:0000000000000000 Jan 23 18:19:58 vesta kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 23 18:19:58 vesta kernel: CR2: 0000000000000000 CR3: 0000001ff3b5a002 CR4: 00000000003606e0 Jan 23 18:19:58 vesta kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jan 23 18:19:58 vesta kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jan 23 18:19:58 vesta kernel: Call Trace: Jan 23 18:19:58 vesta kernel: kernfs_find_ns+0x5e/0xa8 Jan 23 18:19:58 vesta kernel: kernfs_remove_by_name_ns+0x49/0x75 Jan 23 18:19:58 vesta kernel: remove_files+0x38/0x5a Jan 23 18:19:58 vesta kernel: sysfs_remove_group+0x55/0x6f Jan 23 18:19:58 vesta kernel: sysfs_remove_groups+0x28/0x2f Jan 23 18:19:58 vesta kernel: device_remove_attrs+0x33/0x63 Jan 23 18:19:58 vesta kernel: device_del+0x18d/0x2ed Jan 23 18:19:58 vesta kernel: cdev_device_del+0x10/0x26 Jan 23 18:19:58 vesta kernel: posix_clock_unregister+0x1c/0x41 Jan 23 18:19:58 vesta kernel: ptp_clock_unregister+0x69/0x6d Jan 23 18:19:58 vesta kernel: igb_ptp_stop+0x1a/0x44 [igb] Jan 23 18:19:58 vesta kernel: igb_remove+0x39/0xfd [igb] Jan 23 18:19:58 vesta kernel: pci_device_remove+0x36/0x8e Jan 23 18:19:58 vesta kernel: device_release_driver_internal+0x144/0x225 Jan 23 18:19:58 vesta kernel: driver_detach+0x6d/0x77 Jan 23 18:19:58 vesta kernel: bus_remove_driver+0x60/0x7c Jan 23 18:19:58 vesta kernel: pci_unregister_driver+0x1c/0x7f Jan 23 18:19:58 vesta kernel: __se_sys_delete_module+0x10f/0x1ac Jan 23 18:19:58 vesta kernel: ? exit_to_usermode_loop+0x55/0xa2 Jan 23 18:19:58 vesta kernel: do_syscall_64+0x57/0xf2 Jan 23 18:19:58 vesta kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jan 23 18:19:58 vesta kernel: RIP: 0033:0x150ae6d72047 Jan 23 18:19:58 vesta kernel: Code: 73 01 c3 48 8b 0d 49 7e 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 b0 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 19 7e 0c 00 f7 d8 64 89 01 48 Jan 23 18:19:58 vesta kernel: RSP: 002b:00007ffc617bb338 EFLAGS: 00000206 ORIG_RAX: 00000000000000b0 Jan 23 18:19:58 vesta kernel: RAX: ffffffffffffffda RBX: 0000000000427cf0 RCX: 0000150ae6d72047 Jan 23 18:19:58 vesta kernel: RDX: 0000000000000000 RSI: 0000000000000800 RDI: 0000000000427d58 Jan 23 18:19:58 vesta kernel: RBP: 0000000000427d58 R08: 1999999999999999 R09: 0000000000000000 Jan 23 18:19:58 vesta kernel: R10: 0000150ae6de9ac0 R11: 0000000000000206 R12: 0000000000000000 Jan 23 18:19:58 vesta kernel: R13: 0000000000000000 R14: 0000000000427d58 R15: 0000000000425480 Jan 23 18:19:58 vesta kernel: Modules linked in: sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_uncore intel_rapl_perf i2c_i801 ipmi_ssif igb(-) i2c_algo_bit i2c_core smartpqi ahci libahci scsi_transport_sas wmi pcc_cpufreq ipmi_si button [last unloaded: atlantic] Jan 23 18:19:58 vesta kernel: CR2: 0000000000000000 Jan 23 18:19:58 vesta kernel: ---[ end trace bfd77ca2011f6527 ]--- Jan 23 18:19:58 vesta kernel: RIP: 0010:kernfs_name_hash+0x9/0x6d Jan 23 18:19:58 vesta kernel: Code: 48 33 04 25 28 00 00 00 74 05 e8 c3 3d ea ff 48 83 c4 60 4c 89 f0 5b 5d 41 5c 41 5d 41 5e 41 5f c3 48 83 c9 ff 31 c0 49 89 f8 <f2> ae 48 f7 d1 8d 79 ff 31 c9 48 39 cf 74 1f 49 0f be 04 08 48 ff Jan 23 18:19:58 vesta kernel: RSP: 0018:ffffc90006b27cb8 EFLAGS: 00010246 Jan 23 18:19:58 vesta kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffffffffffff Jan 23 18:19:58 vesta kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 Jan 23 18:19:58 vesta kernel: RBP: ffff889fcab65198 R08: 0000000000000000 R09: ffffffff811ac100 Jan 23 18:19:58 vesta kernel: R10: ffffea007f2ad900 R11: ffff889fff075001 R12: ffff889fcab65348 Jan 23 18:19:58 vesta kernel: R13: 0000000000000000 R14: ffff889ff3a6c190 R15: 0000000000000000 Jan 23 18:19:58 vesta kernel: FS: 0000150ae6c37b80(0000) GS:ffff889fff680000(0000) knlGS:0000000000000000 Jan 23 18:19:58 vesta kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Jan 23 18:19:58 vesta kernel: CR2: 0000000000000000 CR3: 0000001ff3b5a002 CR4: 00000000003606e0 Jan 23 18:19:58 vesta kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Jan 23 18:19:58 vesta kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Jan 23 18:19:59 vesta rsyslogd: [origin software="rsyslogd" swVersion="8.1908.0" x-pid="2507" x-info="https://www.rsyslog.com"] start After the call trace the system hangs, and I need to do a power off / power on to get a "proper" boot up

I personally have a UniFi USG router and separate switches and APs which is way overkill for your needs. However I can highly recommend the Netgear Nighthawk (an R6700 or R7000). I also used an Asus RT-N66U for many, many years. It was a true workhouse, but, I eventually retired it a couple of years ago. In the interim before moving to the Ubiquiti gear, I used a Netgear R6400. It was a solid router that I never had to reboot. I bought an R6700 for my sister's house, but, it ended up not working well with their crappy ISP gear (not a Netgear problem), so I gave that one to my son a couple of months ago. They love the R6700 as it provides good coverage throughout their 4000 sq. ft. home (very open two-story + basement) including to basement apartment they rent out. They said it was a much better router than their prior ISP supplied garbage. The R6700/R7000 are basically the same hardware (other than an additional USB port on the R7000) and meet all of the above requirements other than supporting VLANs, ax WiFi, and MU-MIMO. For a price reference, the R7000 is $133 on Amazon https://www.netgear.com/home/products/networking/wifi-routers/R7000.aspx If you want MU-MIMO here are the Netgear models that support that: https://www.netgear.com/landings/MU-MIMO/

This is what I replaced my 66n with a few years back. https://www.amazon.com/dp/B0752FD3XJ/ref=cm_sw_r_sms_apa_i_woDkEbN1DRN87 I've seen some bad reviews in later 2018 might have been some manufacturing issues but mines been solid and I bought it January 2018. The 5ghz radios range is amazing. Sent from my Pixel 2 XL using Tapatalk

CHBMB and I use ours with FreeSat. Yea you would still need to use TVH/TVH Proxy to pipe it into plex. I'm also running a HDHomerun now for Freeview. These integrate straight into Emby/Plex.

Congrats. Waiting for the Dutch translation 😋

@DZMM That's the same permission issue I ran into when creating the setup.sh file using notepad++ and putting it in adb's appdata folder. Start by opening the adb container's console. Check your permissions by typing ls -alh /config I corrected mine using chmod 777 /config/startup.sh and chown root:root /config/startup.sh I also noticed in your post the same formatting errors that I had from c/p with notepad++. Your issue may just be c/p to your post, but verify you don't have the two "(anglebracket)" in your script. If you're not familiar with vi, it's unintuitive at first. After typing vi /config/startup.sh move your cursor to an area where you need to make a change. Hit "i" on your keyboard. Make the necessary changes. Hit the "esc" key when you're done making changes. Type ":wq" to write the changes and close the file. Restart adb.

Because your script is trying to execute /boot/scripts/undervolt. You script needs to execute bash /boot/scripts/undervolt

a lack of punctuation does not help your situation either.

My unraid was on 6.8.1 already and decided to downgrade to the rc5 to see if all works for me. I renamed my bz* files - copied in the rc5 bz* files - copied in the Skitals bz* kernel files. I was forced to Delete VM and recreate new VM, as when I tried to pass through one of the USB devices listed inside Form view - Error about not understanding the "Vendor" of a PCI device. The recreate of the VM and then passing through the device and also passing through the nvme bare metal with the HostDev method in XML view worked perfect. Afterwards I used the VFIO-pci-config tool to create the config file for passing the USB controller through BIND=08:00.0 08.00.1 08.00.3 05.00.0 07.00.0 0f.00.4 I have a extra USB controller card to pass to my VM. And the AMD Navi bug......Working now perfectly. On this note - could Limetech not build this is with a flag to enable if you have a AMD x5700 XT card and experiencing this reset issue....so it becomes mainstream. I am worried that we might get stuck on older builds and having to burden Skitals with rebuild requests of the kernel. Cudos to Skitals for making the fix for us - love it !!!! thanks CrystalDiskMark image included of Win10 VM nvme baremetal....not sure if its good or not. Could not get a driver to replace the redhat one so still on virtualised driver.

+1 to that from me @FoxxMD

If it gives you a playlist (as I think it does), you could just use that with xteve to get it into Plex. xteve is much more reliable than tvhproxy.

Digibit R1 (DVB-S2) https://telestar.de/produkt/digibit-r1/ Couple of us within the team run these with this firmware: https://github.com/perexg/satip-axe

This seems to be happening to various users, in fact it just happened to me after updating one of my servers to v6.8.1: I'll create a bug report about this. Done:

For the record, only write errors cause disks to be disabled, and there is one in your syslog.

correct!

Just thought I'd share in case anyone else lands here like I did. I'm traveling for work and not at home, so there was only so much I could do, but based on my limited success, I can shed some light on getting the docker container config set up on unRAID along with the sh command that seems to be a point of confusion in this thread. Thanks to the video posted by @DZMM, I was able to figure this out fairly easily. I had also initially created the setup.sh script in the /config folder using notepad++, as this is how I frequently do it for Home Assistant, but there were formatting and permission issues (the latter was warned in the video) so I just recreated the file using vi from the container's terminal and presto. ADB isn't enabled on my TV at home, which is the limitation I mentioned earlier so I get the "No route to host" error, but I'm fairly confident this will work when I get it enabled. Good luck!

Or a CPU with an iGPU that can do hardware transcoding (that's what I have) and completely eliminates the need for Unraid Nvidia and a separate GPU. A recent generation i5/i7/i9 or Xeon would take care of it nicely for you. Probably better to stay i7 and above, if possible.

Thanks! That progressed thing a little further 🙂 Everything seems to start up fine but I get this error message in the end: [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. EDIT: Looking back in the thread, I can see that this is apparently only a warning because SteamCMD is not running. I'll try to muck about with it and see if I can find the server in the browser in-game.

I have issues (stutters) with my gaming VM with my Ryzen 3800X. I've almost given up. I thought 6 months was enough for the software to catch up with the hardware, but I was wrong. I still have one last ditch effort moving to the v5 Linux kernel on the last batch of RCs, but after that, I'm surrendering. Anyway, I looked at your XML and I have a couple recommendations (though I don't think it's going to help ... Still maybe better in general though). I expect you did all the normal things, so only going to comment of what's there. I see you're using your emulator pinning on your lowest core. I wouldn't do that. In my testing I have seen an idling VM take a fair amount of CPU usage for the emulator and it can spike under load. You really don't want the scheduler working around some host tasks that usually run on the lowest core. Also, the emulator process is a single thread. I have been using a HT core (i.e. HT coreA, HT coreB) for the emulator too, but just last night I monitored my emulator process and saw it hopping between both HTs while only having 1 active at any given time. Probably ok, maybe not the best for a long running process where you want to minimize latency. Try keeping it to one vcpu. I saw no noticeable difference in either case, but since the process stays alive the whole time the VM is on, there's no reason to have the scheduler move it around. IMO, let the scheduler work around the emulator process. I would try shifting all your cores to the highest cores on your CPU and leave the lowest for the host. Also, maybe limit your VM cores to the ones on the same CCX so they don't have to talk over the InfinityFabric. I tried to find an lstopo of the 3900x on Google but I couldn't find one. Maybe post yours here? Unrelated to the CPU, you are passing in your GPU and HDMI sound as 2 separate addresses. SpaceInvader One talked about it in his Advanced GPU passthrough YouTube video. Probably won't change anything, but take a look at that video and try passing the GPU as a multifunction device. Also, are you stubbing your GPU? @Skitals has a x3900. Maybe he has some more recommendations for you. -JesterEE

found this docker last night: https://hub.docker.com/r/celedhrim/kodi-server he used to be one of the guys that did the kodi-headless patch. he complained about how it wasnt fun to maintain the patch and that the increasing build times was exceeding the allowed time on dockerhub which was causing its own problems. he switched to doing fake Xorg ( with XPRA) and pulseaudio ( kodi complain is no sound card/daemon) no more patch to maintain, uses kodi ppa ubuntu image, which is much faster to build. but does result in more cpu/memory (as it has to waste cycles to do the full interface) and does rely on the ppa images (which only matters if kodi removed old images and you wanted to build an older version) so far its working just fine for me. sonarr talks to it and I see it updates everything as a normal linux box. to set it up I just installed the docker via CA docker (search for: kodi-server) since I wanted to get latest leia: celedhrim/kodi-server:leia added path 'data' and set it to my old kodi-headless dir: /mnt/cache/appdata/.kodi added 'port': 8089 (he exposes this one instead of the default 8080 --- so update advancedsettings webserver port to 8089 (or change mapping)) added 'port': 9090 (so websocket to the docker works)

In principle it should just work Only caveat would be if the disk controllers on one of the machines is nor a standard HBA and is not presenting the drives in the same way on both machines.

Actually you only lose the contents of the failed drives and not the whole array as with Unraid each drive is actually a discrete self-contained file system (one of its strengths in severe failure scenarios). However the gist is correct in that with untrustworthy drives in the array you are at a significant risk of data loss.

Not simply a matter of drive failure during rebuild. Bad disks can also give bad data that makes the rebuild no good.

Another thing you could do with the disks instead of making them part of the array is having them as unassigned disks and pass them to a vm or something to use as a dumping location and that way they still have a use but are not part of the array as such. Perhaps as a onedive or dropbox drive for a vm or some other thing you might use them for.

And we thank you for doing what you do!

We found yesterday there are some issues with the 3rd gen ryzen and caching. There isn't a way to fix it 100%. Technically your cache should be fixed with the below but doubt it will.. If it works you should see a boost in performance but there is a fix needed for virtio/qemu <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='8' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> <feature policy='disable' name='monitor'/> <feature policy='require' name='hypervisor'/> <feature policy='disable' name='svm'/> <feature policy='disable' name='x2apic'/> </cpu>

The fun never stops, I uploaded a new 6.8.0-rc5 kernel today that incorporates a bunch of goodies for this board. Brand new k10temp patches for Ryzen, and a fix for passing through onboard audio!

Unfortunately, the trend in 2020 computing does not favor our collective need for a reasonably sized, quiet, mid/full-ATX chassis with LOTS of mounting locations to accommodate mass storage solutions. It simply doesn't exist ... and really, TBH, it never really did. Fitting 3x 3.5" to 5.25" bay cages for 15 total drives in a tower has always been a workaround, and a pretty expensive one at that when each cage can cost $50-$150! By the time you configure the chassis with the required bays and cooling, you're looking at, at least, $350 ... and that's if you really try hard not to overspend! That's more than I'm willing to drop on a bad solution to a niche problem, but I can't speak for everyone. Also, IMHO, most of the chassis that accommodate these builds are ugly! Even if they were/are reasonably priced, I would not want to build in them even if it is going to sit in the corner or a closet. The notable exception, the Silverstone Temjin TJ11. But at $350 when it was released ~2014 ... and $750 now for the few places that have 1 or 2 left in the back of the stockroom, this was ALWAYS an expensive build. And to uglify it with hot-swappable cages, to me, seems like a sin. Also, a nod to @Harro's functional build. I'd love to find an original Cooler Master Centurion 590 in a dumpster or Good Will somewhere 🤣! Going forward I think we all need to bite the bullet and realize this is just not going to happen unless the winds change direction and personal storage solutions that don't include overpriced and under-powered systems (*cough* Synology) become common place. I think most people that find this thread know that there are server grade racked solutions out there with reasonable second hand prices. But, for someone that really wants to keep their build to a workstation, this is not an option. It even bugs me a little when people flippantly post something like, "just buy a used 4U server ... 24+ bays, problem solved." Not helpful ... at all! If "we" wanted a 26"-30" deep, 100+ lb. tank with jagged corners and awful non-racked standing solutions that sounds like a jet engine ... then yes, problem solved! But, "we" don't. I don't intend to ignite a flame war here ... but after all, this thread is for tower cases. It says it right in the title. Why are people even bringing up rack solutions? I'll give a pass to those recommending casters for rack chassis though. Not what I'm after, but OK. I contacted 45 Drives about their Storonator Workstation. I was pretty sure they only sell them as a configured solution, and they don't post the chassis dimensions, but it couldn't hurt to ask when it has space for 11x 3.5" and 8x 2.5" drives on a single back-plane 🤤. But alas, they don't offer it bare 😭. Here's to hoping that one day they change their mind or make something better to fill this dearth in our niche market segment. For a reasonably sized average 45L volume chassis, with a full back-plane for 10+ drives ... I would pay a premium! There are still some options in production by Fractal Design, Phanteks, and Rosewill that will support 10+ drives without breaking the bank only costing ~$200-$250 all in. Here are some as of January 2020: Fractal Design Fractal Design Vector Fractal Design Define R6 10x 3.5" drives (requires finding/purchasing 4 additional trays) Phanteks Phanteks Enthoo Pro Phanteks Enthoo Luxe 3x 5.25" + 6x 3.5" = 11x 3.5" drives (with 1 cage) Rosewill Rosewill Thor v2 (Might actually be out of production ... but currently available (in white) for $120 USD from Newegg) 6x 5.25" + 6x 3.5" = 16x 3.5" drives (with 2 cages) Also, as other's have reported, you can still find semi-reasonable prices on some second hand towers from the early-2010s. This is the option I am going with for my server. I just bought a NZXT H440, which is a hell of a nice case (IMHO), with lots of space for fans and breath-ability for keeping the drives cool. I plan on doing a simple mod to mount a total of 11x 3.5" drives in this platform. Actually, the last mounting location is odd, sitting on the bottom of the chassis, and I probably will not use it. But this will leave a good amount of "free space" which I was thinking about filling with a 6x 2.5" drive cage if I can find/tap a good mounting solution. I haven't built in it yet, so this is still TBD. But, for $80 shipped (after some hunting ... and sniping) ... DONE! -JesterEE

So I went into my flash drive and under config > plugins I deleted anything related to unassigned devices. Rebooted and installed UD and I am able to mount the remote share, however.. the share is not visible anywhere and can't be navigated to outside of unRAID's Web UI EDIT: Took a few minutes for the share to pop up but I think its working now.

It is, but Ryzen on Linux can lock up due to issues with c-states, make sure bios is up to date, then look for "Power Supply Idle Control" (or similar) and set it to "typical current idle" (or similar), or completely disable C-sates. More info here: https://forums.unraid.net/bug-reports/prereleases/670-rc1-system-hard-lock-r354/

After following this thread I thought I would spin up 2 new, identically configured Windows 10 VMs in Unraid 6.8.0 to see if the i440fx vs Q35 debate shows anything for my system under QEMU 4.1. Originally I had some issues on my QEMU 3.0 i440fx Windows 10 VM with video glitching, so an update was necessary anyway. Before getting entrenched in a VM architecture, I wanted to see which was going to pan out best at the on-set of my new build. For these benchmarks I ran a "gaming oriented" (Hyperv enlightenments, isolated CPUs, emultor pinning, iothread pinning) Windows 10 VM with 4 HT cores of an AMD 3800X in performance mode and pass-through of a Gigabyte NVIDIA GeForce GTX 1060 6GB Windforce. Here are AIDA64 results which show negligible difference in performance between the 2 VMs. Likely, if I ran a statistically relevant number of tests, they would be the same. Notable, in the Q35 VM, NVIDIA System Info reports my PCI-E lanes correctly (x16 PCI-E 3.0 for this card). In the end, I went with the i440fx machine. I'm not saying I agree with getting rid of Q35 as an option. Options are good for everyone (as long as they aren't broken)! Just a data-point. -JesterEE

If you want 10 minutes of runtime, you need to spec at least 20 minutes of advertised capacity at the draw you anticipate. The types of batteries used generally don't like being run down below 50%, so if you want to keep the UPS healthy for as long as possible you need to limit the amount of power you pull out of it. Sounds to me like you would be better off with a mid sized UPS, something around 1000VA. The APC BR1000G is rated for 24 minutes at 200 watts, which is probably a good real world estimate for your rig + router +switch + modem. Keep in mind that shutting down unraid brings the power draw to the absolute upper limit of any system, as it has to spin up all drives to properly unmount them, and high cpu load as all the running services are issued the shutdown commands.

I love this community, half of 'em are screaming like hellfire when a vulnerability goes longer than 30 seconds unpatched, the other half want to switch it off. Me, I'm in the latter camp.

DEPRECATED

This will truncate the docker logs, but just to be certain, data of my individual docker containers aren't affected? I'm not sure if any container logs actual data to the -json.log files.

With Sandybridge or newer you can check the real frequency, with Nehalem it will only show max base frequency (no boost), SSH into your server and type: watch -n 1 grep MHz /proc/cpuinfo