fvdw-sl on WD My Cloud

[Jocko]

Ok so I will just implement the led on/off feature.

Now what color do you want to use green as the WD firmware or blue as Lacie firmware ?

[fvdw]

Please use green, blue is used for indicating correct loading and running kernel and being active in initramfs. It is helpfull to user to see in which stage the nas is, it will turn red when entering firmware install mode

[matt_max]

I agree. Green looks fine to me. Is it possible to set up led light to turn off when nas is off? Now when I run poweroff led remains green even if system is off.

[fvdw]

In the meantime I found a cheap wd mycloud gen 1 on the internet without disk.
I tested file transfer, on samba I get something from 10-12 MB/s, also with smb4, on ftp I get values around 30 MB/s
So seems something is limiting samba transfer rate.
Matt-max can you also test file transfer rate on samba and FTP ? (use a file of at least 100 MB).
Did you also see this rather slow transfer on samba with WD firmware ? (if with WD firmware the rate is like I get with FTP it may something in our samba configuration file)

I see this message in samba log

Code: Select all

[2018/01/01 12:28:25.628031,  0] ../../source3/lib/util_sock.c:357(open_socket_in)
  open_socket_in(): setsockopt: SO_REUSEPORT = true on port 445 failed with error = Protocol not available


seems we miss something in the kernel wrt samba protocols

[fvdw]

I think I know what the issue is, kernel 3.2 doesn't support smb2, that was first introduced in kernel 3.6...
So I expect also in wd firmware that the transfer speed was low

[matt_max]

Well I've got the same errors in log.smbd.
As you probably remember I use my old WD5000LPVX disc (5400rpm) so results may not be adequate. Using TeraCopy and 800MB iso file I've got something between 8 to 15 MB/s (smb4 protocol) and using WinSCP and ftp connection: from 16 to 18 MB/s.

I don't know if it is important but I've got this message in console:

Code: Select all

[ 1095.914826] warning: `proftpd' uses 32-bit capabilities (legacy support in use)


[Jocko]

Hi

Attached a tarball which restores these features :
- switch on/off the led from the fw webinterface
- led OFF on nas rebooting

So save the tarball in fvdw share and perform the command

Code: Select all

tar -xf /direct-usb/fvdw/fvdw-sl-18-x-led-cmd-19oct22.tgz -C /

Do not reboot the nas but make these tests

Code: Select all

led (should return 1 if green led is on)
led -w off (should turn off the green led)
led -w on (should turn on again the green led)
led -w off
led -w 5 (should turn on again the green led)
led -o brightness -w off (should turn off the green led)
led -o brightness -w on (should turn on again the green led)
led -o trigger -w nand-disk (should do nothing)
led -o blinking (should return 'on')
led -o trigger (should return 'none')

if it is ok go the web-interface and load the main "setup" menu. So from the tab 'other settings', try to switch off/on the led

if all is ok, set the option "Led off at the next booting" and reboot the nas. Check if the led is off when the boot script is completed (try later the case "led on at the next booting")

[matt_max]

@Jocko - there is missing ")" in /etc/leds_name_table in line 98. All tests were successful except one:

Code: Select all

root@fvdwsl-base:/ # led -o blinking
unset


[Jocko]

Ouuups

the right option is 'blink' instead of 'blinking'

there is missing ")" in /etc/leds_name_table in line 98

:thumbup I go to fix that in my file. (---edit: I also updated the tarball)

All tests were successful

Nice. So you can try the other tests if you did not reboot the nas

[matt_max]

One more little glitch: when I try to reboot nas using "NAS Restart" button it does nothing. There is a message:

Code: Select all

Web server rebooting
Web interface reloaded in about 86s
Please wait ...


...but nas doesn't reboot - there is sign of rebooting process in console and nas stays on. I need to manually do reboot from ssh or console.
P.S. Now led -o blink show on.