Would fwtablectl work on the My Cloud Home Duo?
Hi @Redah, I have not tested on the Home Duo but should work. Make a backup of the fwtable and keep a USB recovery handy before you edit the fwtable on disk. If I recall correctly, it is on the eMMC.
I’m finding that the hdd sounds as if it’s spun down and almost immediately spinning back up.
it happens frequently every 6mins sometimes.
hdparm is saying advanced power management is disabled.
Guessing that’s going to cause excess wear on the disk.
Any solutions?
(Using Buster without OMV. Stock kernel.)
Hey,
I successfully installed this but all my previously loaded data seems to be in a directory, in an unknown format. How can I get that back or read it?
Hi guys,
Thanks for all these efforts, I bought WD MCH in the last year December 2019. Is there any different step I need to follow? I think I’ve broken my device in this process. Steps I followed were
- Created new non- bootable USB stick using rufus
- Copied all the folders from uploaded archive @Western1
- Used reboot key(config button) on the first to install from USB as mentioned in @ematta post
No luck, I have continuously blinking white light on my device.
My question is
- how to make correct USB key?
- how to maintain folder structure? copy the folder as is or there is any other way?
- Would it be possible to install Debian with current state of MCH device?
1 Like
@AbuG I only have Samba, MPD, and Icecast2 running and my disk actually sleeps for the better part of the day.
You should put most of your /var directories on a Ramdisk (e.g. using folder2ram).
Check lsof for any activity in your /var partition.
I have boot loop issue too, is there a solution for it? @AbuG, did you solve it?
Best regards
Andrew
@andrew01 Yes I did thanks. Alex-N kindly posted his files so I compared mine to his. The problem was due to some symlinks between the files /root /usr and /var. I removed the symlink and copied the corresponding directory from my other file.
I think it was “/bin and /sbin” in the root that I removed symlink and replaced with the /usr/bin and /usr/sbin respectively there was also a third symlink that I replaced but I can’t remember which. I think it was linked to /var/…
Edit: also when making the tar files for /usr and /var make them inside the actually directory otherwise it creates a top directory which you want to avoid… So when installing it becomes /var/var/ & /usr/usr i think this is the most important point that leads to the boot loops. Because the symlinks should work in theory.
cd /new/var
tar cfz /srv/dev-sataa24/21-var.tar.gz *
cd /new/usr
tar cfz /srv/dev-sataa24/22-usr.tar.gz *
@Alex-N Many thanks for your help. I installed folder2ram and used a script that they described on their GitHub to see what’s been running when idle.
@AbuG - thank you very much.
I connected MCH using UART and I saw following error:
/sbin/init: error while loading shared libraries: libseccomp.so.2: cannot open shared object file: No such file or directory
So I just corrected the var and usr files as you wrote and that did the trick 
Now I can login by serial console and ssh (after allowing root to ssh login).
Thanks a lot
Best regards
Andrew
Yes, I found it. Problem was that I couldn’t load the nfs module. I flashed the kernel one more time, set fwtable again then couple of restarts and it just started to work. Thanks a lot one more time for your work with MCH 
Best regards
Andrew
1 Like
Can we do something to avoid errors related to wrong hardware clock? In the syslog the time always start with Feb 14 11:12:19 (2019) and switch to current date:
Feb 14 11:12:19 wdnas systemd[1]: Started The PHP 7.3 FastCGI Process Manager.
Feb 14 11:12:20 wdnas proftpd[2832]: 192.168.2.215 - ProFTPD 1.3.6 (stable) (built Tue Mar 10 2020 23:03:08 UTC) standalone mode STARTUP
Feb 14 11:12:20 wdnas proftpd[2756]: Starting ftp server: proftpd.
Feb 14 11:12:20 wdnas systemd[1]: Started LSB: Starts ProFTPD daemon.
Sep 26 17:14:59 wdnas chronyd[2723]: Selected source 188.165.17.91
Sep 26 17:14:59 wdnas kernel: [ 27.260200] systemd-journal[1301]: syscall 291
Sep 26 17:14:59 wdnas kernel: [ 27.264809] Code: aa0403f4 d2802468 a9025bf5 d4000001 (b140041f)
Sep 26 17:14:59 wdnas kernel: [ 27.271074] CPU: 1 PID: 1301 Comm: systemd-journal Not tainted 4.1.17 #9
That behavior is causing some problems:
Feb 14 11:12:10 wdnas systemd[1]: phpsessionclean.timer: Not using persistent file timestamp Sat 2020-09-26 16:09:04 CEST as it is in the future.
Feb 14 11:12:10 wdnas systemd[1]: Started Clean PHP session files every 30 mins.
Feb 14 11:12:10 wdnas systemd[1]: logrotate.timer: Not using persistent file timestamp Sat 2020-09-26 10:46:52 CEST as it is in the future.
Feb 14 11:12:10 wdnas systemd[1]: Started Daily rotation of log files.
Feb 14 11:12:10 wdnas systemd[1]: fstrim.timer: Not using persistent file timestamp Sat 2020-09-26 10:46:52 CEST as it is in the future.
Feb 14 11:12:10 wdnas systemd[1]: Started Discard unused blocks once a week.
Feb 14 11:12:10 wdnas systemd[1]: Listening on D-Bus System Message Bus Socket.
Feb 14 11:12:10 wdnas systemd[1]: anacron.timer: Not using persistent file timestamp Thu 2019-02-14 11:30:15 CET as it is in the future.
Feb 14 11:12:10 wdnas systemd[1]: Started Trigger anacron every hour.
Feb 14 11:12:10 wdnas systemd[1]: apt-daily.timer: Not using persistent file timestamp Sat 2020-09-26 10:46:52 CEST as it is in the future.
Feb 14 11:12:10 wdnas systemd[1]: Started Daily apt download activities.
Feb 14 11:12:10 wdnas systemd[1]: apt-daily-upgrade.timer: Not using persistent file timestamp Sat 2020-09-26 10:46:52 CEST as it is in the future.
Feb 14 11:12:10 wdnas systemd[1]: Started Daily apt upgrade and clean activities.
Feb 14 11:12:12 wdnas systemd-fsck[2198]: /dev/sataa24: Superblock last write time (Sat Sep 26 17:57:59 2020,
Feb 14 11:12:12 wdnas systemd-fsck[2198]: #011now = Thu Feb 14 11:12:06 2019) is in the future.
Feb 14 11:12:12 wdnas systemd-fsck[2198]: FIXED.
In other topic I found that RTC was added in MC gen 2 but without the battery, and maybe in MCH is the same. Strange is that RTC clock reset also at reboot while MCH is still powered.
Or maybe I shouldn’t care about it?
Best regards
Andrew
Edit: I installed fake-hwclock and it is ok now.
I disabled a lot of verbose logging in the RTC kernel module and was already wondering about how to properly write back the correct time…
Not having a battery backup explains a lot (I didn’t dare to open my case - yet)
Can someone link debian buster (clean or omv) for WD My Cloud Home single bay please?
have a look at Post #114 
Just place these files in the /omv directory on your USB stick
2 Likes
Hello folks,
yesterday I have tried the current images by the Russian website.
1st I tried it with an outdated 320GB SATA drive, which worked. OMV screen appeared.
After that I put in a 14TB drive, WD Elements was opened for that, and repeated the procedure. The MCH behaves the same (light flashing 20 seconds and so on) but the drive won‘t show up in the router settings and isn‘t accessible from browser/ssh.
When plugging the drive back into a Windows PC by usb, there are many, many partitions on, so the MCH least could format the 14TB drive.
Did I miss something?
Hello guys,
so if i want to install the original image of my mycloud home single disk. Maybe we can start a guide about how to restore the original firmware back on the nas. My second question is the speed of debian and omv. How fast can you write data on the nas?
Thanks
Going back to the original image should be fairly easy. If I read cmd_boot.c correctly, setting bootConfig to 5:F:0:; should put the device into BOOT_STATE_RECOVERY which will do a OTA_Update after having booted from the Golden image.
I haven’t tried this myself for obvious reasons 
Regarding the read/write speed, I get wire speed (102MB/s) using Samba and Win10.
Doing rsync onto another MCH I get an average of 60MB/s on regular sized files.
Thank you for your answer. I am a beginner in this topic. How do i change the bootConfig on my wd mycloud. I installed debian on a new drive without the original firmware. I want to try the original firmware. Thank you
I am confused, how did you install Debian on the drive? How did you get the bootloader to pickup the correct partitions?
