fvdw-sl on WD My Cloud

[matt_max]

Did you try the chroot command?

Now is working:

Code: Select all

WDMyCloud:/# chroot /chroot /etc/init.d/rcS
start rcS base wdcloud p10
mount proc
remount root file system rw
mount: mounting /dev/root on / failed: Invalid argument
mount sysfs
start boot log
no boot partition sda1 or sda2 defined cannot load firmware
prepare telnet access
start telnet
------------------------
rcS-wdcloud base finished
------------------------
 list p10 boot.log file
start boot log
no boot partition sda1 or sda2 defined cannot load firmware
prepare telnet access
start telnet
rcS-wdcloud base finished
WDMyCloud:/#


Now I can connect using telnet:

Code: Select all

WDMyCloud login: root
Password:
root@WDMyCloud p5:/ # ls
bin          fvdw-chroot  mnt          p6           root         var
boot         lacie-boot   p1           p7           sbin         www
boot.log     lib          p10          p8           sys
dev          linuxrc      p4           p9           tmp
etc          lost+found   p5           proc         usr
root@WDMyCloud p5:/ #


[fvdw]

:punk alright, so now we can continue because when you connect via the telnet server launched by chrooted sytem you actually use basic fvdw-sl linux system.

What will be next.
To make fvdw-sl possible we are going to change partition scheme of the disk. I will sent later this evening the proposed table.
It seems that the boot process does not change contents of partitions 5 and 8 So we will take the risk to use as well partitons1,2,3,5, 8 and 10
Partition 10 will get a basic fvdw-sl linux system that will start fvdw-sl chrooted from sda1 or sda2.
Sda3 will be swap, sda5 will contain fvdw-sl database, sda6 wiil contain kernel, sda7 will contain barebox env, sda8 will be used as data partition, sda9 will be partition that might be used iso sda5, sda10 will contain raid1 assembled as /dev/md0 so barebox will autodetect it and load it.

This is a first setup to see if fvd-sl runs on this device. Later we might change partition table to minimize risk of batebox iverwriting partitions. With as first trial proposed table we have almost no change to made in the firmware

To be continued...

[matt_max]

:punk alright, so now we can continue because when you connect via the telnet server launched by chrooted sytem you actually use basic fvdw-sl linux system.

What will be next.
To make fvdw-sl possible we are going to change partition scheme of the disk. I will sent later this evening the proposed table.
It seems that the boot process does not change contents of partitions 5 and 8 So we will take the risk to use as well partitons1,2,3,5, 8 and 10
Partition 10 will get a basic fvdw-sl linux system that will start fvdw-sl chrooted from sda1 or sda2.
Sda3 will be swap, sda5 will contain fvdw-sl database, sda6 wiil contain kernel, sda7 will contain barebox env, sda8 will be used as data partition, sda9 will be partition that might be used iso sda5, sda10 will contain raid1 assembled as /dev/md0 so barebox will autodetect it and load it.

This is a first setup to see if fvd-sl runs on this device. Later we might change partition table to minimize risk of batebox iverwriting partitions. With as first trial proposed table we have almost no change to made in the firmware

To be continued...

I'm ready when you are :applause

[fvdw]

One thing to be figured out is how the wd firmware brings the ethernet interface online. That will be needed to be added in sda10 linux system. Maybe you can try to figure that out

[fvdw]

sorry to keep you waitng but I had some unexpected visitors, tomorrow is my wifes birthday so I proceed on Saturday

[matt_max]

No worries. I'm going to visit my parents so I'll be back on Sunday.

[fvdw]

before we are ging to setup a new partition table lets test the basic fvdw-sl rootfs
Attached an updated version. Added are the kernel modles for the debian kernel and an instruction to add ethernet kernel module and bring up ethernet interface eth0 and adding manually ip 192.168.1.200
To be extracted in root (/) of current /dev/md0.
Before extracting the archive remove all existing files from /dev/md0 so the wd file system and old p10rootfs.

After extracting new p10rootfs.tar.gz put the disk in the wd mycloud and see if it boots and enables telnet and that you can access it using telnet client
Note we don't use chroot in this case but fvdw-sl init that will run /etc/init.d/rcS automatically

[matt_max]

I'm not convinced it will work. There is no /etc/mdadm.conf so I think that array cannot be assembled.
Here we go - output from console.

P.S. Ok. md0 was assembled but network cannot be started:

Code: Select all

~ # ip link set eth0 up
ip: SIOCGIFFLAGS: No such device
~ # ifup eth0
ifup: can't open '/etc/network/interfaces': No such file or directory
~ #


[fvdw]

looks promising need to find out how to bring up eth0
You could try before using ifup to create directory /etc/network and /etc/network/interfaces

Can you also post output of this command

Code: Select all

ls -al /sys/class/net


If in there is a file with name eth0 also output of this

Code: Select all

cat /sys/class/net/eth0/operstate

[fvdw]

think it goes wrong here, with p10rootfs when loading pfe module

Code: Select all

<snip>
[   71.192395] pfe_firmware_init: request firmware class_c2000.elf failed
[   71.198962] pfe_hif_exit
[   71.201525] pfe_hif_release_buffers
[   71.205202] pfe_hif_free_descr
[   71.208290] pfe_hif_lib_exit
[   71.211359] pfe_hw_exit
[   71.215030] pfe: probe of pfe.0 failed with error -110
[   71.220746] initcall pfe_module_init+0x0/0x1f [pfe] returned 0 after 59128626 usecs

with wd rootfs we see this

Code: Select all

[   41.516506] pfe_firmware_init: class firmware loaded 0xbc0 0xc3010000
[   41.522991] pfe_load_elf
[   41.527698] pfe_firmware_init: tmu firmware loaded 0x1a0
[   41.533049] pfe_load_elf
[   41.538214] pfe_firmware_init: util firmware loaded 0x1220
[   41.543933] pfe_ctrl_init
[   41.576006] timer_add 83661a50
[   41.579095] timer_add 836619f0
[   41.582167] timer_add 83661a20
[   41.585244] timer_add 83661990
[   41.588316] timer_add 83661978
[   41.591417] timer_add 836619a8
[   42.619101] pe_sync_stop: timeout, 3f 0
[   43.649097] pe_sync_stop: timeout, 3f 0
[   44.679102] pe_sync_stop: timeout, 3f 0
[   45.709098] pe_sync_stop: timeout, 3f 0
[   45.712959] Error updating ICC tables
[   45.716650] timer_add 836619c0
[   45.719742] ipsec_common_hard_init ipsec_baseaddr:90a00000 - espah_base:90a00000
[   45.728545] timer_add 83661960
[   45.731640] pfe_ctrl_init finished
[   45.735062] pfe_eth_init
[   45.738156] pfe_ctrl_timer
[   45.749270] Comcerto MDIO Bus: probed
[   46.779099] pe_sync_stop: timeout, 3f 0
[   46.785328] pfe_eth_init_one: preallocating rx & tx queue buffers
[   46.791745] eth0: pfe_eth_init_one: created interface, baseaddr: 93200000
[   46.798579] pfe_pcap_init
[   46.801768] initcall pfe_module_init+0x0/0x1f [pfe] returned 0 after 5539980 use

so it seems our problem is failing loading of firmware that this module need