ldrax

Just want to express my newfound happiness. My motherboard has only 1 USB controller (to my disappointment), but the USB-C port of 2080Ti comes to the rescue! Using 6.11.5, I just need to VFIO bind (on System Devices), restart, and then pass through the NVidia USB controller. It works! I attached a Dell WD19TB dock that's been laying around forever. It's thunderbolt connection but it works with USB-C. Also attached another USB Hub to the WD19TB. This gives a dozen of USB ports for plug-n-play purpose to the Windows 11 guest OS. Transfer rate is fast, but of course to be shared with all the plugged-in devices. I guess there will be overall bus power limit as well, but I plugged in 3 external SSDs together with a bunch of thumb drives and an SD Card, just to test. This made my day!

I wonder if anyone managed to get module nct6775 working for NCT6791D chip? (this chip is what the sensors-detect output showing) I did `modprobe nct6775` and `modprobe nct6775 0x290` at the command line to no effect. The other command `modprobe coretemp` did result in sensors reporting the CPU temperature (only).

I recently reformatted my disk1 from ReiserFS to XFS, and then I did rsync -avPX /mnt/disk4/ /mnt/disk1 When it's done I ran the xfs_db - frag-f, to my surprise the fragmentation level is 27%, I was kind of hoping to see 0%. Does rsync write some temporary files somewhere on destination drive, and then delete it after completion? Other than that, I'm not sure what might cause the rather significant fragmentation.

