Is it possible to use the control scripts on the DXP480T?

[blaugrau90]

I have the DXP480T Full SSD NAS. Unfortunately, the scripts do not work here. The SMBUS I801 is present, but the script does not find any LEDs that it can control.

Here is the output of i2cdetect -l and i2cdetect -y 0:

~# i2cdetect -l
i2c-0   smbus       SMBus I801 adapter at efa0          SMBus adapter
i2c-1   i2c         Synopsys DesignWare I2C adapter     I2C adapter
i2c-2   i2c         Synopsys DesignWare I2C adapter     I2C adapter
i2c-3   i2c         i915 gmbus dpa                      I2C adapter
i2c-4   i2c         i915 gmbus dpb                      I2C adapter
i2c-5   i2c         i915 gmbus dpc                      I2C adapter
i2c-6   i2c         i915 gmbus tc1                      I2C adapter
i2c-7   i2c         i915 gmbus tc2                      I2C adapter
i2c-8   i2c         i915 gmbus tc3                      I2C adapter
i2c-9   i2c         i915 gmbus tc4                      I2C adapter
i2c-10  i2c         i915 gmbus tc5                      I2C adapter
i2c-11  i2c         i915 gmbus tc6                      I2C adapter
i2c-12  i2c         AUX B/DDI B/PHY B                   I2C adapter
i2c-13  i2c         AUX USBC1/DDI TC1/PHY TC1           I2C adapter
i2c-14  i2c         AUX USBC2/DDI TC2/PHY TC2           I2C adapter
i2c-15  i2c         AUX USBC3/DDI TC3/PHY TC3           I2C adapter
i2c-16  i2c         AUX USBC4/DDI TC4/PHY TC4           I2C adapter

~# i2cdetect -y 0
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         08 -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- 26 -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- 44 -- -- -- 48 -- 4a -- -- -- -- --
50: 50 -- 52 -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

Is there any way to adapt this so that it also works on this NAS? Currently the power LED flashes all the time. There are no other LEDs.

[miskcoo]

I think it is possible to control the power LED, but we need to probe each of these addresses.

According to what I see from the driver, you can read bytes from registers at 0x5a, 0x5b and 0x5d using:

# replace <chip addr> below with the addresses you see from i2cdetect, which is (in your case) 0x08, 0x26, ...
i2cget -y 0  <chip addr>  0x5a b
i2cget -y 0  <chip addr>  0x5b b
sleep 5
i2cget -y 0  <chip addr>  0x5d b

If I am correct, the chip for the power LED will return 0xa5, 0xb5 and the version of this chip, respectively. If you find there is an address returning these outputs, I can check how to turn on/off this LED later.

[blaugrau90]

This is the result of the few commands for my chip address:

#Chip Address
addresses=(0x08 0x26 0x44 0x48 0x4a 0x50 0x52)

for addr in "${addresses[@]}"; do
  i2cget -y 0 $addr 0x5a b
  i2cget -y 0 $addr 0x5b b
done

sleep 5

for addr in "${addresses[@]}"; do
  i2cget -y 0 $addr 0x5d b
done

# Result from the first two commands
Error: Read failed
Error: Read failed
0xa5
0xb5
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00

# Sleep Time 5 sec

# Result of the last command
Error: Read failed
0x06
0x00
0x00
0x00
0x00
0x00

[miskcoo]

Good to see that, it seems 0x26 is the correct address.

It seems the relevant registers at chip 0x26 are 0x50, 0x51, 0xb1, 0xa0, 0xe0, 0xe1. All of them are 8-bits, so we need to use i2cset -y 0 0x26 <reg addr> <data (a byte)> b.

• The LED is initialized by sequentially writing:

  i2cset -y 0 0x26 0x50 0 b
  i2cset -y 0 0x26 0x51 0 b
  i2cset -y 0 0x26 0xb1 2 b
  i2cset -y 0 0x26 0xa0 1 b

