TheScrantonStrangler

Amazing what hitting the 'apply' button will do. To anybody else running into this issue, after doing the above, also set PCIe ACS override to downstream. I originally thought I had tried this even though I thought I didn't need to since my NIC was only in 1 IOMMU group, but I guess I didn't press apply.

Hi all, I am attempting to passthrough a 2nd 2 port BCM5709 Gigabit Ethernet NIC to a pfSense VM (wanting to try pfSense on a VM before building a dedicated box for it) and I keep getting this error. Google suggests that I add append vfio_iommu_type1.allow_unsafe_interrupts=1 vfio-pci.ids=14e4:1639 initrd=/bzroot to my syslinux.cfg file, but I continue to get errors when attempting to boot the VM. I have also confirmed that my new nic shows up as only one IOMMU group. Any thoughts on what else I can do to get this NIC to passthrough correctly? I have also attached a diagnostics.zip file. Thanks for any ideas. tower-diagnostics-20221119-1215.zip

This is a Dell Poweredge r510. The iDrac system event log doesn't show anything that wasn't done by me (the drive being removed was a mistake, and the power supply errors is me unplugging the redundant and re-plugging.)

Received the same message. Log file is attached. I believe that this is the relevant portion. Dec 19 10:08:11 Tower root: Fix Common Problems: Error: Machine Check Events detected on your server Dec 19 10:08:11 Tower root: Hardware event. This is not a software error. Dec 19 10:08:11 Tower root: MCE 0 Dec 19 10:08:11 Tower root: CPU 1 BANK 6 TSC e0507bb7fe8f4 Dec 19 10:08:11 Tower root: MISC a010414 ADDR bdbaeefc0 Dec 19 10:08:11 Tower root: TIME 1639771657 Fri Dec 17 14:07:37 2021 Dec 19 10:08:11 Tower root: MCG status: Dec 19 10:08:11 Tower root: MCi status: Dec 19 10:08:11 Tower root: Corrected error Dec 19 10:08:11 Tower root: MCi_MISC register valid Dec 19 10:08:11 Tower root: MCi_ADDR register valid Dec 19 10:08:11 Tower root: Threshold based error status: green Dec 19 10:08:11 Tower root: MCA: corrected filtering (some unreported errors in same region) Dec 19 10:08:11 Tower root: Generic CACHE Level-2 Data-Write Error Dec 19 10:08:11 Tower root: STATUS 8c2000400001114a MCGSTATUS 0 Dec 19 10:08:11 Tower root: MCGCAP 1c09 APICID 0 SOCKETID 0 Dec 19 10:08:11 Tower root: MICROCODE 1f Dec 19 10:08:11 Tower root: CPUID Vendor Intel Family 6 Model 44 Dec 19 10:08:11 Tower root: mcelog: warning: 8 bytes ignored in each record Dec 19 10:08:11 Tower root: mcelog: consider an update Dec 19 10:08:21 Tower emhttpd: read SMART /dev/sdm Dec 19 10:08:21 Tower emhttpd: read SMART /dev/sdj Dec 19 10:08:21 Tower emhttpd: read SMART /dev/sdh Dec 19 10:08:21 Tower emhttpd: read SMART /dev/sdn Dec 19 10:08:35 Tower emhttpd: read SMART /dev/sdi tower-diagnostics-20211219-1008.zip

