• Posts

  • Joined

  • Last visited

About RifleJock

  • Birthday 11/08/1995


  • Gender
  • Location
    United States

Recent Profile Visitors

715 profile views

RifleJock's Achievements


Newbie (1/14)



  1. I'm down to be a guinea pig for the multi-gpu tests... I'm sure I have some AMD's laying around somewhere I could slap in there as well to test cross vendor support. Also, I've noticed that they have some vGPU support when it comes to the Intel iGPU's... I'm curious if we can get stats on those as well.
  2. While that is a valid point and what I currently do with my anime directories (for plex and other media servers). The goal with the GoPro libraries was not for that of economics, but rather, of performance from the array disks. With the anime libraries, it's setup to where a disk is accessed based on the series you are watching. If you decided to binge the series, the disk will stay spun up as the shows usually don't exceed 45 minutes (post full read and cache of the at each start of an episode) of which, is my disk spin down setting time. For instance Plex will read a disk at the start of an episode. Go full ape in transcode based on your transcode settings. Transcoded files then sit on the cache to be read back live during your stream. If the disk spun down, and the user either decided to change their quality settings, skip the episode at some point, or scrub backwards (sometimes, transcodes are discarded and need to be rerecorded (this was back in the day.. transcodes stick around a little longer now.).). Anyways, it just so happens that 45 minutes until spin-down works perfectly in all the scenarios that I could reference in my system. That combined with specific directory splitting, or disk allocation methods, I've not had to use the spin-up groups as of yet.. though I'm starting to see more of a need for them...
  3. I've never used them. However, was considering it now, but seeing as they might go away, may consider not using them. I had a use case before, when I used 6x 8TB drives. This was on my Media share, where I had used "most-free" and changed the directories split such that each 30 minute GoPro video would be placed among these drives evenly. I would do this so that when reading videos from these drives whilst doing video editing that would reference 4 or 5 videos from the trip of the day, I could get full sequential reads from the Array disks per video. In order to prevent spin-downs, my work around would be to set the disk spin down delay to that of 45 minutes, that way, it was harder for the drive to spin down, while reading from all the drives.
  4. So there is a big difference here... Your physical environment, and your virtual one. All things done within UnRAID are considered your virtual environment, and everything outside of that is considered your physicals. You can either setup UnRAID to have a L2 interface, of which you pass through as a bridge to your virtualized Palo Alto. (There wouldn't be much of a point in running a L2 within Palo if this is the case.) This will allow your Palo to communicate only on that physical L2 interface of UnRAID when trying to communicate with anything else on that same L2 interface in your physical environment. Perhaps a real Palo Alto with the same VLAN tagging for redundancy or whatever. Now lets say you have a virtual Check Point device and a virtual Palo both on your unraid, regardless of what physical interfaces are assigned in UnRAID, whatever bridge you passthrough to the virtual environments, you can create L2 interfaces within your CheckPoint and Palo Devices, and only devices on that same bridge (on UnRAID) in the same virtual L2 LAN will communicate. However, I believe any traffic destined to a network outside of UnRAID will get put onto UnRAID's physical configuration's interface when it is attempting to leave the UnRAID box itself. If your UnRAID is configured as a physical L3 with default tagging, then traffic will leave tagged as such. This type of configuration only separates the virtual traffic within the UnRAID box. Depending on what your scenario is, you could do either or both. It all comes down to your physical and virtual topology. LMK if you have any further questions, I can break this down further if needed. -Jockie.
  5. https://www.youtube.com/watch?v=LkW3niAWAHs https://forums.unraid.net/topic/50882-guide-custom-vm-icons-automatically-downloaded-and-installed-to-unraid/ So, you have several physical interfaces in UnRAID, you can set these to their own VLAN in unraid, and then assign the bridge to Palo. You can also edit the xml I believe to be a different type of interface, rather than inet. Otherwise, just put a managed L2 switch next to your unraid box, and trunk your interfaces to Unraid.
  6. Not exactly, the most recent post made by me I believe is the only thing seen on unraid's forum about Palo setup process. One thing to mention, that might not have been mentioned before is the licensing, if you are going to make this a legit license, you MUST not remove the UUID in your xml file for the device, as Palo Licensing is near impossible to move once established. Save a copy of it somewhere.
  7. Nope, never did get this working. My USB ID's seem to be stable now however, and don't change at all. But the plugin still doesn't seem to ever detect any of the PSU's. -Jockie
  8. Let me first start off by describing the issue I face. I'm a hardware/networking kinda guy. I don't really know much when it comes to software/programming. In attempts to create my own user script, I faced numerous hurdles that I just simply don't know how to solve. Rather than creating a bandage for the issue I face, a simple resolve would be to create a simple fix to the already existing mechanics/programming that exists within the VM Settings of Unraid. Here's the concept of my script: When ran: 1. It would go to the variable for the default ISO storage path, of which the user can fill in the VM settings location. In my example here, the /mnt/user/ISOs/ dir. 2. mv all files named virtio*.iso (as well as any other drivers I added manually) to my "Drivers" dir within the ISOs dir. Here's the simple fix to Unraid's VM Settings. Create another option in the Unraid's VM settings section that would allow me to specify my virtio download and default location, separate from my default isos location. When creating a VM, these would now be separated. Maybe I'm being petty or lazy, but this would allow users to reduce the steps taken in the process of mass downloading virtio drivers (as well as other drivers) and then manually moving them to a "Drivers" dir. -AND- Because they have been moved to the drivers dir, they no longer autofill the first/top option when creating a vm, causing one additional step that has to be taken during the VM creation process. IDK, let me know your thoughts guys. Surely I'm not alone in this. -Jockie
  9. So, I've got a bit of a weird situation. I do need assistance with setting this up as well. Not sure what I'm missing but I can't seem to figure out how to get the plugin to point to the correct device. Also, I happen to be running 3 AXi power supplies, thankfully all different wattage capabilities or I fear that might make things more complicated. Is there a way to setup multiple versions of this plugin to run at once so that I may monitor all three power supplies? By process of elimination, I unplugged one by one the usb to these PSU's to determine the correct device id. 1b1c:0c04 Corsair Link Cooling Node 1b1c:1d00 Corsair (AX1200i) 1b1c:1b12 Corsair (AX860i) 1b1c:1c02 Corsair (AX1500i) Here is the current output. Also, not sure why. but my Bus 003 Device 016: ID 1b1c:1c02 Corsair in this output keeps changing device numbers. 10 minutes ago, it was Device 014, then a few moments later 015. Nothing else seems to be "flapping" causing this counter to change. I believe this PSU is under roughly 98% load atm, and often blinks orange on the led. Also not sure what that means. IOMMU group 39:[8086:8d31] 00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host Controller (rev 05) Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 0b05:180a ASUSTek Computer, Inc. Broadcom BCM20702 Single-Chip Bluetooth 4.0 + LE Bus 003 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 003 Device 005: ID 1b1c:0c04 Corsair Link Cooling Node Bus 003 Device 006: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub Bus 003 Device 007: ID 1b1c:1d00 Corsair Bus 003 Device 009: ID 13fe:4200 Kingston Technology Company Inc. USB DISK 2.0 Bus 003 Device 010: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 003 Device 011: ID 248a:8367 Maxxter Bus 003 Device 012: ID 0781:5571 SanDisk Corp. Cruzer Fit Bus 003 Device 013: ID 1b1c:1b12 Corsair Bus 003 Device 016: ID 1b1c:1c02 Corsair Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub Any help would be greatly appreciated! -Jockie
  10. I re-downloaded a new instance of Version: 6.9.0-beta25 to my flashdrive after a clean wipe/reformat/reinstall. (also went through the website to re-register the flashdrive with the new install). I did some configuring and re-configuring, a few crashing and rebooting. At some point, not sure when. I think either I renamed my cache pool to nvme pool or it just strait up went missing. All my data and disks still exist fine. But I noticed after getting CA Fix Common Problems that the top alert stated that I wasn't using VMs share/dir on my cache drive. Looking into it further, I decided to do a new config (not sure if it's this version, but I'm unable to tell it to keep parity, though a few crashes might have made it to where it wants to reconstruct, thinking it's invalid... perhaps that's why it doesn't show.) None the less, my cache pool still appears to be missing. Upon trying to create one, the default name is cache, and won't allow me to create it keeping that name. (for somewhat obvious reasons). But why does it not show in the first place? Is there a setting I accidentally disabled? I ended up "upgrading" to the same version + nvidia drivers. Still on a new config, here is the diagnostics. (also side note, for some reason, config won't keep my eth assignments straight... keeps putting 10gbe (PCI device 0x1d6a:0xd107 (atlantic)) at the top... whatever...) dash-diagnostics-20200910-1851.zip
  11. Hey jwiener3 and all others, As far as the perf: interrupt messages, I receive these as well, and the system seems to limit my login until it is done spitting those errors. Not sure if there are other processes still booting in the background. I'm assuming the "accessed a protected system..." is your banner/motd. As far as I know, those alerts don't actually cause any issues (that I have found). OH!!! Also, Update. Running Unraid 6.9.0-beta25. I'm now able to run much more interfaces. Currently running 25 (24 + mgmt). Adding the 26th does.... welp, apparently nothing. only eth1/1 - 1/24 show up, nothing after that. Even looking for the logical 26th unraid interface (25th palo alto, other than mgmt) I'm unable to find it's mac address. -Jockie
  12. Diagnostics Attached. dash-diagnostics-20200204-1721.zip
  13. Not sure why, but unraid seems to limit jumbo frame sizing to 9000. However, my 10gbe switched network is currently configured for 16k+ frame sizing in accordance to 802.3 Standards for 10gbe NICs. Looking to get that 99% efficiency in my file transfers. Is this a limitation of unraid?