• 0xb1 appears a control register, a typical value to write is of the form mode << offset, where mode = 1, 2, 3 and I guess offset = 0, 1 but not sure. You can try to write something to this register to see if the light will turn off. It seems writing something with (mode = 3, i.e., write 3 or 6 or ...) will turn it off.
• For setting the brightness, the code looks like there are two different command sequences:
  1. Write something (mode = 2) to 0xb1 and return;
  2. Write something (mode = 1) to 0xb1, and then write something like mode2 << offset2 to 0xa0, and finally write the same byte to both 0xe0, 0xe1, indicating a brightness. <-- this deleted part indicates an error of changing the brightness; so in the mode 1, you only need to write to 0xa0.
• For setting the color, the driver write to one of 0x50 or 0x51 (according a variable, not sure its meaning); and then write to 0xb1 with mode = 3; and then write something to 0xa0.

I guess you can search these undetermined values and try to figure the meaning of them.

Update: Given that mode = 1, 2, 3, I guess the offset is a multple of 3.

[miskcoo]

For reading the status, you can try registers starting from 0x80 (maybe 0x80 and 0x81, the status is represented by 2 bytes). They are also read in byte mode.

[miskcoo]

For blinking and breathing, one pattern is:

1. writing something to 0x50;
2. then write something with mode = 1 to 0xb1;
3. then write something to 0x51;

Finally, for consecutive writes, you may need to add a sleep between them.

[blaugrau90]

With the following code, I was able to stop the LED from flashing. That was very annoying. I assume that the color cannot be changed, it seems to be a white LED. Not an RGB LED.

i2cset -y 0 0x26 0x50 0 b
i2cset -y 0 0x26 0x51 0 b
i2cset -y 0 0x26 0xb1 2 b
i2cset -y 0 0x26 0xa0 1 b

Even though I haven't quite understood what each line of it does. I think i2cset -y 0 0x26 0xb1 2 b has no influence on the LED. At least it lights up continuously even without the command. Could you explain the individual commands to me in detail and what effect they have on the LED?

[miskcoo]

