FW Versions

If you haven’t changed it, it should be:

Login: root
pwd: welc0me

Hope this info helps on determining the diffs between gen1 & gen2

root@WDMyCloud root # cat /proc/cpuinfo
processor: 0
model name: ARMv7 Processor rev 1 (v7l)
BogoMIPS: 1594.16
Features: swp half thumb fastmult vfp edsp neon vfpv3 tls
CPU implementer: 0x41
CPU architecture: 7
CPU variant: 0x4
CPU part: 0xc09
CPU revision: 1

processor: 1
model name: ARMv7 Processor rev 1 (v7l)
BogoMIPS: 1594.16
Features: swp half thumb fastmult vfp edsp neon vfpv3 tls
CPU implementer: 0x41
CPU architecture: 7
CPU variant: 0x4
CPU part: 0xc09
CPU revision: 1

Hardware: Marvell Armada 375 (Device Tree)
Revision: 0000
Serial: 0000000000000000
root@WDMyCloud root # cat /proc/meminfo
MemTotal: 514528 kB
MemFree: 101248 kB
Buffers: 5376 kB
Cached: 141728 kB
SwapCached: 17248 kB
Active: 82432 kB
Inactive: 148480 kB
Active(anon): 28224 kB
Inactive(anon): 72000 kB
Active(file): 54208 kB
Inactive(file): 76480 kB
Unevictable: 6752 kB
Mlocked: 6752 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 514528 kB
LowFree: 101248 kB
SwapTotal: 2097056 kB
SwapFree: 2051744 kB
Dirty: 192 kB
Writeback: 0 kB
AnonPages: 81568 kB
Mapped: 34208 kB
Shmem: 14144 kB
Slab: 82368 kB
SReclaimable: 46912 kB
SUnreclaim: 35456 kB
KernelStack: 1792 kB
PageTables: 16800 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 2354304 kB
Committed_AS: 561472 kB
VmallocTotal: 515072 kB
VmallocUsed: 7872 kB
VmallocChunk: 489984 kB
root@WDMyCloud root #
root@WDMyCloud root # hdparm -i /dev/sda1


Model=WDC WD40EFRX-68WT0N0, FwRev=82.00A82, SerialNo=################
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=7814037168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
AdvancedPM=no WriteCache=enabled
Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7

  • signifies the current active mode

root@WDMyCloud root # sudo ethtool eth0
Settings for eth0:
Cannot get device settings: No such device
Cannot get wake-on-lan settings: No such device
Cannot get message level: No such device
Cannot get link status: No such device
No data available

1 Like

Thanks for that. At a glance, it’s the same dual core ARM7r1, but running about 25% faster, and with twice the memory.

Looks like the Ethernet driver is called something other than eth0. Have a look in /dev to see if you can find it. I’m off to bed…

v2 firmware - is for WDMyCloud Gen2
v03 and v04 - for old WDMC (Gen1)

Gen2 have different hardware:
Gen2 vs Gen1:
Marvell armada 370 (2core, 800MHz) vs Mindspeed Comcerto C2000 (2 core, 650MHz)
512 MB Ram vs 256 MB Ram
Custom linux (Busybox) vs Debian wheezy (Mod. debian in v04 fw)
uBoot vs Barebox as bootloader

Greetings, got a Linux WDMyCloud 3.10.39 #1 SMP Sun Aug 2 12:24:50 CST 2015 2014T20p4 Build-git3e9fe59 armv7l GNU/Linux. If you # cat /etc/version, you get
2.10.310. When you login via ssh (a bit confusing) you end up in busybox. Any idea how to get to a real shell?



You already in “real shell”.
There is no OS. Just raw linux (Busybox as shell and tools + wd stuff).

Untranslatable text:
Если точнее - там внутри RamDisk (Даж не initramfs, а именно Ramdisk с Busybox’ом внутри) и целая куча костылей, которые WD гордо называют “Осью”.
Я натурально [вырезано цензурой] [был в ужасе], когда копался в этой клоаке…

1 Like

Hello Fox_exe,

