Page 1 of 1

D2-310 green led flashing but only in unix.

Posted: 09 Jul 2024, 18:58
by BL4BL0
Greetings, I have a D2-310 on RAID1. I am using it on 3 different devices: Ubuntu, Raspbian and W10.

In all 3 devices it works correctly, but in the two Unix ones (Ubuntu and Raspbian) the green leds on both drives blinking and don't stop from the moment the unit is mounted until it is unmounted.

I have verified that there is no service in the background using the unit.
In addition to the green leds blinking i can hear that the units are working reading and writing.

any ideas?

What could be causing the unit to continually work, even when not actually being used?

Could it be some incorrect mounting option?

my /etc/fstab line:
/dev/sda1 /mnt/RAID ext4 defaults,nofail 0 0



hw:
D2-310 (RAID1)
2 x WD RED 4TB WD40EFAX (ext4)
Usb 3.1 Connection

sf:
- w10 -> everything ok.
- ubuntu 18.4.01 -> everything ok, but green leds blinking
- raspbian Debian version: 12 (bookworm) -> everything ok, but green leds blinking

Re: D2-310 green led flashing but only in unix.

Posted: 12 Jul 2024, 10:28
by TMzethar
If there is no similar problem on Windows,basically there are only two possibilities.
1. Ubuntu, Raspbian OS sends wrong commands, which prevent HD from going to sleep correctly.
2.There are some programs running on the HD in Ubuntu, Raspbian OS, occupying or reading the disk.

Re: D2-310 green led flashing but only in unix.

Posted: 24 Jul 2024, 22:54
by Olli2024
Some filesystems in Unix / Linux do some internal checks and journaling that might take some time, especially on larger drives when they are formatted for the first time. I do not know if that is the case on your system?

Just wait a few days for the drive to finish if the filesystem is just created. This takes place on EXT4 file systems for example.

You can use this command to check I/O on the drive:

sudo blktrace -d /dev/sdX -o - | blkparse -i -

Re: D2-310 green led flashing but only in unix.

Posted: 24 Jul 2024, 23:01
by Olli2024
Another thing that came into my mind was the smartmontools tools service that was continuously checking the drives in my system preventing them from going into sleep mode.

A workaround could be do disable the smartmontools service and check the drive only once a day with a cronjob, which was enough for me.