fvdw-sl on WD My Cloud

[fvdw]

/chroot/bin/busybox is killed

that is to be expected as busybox will use your shared glibc libs in /lib and they are not compatible.
You should try the chroot command. busybox must be execute when being connected to chrooted system

Code: Select all

chroot /chroot /etc/init.d/rcS

and see if that goes ok without the /bin/bash error

[matt_max]

I'm not exactly sure if it suppose to looks like this (after I do dd if=/uImage of=/dev/sda6 and to be sure dd if=/dev/zero of=/dev/sda5).

P.S. Sorry - that is not entire console output.
P.P.S. Now I not able to chroot due to stopped booting process.

Full output from console.

[fvdw]

Well the kernel seems to be running, unfortunate the beginning of kernel output is missing so I cannot check that it is my kernel. Further I need to find the setting to disable the init calls output to make kernel output shorter

[fvdw]

Well it is my kernel, confirmed by creation date

Image Name: Linux-3.2.26
Created: 2022-08-10 11:11:24

Does the system not continue after 5 minutes?

[matt_max]

That is correct:

Code: Select all

: System ready
Running version  now: Mon Aug 22 20:25:46 CEST 2022
: Check if new firmware is available
getNewFirmwareUpgrade.sh: begin script: immediate send_alert
getNewFirmwareUpgrade.sh: http://support.wdc.com/nas/list.asp?devtype=sq&devfw=04.06.00-111&devlang=eng&devsn=&auto=0&devid=*****
INIT: Id "T0" respawning too fast: disabled for 5 minutes
INIT: Id "T0" respawning too fast: disabled for 5 minutes


...and nothing is happening.

[fvdw]

I wonder why loading of firmware is different then when using the original kernel. If you hit ctr-c is then the upgrade script not aborted?

[matt_max]

I wonder why loading of firmware is different then when using the original kernel. If you hit ctr-c is then the upgrade script not aborted?

No it's not. Still INIT: Id "T0" respawning too fast: disabled for 5 minutes

[fvdw]

original kernel

Code: Select all

[info] ####################################.
[info] #                                  #.
[info] # Finalizing Application Run-Level #.
[info] #                                  #.
[info] ####################################.
[info] .
: System ready
..sending alert: 2001
Running version  now: Wed Aug 10 21:58:46 CEST 2022
: Check if new firmware is available
getNewFirmwareUpgrade.sh: begin script: immediate send_alert
getNewFirmwareUpgrade.sh: http://support.wdc.com/nas/list.asp?devtype=sq&devfw=04.06.00-111&devlang=eng&devsn=&auto=0&devid=*****
Error resolving pool.ntp.org: Name or service not known (-2)
 
ntp, new date: Wed Aug 10 21:58:55 CEST 2022
 
 
Debian GNU/Linux 7 WDMyCloud ttyS0
 
WDMyCloud login:


recompiled kernel

Code: Select all

[info] ####################################.
[info] #                                  #.
[info] # Finalizing Application Run-Level #.
[info] #                                  #.
[info] ####################################.
[info] .
: System ready
Running version  now: Mon Aug 22 20:25:46 CEST 2022
: Check if new firmware is available
getNewFirmwareUpgrade.sh: begin script: immediate send_alert
getNewFirmwareUpgrade.sh: http://support.wdc.com/nas/list.asp?devtype=sq&devfw=04.06.00-111&devlang=eng&devsn=&auto=0&devid=*****
INIT: Id "T0" respawning too fast: disabled for 5 minutes


I need to google this mesaage INIT: Id "T0" respawning too fast to see what is causing that

[fvdw]

cause seems to be /etc/inittab

In that file there is apparently a line(s) starting with "To"
disable it by putting # in front of To of that line

Probably you need to do that on your linux PC

[matt_max]

I think it is related to the lack of eth interface but who knows...

Tere is a line in inittab

Code: Select all

T0:2345:respawn:/sbin/getty -L ttyS0 115200 vt100


...so I commented it out. Now out from console looks like this. It hangs at exactly same place but without any message.