Install Debian on WD My Cloud home

Debian 12 and Gentoo for MCH\MCHD.

这个文件需要怎么下载下来,然后怎么使用呢?我是小白,非常感谢您的帮助

你好,请问你找到分区文件了吗

你好,您发的链接里面是2t的分区文件,然而我的设备是4t的,请问可以一样的用吗

Hey
I have mycloud home(single) with new 2tb hdd. I’m trying back to original firmware and i have fail.

I downloaded MyCloudHome_Original_9.5.1-104_v1.1 and copy to flash drive. Booted from flash and type restore-wd.sh for this moment everything was fine.

When i type reboot -f device rebooot and start flashing led.

When i connected to serial i had got:

*** Reboot-Action invalid ***
Hit Esc or Tab key to enter console mode or rescue linux: 0
------------can’t find tmp/factory/recovery
======== Checking into android recovery ====

AHCI 0001.0301 32 slots 2 ports ? Gbps 0x3 impl SATA mode
flags: ncq pm led clo only pmp pio slum part
No port device detected!
Error, SATA device initialization failed!
bootr - boot realtek platform

Usage:
bootr [u/uz]
u - boot from usb
uz - boot from usb (use lzma image)
m - read fw from flash but boot manually (go all)

Enter console mode, disable watchdog …

Realtek>

When im type bootr m i had got:

[Info] getting gpt_ver env and gpt version = 3
** Partition 18 not valid on device 0 **

** Unable to use sata 0:18 for fatload **
wd_read_boot_config: Error, File bootConfig does not exist, exit

[ERROR]: Unknown bootState(6), boot CBR
[FATAL ERROR] CBR not found, boot USB rescue mode.
** Partition 18 not valid on device 0 **

** Unable to use sata 0:18 for fatwrite **
wd_write_boot_config: File bootConfig does not exist, run “wdpp set” command manually
==== boot_rescue_from_usb =====
(Re)start USB…
USB0: USB EHCI 1.00
scanning bus 0 for devices… 1 USB Device(s) found
USB1: USB XHCI 1.10
scanning bus 1 for devices… Unknown request , typeReq = 0x200c
2 USB Device(s) found
USB2: USB XHCI 1.10
scanning bus 2 for devices… Unknown request , typeReq = 0x200c
1 USB Device(s) found
scanning usb for storage devices… Enter is_pmbr_valid
Warning: failed to 0xEE type in MBR
1 Storage Device(s) found

1: Hub, USB Revision 2.0

  • u-boot EHCI Host Controller
  • Class: Hub
  • PacketSize: 64 Configurations: 1
  • Vendor: 0x0000 Product 0x0000 Version 1.0
    Configuration: 1
    • Interfaces: 1 Self Powered 0mA
      Interface: 0
      • Alternate Setting 0, Endpoints: 1
      • Class Hub
      • Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

2: Hub, USB Revision 3.0

  • u-boot XHCI Host Controller
  • Class: Hub
  • PacketSize: 9 Configurations: 1
  • Vendor: 0x0000 Product 0x0000 Version 1.0
    Configuration: 1
    • Interfaces: 1 Self Powered 0mA
      Interface: 0
      • Alternate Setting 0, Endpoints: 1
      • Class Hub
      • Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

3: Mass Storage, USB Revision 2.10

  • SanDisk Ultra 4C530001151204118151
  • Class: (from Interface) Mass Storage
  • PacketSize: 64 Configurations: 1
  • Vendor: 0x0781 Product 0x5581 Version 1.0
    Configuration: 1
    • Interfaces: 1 Bus Powered 224mA
      Interface: 0
      • Alternate Setting 0, Endpoints: 2
      • Class Mass Storage, Transp. SCSI, Bulk only
      • Endpoint 1 In Bulk MaxPacket 512
      • Endpoint 2 Out Bulk MaxPacket 512

4: Hub, USB Revision 3.0

  • u-boot XHCI Host Controller
  • Class: Hub
  • PacketSize: 9 Configurations: 1
  • Vendor: 0x0000 Product 0x0000 Version 1.0
    Configuration: 1
    • Interfaces: 1 Self Powered 0mA
      Interface: 0
      • Alternate Setting 0, Endpoints: 1
      • Class Hub
      • Endpoint 1 In Interrupt MaxPacket 8 Interval 255ms

USB device 0: Vendor: SanDisk Rev: 1.00 Prod: Ultra
Type: Removable Hard Disk
Capacity: 29328.0 MB = 28.6 GB (60063744 x 512)
reading wd_uboot.bin

** Unable to read “wd_uboot.bin” from usb 0:1 **
Loading “wd_uboot.bin” from USB failed. Continue installing OS images
reading rescue.sata.dtb
Filesize: 46818 bytes
46818 bytes
Size: 46818, got: 46818

