Hoopster

Members
  • Posts

    3892
  • Joined

  • Last visited

  • Days Won

    20

Hoopster last won the day on June 7

Hoopster had the most liked content!

7 Followers

Retained

  • Member Title
    unRAIDy to Rumble

Converted

  • Gender
    Male
  • Location
    Utah USA

Recent Profile Visitors

10897 profile views

Hoopster's Achievements

Experienced

Experienced (11/14)

889

Reputation

5

Community Answers

  1. Those are your options with your motherboard. You can try CPU transcoding to see how it keeps up and go with a dedicated GPU if the CPU can't handle it. With CPU (software) transcoding, passmark scores for the CPU are important. Your i3 9100 has a passmark score of 6629. In general, 2000 passmarks are needed for each 1080p stream (forget 4K) you need to transcode plus 1500-2000 for unRAID overhead. With a passmark score of 6629, you can simultaneously transcode two streams and still have enough for unRAID to do its thing. If you put a supported Xeon in your motherboard, the E3-1245 V6 has a passmark score of 8684. That will give you three simultaneous 1080p transcoded streams + unRAID overhead. UPDATE: I incorrectly linked to the passmark score for the i3-9100 CPU when the CPU in question on the Supermicro X11SSL-F motherboard is the i3-6100. The passmark score for the i3-6100 is 4154 meaning only one transcoding stream is possible.
  2. @Froberg As mentioned by @Taddeusz, motherboards based on the C232 chipset do not support QSV and iGPUs. Same with C242, C252, etc. You need the c2X6 chipsets for QSV/iGPU support. I have two motherboards in unRAID servers right now that are based on the C246 chipset and both have IPMI. QSV and the iGPU are supported in addition to the ASpeed chip for IPMI video either via a special BIOS to enable both or by settings in the public BIOS. There are some threads in these forums about the settings needed to enable both iGPU/QSV and IPMI on some Supermicro motherboards but that requires a board with the appropriate chipset which your X11SSL-F does not have.
  3. Yep, that is the case. Monitor output is via VGA connector which is controlled by the ASpeed chip.
  4. iGPU bound to VFIO = no EDID has corrupt header/EDID block 0 is all zeroes errors in syslog. ASpeed bound to VFIO = EDID has corrupt header/EDID block 0 is all zeroes errors in syslog. The iGPU in the case of my servers appears to be the culprit.
  5. Yep, looks harmless. Hopefully it can be suppressed if not eliminated in a future unRAID release. For now, I have rolled back to 6.10.3 on the always-on server. For testing purposes, I have left the backup server on 6.11.0 as it is powered on/off by script for various backups and doesn't spend much time powered on. No danger of the log filling up there.
  6. Go to Settings --> SMB in the GUI and set Enable NetBIOS to Yes
  7. Some packages may be fine as is; others may not. The issue is keeping the packages updated to work with the current version of Slackware (now 15 in unRAID) whatever that happens to be in a particular unRAID version. In the future, something that works now may not work with a new Linux kernel in Slackware. You do not have to modify the kernel or do anything fancy so it is hard to mess up. Just place the desire .txz packages in /boot/extra on the flash drive and they load when unRAID is booted.
  8. Will likely need to roll back both servesr to 6.10.3 due to the EDID has corrupt header /EDID block 0 is all zeroes errors filling the syslog. Plugged in monitor does not help. Cannot blacklist iGPU and AST (IPMI) drivers as they are actively used. Others have reported this makes no difference anyway. medianas-diagnostics-20220926-1028.zip
  9. I have a VGA monitor connected to my server. It does not stop the errors which hit the log every 2 seconds Sep 26 09:59:28 MediaNAS kernel: EDID has corrupt header Sep 26 09:59:28 MediaNAS kernel: EDID block 0 is all zeroes I have an AST (IPMI) on the server and iGPU in the E-2288G processor. I can't blacklist either as I use iGPU for transcoding and AST for KVM access to server via IPMI. Hopefully this gets fixed soon. The problem was not present in 6.10.3 which was running previously on the server. Same issue on my backup server which also has an iGPU and ASpeed chip for IPMI. No monitor is plugged into that server as it is in a closet in the basement. I guess I could try a dummy plug there but an attached monitor on main server does not prevent the errors.
  10. Look in plugins/Nerdpack and open the NerdPack.cfg file in a text editor. Anything with a "yes" is a package you were loading via the Nerd Pack. For example: ipmitool-1_8_18="yes"
  11. This one for Slackware 14.2 still works. ipmitool-1.8.18-x86_64-1.txz
  12. This usually means that since the time you purchased a license and registered your flash device GUID that someone else has attempted to register the same GUID resulting in it being blacklisted in future releases. It is possible your unRAID flash device has a non-unique GUID. In this case, you were fine on the previous version but an upgrade triggered the blacklist on your flash device GUID. This may or may not be the issue in your case, but it does happen.
  13. Expected behavior because a delay set on a docker container does not apply to starting that container. It is a delay that will be applied after the container starts to delay the start of the next container. So, yes, it is more useful on boot when multiple containers are loading. Probably on a stop and start of the Docker service as well.
  14. Updated two servers to 6.11.0 without incident. One from 6.11.0-rc5 and another from 6.10.3. I was aware the Nerd Pack was deprecated for 6.11.0 and placed the necessary packages in /boot/extra before upgrading and rebooting. I am not sure that everyone is aware the Nerd Pack has been deprecated and how to load the necessary packages. It might be wise to include this in the release notes (as if everyone reads those 😀).