Some time ago I bought a “WD MyCloud Home” device in order to remove the hard drive and use it elsewhere. When I got hold of the mainboard again, I actually wanted to throw it away, but first I researched what else I could do with it. And not much later, I now have Debian 11+OMV+Nextcloud 26 (via Docker) running on this device with a hard drive that was left over. I used the information from the well-known Russian 4pda.to forum as a basis. I have to admit, Nextcloud doesn’t even run badly, considering that the device only has 1 GB of RAM.
Now the thing is that I also had an empty “WD MyCloud Home DUO” device lying around (from which I also removed the hard drives). I reactivated it with 2 old 300 GB drives. The latest firmware was automatically installed by Western Digital (version 9. something).
Considering that the DUO device has 8 GB of RAM and two hard drives, it is obvious to want to achieve the same goal here, which is Debian 11 + OMV6 + Docker. Here, the performance of Nextcloud should be even better.
I have done some research on this in the 4pda.to forum and here, but I am not really getting anywhere.
Do I see it correctly that the goal in this case is not as easily achievable as with the single-HD version? In the 4pda.to forum I only found information about an older Debian and OMV combination. Is there also a newer software combination that can be used in a similar way as I did with the single HD?
Can one possibly extend the normal WD firmware, which according to the changelogs is now also based on Debian, with OMV and Docker oneself?
I’ve really tried to look up the answers myself already, but I have to admit that many of the posts here are too technically sophisticated for me to follow.
Perhaps someone can give a brief summary of the current status of OMV6+Docker on the WD MyCloud Home DUO device?
Hello, I don’t know where do you get the idea that MCHD has 8 GB of ram, but you are wrong, it has 1 GB. The Duo and the single versión are exactly the same processor and ram, the differences are that the duo has an EMMC memory as the OS disk, a RTC clock and some other little things, but they are almost the same. You can install debian with forth32 installer WD My Live\Book\Cloud\Cloud Mirror - 4PDA
If you don’t understand much about linux and embedded systems, I recommend you to stay with the easier an reliable installation of forth32. If your Idea is experimenting with the NAS, I have a lot of info published in this forum, including the latest kernel compiled with my personal preferences, and a guide to recover it in case of messing up the EMMC. I’m sorry but I do not had the time or knowledge to build an “installer” for debian 11 and omv 6, i installed it with debootstrap creating a fresh installation, there are a lot of guides on the internet but you need to understand the basics about linux, if not, you can mess up your NAS.
Hey. Thank you for sharing your experience. I have been having the same issue for 2 weeks. It’s a relief to know what is causing the problem.
If you could, can you share the script you used to make partitions?
In case someone else is also interested in this, there’s a script reset_button.sh whoch you can call with argument:
- short - reboots the device
- long - hardware reset, steps down the owner to normal user, and the next user setting up will become owner, doesn't wipe data
- factory - factory reset, wipes all data
ok find it by myself…
set date and time correct and now the install process works.
I got the error Message below, how can i fix this?
root@WDMCH:~# /root/installomv6.sh
Get:1 Index of /public shaitan InRelease [12.8 kB]
Get:2 Index of /debian bullseye InRelease [116 kB]
Get:3 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB]
Get:4 Index of /debian bullseye-updates InRelease [44.1 kB]
Err:1 Index of /public shaitan InRelease
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 7E7A6C592EF35D13 NO_PUBKEY 24863F0C716B980B
Reading package lists… Done
W: GPG error: Index of /public shaitan InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 7E7A6C592EF35D13 NO_PUBKEY 24863F0C716B980B
E: The repository ‘Index of /public shaitan InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Release file for http://deb.debian.org/debian/dists/bullseye/InRelease is not valid yet (invalid for another 446d 12h 19min 39s). Updates for this repository will not be applied.
E: Release file for http://deb.debian.org/debian-security/dists/bullseye-security/InRelease is not valid yet (invalid for another 481d 3h 10min 2s). Updates for this repository will not be applied.
E: Release file for http://deb.debian.org/debian/dists/bullseye-updates/InRelease is not valid yet (invalid for another 481d 17h 47min 55s). Updates for this repository will not be applied.
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
E: Unable to locate package wget
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
E: Unable to locate package python3-psutil
mv: cannot stat ‘/usr/lib/python3/dist-packages/psutil/_pslinux.py’: No such file or directory
mv: cannot move ‘/root/_pslinux.py’ to ‘/usr/lib/python3/dist-packages/psutil/’: No such file or directory
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Package gnupg is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package ‘gnupg’ has no installation candidate
/root/installomv6.sh: 25: wget: not found
E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation
Get:1 Index of /debian bullseye InRelease [116 kB]
Get:2 Index of /public shaitan InRelease [12.8 kB]
Get:3 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB
Get:4 Index of /debian bullseye-updates InRelease [44.1 kB]
Err:2 Index of /public shaitan InRelease
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 7E7A6C592EF35D13 NO_PUBKEY 24863F0C716B980B
Reading package lists… Done
E: Release file for http://deb.debian.org/debian/dists/bullseye/InRelease is not valid yet (invalid for another 446d 12h 19min 37s). Updates for this repository will not be applied.
W: GPG error: Index of /public shaitan InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 7E7A6C592EF35D13 NO_PUBKEY 24863F0C716B980B
E: The repository ‘Index of /public shaitan InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Release file for http://deb.debian.org/debian-security/dists/bullseye-security/InRelease is not valid yet (invalid for another 481d 3h 10min 0s). Updates for this repository will not be applied.
E: Release file for http://deb.debian.org/debian/dists/bullseye-updates/InRelease is not valid yet (invalid for another 481d 17h 47min 53s). Updates for this repository will not be applied.
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
E: Unable to locate package openmediavault-keyring
E: Unable to locate package openmediavault
/root/installomv6.sh: 30: omv-confdbadm: not found
/root/installomv6.sh: 32: wget: not found
launch REBOOT
@danieldd, did you ever figure out a way to boot from USB?
I have a My Cloud Gen 1 that I restored to factory settings, but when I plug in the power with the USB stick in and the reset button pushed, the yellow light flashes once, goes solid and then eventually goes blue after the device is booted to factory settings.
In this Debian 11 firmware of the minimum configuration from August 2022, before installing the OMV, you need to set the current time with the command, for example, the current one will be like this:
ln -sf /usr/share/zoneinfo/Europe/Simferopol /etc/localtime
date --set 13/08/2023
date --set 15:00
thank you for your Answer.
But i found the solution that in must set the Date and Time before install OMV after i wrote my Post.
The installation is done and all works fine.
Hey @Alex-N , does this still work for you on 9.5.0? I’m getting connection refused. I changed the sshd start in the system_init to debug log to a file in /data/ssh, and it doesn’t seem to get any connection. feels like some kind of packet filtering, firewall.
Thanks so much for this @RAH-66. I’ve got everything working pretty much perfectly after some effort. Even have wireguard running for remote access - so it’s essentially much better than a full function MCH.
One thing I can’t get working is qBitTorrent in OMV. I have another OMV setup which I’ve tested it on and it runs correctly. On the MCH there is no data transfer - the WebUI runs but it won’t even pull metadata.
I’m assuming there’s some perms/port issue in this OMV image that’s above my knowledge level. I’ve tried every install method - portainer, docker, ssh and the issue persists.
Has anyone else had issues with this or know how I could deal with it?
Ah, here’s my favorite contributor, @RAH-66! Your being banned on 4PDA was quite a shock to me. Such a relief to see you’re still around!
As it happens, I have a couple questions for you:
Did you compile any of your kernels with CONFIG_USB_UAS enabled? As of now, even the tried and trusted JMS578-based SATA-USB bridge works in old usb-storage mode, not uas, which is a pity. I’m still using the 4.1.17 because I’m reluctant to reinstall the system with nowhere to back up the 3,5TB of my stuff. Might gather the courage (слабоумие и отвага!) to do that eventually.
Any idea why I can’t write to /sys/block/sdb/device/scsi_disk/3:0:0:0/provisioning_mode in OMV even as root (sudo su)? I tried all the tricks in the book to try and change that value from full to unmap to enable TRIM support for an SSD in the SATA-USB box mentioned above, but I failed. Setting that parameter via a rule in /etc/udev/rules.d/ worked, but I’m still perplexed by that unexplained unwriteability. Might it be a problem with OMV or something that you’re responsible for?
Oh, and your instructions to install Docker containers are really obsolete by now (but were really helpful back then) since that radical change to OMV extras’ Docker plugin that caused quite a turmoil in OMV-land.
Can you maybe enable CONFIG_USB_UAS later if you decide to compile the kernel again? Like when WD releases sources for a newer version or when you add new features to an older one?
Speaking of which, any hope for a newer kernel version?
So you’re going to recompile the kernel to enable support for USB Wi-Fi adapters? Sounds exciting! Any ideas as to what other options to enable/change while you’re at it?
My WDMCH’s resources are severely underutilized under OMV6 running only a couple Docker images, so I’m thinking of maybe experimenting with installing HomeAssistant or something.
You misunderstood my Question 2. I’ve found multiple guides on enabling TRIM (unmap) support for SSDs in Linux (including the one you linked to; Jeff’s and Mauro’s are among the best, along with this Gentoo Wiki article).
I wasn’t asking for a how-to, I was just curious why I can’t perform one specific step on my system (the system that you helped create) that other people had no problem with on their (different) systems.
Oh, by the way, TRIM support is enabled (and automated via fstrim.timer) in OMV out of the box, I only had a problem with an SSD not being properly recognized as trimmable.
Anyway, thanks for everything, and I’ll be waiting for more exciting news from you!
@RAH-66, looks like you missed my reply from 20 days ago.
I don’t want to come across as pushy, I’m just curious if you’re going to release a newer kernel any time soon. I’m itching to upgrade from the old 4.1.17, and WD has pushed so many updates over the last 18 months that your 4.9.266 may already be a bit obsolete.
Thanks again for all your work!
You might have to add a new SSHD binary as 9.5.0 is based on Bullseye.
I used this one openssh-server_8.4p1-5+deb11u2_arm64.deb and copied the binary to /data/ssh/sshd
By URL/DNS blocking updates.mycloud.com you should be safe from unwanted updates.
If you chose to update you can still run fw_update -r -v 9.5.0-186 /usr/local/upload/install.img (that is if you extracted the OTA-zip into /usr/local/upload)
That way you can switch out the modified image.cfs before doing a reboot (so you wouldn’t hhave to boot into rescue).
Your being banned on 4PDA was quite a shock to me. Such a relief to see you’re still around!
Might it be a problem with OMV or something that you’re responsible for?