So I'm trying to get this working on my server and I'm having a few issues. #!/bin/bash # TEMPERATURE # Change this to the temperature in celcius you are comfortable with. # If the temperature goes above the set degrees it will send raw IPMI command to enable dynamic fan control MAXTEMP=33 TEMP_STEP1=28 TEMP_STEP2=30 TEMP_STEP3=32 IPMIHOST=192.168.1.120 IPMIUSER=myUserName IPMIPW=myPassword # 28 -> 20% # 30 -> 30% # 32 -> 40% # 33 -> Automatic control # This variable sends a IPMI command to get the temperature, and outputs it as two digits. # Do not edit unless you know what you do. TEMP=$(ipmitool -I lanplus -H $IPMIHOST -U $IPMIUSER -P $IPMIPW sdr type temperature |grep Ambient |grep degrees |grep -Po '\d{2}' | tail -1) echo $TEMP if [ $TEMP -ge $MAXTEMP ]; then echo " $TEMP is > $MAXTEMP. Switching to automatic fan control " ipmitool -I lanplus -H $IPMIHOST -U $IPMIUSER -P $IPMIPW raw 0x30 0x30 0x01 0x01 elif [ $TEMP -le $TEMP_STEP1 ]; then echo " $TEMP is < $TEMP_STEP1. Switching to manual 20% control " ipmitool -I lanplus -H $IPMIHOST -U $IPMIUSER -P $IPMIPW raw 0x30 0x30 0x01 0x00 ipmitool -I lanplus -H $IPMIHOST -U $IPMIUSER -P $IPMIPW raw 0x30 0x30 0x02 0xff 0x14 elif [ $TEMP -le $TEMP_STEP2 ]; then echo " $TEMP is < $TEMP_STEP2. Switching to manual 30% control " ipmitool -I lanplus -H $IPMIHOST -U $IPMIUSER -P $IPMIPW raw 0x30 0x30 0x01 0x00 ipmitool -I lanplus -H $IPMIHOST -U $IPMIUSER -P $IPMIPW raw 0x30 0x30 0x02 0xff 0x1e elif [ $TEMP -le $TEMP_STEP3 ]; then echo " $TEMP is < $TEMP_STEP3. Switching to manual 40% control " ipmitool -I lanplus -H $IPMIHOST -U $IPMIUSER -P $IPMIPW raw 0x30 0x30 0x01 0x00 ipmitool -I lanplus -H $IPMIHOST -U $IPMIUSER -P $IPMIPW raw 0x30 0x30 0x02 0xff 0x28 fi I've added variables for IP address, username, and pwd. When I run the script I get the following: Script location: /tmp/user.scripts/tmpScripts/IPMI_Fan_Control/script Note that closing this window will abort the execution of this script /tmp/user.scripts/tmpScripts/IPMI_Fan_Control/script: line 20: ipmitool: command not found /tmp/user.scripts/tmpScripts/IPMI_Fan_Control/script: line 24: [: -ge: unary operator expected /tmp/user.scripts/tmpScripts/IPMI_Fan_Control/script: line 27: [: -le: unary operator expected /tmp/user.scripts/tmpScripts/IPMI_Fan_Control/script: line 31: [: -le: unary operator expected /tmp/user.scripts/tmpScripts/IPMI_Fan_Control/script: line 35: [: -le: unary operator expected I found this plugin for IMPI and installed it. It says in the post that IPMI Tool is no longer included in the plugin, but when I go to install the package it throws a bunch of errors at me. Is there something I am missing/not understanding? I'm trying to increase the WAF of my server in our apartment and it's not going too well haha. EDIT So I had a brain wave and decided to check NerdTools, and there it was! Now I get this error: Script location: /tmp/user.scripts/tmpScripts/IPMI_Fan_Control/script Note that closing this window will abort the execution of this script 27 27 is < 28. Switching to manual 20% control Unable to send RAW command (channel=0x0 netfn=0x30 lun=0x0 cmd=0x30 rsp=0xcc): Invalid data field in request Any suggestions? EDIT2 Turns out that is a normal message! It works!! Now for another nooby question: How often do I need to run this?

Hi all, I recently purchased a 12(+2) bay Dell r510 and dropped in a H200 LSI 9211-8i without doing proper research on whether or not it would work for my use case. Apparently that particular card doesn't support TRIM on most SSD's aside from a very select few. Luckily for me, the Crucial bx500 SSD I have as my cache drive supports it. Linux 4.19.56-Unraid. root@Tower:~# hdparm -I /dev/sdf | grep TRIM # Crucial bx500 used as cache drive * Data Set Management TRIM supported (limit 8 blocks) * Deterministic read ZEROs after TRIM root@Tower:~# hdparm -I /dev/sde | grep TRIM # Samsung 850 unassigned drive * Data Set Management TRIM supported (limit 8 blocks) root@Tower:~# fstrim -h Unfortunately, when I run fstrim -v /mnt/cache/, I get this relatively cryptic error. root@Tower:~# fstrim -v /mnt/cache/ fstrim: /mnt/cache/: FITRIM ioctl failed: Remote I/O error Is there anything to be done to get TRIM working on my system? Anybody else with an r510 have any suggestions on what I should do? I am still within the return window for the LSI 9211-8i but would rather not have to return it as it took the card about 3 weeks to arrive to me from the US. tower-diagnostics-20190708-1830.zip

Did you ever find a solution to this? I am getting the exact same issues as you. Should be getting 15ms ping, 180Mbps down, 25Mbps up. Recently, I've also been getting no results at all. /shrug

I get this same issue too. I just switched to Edge and it worked. Will look into why Chrome isn't working on latest Windows 10. People here recommend clearing cache.

I'm trying to setup multiple instances of this Docker but am having some trouble getting it working. Every time I log in to one WebUI it kicks me out of the other. Is there something I am doing wrong?

Alright, thanks dude. That's exactly what I wanted to know. Kind of sucks that it is the WD Red drive when I have a crappy Seagate that has an extra 8 months powered on time compared to that drive in the same array. EDIT By needs to be replaced now, does that mean that it is somehow affecting the rest of the array? Or can I safely just let Disk 3 ride until she dies?

Hey there, After many good years with FreeNAS, I have decided to try out unRAID and so far I absolutely love it. After the initial heartbreak of having a drive die on me (all easily replaceable data thankfully!) during the FreeNAS -> temp storage -> unRAID transition I am having some other problems that I'm now turning to the community here to help me with. I've had 2 drives, Disk 1 and Disk 3, give me 'Current pending sector' errors, and after running the 'SMART extended self-test' Disk 1 has returned to normal while Disk 3 is still giving me Current Pending Sector errors. These drives are getting quite old (around 3.5 years of power on hours) so if they are indeed on their way out I won't be too disappointed, but I'd still like to hear what people here have to say about it. I'll attach some log files below. Thanks. Disk 1 SMART report Disk 3 SMART report syslog.txt