mindedc

I had meant a corruption of a single drive which the whitepaper clearly indicates is detected and repaired in a parity recalculation. After the last sentence you quoted they go on to state that such detection is possible but the code doesn't support more than two drives right now which is completely reasonable. Thank you so much for your support.

Wanted to validate if Unraid uses a standard Raid 6 type mechanism (typically Reed-Solomon coding) under the hood when using dual parity? The question is specifically to address if Dual parity would correct a bit flip or corruption in the resilvering (parity check) process. If not then would dual parity only help in the case of multiple drive failures? Hoping to hear from someone from Unraid with an official answer. Thank you

I'm trying to get mine going. I'm building a new server and was going to move my USB and drives from the old server over. I am making sure all the hardware works before taking down the old server so I just downloaded a new copy of unraid 6.12.10 and am running without an array. I have a commander XT that was bought but not used for a gaming setup and it would be super handy to use as I have more fans in the new machine than fan ports on the motherboard. I also want to use the temp sensor to get the temperature from the LSI card so I can monitor/use that for fan control. The commander shows up but sensors doesn't see it: root@Test:~# lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 010: ID 05ac:024f Apple, Inc. Aluminium Keyboard (ANSI) Bus 001 Device 009: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard Bus 001 Device 003: ID 154b:007a PNY Classic Attache Flash Drive Bus 001 Device 006: ID 0b1f:03ee Insyde Software Corp. RNDIS/Ethernet Gadget Bus 001 Device 004: ID 0557:9241 ATEN International Co., Ltd SMCI HID KM Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub Bus 001 Device 007: ID 1b1c:0c2a Corsair CORSAIR iCUE COMMANDER CORE XT Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@Test:~# Here is what I get from sensors: root@Test:~# sensors nct6798-isa-0a30 Adapter: ISA adapter in0: 160.00 mV (min = +0.00 V, max = +1.74 V) in1: 1.25 V (min = +0.00 V, max = +0.00 V) ALARM in2: 3.33 V (min = +0.00 V, max = +0.00 V) ALARM in3: 3.28 V (min = +0.00 V, max = +0.00 V) ALARM in4: 1.82 V (min = +0.00 V, max = +0.00 V) ALARM in5: 1.06 V (min = +0.00 V, max = +0.00 V) ALARM in6: 1.05 V (min = +0.00 V, max = +0.00 V) ALARM in7: 3.33 V (min = +0.00 V, max = +0.00 V) ALARM in8: 2.86 V (min = +0.00 V, max = +0.00 V) ALARM in9: 520.00 mV (min = +0.00 V, max = +0.00 V) ALARM in10: 0.00 V (min = +0.00 V, max = +0.00 V) in11: 904.00 mV (min = +0.00 V, max = +0.00 V) ALARM in12: 1.05 V (min = +0.00 V, max = +0.00 V) ALARM in13: 1.11 V (min = +0.00 V, max = +0.00 V) ALARM in14: 1.78 V (min = +0.00 V, max = +0.00 V) ALARM fan1: 0 RPM (min = 0 RPM) fan2: 0 RPM (min = 0 RPM) fan3: 0 RPM (min = 0 RPM) fan4: 0 RPM (min = 0 RPM) fan5: 0 RPM (min = 0 RPM) fan7: 0 RPM (min = 0 RPM) SYSTIN: +35.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor CPUTIN: +127.5°C (high = +80.0°C, hyst = +75.0°C) ALARM sensor = CPU diode AUXTIN0: +23.5°C sensor = thermistor AUXTIN1: -128.0°C sensor = thermistor AUXTIN2: -23.0°C sensor = thermistor AUXTIN3: -21.0°C sensor = thermistor PCH_CHIP_CPU_MAX_TEMP: +0.0°C PCH_CHIP_TEMP: +0.0°C PCH_CPU_TEMP: +0.0°C PCH_MCH_TEMP: +0.0°C intrusion0: ALARM intrusion1: ALARM beep_enable: disabled acpitz-acpi-0 Adapter: ACPI interface temp1: +27.8°C (crit = +105.0°C) coretemp-isa-0000 Adapter: ISA adapter Package id 0: +31.0°C (high = +80.0°C, crit = +100.0°C) Core 0: +23.0°C (high = +80.0°C, crit = +100.0°C) Core 4: +26.0°C (high = +80.0°C, crit = +100.0°C) Core 8: +26.0°C (high = +80.0°C, crit = +100.0°C) Core 12: +23.0°C (high = +80.0°C, crit = +100.0°C) Core 16: +31.0°C (high = +80.0°C, crit = +100.0°C) Core 20: +26.0°C (high = +80.0°C, crit = +100.0°C) Core 24: +26.0°C (high = +80.0°C, crit = +100.0°C) Core 28: +27.0°C (high = +80.0°C, crit = +100.0°C) Core 36: +24.0°C (high = +80.0°C, crit = +100.0°C) Core 37: +24.0°C (high = +80.0°C, crit = +100.0°C) Core 38: +24.0°C (high = +80.0°C, crit = +100.0°C) Core 39: +24.0°C (high = +80.0°C, crit = +100.0°C) I tried sensors-detect but its not seeing the commander. Any ideas?

Over two years, then needed to add some ram. Upgraded OS and was up for 266 days before needed to look at something on the board a few days ago because I'm planning an upgrade. Gotta love supermicro server grade hardware.

Any fix that doesn't kill browsing for windows machines? This has been ongoing for months..... kinda sucks that I basically don't have access to one of my CPU cores for VMs/Containers/etc... Is this a more generic SMB problem or something unraid specific?