Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 11/08/19 in all areas

  1. 2 points
    I know that feeling. There is always that one guy that has another little tweak πŸ˜‚ Already seeing a 19% improvement in the memory score with this set. I'll also test hugepages. By using "interleave" you spread the RAM accross all memory controllers from all nodes, even the ones from the node you're maybe not using in the VM. On first gen TR4 this was a big issue, because it added a lot of RAM latency. Sure you get the higher memory bandwith by using "quad channel" but in most scenarios in my tests the lower latency was the preferred option. Not exactly sure how big of a difference it is on second gen TR4, but using "Preferred" or "Strict" was the better choice for me. Every program, game or benchmark is more or less affected by the lower bandwith by basically turning the RAM into a dual channel configuration. The bigger impact I saw by reducing the latency by using the "strict" setting. Maybe have a look into the "Cache & Memory Benchmark" which comes with AIDA64 to test this. This is a part of the extra CPU flags I use for a while now. <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>EPYC</model> <topology sockets='1' cores='7' threads='2'/> <cache level='3' mode='emulate'/> <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> By forcing Windows into recognizing the CPU as an EPYC with these tweaks, it also recognizes the correct L1, L2 and L3 cache sizes which the node has to offer. Without it showed wrong cache sizes and wrong mapping numbers. Without these tweaks and the correct readings, starting up 3DMark for example always crashed or frooze the VM completly at the point, where it gathers the system infos. Not sure which other software might be affected, but this helped me in this scenario. Obvisiously the vcore is reported wrong, but the cache info is reported correctly with this tweak. 1 core is used for iothread and emulatorpin <emulatorpin cpuset='8,24'/> <iothreadpin iothread='1' cpuset='8,24'/> and the rest only specifically for this one VM. One 8 core die of the 2 from the 1950x is dedicated to this VM only and by adding up the numbers it exactly matches the specs of AMD. BUT this isn't the complete list of tweaks. There are way more you can play around with πŸ˜‚πŸ˜‚πŸ˜‚ <cpu mode='custom' match='exact' check='full'> <model fallback='forbid'>EPYC-IBPB</model> <vendor>AMD</vendor> <topology sockets='1' cores='4' threads='2'/> <feature policy='require' name='tsc-deadline'/> <feature policy='require' name='tsc_adjust'/> <feature policy='require' name='arch-capabilities'/> <feature policy='require' name='cmp_legacy'/> <feature policy='require' name='perfctr_core'/> <feature policy='require' name='virt-ssbd'/> <feature policy='require' name='skip-l1dfl-vmentry'/> <feature policy='require' name='invtsc'/> </cpu> At some point I stopped, because I had no time back than to fiddle arround with it even further and the system was stable enough anyways. Main programs run fine and games performed great. Edit: Forgot to mention it reports "Hyperthreaded" for me in CoreInfo.
  2. 2 points
    The macinabox template uses custom ovmf files. If you change <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/e930dfa3-ce5f-4a14-a642-d140ed8035bd_VARS-pure-efi.fd</nvram> </os> to be as below you will be back without the screen corruption. <os> <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/domains/MacinaboxCatalina/ovmf/OVMF_CODE.fd</loader> <nvram>/mnt/user/domains/MacinaboxCatalina/ovmf/OVMF_VARS.fd</nvram> </os> hope that helps πŸ˜€
  3. 1 point
    Application Name: Heimdall Application Site: https://heimdall.site or https://github.com/linuxserver/Heimdall Docker Hub: https://hub.docker.com/r/linuxserver/heimdall/ Github: https://github.com/linuxserver/docker-heimdall 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.
  4. 1 point
    Probably could use a change to the default label to add something like "non-UEFI only" to prevent against confusion.
  5. 1 point
    You can only run the memtest included with Unraid if booting in legacy mode. If you want a version that can be used when booting in UEFI mode then you need to download it yourself from the memtest web site.
  6. 1 point
    I have several containers that I need to have their own IPs in order to route them through my routers VPN, all other traffic is fine to go over standard network. Unfortunately I've noticed that the dockers that are using br0 are unable to communicate with each other thus I'm not able to use nginx to route to these containers. What is the best way of doing this? I'm sure further information will be needed but please let me know where to start. Thank you!
  7. 1 point
    Don't use Jumbo frames. Keep MTU at the recommended default - generally about 1400 to 1500. This is probably causing your issues with SMB mounts.
  8. 1 point
    Found eventually a solution for your problem if you are using the old database you must do this commands within the container in mysql *LINK* If you are using a new instance of the container the error is also there but it's just a WARNING and not an error that doesn't start the container.
  9. 1 point
  10. 1 point
    It's best to not mess with these files. I suggested in an earlier post that you set the UD Setting for the SMB shares to enable Hidden shares. The shares will not be browseable in Windows. Isn't this what you are looking for?
  11. 1 point
    New Intel microcode for MOAR CVE: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/tag/microcode-20191112 https://www.phoronix.com/scan.php?page=news_item&px=iITLB-Multihit-TAA-Kernel-Code
  12. 1 point
    i think so, see https://wiki.unraid.net/Boot_Codes
  13. 1 point
    Yes, that's right: the man, the myth, the legend Spaceinvader One has graciously agreed to sit down for an interview with us. If you could ask him something, what would it be? Best questions will make it in to an upcoming interview blog. Fire away!
  14. 1 point
    You could go with a Rosewill or Norco case but if you want to do it right, buy a used Supermicro chassis. They are well worth the cost. A CSE-826 (2u, 12 x 3.5” drives) or CSE-743 (4u, 8 x 3.5” drives), would be some good options that meet what you want. CSE-836 and 846 are also great and give you a lot more room to expand. Do it right and buy something that’ll be dependable. Let me know if you’re interested and I can explain what some of the model differences are and ways to keep them cool and quiet.
  15. 1 point
  16. 1 point
    Not just you... this docker has a very frequent update. The auto updater plugin is your friend in this case, set it and forget it.
  17. 1 point
    Have you try boot in safe mode ? Pls also confirm BIOS up to date and check BIOS power limit setting. And CPU power supply wire in 4pin / 8pin ?
  18. 1 point
    The nmap package was updated by me. The repository was not compromised. This has been discussed ad-nauseum. I removed the package, and then I agreed to leave nmap in as a convenience to users. I won't remove the package from the plugin. Conditional plugin installation is not easy. I'm not sure what could be done except your manual removal.
  19. 1 point
    I would setup a VPN server on unRAID and then client on your laptop or remote computer to establish a secure VPN connection between the remote computer and the unRAID server, then you can do whatever you want across the VPN tunnel.
  20. 1 point
    @theDrell The fix is now live in the latest beta and might get it's own point release as v1.50.2. If the beta fixes your problem please report back in this thread
  21. 1 point
    metadata location (as in /config) is shown in unraid web ui/docker tab/ left click plex, select edit, click 'advanced view' top right, click on 'show more settings' and you should then see the host path defined for container path /config.
  22. 1 point
    This worked! I tried a few options, but found that PCIe ACS override being set to Multi function worked for me. Thanks for the help!
  23. 1 point
    Kernel update: * build for 6.8.0rc5 with 5.3.8 * add navi-reset.patch * add vega-reset.patch * add pci-reset-quirk.patch to thoes who can't do bios update
  24. 1 point
    There was an update for the container midnight and my server auto updated at 6am without problems, and looks like my dbengine database files are persistent now. So looks like the "delete obsolete charts files = no" setting solved the problem.
  25. 1 point
  26. 1 point
    The parity drive has nothing to do with the cache drive. But, if the parity drive is even 1 byte less than any data drive (perhaps due to a HPA partition present on it) then the system will do what you're stating.
  27. 1 point
    Well you are not alone, thanks for helping out another idiot
  28. 1 point
    I dont use array encryption myself so I am not completely sure about this, but if you have your server sleeping that wont cause the array to lock will it? I used the the S3 sleep plugin myself for quite some time (the only method of sleep i am aware of for unRAID). If i remember correctly S3/Standby leaves the array mounted and thus unlocked.
  29. 1 point
    You only need it for private shares. If you set the Security option to Private a Rule box appears into which you need to enter the code. Public shares are easier. I'd experiment with those first. On the client you mount an NFS share using the mount command like this: mount -t nfs tower:/mnt/user/name-of-share /mnt/mount-point which is similar to how you would mount an SMB share. Note that you have to specify the full path to the mount (i.e. tower:/name-of-share wouldn't work) and /mnt/mount-point must already exist on the client. To unmount the share you use either umount tower:/mnt/user/name-of-share or umount /mnt/mount-point This information is summarised here: https://linuxize.com/post/how-to-mount-an-nfs-share-in-linux/
  30. 1 point
    Probably, I saw some older read errors on parity2 on the first diags, but since they were old (a year or so ago) didn't mentioned them, but since there are more now, and they are a disk problem, you should replace it, it's even possibly the disk was causing the sync errors, though disks shouldn't return wrong data, it's been known to happen.
  31. 1 point
    Oct 12 03:35:17 Storage kernel: tun: unexpected GSO type: 0x0, gso_size 1357, hdr_len 1411 Oct 12 03:35:17 Storage kernel: tun: 13 e4 3d f7 10 86 b8 9e 87 b1 5f 81 d9 7a 98 c9 ..=......._..z.. Oct 12 03:35:17 Storage kernel: tun: 26 fa 2d 78 50 03 f2 b2 22 55 bc 68 29 75 83 46 &.-xP..."U.h)u.F Oct 12 03:35:17 Storage kernel: tun: 04 35 d4 e4 71 d8 5c 04 e3 e2 a2 6d 4e 1f 22 9d .5..q.\....mN.". Oct 12 03:35:17 Storage kernel: tun: 6f 97 72 60 c9 63 2b dc f4 ec c7 4f 68 60 66 9e o.r`.c+....Oh`f. Getting the above message repeated over and over again in the log whenever a docker tries to access the NIC. storage-diagnostics-20191012-0237.zip
  32. 1 point
    The next thing to test is the USB stick itself. Shutdown your server and plug your USB stick into a PC and check/repair the file system on it. With Windows you can right click and choose Properties, then Tools and check/repair the device. With macOS you can use the Disk Utility.
  33. 1 point
    Thank you for setting this up! I had to change the ports to UDP for it to work but after that, connected beautifully.
  34. 1 point
    The corruption occurred as a result of failing a read-ahead I/O operation with "BLK_STS_IOERR" status. In the Linux block layer each READ or WRITE can have various modifier bits set. In the case of a read-ahead you get READ|REQ_RAHEAD which tells I/O driver this is a read-ahead. In this case, if there are insufficient resources at the time this request is received, the driver is permitted to terminate the operation with BLK_STS_IOERR status. Here is an example in Linux md/raid5 driver. In case of Unraid it can definitely happen under heavy load that a read-ahead comes along and there are no 'stripe buffers' immediately available. In this case, instead of making calling process wait, it terminated the I/O. This has worked this way for years. When this problem first happened there were conflicting reports of the config in which it happened. My first thought was an issue in user share file system. Eventually ruled that out and next thought was cache vs. array. Some reports seemed to indicate it happened with all databases on cache - but I think those reports were mistaken for various reasons. Ultimately decided issue had to be with md/unraid driver. Our big problem was that we could not reproduce the issue but others seemed to be able to reproduce with ease. Honestly, thinking failing read-aheads could be the issue was a "hunch" - it was either that or some logic in scheduler that merged I/O's incorrectly (there were kernel bugs related to this with some pretty extensive patches and I thought maybe developer missed a corner case - this is why I added config setting for which scheduler to use). This resulted in release with those 'md_restrict' flags to determine if one of those was the culprit, and what-do-you-know, not failing read-aheads makes the issue go away. What I suspect is that this is a bug in SQLite - I think SQLite is using direct-I/O (bypassing page cache) and issuing it's own read-aheads and their logic to handle failing read-ahead is broken. But I did not follow that rabbit hole - too many other problems to work on
  35. 1 point
    1 thing I forgot to add. mount_unionfs will also protect your cloud storage since any change will be downloaded first and then any change is done (including delete - which unionfs just hides the file).
  36. 1 point
    remove the space after the coma for the last device id and reboot. you would have to check your scheduler and the logs to see what is happening at that time.... could be trim, could be anything.
  37. 1 point
    Great interview! Fantastic videos, they got me into unRAID and I watch every one you release @SpaceInvaderOne. A live stream would be great, you should do a regular slot! Neat setup with the servers, it gave me some ideas for my three servers. Keep up the excellent work.
  38. 1 point
    Awesome interview... really looking forward to future videos. BTW - pfSense in an Atari 800xl... priceless...
  39. 1 point
    You should recreate the docker image, but before doing it appears there was an unclean shutdown during a cache balance operation, and the cache pool is now stuck trying to continue the balance, better to backup anything on cache and recreate the pool, and since you're v6.8 it will be created with redundancy, unlike it was because of a bug with v6.7.
  40. 1 point
    Same here. Would not have found and build my unraid environments without Spaceinvader and Linus. Both added in different ways , ideas , methods etc
  41. 1 point
    Thanks Unraid for the interview, and especially thanks @SpaceInvaderOne for all you've contributed to the community! Without you I doubt I would have ever been able to get my own home server running let alone built or even considered in the first place. I've watched so many of your videos and they are all truly helpful. Please don't ever stop making them! 😊
  42. 1 point
    Yea, those lists. Problem solves itself by using the "Safe docker permissions" thingy, but as soon as I download something new the rights gets broken. Hmm, well it seems that I was correct using TRANSMISSION_UMASK as I did at the start, I have now switched back, will try with some small downloads. What I have read, 000 is the same as 777 so I am going back to this to try again, maybe I missed something. Thanks, will report back my findings.
  43. 1 point
    Overview: Support for Docker image arch-jellyfin in the binhex repo. Application: Jellyfin - https://github.com/jellyfin/jellyfin Docker Hub: https://hub.docker.com/r/binhex/arch-jellyfin/ GitHub: https://github.com/binhex/arch-jellyfin Documentation: https://github.com/binhex/documentation If you appreciate my work, then please consider buying me a beer 😁 For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here
  44. 1 point
    @Rick Sanchez - I just created a new Win10 VM for myself. I thought I was stuck at the same place. However, It's a super simple fix if it's the same issue. You need to connect to the VNC _REALLY FAST_ so you can catch the boot screen where it says "Press any button to boot into the CDROM...". It may take a couple of tries, but you'll see it if you have your VNC client ready to go as soon as you hit Start on the VM.
  45. 1 point
    I can confirm that Plex hardware transcoding continues to work with the above settings. Very happy with my setup now.
  46. 1 point
    I don't use unraid yet, but I can confirm I have IPMI VGA remote console working alongside with working IGFX Quicksync or other 3D offloading tasks. This is working with either Windows physical machine or in ESXI where you setup Intel IGFX for passthrough so your VM can use Quicksync (tested with Windows VM) I was not able achieve simultaneous picture from IPMI VGA remote console and IGFX connected digital display though. Either IPMI VGA has active display or IGFX, but not both at same time, I guess this really BIOS limitation, but at least you should be able to use Quicksync with IPMI VGA remote console. X11SCA-F BIOS settings Primary Display : PCI Internal Graphics: Enable after reboot IGFX GOP Version is populated in BIOS. Other observations with this board someone could use. Passthrough of motherboard AHCI controller is possible with ESXI, but only when you boot your VM with BIOS. With EFI VM gets powered off. You can use HDD ATA Security with compatible drives (User HDD Password)
  47. 1 point
    You mean something like this: Copy the file to your flash drive (named something like background.jpg) Add the following to you go file (config folder on the flash drive) before the emhttp line cp /boot/background.jpg /usr/share/slim/themes/default/background.jpg
  48. 1 point
    Please post either your diagnostics or a crystal ball.
  49. 1 point
    If the file(s) were say on a disk you copied over to a share via something like mounting the drive with Unassigned Devices and using Krusader or unBalance or whatnot to move the files over, then permission issues are possible. The only time I've ever had permission issues with files created on Windows and transferred over SMB to a share was with using robocopy, which trashes normal smb permissions.
  50. 1 point
    How do I keep my sparse vdisk as small as possible? How do enable trim on my Windows 8/10 or Windows Server 2012/2016 VM? By default vdisks are sparse, i.e., you can chose 30GB capacity but it will only allocate the actual required space and use more as required, you can see the current capacity vs allocated size by clicking on the VM name, problem is that over time as files are written and deleted, updates installed, etc, the vdisk grows and it doesn't recover from the deleted files. This has two consequences, space is wasted (doesn't matter if the vdisk is on an SSD or HDD) and if the vdisk in on an SSD that unused space is not trimmed, it's possible to "re-sparsify" the vdisk e.g., by cping it to another file, but this it's not very practical and there's a better way. You can use the vitio-scsi controller together with discard='unmap', this allows Windows 8/10 to detect the vdisk as "thin provisioned drive", and any files deleted on the vdisk are immediately recovered as free space on the host (again both on an SSD or HDD), and this also allows fstrim to then trim those now free sectors when the vdisk is on an SSD. On an existing vdisk it's also possible to run Windows defrag to recover all unused space after changing to that controller. Steps to change an existing Windows8/10 VM (also works for Windows Server 2012/2016): 1) First we need to install the SCSI controller, shutdown the VM (For Windows 8/10 I recommend disabling Windows fast Startup -> Control Panel\All Control Panel Items\Power Options\System Settings before shutdown, or else the VM might crash on first boot after changing the controller). Then edit the VM in form mode (toggle between form and XML views is on the upper right side), and change an existing device other than your main vdisk or virtio driver cdrom to SCSI, for example your OS installation device if you still have it, if not you can also add a second small vdisk and chose SCSI as the vdisk bus, save changes 2) Start the VM and install the driver for the new "SCSI controller", look for it on the virtio driver ISO (e.g., vioscsi\w10) 3) Shutdown the VM, edit the VM again, again using the form view and change the main vdisk controller to "SCSI", now change view to XML and add "discard='unmap'" to the SCSI controller: Add after cache='writeback', e.g. before: After: 4) Start the VM (if you added a 2nd vdisk you can remove it now before starting), it's should boot normally, you can re-enable Windows fast startup. 5) Run Windows Defrag and Optimize drives, check that he disk is now detected as "Thin provisioned drive" and run optimize to recover all previous unused space. From now on all deleted files on the vdisk should be immediately trimmed. Note: If after this you edit the VM using the GUI editor these changes will be lost and will need to be redone.