Hoopster

Members
  • Posts

    4542
  • Joined

  • Last visited

  • Days Won

    26

Everything posted by Hoopster

  1. The IPMI implementation in this board is HTML5. One issue for which there is no workaround when using the iGPU for transcoding is loss of video signal when the i915 driver loads at the end of the boot cycle. This is what you will see if you attempt to launch the KVM after the system has booted completely: During boot up, there is video and you can watch the system boot and record videos; however, as soon as 'modprobe i915' is executed in the 'go' file, video control switches from the bmc to the iGPU. Console access and video recording though IPMI/KVM are then disabled. Of course, with unRAID up and running, you have console access through the GUI, PuTTY, etc. Even though I have IPMI on this board, I have a small monitor attached to the server for troubleshooting, that goes blank as well (as you would expect since it receives the BMC video signal) at the end up the boot cycle. Unfortunately, that is the tradeoff with a BIOS that supports both the BMC/IPMI and the iGPU. All other IPMI functions still work other than KVM video.
  2. Hmmm, according to the 5.14.23 release notes, you should be able to do a direct upgrade from 5.6.42. You might try changing the tag from LTS to 5.9 to see if that upgrade works. Then from 5.9 to the 5.14.23 tag.
  3. Right, there are plenty of C236 boards with IPMI. Mine just did not happen to have it so I don't know if QuickSync was still supported by ASRock in the public BIOS with that generation as it was with the C226 boards. What other manufacturers may support in their boards/BIOS I do not know as my latest several server boards have all been ASRock.
  4. The issue is really does the BIOS support it. On my C226 board with IPMI the public BIOS supported QuickSync without issue and there was a setting to enable it. My C236 ASrock workstation board and BIOS also supported QuickSync but did not have IPMI. On the C246 boards with IPMI, ASRock has decided that supporting QuickSync in addition to IPMI is a special BIOS thing for some reason and it has never made it into a public release. Not sure why.
  5. Can you edit other things from other folders on your server in Windows? I wonder if the "permission denied" error is on the Windows side if it is not using the right user to give it access to the server.
  6. Sorry, I misunderstood what you meant by this statement. If you go to the GUS directory in the console and list the contents, what does it show for permissions? Here are mine (I have no trouble editing telegraf.conf in notepad++):
  7. EAE errors are usually fixed by deleting the contents of the codecs folder in Plex which forces a new download of each codec as needed. Sometime they get messed up. Codecs folder is under LIbrary>Application Support>Plex Media Server in your Plex appdata path.
  8. Here are the folders in the appdata directory for GUS (from a Windows viewpoint): They are in {your path to appdata}/Grafana-Unraid-Stack/{folder you are trying to modify} I am a bit confused as to why you need to modify permissions as the GUS docker install should have been done with appropriate permissions unless appdata itself is messed up permission wise. I mention this only because I did the same you did when I first started. I had tried to install Telegraf, InfluxDB and Grafana separately a couple of years before installing GUS. I had deleted those docker containers but not the corresponding folders in appdata. When I was trying to modify telegraf.conf, I was in fact modifying the old one in the wrong path instead of the GUS path to telegraf.conf. I blew away the non-GUS folders and contents and then modified the proper telegraf.conf and all was well.
  9. it's a Mini-ITX board; E3C226D2I. I doubt you can find it anymore (maybe on eBay?). The "C226" models in different form factors also support Haswell processors.
  10. It will accept 32GB non-ECC RAM according to spec on MB web page. I cannot comment on that specific RAM, however, I have used RAM in the past on ASRock boards that were not on the RAM QVL. ASRock support told me directly that as long as the RAM meets the general RAM specs for the board, there is a high probability that it will work just fine whether or not it is on the QVL. There are lots of T Core processors on the supported CPU list for the board as I am sure you already checked. There are really no special considerations for using a non-Xeon CPU and non-ECC RAM. You just don't get whatever "features" those parts support but it does not change the behavior of the system or require any special configuration or consideration. My backup server (also an ASRock board with IPMI) is running with a core i5-4590 CPU with QuickSync and non-ECC RAM (not on the QVL for that board) and there are zero issues, concerns or special considerations.
  11. You can enter a specific version tag (e.g. linuxserver/unifi-controller:5.14.23-ls76) in the repository. I am running 5.14.23 (the latest in the 5.14 line) and it appears to be working great. No need to stick with a very old 5.9 unless you wish to. 5.14.23 is very stable and is not missing features like the 6.0 releases. No, 5.14.3 or higher is needed for WiFi 6 support.
  12. If by order of the drives you mean connected to the same SATA ports as before or in the same drive slots in the case/cage or previous disk 1 as new disk 1 ..., in the unRAID array slots, etc., this does not matter. UnRAID tracks drives by serial number. All the data on your existing data drives is still intact. Just make sure the parity drive is parity and the data drives are assigned to the array. They may not be in the same order (disk 1, disk 2, disk 3, etc.) as they were before but the shares and data will be intact even with a new drive order. You should not be prompted to format anything as the filesystem on each drive should still be intact as well. EDIT: Even though it does not matter, that's why I put a sticker on the front of each drive with its unRAID slot number and drive serial number. I just like knowing the order in which they were assigned in the array in case I ever do a new config.
  13. Yes, you just described a large portion of the user community. Those who know are willing help those who don't; then, they become those who know and help others who come on board. EDIT: Since you mentioned you have FreeNAS experience let me say that support here is not like it is for FreeNAS (from what I hear from many unRAID converts) and I mean that in a very positive way. I have no personal experience with FreeNAS but I hear there is some "you dummy, why don't you know that" attitude in their support forums. This is not intended as a slam on FreeNAS.
  14. What @kizer said sums it up for me. I also backup everything to a second server and to external hard drives (in addition to the cloud). However, when it comes to replacing or upgrading a drive, it is a far easier process because of parity. Unless you are backing up drive by drive (instead of by shares), you will have to figure out what is missing from the failed drive or what belongs on the larger replacement drive rather than parity doing it for you.
  15. Tom has done all he could be expected to do in this situation. Unfortunately, the genie is out of the bottle and cannot be put back. He has acknowledged that the rift was entirely of his making and has outlined every misstep he made which caused the situation. Some of the LSIO guys impacted by this are probably taking a break to let things simmer down and consider what, if anything, should be their public response post-apology. It may in fact be best to let it alone publicly for a while. If the schism is repaired behind the scenes and (and as alluded to by Jon P.) steps are taken to "better engage with the community beyond just this issue" then I think that will be at least one silver lining in this rather large storm cloud and perhaps some of the additional steps mentioned by @danioj can be taken. EDIT: BTW, I support the sentiment expressed by danioj but I suspect those impacted most might also be taking some time to measure their response.
  16. This is where tweaking telegraf.conf and providing certain variables and manipulating the UUD configuration to your needs comes into play.
  17. When I installed the GUS docker there was an admin account already setup in Grafana I believe. I have changed the password so I do not remember the default password. Perhaps it is documented in the dockerhub or github pages for GUS (looking now to see what it says about adding or changing account info).
  18. Down at the bottom on the left side of Grafana is where you can log in and manage accounts and preferences. Logged out it will look a little different, but there should be a log in option.
  19. For some things to appear you have to be logged in to Grafana. This is what you should see if logged in:
  20. One of the other advantages of GUS is that it includes Loki and Promtail all pre-configured and ready to go. These greatly improve Grafana logging capabilities.
  21. Are you installing each of the docker containers separately (Telegraf, InfluxDB, Grafana) and trying to configure each one as per that guide? I assume so or why follow the guide! I found it much easier to install the Grafana unRAID Stack (GUS) docker container which installs and configures all three containers. After that, all I had to do was make sure the telegraf.conf was configured for the sources I wanted (basically uncommenting a few lines and adding one source that was "missing"). I then imported UUD as the dashboard used in GUS. It was all very easy compared to trying to work with the containers individually.
  22. This is a Plex Pass feature so you have to start with a Plex Pass version. The HDHomeRun can be used to record OTA shows through Plex and store them in unRAID shares for viewing via any Plex client. Basically, you are using Plex as the channel guide/DVR for recording and unRAID as the storage instead of the native HDHR DVR/NAS functionality. You can also watch live TV via Plex. I have done this several times when traveling as it allows me to watch my local TV from anywhere with an Internet connection. HDHomeRun devices are setup under the Live TV & DVR section of Plex Settings (be sure you are in Settings) Add the appropriate devices and enable/assign the channels you want to appear in the schedule and define device settings as you wish. Your guide for your local market will then be downloaded and you can schedule DVR recordings in the Guide or watch Live TV from Live TV & DVR in the client.
  23. Yes, I have two of them working standalone and integrated with Plex. There is a cable card version, but I use then with OTA antennas only. The DVB drivers are for DVB-T tuner cards (non-networked tuners).
  24. Last time I experienced something similar was because the power supply was failing. When it exceeded a certain load, the PC locked up then shut down. Replaced the PSU and problem solved. No way to tell if that is definitely the issue unless you have another power supply you can try in the server or a power supply tester.