Egads… I see it now… Ewwww…

Thanks for the news… I was hoping that upgrading it would suddenly fix
all my misgivings about this box, it did not. I suppose when you get to
the more expensive “big boy” models you get a real Linux…

Well on the positive side, rsync works out of the box, though I cannot see
where it comes into play - maybe WD compiled it into the kernal… But as
far as I can see rsyncd only seems to work for the root account.
Additionally you need to rehome /home/root using a symlink (ln -s) to the
big terrabyte mounted volume before it is useful…

Please tell me that they are kidding?

I picked up two of these on amazon, maybe I will try humping debian on the
other one… It is a shame that WD screwed around so much with an already
working system.

Fnially thnaks for the answer, I will try to follow your threads in this



Yeah… Good hardware, great design (Internal, hardware), but OS… Using busybox - good idea, but realisation…

*** Just my “soul scream” about this s**t ***
Что сделали WD? Грузится рамдиск, монтирует раздел с флешки в режиме ридонли, запускает с него скрипты… /etc/init.d/ игнорируется и практически никак не используется, хотя мог бы облегчить жизнь в разы.
Ещё и сетевуху переименовали в egiga… Накой фиг - совершенно неясно, но весь софт идёт лесом, т.к. 99% прог будут искать eth.
Как надо было сделать? Грузить initramfs, который проверяет разметку диска и доступность основных файлов. При необходимости запускает Recovery для восстановления и/или разметки диска. В дальнейшем - распаковывает образ системы с флешки на диск (При первом запуске), выполняет switch_root, запуская основную систему с диска.
Как вариант - монтировать сжатый образ системы с флешки, и поверх запускать unionfs, который будет сохранять изменения (конфиги) на другом разделе флешки каждые n часов и при выключении.

Но нетже - надо было сделать всё через задницу…

1 Like

It’s a NAS, not a generic Linux computer. So root is only big enough to support the services required for NAS functions, leaving the vast majority of the HDD for data storage.

If you want a cheap Linux box to play with, buy a RaspberryPi.

Amen to the Raspberry Pi - got the Pi3 with the WiFi and gosh, this is a sexy beast. I would have imagined that someone over at WD My Cloud design would have taken a look at the whole Pi phenomena and realized their software in a similar light…

So the rest of us are left - knowing what the right answer is, but also knowing that we can’t get there from here…



I wouldn’t. The MyCloud is a product, using embedded linux as a means to an endz like a huge number of other products using embedded Linux.

No. The rest of us are left with what we purchased; a NAS, and we’re happy that the HDD is partitioned to maximise the amount of space available for data storage, and the minimal amount set aside for the operating system.

If you want to convert the MyCloud into a Linux box, why not repartition the HDD?

No I’m good. The silly thing has rsyncd.

The Ethernet device name is: “egiga0”

I assume it stands for “Gigabit Ethernet dev 0”

Yeay, something like that. “eGiga” - name of a Network driver in Marvell/Armada kernel.
idk why, but WD add this “workaround” to kernel… (In Marvell sources its “eth0”).

Sometime wd software make me ■■■■ bricks…

can I install v2 on my v04 running cloud or would it fail?

No the gen1 and gen2 have different hardware.

Ok understood that but at the WD website and in the internet, I can’t find any naming called “Gen1” and “Gen2”. My product is only called Single Bay MyCloud. How can I understand the difference?

So is mine a Gen1? as it runs v0.2?

Yes, we know it’s stupid.
We told WD that not changing the name would lead to confusion.
We told them it was stupid to have later firmware with what appears to be an earlier version.

Did they listen to wise counsel? No.

Look at the firmware version in the My Cloud Dashboard or at the P/N number on the bottom on the single bay My Cloud enclosure.
1st gen = v3.x/v4/x firmware
2nd gen = v2.x firmware

1st gen P/N ends with -00
2nd gen P/N ends with -10

Yes its stupid. And yes many others have complained about this confusion in the past.

The hardware is slightly different with the 2nd gen single bay My Cloud units.