I do not know the exact meaning of them, neither. It was found in the de-compiled code of the kernel module named leds-mcu-n76e003.ko. To determine their meaning, we need to either look at the code in detail, but it requires many efforts; or alternatively, with a device at hand (I don't have it, so I cannot do this), we can try to write I2C registers according to the observed command sequences in that module, and check the LED's status.

Basically, I think i2cset -y 0 0x26 0xb1 <data> b is used to change the basic state (on / off / blink) of this LED; and similarly for i2cset -y 0 0x26 0xa0 <data> b; and i2cset -y 0 0x26 0x50 <data> b and i2cset -y 0 0x26 0x51 <data> b look like the additional information (e.g., the blink delay; color?).

I guess to turn-off the light, you can use i2cset -y 0 0x26 0xb1 3 b. To investigate more, you can try to run a grid search and observe the status of your LED. For example,

# change only one register
for i in $(seq 0 7); do
    i2cset -y 0 0x26 0xb1 $i b
    sleep 1
done

# change two registers
for i in $(seq 0 7); do
    for j in $(seq 0 7); do
        i2cset -y 0 0x26 0xb1 $i b
        sleep 0.5
        i2cset -y 0 0x26 0xa0 $j b
    done
    sleep 1
done

[blaugrau90]

I have found out which commands are suitable for what. Pulsing: Permanently on i2cset -y 0 0x26 0x50 0 b

Fast flashing i2cset -y 0 0x26 0x50 1 b

Slow flashing i2cset -y 0 0x26 0x51 1 b

Breathing slowly i2cset -y 0 0x26 0x50 2 b

No slow Flashing / breathing i2cset -y 0 0x26 0x51 0 b

Colors: Red LED on after off i2cset -y 0 0x26 0xb1 1 b or i2cset -y 0 0x26 0xb1 5 b Red LED off after on i2cset -y 0 0x26 0xa0 1 b or i2cset -y 0 0x26 0xa0 5 b

White LED on after off i2cset -y 0 0x26 0xb1 2 b or i2cset -y 0 0x26 0xb1 6 b White LED off after on i2cset -y 0 0x26 0xa0 2 b or i2cset -y 0 0x26 0xa0 6 b

If both LEDs are on, the one that was switched on first wins. If this is then switched off, the other LED that is still switched on remains on. After the LED is switched from Breathering to permanent, it remains at the current brightness level. depending on when you switch, it may be almost completely dark or completely bright. You then have to switch it back to full brightness with the 0xb1.

[blaugrau90]

Summarized here, every possible LED function that seems to exist.

### Applies to the UGREEN DXP480T NAS ###

## Permanently ON
## i2cset -y 0 0x26 0x50 0 b

## Fast Flashing
## i2cset -y 0 0x26 0x50 1 b

## Breathing
## i2cset -y 0 0x26 0x50 2 b

## Slowly Flashing
## i2cset -y 0 0x26 0x51 1 b

## Preset for Effects:
## i2cset -y 0 0x26 0xa0 1 b # red off
## i2cset -y 0 0x26 0xa0 2 b # white off
## i2cset -y 0 0x26 0x50 0 b # Permanently on

## red on
i2cset -y 0 0x26 0xa0 1 b # red off
i2cset -y 0 0x26 0xa0 2 b # white off

i2cset -y 0 0x26 0xb1 1 b # red on
i2cset -y 0 0x26 0x51 0 b # Slow Flash off
i2cset -y 0 0x26 0x50 0 b # Permanently on

## white on
i2cset -y 0 0x26 0xa0 1 b # red off
i2cset -y 0 0x26 0xa0 2 b # white off

i2cset -y 0 0x26 0xb1 2 b # white on
i2cset -y 0 0x26 0x51 0 b # Slow Flash off
i2cset -y 0 0x26 0x50 0 b # Permanently on

## red Fast Flashing
i2cset -y 0 0x26 0xa0 1 b # red off
i2cset -y 0 0x26 0xa0 2 b # white off
i2cset -y 0 0x26 0x50 0 b # Permanently on

i2cset -y 0 0x26 0xb1 1 b # red on
i2cset -y 0 0x26 0x51 0 b # Slow Flash off
i2cset -y 0 0x26 0x50 1 b # Fast Flash on

## white Fast Flashing
i2cset -y 0 0x26 0xa0 1 b # red off
i2cset -y 0 0x26 0xa0 2 b # white off
i2cset -y 0 0x26 0x50 0 b # Permanently on

i2cset -y 0 0x26 0xb1 2 b # white on
i2cset -y 0 0x26 0x51 0 b # Slow Flash off
i2cset -y 0 0x26 0x50 1 b # Fast Flash on

## red Slowly Flashing
i2cset -y 0 0x26 0xa0 1 b # red off
i2cset -y 0 0x26 0xa0 2 b # white off
i2cset -y 0 0x26 0x50 0 b # Permanently on

i2cset -y 0 0x26 0xb1 1 b # red on
i2cset -y 0 0x26 0x50 0 b # Fast Flash / Breathing off
i2cset -y 0 0x26 0x51 1 b # Slow Flash on

## white Slowly Flashing
i2cset -y 0 0x26 0xa0 1 b # red off
i2cset -y 0 0x26 0xa0 2 b # white off
i2cset -y 0 0x26 0x50 0 b # Permanently on

i2cset -y 0 0x26 0xb1 2 b # white on
i2cset -y 0 0x26 0x50 0 b # Fast Flash / Breathing off
i2cset -y 0 0x26 0x51 1 b # Slow Flash on

## red Breathing
i2cset -y 0 0x26 0xa0 1 b # red off
i2cset -y 0 0x26 0xa0 2 b # white off
i2cset -y 0 0x26 0x50 0 b # Permanently on

i2cset -y 0 0x26 0xb1 1 b # red on
i2cset -y 0 0x26 0x51 0 b # Slow Flash off
i2cset -y 0 0x26 0x50 2 b # Breathing on

## white Breathing
i2cset -y 0 0x26 0xa0 1 b # red off
i2cset -y 0 0x26 0xa0 2 b # white off
i2cset -y 0 0x26 0x50 0 b # Permanently on

i2cset -y 0 0x26 0xb1 2 b # white on
i2cset -y 0 0x26 0x51 0 b # Slow Flash off
i2cset -y 0 0x26 0x50 2 b # Breathing on

[Erani0]

Oh nice I just knew it was on the HDD Nas systems. What would that look like if you wanted to use it? I've never worked with anything like this before.

[blaugrau90]

My primary concern was that the power LED kept flashing after I replaced the UGOS with a different OS. That's why I wanted to know how to control the LED. I found out with the help of this repo and the developer. Now a script always runs when the system boots, which sets the LED to permanently white.

[miskcoo]

@blaugrau90 Great to hear that! It seems we now have full control of the power LED on DXP480 Plus.

@Erani0 I guess in UGOS the light will also indicate device faults. If you want to use it in such a way, you must write a script (e.g., scripts/ugreen-diskiomon in this repo, and update-leds.sh in meyergru's repo) to monitor events such as disk failure, network failure, etc., and change the status of the light based on the above commands.

[Erani0]

I use Proxmox now

An i have no idea ro write Linux scripts

[YugiFanGX]

TrueNAS Scale, no output from i2cdetect -l ...

[miskcoo]

do you load the i2c-dev module? please check the output of lsmod.

On Sat, Jun 15, 2024, 02:52 YugiFanGX @.***> wrote:

TrueNAS Scale, no output from i2cdetect -l ...

— Reply to this email directly, view it on GitHub https://github.com/miskcoo/ugreen_dx4600_leds_controller/issues/6#issuecomment-2168583053, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABBGJTAFNQOWWRJYJQLNLNDZHM3WPAVCNFSM6AAAAABJA7Y4T6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRYGU4DGMBVGM . You are receiving this because you commented.Message ID: @.***>

[YugiFanGX]

That solved the issue. Thank you!

[Dataninja126]

I'm passing the SATA controllers for Proxmox into a TrueNAS VM and I believe the passing of the controllers may be affecting the device IDs? None of the commands in the exhaustive list above work and I get an Error: Write failed in both. Any suggestions?

Here is the output of i2cdetect -l and i2cdetect -y 0 in TrueNAS VM:

i2c-0   smbus           SMBus PIIX4 adapter at 0700             SMBus adapter

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: 50 51 52 53 54 55 56 57 -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --   

Here is the output of i2cdetect -l and i2cdetect -y 0 in Proxmox:

i2c-1   i2c             Synopsys DesignWare I2C adapter         I2C adapter
i2c-2   i2c             Synopsys DesignWare I2C adapter         I2C adapter
i2c-3   i2c             i915 gmbus dpa                          I2C adapter
i2c-4   i2c             i915 gmbus dpb                          I2C adapter
i2c-5   i2c             i915 gmbus dpc                          I2C adapter
i2c-6   i2c             i915 gmbus tc1                          I2C adapter
i2c-7   i2c             i915 gmbus tc2                          I2C adapter
i2c-8   i2c             i915 gmbus tc3                          I2C adapter
i2c-9   i2c             i915 gmbus tc4                          I2C adapter
i2c-10  i2c             i915 gmbus tc5                          I2C adapter
i2c-11  i2c             i915 gmbus tc6                          I2C adapter
i2c-12  i2c             AUX B/DDI B/PHY B                       I2C adapter
i2c-13  i2c             AUX USBC1/DDI TC1/PHY TC1               I2C adapter
i2c-14  i2c             AUX USBC2/DDI TC2/PHY TC2               I2C adapter
i2c-15  i2c             AUX USBC3/DDI TC3/PHY TC3               I2C adapter
i2c-16  i2c             AUX USBC4/DDI TC4/PHY TC4               I2C adapter

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:                         08 -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- 3a -- -- -- -- -- 
40: -- -- -- -- 44 -- -- -- 48 -- 4a -- -- -- -- -- 
50: 50 -- 52 -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --  ```

[miskcoo]

@Dataninja126 at the moment you cannot use this tool in a VM -- it should be run in the host (i.e., your proxmox);

for the outputs in proxmox, is i2c-0 missing? and what's your NAS model?

[Dataninja126]

@Dataninja126 at the moment you cannot use this tool in a VM -- it should be run in the host (i.e., your proxmox);

for the outputs in proxmox, is i2c-0 missing? and what's your NAS model?

Sorry I must have accidently omitted that line and I have the 6800Pro

i2c-0   smbus           SMBus I801 adapter at efa0              SMBus adapter
i2c-1   i2c             Synopsys DesignWare I2C adapter         I2C adapter
i2c-2   i2c             Synopsys DesignWare I2C adapter         I2C adapter
i2c-3   i2c             i915 gmbus dpa                          I2C adapter
i2c-4   i2c             i915 gmbus dpb                          I2C adapter
i2c-5   i2c             i915 gmbus dpc                          I2C adapter
i2c-6   i2c             i915 gmbus tc1                          I2C adapter
i2c-7   i2c             i915 gmbus tc2                          I2C adapter
i2c-8   i2c             i915 gmbus tc3                          I2C adapter
i2c-9   i2c             i915 gmbus tc4                          I2C adapter
i2c-10  i2c             i915 gmbus tc5                          I2C adapter
i2c-11  i2c             i915 gmbus tc6                          I2C adapter
i2c-12  i2c             AUX B/DDI B/PHY B                       I2C adapter
i2c-13  i2c             AUX USBC1/DDI TC1/PHY TC1               I2C adapter
i2c-14  i2c             AUX USBC2/DDI TC2/PHY TC2               I2C adapter
i2c-15  i2c             AUX USBC3/DDI TC3/PHY TC3               I2C adapter
i2c-16  i2c             AUX USBC4/DDI TC4/PHY TC4               I2C adapter

[miskcoo]

@Dataninja126 at the moment you cannot use this tool in a VM -- it should be run in the host (i.e., your proxmox); for the outputs in proxmox, is i2c-0 missing? and what's your NAS model?

Sorry I must have accidently omitted that line and I have the 6800Pro

i2c-0   smbus           SMBus I801 adapter at efa0              SMBus adapter
i2c-1   i2c             Synopsys DesignWare I2C adapter         I2C adapter
i2c-2   i2c             Synopsys DesignWare I2C adapter         I2C adapter
i2c-3   i2c             i915 gmbus dpa                          I2C adapter
i2c-4   i2c             i915 gmbus dpb                          I2C adapter
i2c-5   i2c             i915 gmbus dpc                          I2C adapter
i2c-6   i2c             i915 gmbus tc1                          I2C adapter
i2c-7   i2c             i915 gmbus tc2                          I2C adapter
i2c-8   i2c             i915 gmbus tc3                          I2C adapter
i2c-9   i2c             i915 gmbus tc4                          I2C adapter
i2c-10  i2c             i915 gmbus tc5                          I2C adapter
i2c-11  i2c             i915 gmbus tc6                          I2C adapter
i2c-12  i2c             AUX B/DDI B/PHY B                       I2C adapter
i2c-13  i2c             AUX USBC1/DDI TC1/PHY TC1               I2C adapter
i2c-14  i2c             AUX USBC2/DDI TC2/PHY TC2               I2C adapter
i2c-15  i2c             AUX USBC3/DDI TC3/PHY TC3               I2C adapter
i2c-16  i2c             AUX USBC4/DDI TC4/PHY TC4               I2C adapter

Have you tried the cli tool in proxmox? I think it will work. This issue and the commands above are about 480T -- it is different from other HDD models.

[Dataninja126]

@Dataninja126 at the moment you cannot use this tool in a VM -- it should be run in the host (i.e., your proxmox); for the outputs in proxmox, is i2c-0 missing? and what's your NAS model?

Sorry I must have accidently omitted that line and I have the 6800Pro

i2c-0   smbus           SMBus I801 adapter at efa0              SMBus adapter
i2c-1   i2c             Synopsys DesignWare I2C adapter         I2C adapter
i2c-2   i2c             Synopsys DesignWare I2C adapter         I2C adapter
i2c-3   i2c             i915 gmbus dpa                          I2C adapter
i2c-4   i2c             i915 gmbus dpb                          I2C adapter
i2c-5   i2c             i915 gmbus dpc                          I2C adapter
i2c-6   i2c             i915 gmbus tc1                          I2C adapter
i2c-7   i2c             i915 gmbus tc2                          I2C adapter
i2c-8   i2c             i915 gmbus tc3                          I2C adapter
i2c-9   i2c             i915 gmbus tc4                          I2C adapter
i2c-10  i2c             i915 gmbus tc5                          I2C adapter
i2c-11  i2c             i915 gmbus tc6                          I2C adapter
i2c-12  i2c             AUX B/DDI B/PHY B                       I2C adapter
i2c-13  i2c             AUX USBC1/DDI TC1/PHY TC1               I2C adapter
i2c-14  i2c             AUX USBC2/DDI TC2/PHY TC2               I2C adapter
i2c-15  i2c             AUX USBC3/DDI TC3/PHY TC3               I2C adapter
i2c-16  i2c             AUX USBC4/DDI TC4/PHY TC4               I2C adapter

Have you tried the cli tool in proxmox? I think it will work. This issue and the commands above are about 480T -- it is different from other HDD models.

Well, the script worked in a sense that it stopped the trailing lights, but because the SATA controllers are passed through it's triggering the following:

Mapping devices...
Hardware mapping (hwmap):
Checking zpool status...
no pools available
Processing  with status 
./ugreen_leds6800.sh: line 49: hwmap: bad array subscript
Warning: No mapping found for 
Final device statuses:
0: p
1: u
2: x
3: x
4: x
5: x
6: x
7: x

[miskcoo]

@Dataninja126 at the moment you cannot use this tool in a VM -- it should be run in the host (i.e., your proxmox); for the outputs in proxmox, is i2c-0 missing? and what's your NAS model?

Sorry I must have accidently omitted that line and I have the 6800Pro

i2c-0   smbus           SMBus I801 adapter at efa0              SMBus adapter
i2c-1   i2c             Synopsys DesignWare I2C adapter         I2C adapter
i2c-2   i2c             Synopsys DesignWare I2C adapter         I2C adapter
i2c-3   i2c             i915 gmbus dpa                          I2C adapter
i2c-4   i2c             i915 gmbus dpb                          I2C adapter
i2c-5   i2c             i915 gmbus dpc                          I2C adapter
i2c-6   i2c             i915 gmbus tc1                          I2C adapter
i2c-7   i2c             i915 gmbus tc2                          I2C adapter
i2c-8   i2c             i915 gmbus tc3                          I2C adapter
i2c-9   i2c             i915 gmbus tc4                          I2C adapter
i2c-10  i2c             i915 gmbus tc5                          I2C adapter
i2c-11  i2c             i915 gmbus tc6                          I2C adapter
i2c-12  i2c             AUX B/DDI B/PHY B                       I2C adapter
i2c-13  i2c             AUX USBC1/DDI TC1/PHY TC1               I2C adapter
i2c-14  i2c             AUX USBC2/DDI TC2/PHY TC2               I2C adapter
i2c-15  i2c             AUX USBC3/DDI TC3/PHY TC3               I2C adapter
i2c-16  i2c             AUX USBC4/DDI TC4/PHY TC4               I2C adapter

Have you tried the cli tool in proxmox? I think it will work. This issue and the commands above are about 480T -- it is different from other HDD models.

Well, the script worked in a sense that it stopped the trailing lights, but because the SATA controllers are passed through it's triggering the following:

Mapping devices...
Hardware mapping (hwmap):
Checking zpool status...
no pools available
Processing  with status 
./ugreen_leds6800.sh: line 49: hwmap: bad array subscript
Warning: No mapping found for 
Final device statuses:
0: p
1: u
2: x
3: x
4: x
5: x
6: x
7: x

I think this is an expected behavior, supporting this case will be complicated, though it is possible.

[Dataninja126]

I think this is an expected behavior, supporting this case will be complicated, though it is possible.

Thanks for the quick replies. I'm okay with the lights not flashing.

Because I'm not well versed in this space, I was considering passing through i2c-0, but not sure how that would affect my Proxmox system...

i2c-0   smbus           SMBus I801 adapter at efa0              SMBus adapter

Edit: nevermind, I'm not going to try, quick google search it supports critical functions of motherboard/periphal communication.

[bangity]

My primary concern was that the power LED kept flashing after I replaced the UGOS with a different OS. That's why I wanted to know how to control the LED. I found out with the help of this repo and the developer. Now a script always runs when the system boots, which sets the LED to permanently white.

@blaugrau90 can you please share this script? I have the same machine and tried Proxmox, not sure why it kept flashing until now. I also get random reboot and intermittenly lose Web GUI Proxmox activity. Have you experience that?

Thanks.