AgentXXL

Members
  • Posts

    399
  • Joined

  • Last visited

Everything posted by AgentXXL

  1. Hi Rysz. I'm giving your mergerfs plugin a try and have a couple of quick questions. For my test I'm using my test box. I've added 10 drives from my offline backups ranging in size from 2TB to 8TB. All are XFS formatted with a single partition and all use the same root disk name of OfflineBU, eg. OfflineBU00, OfflineBU01, etc. If I try to use mergerfs via commandline with the following command, it fails: root@AnimTest:~# mergerfs -o cache.files=partial,dropcacheonclose=true,category.create=mfs /mnt/disks/OfflineBU* /mnt/addons/BUPool fuse: invalid argument `/mnt/disks/OfflineBU02' It appears to work if I don't use a wildcard but list each drive separately like this: mergerfs -o cache.files=partial,dropcacheonclose=true,category.create=mfs /mnt/disks/OfflineBU00:/mnt/disks/OfflineBU01:/mnt/disks/OfflineBU02:/mnt/disks/OfflineBU03:/mnt/disks/OfflineBU04:/mnt/disks/OfflineBU05:/mnt/disks/OfflineBU06:/mnt/disks/OfflineBU07:/mnt/disks/OfflineBU08:/mnt/disks/OfflineBU09 /mnt/addons/BUPool It appears all disks in the mergerfs pool will still show up under Unassigned Devices. I suspect there's no way to hide these drives from showing under UD? Any thoughts on why I can't use a wildcard with all drives mounted using the same root disk name? If I have to use all drives on the command line, it's going to get quite long - the pool I want to mount on my production server will have 30 disks. Not sure if unRAID has a limit to the length of the command? Appearing under UD isn't a big issue, other than each visit to the Main tab takes longer to refresh while it waits for the list from UD to populate.
  2. Agreed. Especially since I really only look at the Dashboard widget when troubleshooting a transcode issue, and that's pretty rare with QSV. I expect I won't even worry about the lack of power draw info as my efforts to reduce power consumption in the homelab are starting to show some fruit already. Thanks for looking into it!
  3. I expected Emby was also working but I don't use it myself. And yes, the test AV1 encodes I've done were all on Windows. Hadn't even looked at it for Linux. Yes, I fully realize that they aren't the same thing. I suspect the Windows focus (possibly better sensor support) is why I was able to pull power draw from GPU-Z. I made the mistake of going to pkgs.org and looking for the generic intel-gpu-tools package, which intel_gpu_top is apparently part of. The package returned has the 2.99.917 version number, but I haven't gone as far as extracting the package to see if intel_gpu_top has been updated. Plus the package appears to only be available as a .rpm so I'll have to run it through rpm2targz to convert it for Slackware. Need to get my test box back in service before I try that. Link here if you want to take a look: https://pkgs.org/download/intel-gpu-tools So ignore my fumbling... 🤔 🤣 And thanks again for your quick response. When do you get time to sleep? 😂
  4. I'm one of those who have access to the 6.13 beta. I installed an A380 a couple of days ago. Intel GPU Top is installed and the /dev/dri/ device has been added to each template and transcoding is working fine with Plex and Jellyfin. Intel GPU Top is installed as the GPU Statistics plugin requires it. Alas the version of Intel GPU Top in the Apps store doesn't appear to have all sensors added to it as power draw is not being displayed for the A380, but it is working on my N100 uSFF PC which uses the UHD770 iGPU. And I know I can get power draw from the A380 as I did test it with GPU-Z on Windows. There's an odd change in version numbering for intel_gpu_top - looks like yours is 1.28 and the latest is only one generation newer but it's listed as version 2.99.917. Kind of an odd bump in version so that needs further investigation.
  5. @ich777 Is there a way of setting the name of the browser tab/window that opens when you open the webgui? I have Krusader installed on all 3 unRAID systems and often will have all of them open at the same time. Being able to set the tab name would make it easier to identify which tab is for which server. I can use a browser extension to right-click and rename, but that's necessary each time the container is started. FYI - the binhex-krusader container can do this by adding an environment variable called WEBPAGE_TITLE and setting its value to the name you want for the tab/window. Any chance of similar functionality in your containers? Thanks!
  6. As I'm dealing with very erratic power pricing and have limited disability income, I'm getting desperate to combine my two unRAID systems into one. I was hoping that 6.13/7.0 would have the ability to run multiple pools with the unRAID parity scheme, but the 6.13 beta test is just underway so it'll be a while yet before we see a RC. It's now confirmed that 6.13 will not implement the change to an 'all pool' model and hence the idea of using multiple pools with the unRAID parity scheme is moot until a future release implements it. As I need to tackle my power consumption ASAP, I'm looking at 2 options: 1. Create an unRAID VM on my main unRAID system. I have a HBA and USB ports to passthrough so that shouldn't be an issue. It will be for storage only - no other containers or VMs would be run on the unRAID VM. Only the absolutely necessary plugins like the UD series will be installed. 2. Use the mergerfs plugin to create a pool of different sized devices. Alas I don't see a way to do this and also implement something like SnapRAID so that there's some fault tolerance. I see multiple SnapRAID containers on Dockerhub but none are available in the unRAID App store so I'll have to try and build a container template for it. Looks like the official releases are from https://github.com/amadvance/snapraid Suggestions or other ideas?
  7. I've asked Eluteng since they are the ones who make the mSATA adapter that has a unique GUID. So far they haven't responded - asked them the expected lifetime of the mSATA adapters and if they could confirm if their m.2 to USB adapter also offers the unique GUID.
  8. That's certainly another option. I'm tempted to buy one of the Eluteng to m.2 SSD adapters that looks like it will also have a unique GUID. Too bad the GUID isn't just the enclosure for this Transcend model as that still means a license transfer if/when the SSD dies. But as m.2 SSDs use the higher quality NVRAM, it may have a long life. I had one of my systems corrupt the mSATA SSD about 8 months into use. I swapped on a replacement mSATA SSD, used the Creator Tool and then restored my backup and was back up and running in 10 minutes. With the Transcend adapter that might take a bit longer as you have to transfer the license as the GUID will change with a replacement m.2 SSD. That said, I fully tested the mSATA SSD that got corrupted and it's fine. Ran multiple tests and nothing wrong at all, so it was just a random corruption but no actual failure. I suspect a m.2 SSD would behave similarly - you would just have to reformat, rebuild using the Creator tool and restore your backup instead of replacing the m.2 SSD. That way the GUID remains unchanged and no license transfer will be required.
  9. Yes, checked the temps with the solid case models I've tried and no issues. Your case most certainly won't have any issues with all that ventilation. Good job!
  10. @ChatNoir I validated that the USB key or boot device is not counted when using the USB to mSATA adapter. You can go to Tools --> Registration and it will show you the number of drives counted against your license. On my main unRAID server that's 41 drives, but I have 42 if I include the USB to mSATA SSD adapter.
  11. Sorry, had a flare-up with some health issues so I haven't grabbed them yet. I noticed a new version of the plugin was released today so I installed and it's now working. I suspect it was the increased timeout. Thanks for incorporating this fix!
  12. There are some models for a case already available on 3D printing repositories like Thingiverse. I've tried all the ones I could find and none of them are an exact match for the Eluteng adapter. I've been meaning to make one with unRAID engraved into the case, but it's become a back-burner project. Guess I might have to get on that. For now I'm using just the case portion of one of the ones I printed - the end cap where the USB plug sticks out isn't a good fit for the Eluteng adapter so I just left it off.
  13. Hi Simon, I'm working through an issue with the Open Files plugin made by dlandon. It has stopped working on one of my unRAID systems and times out trying to get the list of open files and processes. I enabled logging at Tools --> PHP Settings and it's reporting this error: [26-Feb-2024 14:04:42 America/Denver] PHP Warning: Undefined variable $display in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [26-Feb-2024 14:04:42 America/Denver] PHP Warning: Trying to access array offset on value of type null in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [26-Feb-2024 14:04:57 America/Denver] PHP Warning: Undefined variable $display in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [26-Feb-2024 14:04:57 America/Denver] PHP Warning: Trying to access array offset on value of type null in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 The 2 lines repeat ad-nauseum every 5 - 15 seconds. I've removed the IPMI plugin to see if that would fix the Open Files issue, but dlandon suggested I mention this to you. Alas removing it didn't fix my Open Files issue. Let me know if you need any further details. Thanks!
  14. Thanks for the speedy reply! OK, removed the plugin and am reporting it to the author, but it still didn't fix the Open Files issue. Nothing is now showing in the PHP logs, and no errors/warnings in syslog. I rebooted after removing the plugin, but still have the same symptoms - it works when the array is stopped and when 1st started. Once the Docker service is enabled (with no containers started), Open Files will sometimes work but most of the time it times out. And when any containers are started, it will always time out. Anything else you can think of?
  15. NOTE: This solution is no longer valid as the manufacturer is not longer implementing a unique GUID on the adapter. Sorry for bad news. Thanks Spencer! If folks have a Discord account and want to see my original post, they can find it here: https://discord.com/channels/216281096667529216/786598782870880258/1002363967508861008
  16. I'm experiencing an issue with Open Files on one of my unRAID servers. I get the following error: Initially syslog was showing errors about not enough user watches so I went into Tip & Tweaks and doubled them, as well as doubling max user instances. So 1048576 for watches and 256 for instances. That's resolved the inotify errors that were appearing in syslog. I just did some more testing and Open Files is working fine after a reboot before the array is started. Once the array is started it also works. But as soon as I enable the Docker service, Open Files errors out again with the same message as shown in the screenshot. I've also gone into Tools --> PHP Settings and enabled logging for everything. Open Files is still not working but I'm not seeing any messages in the PHP logs except this: [26-Feb-2024 14:04:42 America/Denver] PHP Warning: Undefined variable $display in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [26-Feb-2024 14:04:42 America/Denver] PHP Warning: Trying to access array offset on value of type null in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [26-Feb-2024 14:04:57 America/Denver] PHP Warning: Undefined variable $display in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [26-Feb-2024 14:04:57 America/Denver] PHP Warning: Trying to access array offset on value of type null in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [26-Feb-2024 14:05:01 America/Denver] PHP Warning: Undefined variable $display in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 If I disable the Docker service, Open Files runs fine. I've also tried starting one container at a time, but no matter which container I try, Open Files no longer works when the container is started. There's nothing showing in syslog or the PHP logs except the errors in the code block above, which are still repeating at about 10 second intervals. Any ideas of something else to try? Thanks!
  17. You're not using the correct driver for the T1000. If you go to the Nvidia site and do a search for the latest driver for Linux x64, you'll find that you need to use the 535.154.05 version.
  18. There's a couple of ways to do it, but it's commandline no matter what. There's no GUI to use with a mouse. The full instructions are in the manual I've attached, but it comes down to a couple of commands: Extract the archive from that download link to a location on your Windows system. In the extracted folder are sub-folders called Firmware, sas3flash_win_x64_rel and sasbios_rel. Copy the SAS9305_24i_IT_P.bin, sas3flash.exe and mptsas3.rom files from each folder respectively to another folder, eg. create a folder on c:\ called Flash and copy those 3 files into it. The BIOS is optional - I don't bother flashing the BIOS as it's just one more delay during bootup. Change directory in the command prompt session to the folder containing those files, eg. cd c:\Flash if you used the name and location I suggested. 1. Validate that the sas3flash tool can see your 9305-24i with the command: sas3flash.exe -listall. If no adapters are found, you'll need to figure that out 1st. 2. Use the command: sas3flash.exe -o -listsasadd to retrieve the SAS adapter address, similar to a MAC address on a NIC. Record the SAS address for future reference. 3. Erase the existing flash firmware, BIOS and SAS address with the command: sas3flash.exe –o –e 6 4. Flash the IT firmware with the command: sas3flash.exe -o -f SAS9305_24i_IT_P.bin 5. Optional: Flash the BIOS with the command: sas3flash.exe -b mptsas3.rom 6. Re-program the SAS Address with the command: sas3flash –o –sasadd <sasaddress> where <sasaddress> is the value you recorded in step 2. 7. Re-check the 9305-24i to make sure it was updated by using the same command used in step 1. You should see the new firmware listed. See the attached manual (also in the original archive) for any further clarification on commands or examples of how they are used. I've done the same with my 9305-24i, but I used the UEFI version of sas3flash - doesn't matter if you use the DOS, Win, Linux or UEFI version of the command, they all should work similarly. Let me know if you need any clarifications. Oh, and try to do it on a system powered with a UPS - if power were to fail during the flash, your HBA could get bricked. sas3Flash_quickRefGuide_rev1-0.pdf
  19. Let's just say I'm a dumbass... I shouldn't try to make changes until my brain has woken up fully. I have this habit of checking all containers and plugins every day, usually one of my first tasks of the day. I was looking at the authentication in the email notifications section, not on the web UI page... DOH!! Thanks for the quick response!
  20. After the latest update today, it seems the credentials were set back to default. If I look at the settings, it looks like the new password is stored there based on the number of characters, but I can only login to qBt using the default password. I've also noticed that the option to use secure connections (SSL) is not enabled or selectable, and the authentication tickbox is greyed out. I did still have to login using the default credentials. I do have uPNP disabled in qBt. Was looking in the wrong section of options as stated below... DOH! Also noted this in the logs, and I don't recall seeing those errors previously. qBt seems to have started up properly otherwise, with Wireguard configured. Thoughts?
  21. I'm open to keeping it... having more information is preferable to not having enough.
  22. I'm also seeing this message. I did a few test reboots and it occurred everytime the array was started, but did not start an actual parity check. I know I had proper shutdowns - I'm pretty OCD driven to manually stop the running containers and then disable the Docker service. My VM service is also disabled as I don't run any VMs on unRAID at this time. I then manually unmount all UD-mounted shares, stop the array and then perform the reboot. I tried manually deleting the file /config/forcesync but I still got the notification on the next array start. I'll wait to see if an upcoming update to the parity check tuning plugin fixes it. Worst case is I wait until my next scheduled parity check and see if that clears it up.
  23. FYI - the Jonsbo N3 is now available: https://www.aliexpress.com/w/wholesale-Jonsbo-n3.html
  24. Sorry, my code review skills are a little weak, but both 153 - 155 and 179 - 180 still show the sections in red from that link, vs the updated code shown in green. Note that the NUT settings page and the footer itself are still showing the correct info, just the Dashboard component that's messed up. I'm using NUT on both of my unRAID servers with one physically connected to the UPS via USB cable and configured as the netserver, and the other as a slave. EDIT: I'm currently finishing a parity rebuild on the server that's connected to the UPS via USB, but will try rebooting it once the parity rebuild completes (about 4 hrs remaining). I have just rebooted the slave system and the Dashboard error seems to be resolved. I suspect the changes weren't applied to the running plugin, but a reboot seems to have fixed that.