46818 bytes read (take 40ms)
Loading “rescue.sata.dtb” to 0x01F00000 is OK.

reading sata.uImage
Filesize: 7409861 bytes
7409861 bytes
Size: 7409861, got: 7409861

7409861 bytes read (take 273ms)
Loading “sata.uImage” to 0x03000000 is OK.

reading rescue.root.sata.cpio.gz_pad.img
Filesize: 4194304 bytes
4194304 bytes
Size: 4194304, got: 4194304

4194304 bytes read (take 169ms)
Loading “rescue.root.sata.cpio.gz_pad.img” to 0x02200000 is OK.

reading bluecore.audio

** Unable to read “bluecore.audio” from usb 0:1 **
Loading “bluecore.audio” from USB failed.
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
Info: Try to add new node /factory…


factory {
bootstate = “0”;
bna = “0”;
nbr = “F”;
ver = “4.1.4”;
ipaddr = “192.168.100.1”;
ethaddr = “00:10:20:30:40:50”;
};


EXPORT ENV AT 0x10000000, ENV size info:0x00002000,0x00001ffc,0x00000004
rtk_preload_bootimages_spi : header info
0x00000600 0x00067440 0x00010b00 0x00000000
0x00005040 0x00000000 0x00000000 0x00026360
0x00000000
rtk_preload_bootimages_spi : load U-Boot 64 from 0x8819de60 to 0x01500000 with size 0x00026360
rtk_preload_bootimages_spi : load BL31 from 0x88198e00 to 0x10120000 with size 0x00005040
copy_2nd_bootloader_and_run : src:0x01500000, dst:0x00021000, size:0x00028000
Jumping to 2nd bootloader…

U-Boot 2015.07-g5a4a178-dirty (Jun 22 2016 - 11:33:46 +0800)

CPU : Cortex-A53 Quad Core
Board: Realtek QA Board
[ERR] get_accessible_ddr_size: hw setting error. (impossible value 0x0)
[ERR] Fall back to using CONFIG_SYS_RAM_DCU1_SIZE
DRAM: 1 GiB
mapping memory 0x20000000-0x40000000 non-cached
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
rtk_plat_set_fw not port yet, use default configs
Not raw Image, Starting Decompress Image.gz…

Flattened Device Tree blob at 01f00000

Booting using the fdt blob at 0x1f00000
reserving fdt memory region: addr=0 size=100000
reserving fdt memory region: addr=1f000 size=1000
reserving fdt memory region: addr=1b00000 size=400000
reserving fdt memory region: addr=1ffe000 size=4000
reserving fdt memory region: addr=2200000 size=400000
reserving fdt memory region: addr=2600000 size=400
reserving fdt memory region: addr=2e00000 size=400
reserving fdt memory region: addr=10000000 size=14000
reserving fdt memory region: addr=12000000 size=1000000
reserving fdt memory region: addr=22000000 size=200000
Using Device Tree in place at 0000000001f00000, end 0000000001f0e6e1
Bring UP slave CPUs

Starting Kernel …

