Alternative Firmware (Debian Jessie, Synology DSM6)

zorro3210 · January 13, 2017, 10:44pm

Hello nice threads
I have a miror gen1 and I have seen on your GDrive an app Debian (WDMyCloudMirror_Debian_8.0-1.bin file).
What is it?
What is the use of it?
thanks

zorro3210 · January 13, 2017, 11:06pm

I would like also install DSM but I do not get so well the step to install (info.txt)

EN:

Install wdfw-boot-to-dsm6-7321-test from WebGUI or Recovery.
Wait ~5 min and connect to WDMC again (IP and MAC will changed!)
Chose “Manual install”, use dsm6-7321-test.pat for installation (Not online method!!!)
I guess it is wdfw-boot-to-dsm6-8xxx? How do you do it from WebGUI (it is the webconsole?)
I guess it is now DSM-wdmc-mirror-8451.pat.

Fox_exe · January 14, 2017, 7:32am

Old info. “Press [1] to stop autoboot” - correct.

Its chrooted debian jessie. Use it for install any software inside. (Note: our arch is “armhf”, not i686)
wdfw-boot-to-dsm6-8xxx - Its WD Firmware file. Use it in “Upgrade firmware” tab in WD web-gui.
After reboot you can see DSM installer (web interface). Follow instructions and install .pat.

KGreator · January 14, 2017, 8:31am

updated the guide, thanks for reminding！

zorro3210 · January 14, 2017, 10:37am

Thanks
I will see it how this web interface by going to https://192/168…?

I should do this upgrade with my 2 discs in? or better to remove them?
If I remove them when I put them back they will be formated?

thanks for your help

Q-Fireball · January 14, 2017, 1:49pm

Thank you very much, such guides should be needed for every WD model and maybe Fox_exe could host it on his Gdrive?!

@KGreator
Is the exact ip 192.168.8.1 needed or could it be any ip?

@Fox_exe
Now I understand that “s**t” WD produced with WD Mirror Gen2. Can you modify the firmware/bootloader to change the bootorder?!

Fox_exe · January 14, 2017, 1:56pm

We can edit uboot env data from OS (Need u-boot-tools package).
Then - just change bootcmd var to something like “boot_order tftp usb hdd nand”.

Q-Fireball · January 14, 2017, 2:37pm

Can this also been done from running debian-app chroot env?

Fox_exe · January 14, 2017, 3:04pm

Yes, its possible from chroot. (Inside chroot - /dev already mounted, so we have access to all hardware)

KGreator · January 14, 2017, 6:37pm

Hi there!

As what I did before, I used Wireshark to capture the ARP packages and found the IP of MCM2 is that[quote=“KGreator, post:217, topic:156551”]
I used Wireshark to find out what does the network do today and just like this
[/quote]

But Im not sure if that IP is the exact one, you can use Wireshark to find it out. (Click here to download)

Remember to make your MCM2 and your PC IP are in the same subnet.

Good luck!

Umidare · January 17, 2017, 11:25am

I successfully installed DSM6 on my MCM2
So far so good, I even setup Surveillance Station

As @Fox_exe, @Q-Fireball and some other people mentioned
Power LED constantly blinking and Fan speed at 100% all the time

I stumbled upon this fan-daemon.py and using that as a reference, I ssh-ed and did the following:

