Jump to content

Darksurf

Members
  • Content Count

    109
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Darksurf

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Excellent! How hard would it be to get this package added to nerd tools plugin I wonder? Thanks for the assistance!
  2. 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
  3. 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!
  4. 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!
  5. 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.
  6. 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?
  7. Still looking for a solution. Its hard to test and purchase unraid if it doesn't boot.
  8. 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.
  9. 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?
  10. 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.
  11. 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.
  12. 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
  13. 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.
  14. 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.