[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.330 (kman@kmachine) (gcc version 10.2.1 20210110 (Debian 10.2.1-6) ) #2 SMP PREEMPT Wed Feb 14 19:15:59 +03 2024
[ 0.000000] Boot CPU: AArch64 Processor [410fd034]
[ 0.000000] earlycon: uart8250 at MMIO32 0x0000000098007800 (options ‘’)
[ 0.000000] bootconsole [uart8250] enabled
[ 0.000000] rsvmem_remap 167, ioremap(1f000,1000)
[ 0.000000] rsvmem_remap 170, ioremap failed
[ 0.000000] rsvmem_remap 167, ioremap(1ffe000,4000)
[ 0.000000] rsvmem_remap 170, ioremap failed
[ 0.000000] rsvmem_remap 167, ioremap(98000000,200000)
[ 0.000000] rsvmem_remap 170, ioremap failed
[ 0.358068] ****** rtk_lockapi_init 649, chip: id=0x00000000, revision=0x00000a01
[ 1.510451] [RTD129x_PM] wakeup-gpio[0] States is disable![ 1.516463] (en:0 act:1 gpio:115)
[ 1.520328] [RTD129x_PM] wakeup-gpio[1] States is disable![ 1.526336] (en:0 act:0 gpio:134)
[ 1.531717] dmi: Firmware registration failed.
[ 1.540534] rtk-usb-manager 98000000.rtk_usb_power_manager: create_debug_files
[ 1.901441] rtk_i2c 98007d00.i2c: can’t get pin state, bus recovery not support
[ 1.910312] rtk_i2c 98007c00.i2c: can’t get pin state, bus recovery not support
[ 1.918902] rtk_i2c 9801b700.i2c: can’t get pin state, bus recovery not support
[ 1.927495] rtk_i2c 9801b900.i2c: can’t get pin state, bus recovery not support
[ 1.936077] rtk_i2c 9801bb00.i2c: can’t get pin state, bus recovery not support
[ 2.094762] rtk-dwc3-type_c 98013200.rtk_dwc3_drd_type_c: Error rd_ctrl-gpio no found for RTD1295
[ 2.104148] rtk-dwc3-type_c 98013200.rtk_dwc3_drd_type_c: create_debug_files
[ 2.118331] hub 2-0:1.0: config failed, hub doesn’t have any ports! (err -19)
[ 2.142777] rtk-ohci 98013400.ohci: _ohci_readl [USB Workaround] fixed force to enable ohci clock
[ 3.658044] rtk-dwc3-type_c 98013200.rtk_dwc3_drd_type_c: Connection change OK: IN host mode to attach device at cc1 (cc_status=0x3b)
[ 22.105619] rtk-rtc 9801b600.rtc: Cannot get MTD device
[ 22.154221] rtk-rtc 9801b600.rtc: Cannot get MTD device
[ 22.159596] rtk-rtc 9801b600.rtc: hctosys: unable to read the hardware clock
rm: can’t remove ‘/dev/null’: No such file or directory
[ 22.212379] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[ 22.221363] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
udhcpc: started, v1.36.1
udhcpc: executing /etc/udhcpc.script deconfig
Setting IP address 0.0.0.0 on eth0
udhcpc: entering listen mode: raw
udhcpc: broadcasting discover
udhcpc: waiting 3 seconds
udhcpc: broadcasting discover
udhcpc: waiting 3 seconds
[ 25.491316] r8169 98016000.gmac eth0: rtl_csiar_cond == 0 (loop: 100, delay: 10).
[ 25.500273] r8169 98016000.gmac eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
udhcpc: broadcasting discover
udhcpc: waiting 3 seconds
udhcpc: received offer of 192.168.55.112
udhcpc: broadcasting select for 192.168.55.112, server 192.168.55.1
udhcpc: waiting 3 seconds
udhcpc: entering listen mode: none
udhcpc: lease of 192.168.55.112 obtained from 192.168.55.1, lease time 3600
udhcpc: executing /etc/udhcpc.script bound
Setting IP address 192.168.55.112 on eth0
Deleting routers
route: SIOCDELRT: No such process
Adding router 192.168.55.1
Recreating /etc/resolv.conf
Adding DNS server 192.168.55.1
Thu Feb 1 12:00:00 UTC 2024
ntpd: setting time to 2024-06-09 11:24:20.027773 (offset +11143458.950140s)
===boot complete===
sh: can’t access tty; job control turned off
tcpsvd: listening on 0.0.0.0:21, starting
~ # [ 33.328508] start dump register from port 0
[ 33.332811] 0x10 = 0x400040
[ 33.335677] 0x14 = 0x0
[ 33.338099] 0x18 = 0x4016
[ 33.340781] 0x20 = 0x150
[ 33.343379] 0x24 = 0x101
[ 33.345977] 0x28 = 0x133
[ 33.348571] 0x2c = 0x300
[ 33.351170] 0x30 = 0x4050002
[ 33.354124] 0x34 = 0x0
[ 33.356540] 0x38 = 0x0
[ 33.358960] 0x3c = 0x0
[ 33.361379] dump register finish

I’m glad for any suggestion what doing next.

1 Like
  1. After installation, disconnect the flash drive.
  2. Try resetting to factory settings by pressing the Reset button for 60 seconds. After another ~10 minutes, try logging into the web interface.

If it doesn’t help, try restoring FW 7.15.0-160, doing a reset, wait 30 min. And then try restoring FW 9.5.1-104, doing a reset and wait 60 min.

1 Like

I am also going to saying the same process. :sweat_smile:

Thank you for your response.

I recently recovered an old Pogoplug V4 with a 16GB USB running Arch Linux and Nextcloud, but it’s very slow. I’m considering a similar setup using a WD HDD for better performance.

If there’s any way I can assist you with this project, I’d be happy to contribute my efforts.

1 Like

You can, for example, install Debian 12 + CasaOS for MCH\MCHD (my builds, link above).

1 Like

I successfully installed it, but I’m encountering issues with installing the Docker plugin. Additionally, the media files were not deleted; instead, they were moved to a backup folder in the srv directory. Has anyone managed to install the Docker plugin successfully?

1 Like

Thanks for sharing. Using WD HDD should definitely boost performance compared to the Pogoplug V4 setup. I am curious about how it turns out!