root@WDMCMirrorG2:~# python
Python 2.7.12 (default, Aug 17 2016, 05:17:04) 
[GCC 4.9.3 20150311 (prerelease)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import serial
>>> port = serial.Serial("/dev/ttyS1", 19200, 8, "N", 1, 0.1)
>>> data = "\xfa\x02\x00\x00\x00\x00\xfb"
>>> port.write(data)
7
>>> 
Broadcast message from root@WDMCMirrorG2
	(unknown) at 17:31 ...

The system is going down for power off NOW!
Connection to 192.168.0.2 closed by remote host.
Connection to 192.168.0.2 closed.

The fan did went off but so does my device. Lol
Strangely the LEDs are still lit without any changes

Any idea why and how did this happened?

Fox_exe · January 17, 2017, 6:08pm

https://ftp.anionix.ru/WDMyCloud/Other/Weltrend_MCU/
For testing and research.
Commands seems like different (Not same as in WDMC Gen2 or DLink DNS320l)

Umidare · January 17, 2017, 7:20pm

I haven’t setup build-essentials so I’m using the precompiled test

root@WDMCMirrorG2:~$ uname -a
Linux WDMCMirrorG2 3.10.35 #1 SMP Thu Jan 12 21:52:33 +05 2017 armv7l GNU/Linux synology_armada38x_ds216

Still got device shutdown everytime

root@WDMCMirrorG2:~$ ./test 2 1 0 0 0
>>: fa 02 01 00 00 00 fb
<<: fa 02 01 00 00 21 fb
root@WDMCMirrorG2:~$ 
Broadcast message from root@WDMCMirrorG2
	(unknown) at 1:53 ...

The system is going down for power off NOW!

Found a way to “cheat” it by running init 2

root@WDMCMirrorG2:~$ ./test 2 0 0 0 0 && init 2
>>: fa 02 00 00 00 00 fb
<<: fa 30 00 00 00 00 fb
root@WDMCMirrorG2:~$ ./test 3 6 1 0 1 && init 2
>>: fa 03 06 01 00 01 fb
<<: fa 30 00 00 00 00 fb
root@WDMCMirrorG2:~$ ./test 3 1 0 0 0 && init 2
>>: fa 03 01 00 00 00 fb
<<: fa 30 00 00 00 fb
root@WDMCMirrorG2:~$ ./test 2 0 20 0 0 && init 2
>>: fa 02 00 20 00 00 fb
<<: fa 30 00 00 00 fb
root@WDMCMirrorG2:~$ ./test 2 0 35 0 0 && init 2
>>: fa 02 00 35 00 00 fb
<<: fa 30 00 00 00 00 fb
root@WDMCMirrorG2:~$ ./test 2 0 40 0 0 && init 2
>>: fa 02 00 40 00 00 fb
<<: fa 00 00 00 00 fb
root@WDMCMirrorG2:~$
Broadcast message from root@WDMCMirrorG2
    (unknown) at 2:08 ...

The system is going down for power off NOW!

Seems like I ran the latter commands to fast and the device went shutdown

I’ll setup build-essentials tomorrow and compile the test tool and do some more testing
Thank you for your efforts!

EDIT: -Additional info-
I wasn’t on the latest firmware version when I flashed MCMG2 to DSM
I was on WD firmware version 2.11.140 (03/29/2016) if I’m not mistaken

Fox_exe · January 17, 2017, 7:27pm

Strange thing…
Maybe DSM “listen” /dev/ttyS1 for respond from Synology MCU (“Synobios”), but got wrong command and recognize it as Hardware error (And going to shutdown for prevent future hardware damage).
But i disabled MCU everywhere where i find it (Include Synobios).

BTW: anything in dmesg or other logs?

Umidare · January 17, 2017, 7:45pm

complete dmesg

Unfortunately the logs might not help much
dmesg was flooded with mvEthPhyRegRead: SMI busy timeout
So I used the following
root@WDMCMirrorG2:~# tail -f /var/log/{messages,kern.log,dmesg,syslog.log} | grep -v SMI

Results are

==> /var/log/syslog.log <==
1970-01-01T07:00:23+07:00 WDMCMirrorG2 syslog-ng[1057]: Referenced filter rule not found in filter() expression; rule='f_synodr_replica_programs'
1970-01-01T07:00:23+07:00 WDMCMirrorG2 syslog-ng[1057]: Configuration reload request received, reloading configuration;
2017-01-17T22:41:26+07:00 WDMCMirrorG2 syslog-ng[1057]: syslog-ng shutting down; version='3.5.5'
1970-01-01T07:00:18+07:00 WDMCMirrorG2 syslog-ng[1064]: syslog-ng starting up; version='3.5.5'
1970-01-01T07:00:23+07:00 WDMCMirrorG2 syslog-ng[1064]: Referenced filter rule not found in filter() expression; rule='f_synodr_replica_programs'
1970-01-01T07:00:23+07:00 WDMCMirrorG2 syslog-ng[1064]: Configuration reload request received, reloading configuration;
2017-01-17T23:04:33+07:00 WDMCMirrorG2 syslog-ng[1064]: syslog-ng shutting down; version='3.5.5'
1970-01-01T07:00:18+07:00 WDMCMirrorG2 syslog-ng[1061]: syslog-ng starting up; version='3.5.5'
1970-01-01T07:00:23+07:00 WDMCMirrorG2 syslog-ng[1061]: Referenced filter rule not found in filter() expression; rule='f_synodr_replica_programs'
1970-01-01T07:00:23+07:00 WDMCMirrorG2 syslog-ng[1061]: Configuration reload request received, reloading configuration;

==> /var/log/messages <==
2017-01-17T23:18:43+07:00 WDMCMirrorG2 synopoweroff: system_sys_init.c:90 synopoweroff: System is going to poweroff

Broadcast message from root@WDMCMirrorG2
	(unknown) at 23:18 ...

The system is going down for power off NOW!
2017-01-17T23:18:44+07:00 WDMCMirrorG2 [  814.777938] init: synonetd main process (1731) killed by TERM signal
2017-01-17T23:18:44+07:00 WDMCMirrorG2 [  814.796173] init: synostoraged main process (4547) terminated with status 15
2017-01-17T23:18:44+07:00 WDMCMirrorG2 [  814.815906] init: hotplugd main process (5372) killed by TERM signal
2017-01-17T23:18:44+07:00 WDMCMirrorG2 [  814.841643] init: smbd main process (6321) killed by TERM signal
2017-01-17T23:18:44+07:00 WDMCMirrorG2 [  814.879211] init: synortc main process (8070) terminated with status 255
2017-01-17T23:18:44+07:00 WDMCMirrorG2 syno_poweroff_task: System is acting poweroff.
Connection to 192.168.0.2 closed by remote host.
Connection to 192.168.0.2 closed.

Any other logs I should get and post here?

-Additional info-
I wasn’t on the latest firmware version when I flashed MCMG2 to DSM
I was on WD firmware version 2.11.140 (03/29/2016) if I’m not mistaken

I also have tried a few things before posting here

/etc.defaults/synoinfo.conf

#changed yes to no
support_fan="no"
support_fan_adjust_dual_mode="no"

/usr/syno/etc.defaults/scemd.xml

#changed all action="SHUTDOWN" to "NONE"
#example:

<disk_temperature action="SHUTDOWN" fan_speed="111">61</disk_temperature>
to
<disk_temperature action="NONE" fan_speed="111">61</disk_temperature>

Umidare · January 17, 2017, 7:53pm

-Additional info-

Before running test

root@WDMCMirrorG2:~# stty -F /dev/ttyS0
speed 115200 baud; line = 0;
kill = ^X; min = 1; time = 0;
-brkint -icrnl -imaxbel
-isig -icanon -iexten -echo -echoe -echok -echoctl -echoke
root@WDMCMirrorG2:~# stty < /dev/ttyS1
speed 0 baud; line = 0;
min = 0; time = 0;
-brkint -icrnl -imaxbel
-opost -onlcr
-isig -icanon -iexten -echo -echoe -echok -echoctl -echoke

After running test

root@WDMCMirrorG2:~# stty < /dev/ttyS0
speed 115200 baud; line = 0;
kill = ^X; min = 1; time = 0;
-brkint -icrnl -imaxbel
-isig -icanon -iexten -echo -echoe -echok -echoctl -echoke
root@WDMCMirrorG2:~# stty < /dev/ttyS1
speed 19200 baud; line = 0;
min = 0; time = 5;
-brkint -imaxbel
-opost -onlcr
-isig -icanon -iexten -echo -echoe -echok -echoctl -echoke

rdelpopolo · January 18, 2017, 11:28am

Serial connection without dissembly? http://forum.doozan.com/file.php?2,file=928,filename=WDMCMG2_board_bottom_ser_small.jpg
Someone suggest to use a sata cable. I tried myself and the plug needs to be forced.

Restore procedure without serial cable? WD MyCloud Mirror Gen2 (BWVZ, GrandTeton)

Finally, based on your experience, what’s better between openmediavault and dsm regarding gui, cloud functionality, expandability and desktop apps?

Cricket-RJ · January 19, 2017, 1:00am

Noob question…

I’m not getting lucky connecting with putty. Managed to solder the UART cable, looking good. But what type of connection should I use with Putty? Telnet, SSH or Serial? If Telnet or SSH, what IP and port should I use? If serial, I’ve tried to use the same COM port assigned to my USB FTDI and changed speed to 115200 (also set parity and stuff on windows properties). I’ve tried swaping RX and TX on UART also…

Putty keep blank no matter what I do…

What am I doing wrong?

KGreator · January 19, 2017, 5:39am

Hi there!

I got you.@Cricket-RJ
Use Serial, COM port properties set as default except speed just like this

Then press open and apply power of MCM2.

I just used three cable of all those,TX、RX and GND, no need others.

What kind of UART moudle do you have, what is its main-chip, by the way?

Cricket-RJ · January 19, 2017, 10:29am

Thx, mate!

I was doing the serial the right way so. But absolutely nothing appeared. So I’ve double checked the wiring from MCM2 to UART (FT232RL), when some weird ASCII chars started showing.

So I have 3 guesses:

Bad soldering (probably this one)
Bad UART
Bad MCM2

I’ll try the SATA cable today…