Some personal findings:
- My wdbctl0030hwt is a WDMyCloud-Gen1 (though the BCTL model is not listed in https://ftp.anionix.ru/WDMyCloud/WDMC-Codenames.txt)
- The 64-k page distro (CleanDebian64k.tar.gz) did not work well with the generally available packages: If you apt-install from the Debian repositories, sometimes the processes bails out and exit.
- Stick to the CleanDebian-Jessie.tgz release instead
- The default system cmdline includes some debug clauses in the cmdline: debug initcall_debug. This cause systemd and kernel to throw lots of unneeded messages. The only way to fix it is writing a new configuration partition. This is how I did it.
USE AT YOUR VERY OWN RISK
1. Log in your WD box and fetch the current kernel configuration:
# dd if=/dev/sda7 of=config.img
2. Extract the configuration using the strings command:
strings config.img > config.txt
3. Edit config.txt, remove the clauses debug initcall_debug and save the resulting file in a PC running Linux.
4. In the PC, download bareboxenv32 from the GPL toolchain (I got from gpl-source-wd_my_cloud-04.01.02-417.zip) from WD at https://support.wdc.com/downloads.aspx?p=213&lang=en. The file is located at packages/barebox-2011.06.0/scripts/
5. Take the file that you got from step 3 and save it in a same directory that has bareboxenv32. Then run:
chmod 755 bareboxenv32
./bareboxenv32 -s config.txt new-config.img
6. Save the resulting file new-config.img to your WD box
7. Blank your WD box partition 7 config data:
dd if=/dev/zero of=/dev/sda7
8. And then, load your new config data:
dd if=new-config.img of=/dev/sda7
9. You may then reboot your system.
Of course you may also use this procedure to add something you want to the linux boot cmdline. Just add/remove it in step 3 and follow the rest of the procedure.
Kudos to fox_exe o/