Darksurf

Members
  • Posts

    166
  • Joined

  • Last visited

Everything posted by Darksurf

  1. So just an update, I'm currently stuck between a rock and a hard place. I can switch to Unraid 6.9-rc1 and have no hardware transcoding OR I can stay on 6.8.3 and keep hardware transcoding for my Plex Docker, but lose the ability to monitor temps, efficient VMs, etc.
  2. I just wanted to thank Limetech for getting Unraid 6.9-rc1 out with the 5.5 Kernel. Thanks guys, I really do appreciate it. This should get me going without much issue. The only part I lack is the CPU itself and I plan to order it in the next couple of weeks so this really smooths out my server transition. I'll update with what support looks like after the server switch. Thanks again.
  3. I don't plan on overclocking. The CPU is plenty beefy by default. I do plan to "OC" memory but I don't see 2933mhz on unbuffered ECC as pushing my luck. I avoid gigabyte like the plague after running though a BIOS bug that would hardlock the system (even in the BIOS before reaching the OS!) Using a configuration they claimed to support and they blamed it on the fact that I use Linux and refused to support me. Even after explaining it locked up without even reaching an OS, they finally relented but claimed their bench test station doesn't have the hardware they claimed to support so they couldn't test. They basically left me hanging and kept claiming it was Linux so they could close the case. The specific scenario was using a specific AMD APU with 2400mhz DDR3 with the GPU set to 2G instead of 1G. They aren't Linux supporters and they suck when it comes to my experience with them. I'm normally an AMDGPU user, but my Unraid server uses a GTX 1050Ti for video transcoding in my Plex docker. It's my only Nvidia GPU.
  4. I dunno, the reviews claim its a decent linux workstation board, albeit with an issue with the sound card possibly fixed in newer kernels? I've had pretty good luck with ASRock. Even my Desktop uses the ASRock Phantom Gaming ITX X570. I've used ASRock Rack boards in the past too without issue. Wendell with LVL1Techs did a review and decided it was a decent board, especially for the money. He said the VRM heatsink actually did pretty well and the VRM may only be 8-phase, but it was high quality. The Fan can be loud, but it's going to be in a server chassis in a rack so I'm not really worried about that. The VRM is sufficiently cooled to even during overclock. Cinebench, Blender,, and even 7zip Benchmarks all showed the same Scores as all the other boards. There was no real difference outside of margin of error and ECC memory works and is supported by the board. What's not to like? It's perfect and affordable for my situation.
  5. Thanks, I need QEMU for this server to even work. No point in me having a 32-core 64-thread server if VMs are a no-go... I guess I just need to find a solution to get a 5.4+ kernel and have Nvidia card support? Sounds like a steep request considering unraid is very much like a "live distro". Guess I'll have to look into solutions for the 5.x kernel problem?
  6. I'm looking to upgrade my server to the next level. I need a beefier VM for Sabayon Linux Development. Due to this I'm looking at throwing a lot of money into a Threadripper 3960X 24 core or 3970X 32 core. I'm also looking at the ASRock sTRX40 Creator board. Will unraid support this? I know for much of Ryzen stuff (especially Threadripper) 5.4+ kernel is recommended. The 2 NICs could also be an issue with older kernels.. https://www.asrock.com/mb/AMD/TRX40%20Creator/ 1 x 10 Gigabit LAN 100/1000/2500/5000/10000 Mb/s (AQUANTIA® AQC107): 1 x 2.5 Gigabit LAN 10/100/1000/2500 Mb/s (Dragon RTL8125AG):
  7. Is there an ETA on a 5.4 LTS kernel? I need it for the threadripper server I'm building with an ASRock sTRX40 Creator MB. My current 8-core Xeon is doing OK, but I plan on needing a beefier chip in the near future as I'm hosting a VM for a Linux distro build server.
  8. Excellent! How hard would it be to get this package added to nerd tools plugin I wonder? Thanks for the assistance!
  9. So evidently there are 2 versions of the rename command. Besides this being utterly terrible, the one packaged with unraid comes from util-linux and sadly doesn't support regex as far as i can tell. I'd like to know if unraid can ditch the rename command from util-linux and replace it with the more capable Perl version or maybe give me some instruction on how to do so myself. Thanks, Darksurf
  10. Just upgraded from 6.6.7 using LSI HBA-mode RAID card. LSI Logic / Symbios Logic SAS2004 PCI-Express Fusion-MPT SAS-2 [Spitfire] Everything works great so far. All dockers loaded, VMs running, logs are clean. Great work! It doesn't like edits to the /boot/config/go file. Is it still needed to bump the size of the logs partition? Is there any way to do this via webui configuration yet? darksurf@cold-rewind:/$ cat /boot/config/go #!/bin/bash # Enlarge the LOG partition (because Dynamix System Stats needs at least 186Mb, default LOG is 128Mb) mount -o remount,size=500m /var/log # Start the Management Utility /usr/local/sbin/emhttp -p 80,443 & Thanks again for the hard work guys! 6.7 is working up to be an excellent release!
  11. OK, I just realized the issue. Evidently UNRAID is not aware that proxynet is a bridge. I had to select the default bridge and it then gave me a container port option! After setting the container port option, I was able to set the network interface back to the proxynet bridge and it worked!
  12. having an issue with this docker. I kind of want to blame unraid for this though. All my other dockers are working fine. In fact, this docker is working. The problem is I'm not getting a port mapping from the host to the docker and I can't even specify one completely. You can see in my attachment that I attempt to create a port map, but the options don't give me a place to choose a docker port, only a host port. and if you look in dockers tab, you see there's no mappings meanwhile the other dockers have no issues.
  13. I just added an old Radeon HD7850 which is supported by AMDGPU. I'd like to pass this device through to a PLEX docker. PLEX claims to support VAAPI encode/decode (which is what intel iGPU drivers use for intel quick sync). AMDGPU VCE/VCD also supports VAAPI, OpenMAX, and VDPAU. I was hoping to use this (even if unsupported) for my plex docker. Unfortunately, modprobe radeonsi results in module not found. Is UNRAID compiling kernels without AMDGPU support?
  14. Still looking for a solution. Its hard to test and purchase unraid if it doesn't boot.
  15. intel-microcode: version 20171117 Crud, you're right! I'm not sure how its loading it because /lib/firmware doesn't contain an intel-ucode directory, but that doesn't mean its not loaded somewhere. Thanks for the notice.
  16. So is there a way to add intel-ucode patching at boot? His BIOS are not receiving updates at this point so he's not getting any new microcode updates from his BIOS. I'm currently under the impression that intel microcode updates would fix his issue. There are 2 ways to update the microcode and upgrades are on volatile memory in the CPU meaning its gone on power loss. CPUs come with a base microcode and then can be pushed patches from BIOS or during early boot/kernel loading. Does unraid have a method of adding microcode updates?
  17. unfortunately neither of those hold a solution. One is fixed by updating the ucode/microcode. microcode 0x22 (2017) is already installed. To take the newest microcode would be the spectre fixes that make the CPU unstable (thanks intel). The other is about VMs and hypervisor patches when this is bare metal.
  18. Nope, its a custom, but its not impossible to be the same issue. HP does have micro servers with the E3 1231 v3 and such.
  19. This thread is about his machine actually. He just created this account a few minutes ago so he could follow the thread and get his server going
  20. Yes, this method was used. (windows) It was then changed 6.4.0, and then 6.3.5, and back to 6.4.1 in Linux with no change. UEFI is not being used. BIOS CSM is set to legacy only. The current method just takes the flash drive, formats fat32, and sets the bootable flag on the partition, then drops the zip contents on the flashdrive. Forgot to mention. Unraid boots perfectly fine on his desktop when booting from the drive. It just seems to have a problem with his server.
  21. unetbootin, dd, flashed, imaged, etc. to put an image on a media. Just as a clarification, the second 2 pictures are from the other distribution we used to test as a comparison.
  22. Here's what were seeing if that helps at all.
  23. I currently own a copy of Unraid Pro and swear by it. A buddy has become interested and wanted to get the trial copy going before buying. He bought a suggested flash drive, imaged it, and it just hangs. I tried another distro, it also hangs at INIT and complains of microcode needing to be 0x22 or higher (it currently IS 0x22). These 2 distros have one thing in common, they're using a much more recent kernel. System is currently using ubuntu 16.04 just fine with a 4.4 kernel. What is happening here? On unraid it boots all the way up to INIT: version 2.88 booting and it hangs right around there. sometimes it gets to mounting tmpfs and hangs, but it never gets much further. I have no way to get logs or anything useful. We've tried disabling ACPI, we added the acpi=off noacpi noapic flags, but it doesn't help. ANY assistance would be greatly appreciated. booting from SanDisk Cruzer Fit CZ33 16GB USB 2.0 Low-Profile Flash Drive- SDCZ33-016G-B35 I've tried unraid 6.4.1, 6.4.0, 6.3.5 Intel Xeon E3-1231V3 Haswell 3.4 GHz 4 x 256KB L2 Cache 8MB L3 Cache LGA 1150 80W BX80646E31231V3 Server Processor ASUS P9D-M Micro ATX Server Motherboard LGA 1150 DDR3 1600/1333 (Latest BIOS 1801) Crucial 16GB (2 x 8GB) 240-Pin DDR3 SDRAM ECC Unbuffered DDR3L 1600 (PC3L 12800) Server Memory Model CT2KIT102472BD160B
  24. Sorry guys, didn't mean to cause you trouble, I evidently caught the flu right not long after that tweak. I had intentions to go back and fix that, but flu hit me pretty hard, I'm at the end of it now. Seems like you guys got it under control! Thanks for the fix and sorry for the trouble.