fvdw-sl on WD My Cloud

[fvdw]

Sorry to keep you waiting matt_max but Jocko is currently not available. I need to agree with him on changes to be made in the firmware

[matt_max]

Sorry to keep you waiting matt_max but Jocko is currently not available. I need to agree with him on changes to be made in the firmware

Take your time. I won't be able to test new features/releases because I'm going on vacation soon (from 8th of September to 24th of September). I'll let you know when I get back.

[matt_max]

Hi guys - I'm back but not fully healthly - f***g covid gets me. However I cannot wait to test new versions of firmware fvdw-sl for my wd nas.

[fvdw]

Hi matt_max, hopefully you will recover fast. On the moment I and Jocko have little time to work on this. In a few weeks it will be better.
In the past weeks I spend time to compile our own kernel. Not easy as this cpu of the mycloud is not part of mainline linux. But I am almost there. A custom kernel is required at the end to get all features of the firmware running and available

[matt_max]

Hi matt_max, hopefully you will recover fast. On the moment I and Jocko have little time to work on this. In a few weeks it will be better.
In the past weeks I spend time to compile our own kernel. Not easy as this cpu of the mycloud is not part of mainline linux. But I am almost there. A custom kernel is required at the end to get all features of the firmware running and available

Good news :thumbup Just let me know when I can test a new kernel.

[fvdw]

There is some progress, new kernel is running. As disassembling harddisk and soldering wires to serial port will be a bridge to far for new users I will make a kernel with initramfs that can be used to install firmware and can boot our firmware from any partition and no need to assemble a raid array The only thing new users will have to do is when still running wd firmware gaining ssh access and write the new kernel to sda5 and reboot. The new kernel will not find fvdw-sl firmware at this first boot and enter install mode with telnet access. Connecting via telnet and using an installer script the kernel will erase partition table and create a new one. After that we will get required files to install firmware via usb or tftp server and write those to disk. If finished the nas must be rebooted and firmware should come up. If getting firmware fails the nas should still boot into install mode as we will write first the kernel partition 6 and a modified image to partition 7 to instruct barebox to load kernel from p 6.
There will be no partition 9 and 10 anymore and no raid array.

[matt_max]

Brilliant :applause
That's very good news. I still have 6 TB disc from my WD nas with unchanged partitions so I can do some more tests with installation procedure if you wish.
I think raid is not necessary with only one disc available.

[fvdw]

check your pm box, some files for testing auto install

[matt_max]

I think that the procedure went well. During the install process system asked me to format raid partitions:

$matches[2]

Then after restart I was able to login in properly:

picture2a.jpg

Check the output from console. There are some bugs but mostly not so important:

• firmware still try to boot from md array:
  commandline: console=ttyS0,115200n8, init=/sbin/init root=/dev/md0 raid=autodetect rootfstype=ext3 rw noinitrd debug initcall_debug swapaccount=1 panic=3 mac_addr=00:90:A9:D8:5E:AD model=sq serial= board_test= btn_status=0
• update smart db cannot be done:
  /usr/sbin/update-smart-drivedb: download from trunk failed (HTTP error)
• I can't install minidlna - Fail: install command failed (17)
  and Transmission - Fail: can not retrieve the package, -99
• Power LED Off button doesn't do anything. LED is still on.
• NAS Shutdown doesn't work - I need to poweroff NAS from console.

Everything else working as expected. :applause :rock

[fvdw]

thanks for testing :thumbup and your feedback

I think that the procedure went well. During the install process system asked me to format raid partitions:

Well sda8 is now no longer a raid partition. You get this message because sda8 contained a raid member and file system from previous setup. The script ask if you want to overwrite it, In your case you should say yes. In case you would reinstall fvdw-sl on a disk were previous also fvdw-sl was installed but got corrupt the user might want to keep data on the data partition, in that case you can say no.

There are some bugs but mostly not so important:
firmware still try to boot from md array:
commandline: console=ttyS0,115200n8, init=/sbin/init root=/dev/md0 raid=autodetect rootfstype=ext3 rw noinitrd debug initcall_debug swapaccount=1 panic=3 mac_addr=00:90:A9:D8:5E:AD model=sq serial= board_test= btn_status=0

Barebox give this command line when loading the kernel, but the kernel does not use it :snicker
It uses a script inside the initramfs compiled within the kernel to load the firmware from the right partition 8-)

update smart db cannot be done:
/usr/sbin/update-smart-drivedb: download from trunk failed (HTTP error)

to be investigated
---edit Jocko :
It is a known bug but only fixing with version 18.2 (see: https://plugout.net/viewtopic.php?f=7&t=3149#p36493 )
However I can quickly patch the relevant files of version 18-1

I can't install minidlna - Fail: install command failed (17)
and Transmission - Fail: can not retrieve the package, -99

For this you need to install a patch for 18-1 (see plugout website https://plugout.net/viewtopic.php?f=7&t=3532#p35900) and enter your plugout credentials in system mgt>set-up tab firmware interface

Power LED Off button doesn't do anything. LED is still on.
NAS Shutdown doesn't work - I need to poweroff NAS from console.

correct, this is not yet implemented

ps did the leds changed color during boot ?

To be continued..