fvdw-sl on WD My Cloud

[matt_max]

After I applied contents of tgz archive output looks like this. Ethernet interface is present.
Even newer kernel (5.10.109) can be build and applied to WD Mycloud but unfortunately there is other chip (Armanda) inside WD Mycloud EX2.
This one is interesting too.
P.S. I cannot shut it down - but that is not important right now:

Code: Select all

WDMyCloud:~# shutdown -h now

Broadcast message from root@WDMyCloud (ttyS0) (Thu Aug 25 18:42:00 2022):

The system is going down for system halt NOW!
INIT: m[ 1084.095776] here before:pfe_module_exit
[ 1084.099677] pfe_platform_remove
[ 1084.102869] pfe_remove
[ 1084.105295] pfe_pcap_exit
[ 1084.107932] pfe_eth_exit
[ 1084.110483] eth0: pfe_eth_exit_one
[ 1084.114036] eth0: pfe_eth_close
[ 1084.117257] hif_lib_client_unregister : client: 8de80424, client_id: 0, txQ_depth: 1024, rxQ_depth: 256
[ 1084.126725] hif_process_client_req: unregister client_id 0
[ 1084.132242] pfe_hif_client_unregister
[ 1084.172930] pfe_ctrl_exit
[ 1084.175584] timer_del 83661960
[ 1084.178695] timer_del 836619c0
[ 1084.181778] timer_del 836619a8
[ 1084.184922] timer_del 83661978
[ 1084.188006] timer_del 83661990
[ 1084.191098] timer_del 83661a38
[ 1084.194231] timer_del 83661a20
[ 1084.197314] timer_del 83661a08
[ 1084.200391] timer_del 836619f0
[ 1084.203523] timer_del 83661a50
[ 1084.211152] pfe_ctrl_timer exiting
[ 1084.222220] pfe_firmware_exit
[ 1084.225302] pfe_hif_exit
[ 1084.227875] pfe_hif_release_buffers
[ 1084.231533] pfe_hif_free_descr
[ 1084.234692] pfe_hif_lib_exit
[ 1084.237900] pfe_hw_exit
[ 1084.242202] here after:pfe_module_exit


...and system hangs.

[fvdw]

Finally some succes :-D

Console output looks good, lets see if we can activate telnet and/or ssh

For telnet this command should do it

Code: Select all

/sbin/telnetd

For ssh it depends which daemon is available
T

[fvdw]

The single bay wd nas you mention with newer kernel is a wd mycloud home. Has a different cpu then the wd mycloud.
This wd mycloud is the only one with this mindspeed comcerto cpu of which there is no support in mainline linux kernel

[fvdw]

Is the p10rootfs still in the root file system. If yes you could try the chroot command

[matt_max]

Finally some succes :-D

Console output looks good, lets see if we can activate telnet and/or ssh

For telnet this command should do it

Code: Select all

/sbin/telnetd

For ssh it depends which daemon is available
T

There is no telnetd in /sbin/ folder. I cannot find it anywhere.
sshd is present in /usr/sbin/ and I can start it and then I was able to login thru the ssh.

Code: Select all

login as: root
root@192.168.1.233's password:
Linux WDMyCloud 3.2.68 #22 SMP Sat Nov 28 13:38:43 UTC 2015 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Aug 25 19:15:05 2022
WDMyCloud:~# whereis telnetd
telnetd:
WDMyCloud:~# whereis sshd
sshd: /usr/sbin/sshd
WDMyCloud:~#


[fvdw]

What password has user root?

[matt_max]

What passwordvhas user root?

When I first set up original wd system I've change root password to my own (giveit2me). Now it is still the same.

[fvdw]

Now that you have ssh access you could use a program like winscp to acces file system and transfer files.

[matt_max]

Now that you have ssh access you could use a program like winscp to acces file system and transfer files.

That is correct. I've got full access to system right now. Because samba is working I can open shared folders under Windows etc.

[fvdw]

Did you try the chroot command?