gisab/wdmc-ex2

Steps to update your Linux Kernel for WD My Cloud Ex2

wdmc-ex2's Issues

Unable to get UART working..

Hi!

I have a WD EX2 Ultra, and I need your help.

I’ve solder the uart interface but it doesn’t work. I don’t know why, but I don’t get anything when the nas boot up. I press space, 1, all the combinations available,but nothing works. I have tested the connections several times, and it seem they are fine. WIth a multi tester I see there is connectivity between the two sides, and I don’t know what else I can do to fix or figure out what is going on here.

After one week, troubleshooting with @bodhi in this thread https://forum.doozan.com/read.php?2,132015,133249,page=3#msg-133249, and seeing that it’s imposible that the WD boot with the new kernel and the ram disk without the u-boot updated, I need a dump of that partition ( /devmtd0) to flash my hand.

Could you please dump your u-boot partition? I guess it could the only chance I have to upgrade the WD to the new kernel.

Many thanks in advanced,

OMV for the WD MyCloud Home Duo

Hey i´m searching for a working Debian and OMV for the WD MyCloud Home Duo. I found a russian hack. Got it to work on one MyCloud Home Duo but now I´m currently working on a second one and i only got to the Telnet window but when I started the install script it wont boot. So I dont got ssh to work no IP adress.

If anyone knows anything please let me know. If needed I can share the current printouts of df -h and so on...

Thanks and a nice day :)

Issue with "starting kernel"

Can be deleted! Issue was about the wrong partition

does this kernel work for the WD cloud HOME?

The guide says Ex2, does this mean this does not apply to the WD cloud HOME?

booting w/initrd has overlap error

I have a gen1 (armada 370)
Error is
INITRD: 0x00a00000+0x00519000 overlaps in-use memory region - disabling initrd

Does this error have to do with the stock uboot? Uboot guides I have found are for about updating uboot on Gen2. Is this possible on Gen1?

I am trying to run lvm root on mdraid but afaik the the only way is activating in initrd before booting the kernel.

Marvell>> ext2load ide 1:1 0x500000 /uImage-v5.10.109gs
Loading file "/uImage-v5.10.109gs" from ide device 1:1 (Linux filesystem)
4147257 bytes read
Marvell>> ext2load ide 1:1 0xa00000 /uInitrd 
Loading file "/uInitrd" from ide device 1:1 (Linux filesystem)
5341331 bytes read
Marvell>> bootm 0x500000 0xa00000
## Booting image at 00500000 ...
## Booting kernel from Legacy Image at 00500000 ...
   Image Name:   v5.10-github.com/gisab/WDMC-Ex2
   Created:      2022-04-03  10:54:59 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4147193 Bytes = 4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 00a00000 ...
   Image Name:   Custom initramfs
   Created:      2023-05-28  23:11:36 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    5341267 Bytes = 5.1 MiB
   Load Address: 00e00000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

DTB:0x003F8DB0 (0x00003A49)
C:0x000080C0-0x003FC8C0->0x00D7AE00-0x0116F600
DTB:0x0116BAF0 (0x00003AFA)
Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0x0
Linux version 5.10.109 (pi@rpi6) (arm-linux-gnueabihf-gcc (Raspbian 10.2.1-6+rpi1) 10.2.1 20210110, GNU ld (GNU Binutil2
CPU: ARMv7 Processor [561f5811] revision 1 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
OF: fdt: Machine model: WD MyCloud Mirror
Memory policy: Data cache writeback
INITRD: 0x00a00000+0x00519000 overlaps in-use memory region - disabling initrd
<remaining output purposely omitted>