XiuzSu

Members
  • Content Count

    119
  • Joined

  • Last visited

Everything posted by XiuzSu

  1. I would like to request the ability to log performance CPU/RAM usage for dockers/VM's/Unraid. This way, we can see how much they use on average and what they use/need when they peak. With this information it would help the user to properly assign cores by workload for optimal performance.
  2. As said above, we would need more details. However, if you're referring to the flashing process itself it SHOULD be pretty straight forward. It sounds like you've done plenty of research. If so, you should be able to do it within 1-2 hours. The process is pretty straight forward. If you can't get it to flash the reason can be from the card not being able to be flashes by your hardware or the card itself its soft 'locked' to not allow flashing to IT. I read that somewhere. Either way, I would strongly advice to save the large amount of time you're going to waste trying to figure this out as in
  3. If you're having issues with your pfSense only seen 1 port, then do the following. 1) If you're looking for a guide go click here. 2) Once you are in part 3 of the SpaceInvader video to edit the XML do the follow: A. Remove the following code, the 'interface'. B. Go to the bottom section and make sure the BUS and the SLOT is the same for the 4 'pci' ports as the 'pci' from the FIRST port. C. ADD "multifunction='on'" to the FIRST PCI (port). D. Make sure the Functions starting with 0, go in increasing number. Example 0,1,2,3.
  4. Thanks so much for the info. I'll get on it this afternoon!
  5. I'm getting the error below: I think this is my cache drive, but I'm not sure and I'm also not sure on how to proceed with this. I recently had purchased bad RAM which caused many issues with UNRAID and corrupted 2 files which I just deleted after replacing the RAM. Apparently there is still some damage. Could you guys also take a quick look at my diagnostic file to see if anything else aside from the error above is damage/broken that I may have missed? Thank you! (edit) I scrub the cache drive and came back with no errors found. Also, I'd like to note that I originally h
  6. I appreciate the help! The new card works right away, in IT mode, I disabled OpROM and that pesky delay went away and UNRAID booted. All drives detected. I'm going to go ahead and call this a win. Anyone looking at this in the future, I would simply suggest getting a card that already comes with IT mode. Not worth the 10-20$ in savings.
  7. That sounds what I will probably do. UNRAID should still boot fine from the USB without problem though right?
  8. @BensonYea, after the first 'sas2flash.efi -o -e 6' nothing has actually worked after that, other than 'sas2flash.efi -listall' to see it. I literally been on this for about a week now and I'm done with this card. I bought and installed a LSI Logic SAS 9207-8i and is currently in FW Revision 18, already in IT mode. It did cost me $20 more; However the original is still within the return time frame so I will be returning it. I don't know about you, but when its been over a week and someone still can't flash a firmware, I would go ahead and call that defective. I think the latest versi
  9. This is not working. It is asking that a firmware hostboot is required, and to enter one. I try entering the file name for the firmware and it throws an error. "selected adapter does not have valid firmware! Please run utility again and flash firmware. due to error remaining commands will not be executed. Unable to process commands. exiting sas2flash." Tried flashing again, and no dice.
  10. I don't have the specific details as to what it does, other than it fixes an issue with the kernel for the GPU and other devices passthro. I can only speculate to be honest. I'm just happy the issue was fixed.
  11. Isn't the address something that is set after the firmware update? I kinda don't wanna keep trying to remove stuff from it but at this point I guess I'll try it. If this doesn't work out I may try the SAS 9207-8i as it appears to come pre-flashed to IT. However, I would like to know which card is better for unraid and/or overall, the SAS 9207-8i or the LSI 9211-8i?
  12. I have tried using a different keyboard, and changing the flash file to "it.bin" in case the issue was being caused by being too long or by the numbers and no luck. I've also try to use 'sas2flash.efi -o -f it.bin' and 'sas2flash.efi -o -b mptsas2.rom'. I still get the syntax error. Any other suggestions?
  13. I bought a LSI 9211-8i and I've been trying to flash it using my x79 motherboard, and following a few guides like the ones below: https://nguvu.org/freenas/Convert-LSI-HBA-card-to-IT-mode/ https://nullsec.us/raid-on-home-esxi-lab/ The one that got me the farthest is the last one as I have to use UEFI. I've gotten all the way till the "fs0:/> sas2flash.efi -o -e 6" command; However, the "sas2flash.efi -o -f 2118ir.bin" (I'm not trying to install the .rom) isn't working. Even if I do it with the full "sas2flash.efi -o -f 2118ir.bin -b mptsas2.rom" command. I h
  14. I guess this is for anyone who finds this threat in the future. I finally FIXED IT Special thanks to @peter_sm I followed a bunch of his threads and the information from the Lv1Forums where I found that adding "pcie_no_flr=1022:149c,1022:1487" would solve this issue. They (2 of them) suspected that this is related to the x79 platform (which is also what I have). Anyway, I have shut it down, restarted, and updated it more times that I cared to count without issues. I've also left the VM on over night, played heavy games on it, and there was still no issue. Now that everything
  15. I'm still experiencing this issue which is making it impossible for me to even have VM's. I have read around the forum and I can't find the solution as similar problems just don't get replied to and slowly just disappear. Anyone have any ideas? At this time, I'm just testing if this is due to the GPU passthrough by using VNC as I've basically tried almost everything else. If this fails, I'm considering try to run ESXI and unraid on top solemmly for the data array. (Edit) I have been turning it off and on without issues after using VNC only.
  16. So its normal for it to say "ERROR Register 3 (rev 4)" ?
  17. IOMMU group 36:[8086:0ea8] ff:0f.0 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Target Address/Thermal Registers (rev 04) [8086:0e71] ff:0f.1 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 RAS Registers (rev 04) [8086:0eaa] ff:0f.2 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder Registers (rev 04) [8086:0eab] ff:0f.3 System peripheral: Intel Corporation Xeon E7 v2/Xeon E5 v2/Core i7 Integrated Mem
  18. I'm a bit new but I did looked over your diagnostics file and couldn't figure out what is causing your issue. I would suggest you try turning your VM's/Docker's one at the time until you can ping point the root cause a bit better. Hope someone can help you a little more.
  19. Update; [FIX to VM crashing unraid] Unraid was crashing whenever you sometimes reset/shutdown a VM due to the short 'disconnect' timer from unraid. Go to Settings->VM Manager->VM shutdown time-out, and set it to 300 (5 minutes). Go to Settings->Disk Settings->Shutdown time-out, and change the time-out to 420 (7 minutes). I'm not sure why the time-out would outright crash unraid, something must be wrong. If you're interested as to why this happens and want to know the full details, please read the post below: (edit) Update 4/24/20
  20. I have been on the forums posting about an issue with 100% CPU usage and I have seen other people with THAT issue. However, yours is different. I had an issue like yours. Turned out to be a docker or a VM having an incorrect path and there was an error being thrown into the log until it eventually filled it. When does this start?
  21. Update: So far, this is what I've found; I actually have 2 issue, the VM crashing unraid, and the core(s) going to 100% are two separate issues. I thought it was one. The core(s) going 100% appear to be caused by WSD. So I've disabled it to have fixed this issue. Before you ask, yes the server still appears under my network in Windows....after you've browsed to it directly, and it will disappear once you close the File Explorer. But who cares, you can still access it, or if you have it mapped it still there, still works, just not discovered automatically. Yes, its not gre
  22. @bastl That ISO was from a totallylegitamentwebsite. 😁 I was having the issue with my W10 and Windows Server 2019 both of which were different ISO's (obviously) acquire from different places. I think I may have fixed this issue. Just want to run it for 24-48 hrs before posting my findings and how I resolved it.
  23. I would like to add that I would actually like to see a schedule section. So that you can schedule unraid/dockers/vm's to restart/start/stop.