Autofan questions. Q1 I understand that autofan is controlling speed by pwm. Is it also working with 3-pin fans header with no PWM, that is, will it do voltage-based speed control using pin #3? If not, is there such plugin? Q2 I'm wondering about the issue of minimum PWM. I clicked DETECT next to "Minimum PWM value:" settings a few times, but the field remains blank. Meanwhile, syslog is reporting 0 rpm at certain PWM values, logs below. Is this all fine or do I need to adjust something somewhere? Oct 27 05:38:09 Tower autofan: Highest disk temp is 40C, adjusting fan speed from: 189 (74% @ 2265rpm) to: 145 (56% @ 1771rpm) Oct 27 05:43:14 Tower autofan: Highest disk temp is 39C, adjusting fan speed from: 145 (56% @ 1767rpm) to: 123 (48% @ 1500rpm) Oct 27 06:08:23 Tower autofan: Highest disk temp is 38C, adjusting fan speed from: 123 (48% @ 1500rpm) to: 101 (39% @ 0rpm) Oct 27 06:13:28 Tower autofan: Highest disk temp is 34C, adjusting fan speed from: 101 (39% @ 0rpm) to: OFF (0% @ 0rpm) Oct 27 06:23:33 Tower autofan: Highest disk temp is 36C, adjusting fan speed from: OFF (0% @ 0rpm) to: 57 (22% @ 0rpm) Oct 27 06:33:38 Tower autofan: Highest disk temp is 37C, adjusting fan speed from: 57 (22% @ 0rpm) to: 79 (30% @ 0rpm) Oct 27 06:48:43 Tower autofan: Highest disk temp is 38C, adjusting fan speed from: 79 (30% @ 0rpm) to: 101 (39% @ 0rpm) Oct 27 07:03:49 Tower autofan: Highest disk temp is 0C, adjusting fan speed from: 101 (39% @ 0rpm) to: OFF (0% @ 0rpm) Oct 27 07:28:54 Tower autofan: Highest disk temp is 39C, adjusting fan speed from: OFF (0% @ 0rpm) to: 123 (48% @ 0rpm) Oct 27 07:33:59 Tower autofan: Highest disk temp is 37C, adjusting fan speed from: 123 (48% @ 1513rpm) to: 79 (30% @ 0rpm) Oct 27 07:44:04 Tower autofan: Highest disk temp is 38C, adjusting fan speed from: 79 (30% @ 0rpm) to: 101 (39% @ 0rpm) Oct 27 07:54:10 Tower autofan: Highest disk temp is 39C, adjusting fan speed from: 101 (39% @ 0rpm) to: 123 (48% @ 1500rpm) Oct 27 07:59:15 Tower autofan: Highest disk temp is 37C, adjusting fan speed from: 123 (48% @ 1510rpm) to: 79 (30% @ 0rpm) Oct 27 08:04:20 Tower autofan: Highest disk temp is 38C, adjusting fan speed from: 79 (30% @ 0rpm) to: 101 (39% @ 0rpm) Oct 27 08:14:25 Tower autofan: Highest disk temp is 39C, adjusting fan speed from: 101 (39% @ 0rpm) to: 123 (48% @ 1496rpm) Oct 27 08:19:30 Tower autofan: Highest disk temp is 37C, adjusting fan speed from: 123 (48% @ 1510rpm) to: 79 (30% @ 0rpm) Oct 27 08:24:35 Tower autofan: Highest disk temp is 38C, adjusting fan speed from: 79 (30% @ 0rpm) to: 101 (39% @ 0rpm) Oct 27 08:34:40 Tower autofan: Highest disk temp is 39C, adjusting fan speed from: 101 (39% @ 0rpm) to: 123 (48% @ 1490rpm) Oct 27 08:39:45 Tower autofan: Highest disk temp is 37C, adjusting fan speed from: 123 (48% @ 1510rpm) to: 79 (30% @ 0rpm) Oct 27 08:44:51 Tower autofan: Highest disk temp is 38C, adjusting fan speed from: 79 (30% @ 0rpm) to: 101 (39% @ 0rpm) Oct 27 08:54:56 Tower autofan: Highest disk temp is 39C, adjusting fan speed from: 101 (39% @ 0rpm) to: 123 (48% @ 1486rpm) Oct 27 09:00:01 Tower autofan: Highest disk temp is 37C, adjusting fan speed from: 123 (48% @ 1510rpm) to: 79 (30% @ 0rpm) Oct 27 09:05:06 Tower autofan: Highest disk temp is 38C, adjusting fan speed from: 79 (30% @ 0rpm) to: 101 (39% @ 0rpm) Oct 27 09:15:11 Tower autofan: Highest disk temp is 39C, adjusting fan speed from: 101 (39% @ 0rpm) to: 123 (48% @ 1503rpm) Oct 27 09:20:16 Tower autofan: Highest disk temp is 37C, adjusting fan speed from: 123 (48% @ 1510rpm) to: 79 (30% @ 0rpm) Oct 27 09:25:21 Tower autofan: Highest disk temp is 38C, adjusting fan speed from: 79 (30% @ 0rpm) to: 101 (39% @ 0rpm)

after 97 hours of 3 cycles of preclearing a 3TB drive, this is the result. There were 65535 sectors pending re-allocation for the whole time, and no sectors had been reallocated at any cycle. I guess I need to run another cycle or two, but wondering if the result will still be the same. ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 100 200 0 ok 0 Power_On_Hours = 89 90 0 ok 8064 Temperature_Celsius = 111 121 0 ok 41 No SMART attributes are FAILING_NOW 65535 sectors were pending re-allocation before the start of the preclear. 65535 sectors were pending re-allocation after pre-read in cycle 1 of 3. 65535 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 65535 sectors were pending re-allocation after post-read in cycle 1 of 3. 65535 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 65535 sectors were pending re-allocation after post-read in cycle 2 of 3. 65535 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 65535 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================

Thanks Joe! Also, I suppose there's no difference if I do one cycle at a time and repeat three times, rather than 3 cycles in one go?

I'm doing an initial preclear for my 3TB Seagate drive, the following is the result if the first cycle, should I be concerned with the 'near threshold' statuses? == ST3000DM001-9YN166 Z1F12YES == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 115 117 6 ok 98467112 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 57 64 45 near_thresh 43 Temperature_Celsius = 43 36 0 ok 43 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. a side note, I simultaneously precleared this disk with two other drives (2TB Hitachi and WD Green), surprisingly the preclear for this disk finished earlier!