Initial OP updated with new links for new v2.x firmware along with newer GPL firmware links for v4.x and v2.x.
Linux WDMyCloud 3.2.26 #1 SMP Thu Jul 9 11:14:15 PDT 2015 wd-2.4-rel armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
WDMyCloud:~# cd /DataVolume/shares/Public/
WDMyCloud:/DataVolume/shares/Public# /usr/local/sbin/updateFirmwareFromFile.sh /DataVolume/shares/Public/sq-040500-342-20190805.deb updateFirmwareFromFile.sh:01/19/20 12:27:36:: ( /DataVolume/shares/Public/sq-040500-342-20190805.deb )
updateFirmwareFromFile.sh:01/19/20 12:27:36:upgrade start: /DataVolume/shares/Public/sq-040500-342-20190805.deb
updateFirmwareFromFile.sh:01/19/20 12:27:37:check_size=
updateFirmwareFromFile.sh:01/19/20 12:27:37:version_current=040401112
updateFirmwareFromFile.sh:01/19/20 12:27:37:version_newfile=040500342
updateFirmwareFromFile.sh:01/19/20 12:27:37:package_newfile=sq
updateFirmwareFromFile.sh:01/19/20 12:27:37:master_package_name=sq
updateFirmwareFromFile.sh:01/19/20 12:27:38:master_package_new=sq
updateFirmwareFromFile.sh:01/19/20 12:27:38:update_container=
[ ok ] Stopping periodic command scheduler: cron.
[ ok ] Stopping standby monitor: monitorio.
[ ok ] Stopping temperature monitor: monitorTemperature.
Stopping Twonky MediaServer …
[ ok ] Stopping itunes server: forked-daapd.
[ ok ] Stopping wdphotodbmerger: wdphotodbmerger.
[ ok ] Stopping wdmcserver: wdmcserver.
[ ok ] Stopping Samba daemons: nmbd smbd.
Stopping Netatalk Daemons: afpd.
[ ok ] Stopping upnp nas device: upnpnasd.
[ ok ] Stopping wdnotifier: wdnotifier.
[ ok ] Stopping wdnotifier: wdnotifier.
[ ok ] Stopping NFS kernel daemon: mountd nfsd.
[ ok ] Unexporting directories for NFS kernel daemon…
[ ok ] Stopping NFS common utilities:.
updateFirmwareFromFile.sh:01/19/20 12:27:55:new_upgrade_version=2
updateFirmwareFromFile.sh:01/19/20 12:27:55:current_upgrade_version=2
/tmp/tmp.HUUXBJpzCQ/upgrade-version' -> /CacheVolume/upgrade/upgrade-version’
updateFirmwareFromFile.sh:01/19/20 12:27:56:Newer upgrade scripts in update package, use normal update method
(Reading database … 25551 files and directories currently installed.)
Preparing to replace sq 04.05.00-334 (using …/sq-040500-342-20190805.deb) …
preinst_project-control: begin
/DataVolume/shares/Public
isImage=true
Master package name: sq
sq-preinst: action=upgrade
currentRootDevice=/dev/md1
forked-daapd: no process found
disable lazy init
root: disable lazy init
stopping duplicate md device /dev/md0
Restore raid device: /dev/sda1
Restore raid device: /dev/sda2
Prepare for upgrade pkg install…
mdadm: set /dev/sda1 faulty in /dev/md1
mdadm: hot removed /dev/sda1 from /dev/md1
Preparing FW upgrade image on: “/dev/md0”
preinst: currentRootDevice=/dev/md1
preinst: upgradePath=/mnt/rootfs
preinst: upgradePart=/dev/sda1
preinst: upgradeDevice=/dev/md0
send_update_log=200
Unpacking…
Unpacking replacement sq …
Setting up sq (04.05.00-342) …
postinst_project-control: begin
/DataVolume/shares/Public
root: ## postinst_body ##
root: ## postinst_header ##
postinst: isImage=true
postinst: Master package name: sq
postinst: sq-postinst: action=configure
postinst: currentRootDevice=/dev/md1
postinst: upgradeDevice=/dev/md0
postinst: upgradePart=/dev/sda1
postinst: upgradePath=/mnt/rootfs
root: ## postinst_image ##
Copy image to upgrade device /dev/md0:
blockSize=64k blockCount=31247
Compare checksum
-: FAILED
md5sum: WARNING: 1 computed checksum did NOT match
ok 1
Upgrade failed
mdadm: stopped /dev/md0
mdadm: added /dev/sda1
send_update_log=200
these are putty’s log. something went wrong but i dont understand.
wd my cloud gen1 out of order
broken hdd
replaced with a new one
firmware from the site
problem
when executing the command
cp /mnt/rootfs//usr/local/share/bootmd0.scr /mnt/rootfs/boot/boot.scr
the bootmd0.scr file is missing from the firmware
where can I find it?
thanks
Did you run one of the unbrick directions for the first gen single bay My Cloud? If so which one? Once a successful unbrick was done did you download the latest gen 1 single bay My cloud firmware from the WD site (04.05.00-342 (09/04/2019)) and perform a manual firmware update through the My Cloud Dashboard?
Where are you executing that command and why are you executing that command?
My action:
download the firmware (04.05.00-342 (09/04/2019)), unpacked, extracted the file rootfs. img
then this file using the script debrick.sh I put it on hdd
when the script is running, this error appears “cp /mnt/rootfs//usr/local/share/bootmd0.scr /mnt/rootfs/boot/boot.screen”
I install the hard drive in wd my cloud-the light bulb is green for 10-15 seconds, then red.
nas does not see the boot sector
what actions are my incorrect?
wdbctl0030hwt - 00
What specific directions are you using to unbrick the My Cloud? What directions are instructing you to run a script called: debrick.sh?
There are several methods to “unbricking” a My Cloud. User Fox_exe has a set of directions for both a first gen single bay My Cloud and the second gen single bay My Cloud that some have used to unbrick an existing My Cloud hard drive or configure a new drive for use in the My Cloud enclosure.
Generally though after initial unbrick one may still get a solid red front LED. If this is the case oen should try to access the My Cloud Dashboard and if that is successful, navigate to Settings > Utilities and perform a System Only factory restore. That usually fixes the initial red led after unbrick and the 0K issue in the Capacity section of the Dashboard Home page.
performed recovery using the original image “WDMyCloud3TBVDI”
connected hdd to the nas
the nas is always green, goes out for 1 second and lights up. And so about 1 time in 3-4 minutes. It’s like it’s rebooting.
The network interface blinks “link” (one light), the second light does not blink. Accordingly, there is no nas in the network.
The “reset” button on the case doesn’t help.
Again, what directions are you following? Where did you find these directions? Post a link to the directions.
What is the “WDMyCloud3TBVDI” file? Where did you obtain it? What directions are telling you to use that file?
Without knowing what directions you are using to restore the My Cloud operating system to a hard drive, it’s hard to provide any additional assistance.
everything worked out!
thank you!
Initial posted updated with just released single bay v2.x My Cloud firmware.
Version: 2.41.116 Release Date: 12/08/2020 | Release Notes
Direct download link: https://downloads.wdc.com/nas/My_Cloud_GLCR_2.41.116.bin
What’s new!
Please visit Western Digital’s Product Security Portal to find more information about our security fixes.
- Security Fixes
- Resolved Escalation of Privileges Vulnerability (CVE-2019-18929, CVE-2019-18930, CVE-2019-18931)
- Other Updates
- Updated Privacy Statement.
I am a little confused. Some of the latest New_Rease-Titles on the annoucement forum page starts with “my Cloud OS 3”, What is OS 3 ??? Which product is it? And additionally to that Bennor wrote:
Furthermore, here New Firmware for 2nd generation My Cloud is available for download - #2 by Bennor and in the other New_Release-Posts there is no MyCloud unit mentioned, just MyCloud Mirror but this is a different product.
could one please clarify!
Yes it’s confusing isn’t it? Its something many of us pointed out would happen when WD made the decision’s they made to introduce the second gen My Cloud and give it different firmware than the first gen My Cloud. Made more confusing by the release of OS 3 four years ago. WD tossed in a confusing firmware numbering scheme (v4.x for first gen, v2.x for second gen) to further confuse things. Then WD doubled down on the confusion by introducing a completely different product that uses a completely different OS, My Cloud Home, that a great many confused and STILL to this day confuse with the My Cloud line of devices. Now WD goes and creates OS 5 to confuse people even more.
What is OS 3? Basically WD, back in 2016, streamlined the firmware and units to using new features including revamping the remote access website WD2Go.com to MyCloud.com. This included the loss of being able to remotely map a Share on the single bay My Cloud’s using the web portal.
In the WD announcement New Release - My Cloud OS 3 Firmware Version 2.41.116 (12/01/2020) the second gen single bay My Cloud IS mentioned. It is listed as: My Cloud (FW 2.x).
WD releases OS 5 web portal, and firmware for only certain existing My Cloud devices. The single bay/single drive My Cloud unit IS NOT supported by OS 5. This entire post discussion and all links to firmware *is strictly for the single bay/single drive My Cloud unit. If one wants to discuss OS 5 then see the specific subforum for OS 5 supported devices (https://community.wd.com/c/OS5/252).
I made the initial post to kick off this long thread as a place where all firmware for the single bay/single drive My cloud units could be found. Many people were trying to roll back to earlier firmware (for what ever reason) and couldn’t find links to that earlier firmware. The initial post evolved to having more information including links to past WD released GNU firmware files so people could find earlier versions to roll their own firmware.
It appears this is the current list of devices supported by OS 3 and by OS 5:
OS 3
My Cloud
My Cloud Mirror
My Cloud EX2
My Cloud EX3
My Cloud EX2100
My Cloud DL2100
My Cloud DL4100
OS 5
My Cloud EX2 Ultra
My cloud EX4100
My CloudPR2100
My Cloud PR4100
My Cloud Mirror (Gen 2)
On a personal note. No idea why WD continues to do things that only serve to confuse it’s customers and users. Some of decisions made (from a user standpoint) seem like someone at WD ignored or rejected basic common sense.
Edit to add: One should also note that WD retires support for devices (i.e. End of Life) and software/apps. The first gen single bay My Cloud is no longer supported. The second gen single bay My Cloud has limited support which is why it’s still getting firmware updates to fix various (security) issues. We first gen users are out of luck apparently for having any existing or newly discovered security issues fixed. It appears the OS 3 devices are at end of support or are in limited support. Eventually WD will move limited support products to end of support.
oh my dear! Are the WD people crazy.
OS3 since 3 years ?!?! Wow, have not noticed this. But ok, I do have 2nd Gen. single bay MyCloud so I use this OS3 firmware
If you have having a problem with your device, use the forum search feature, magnifying glass icon upper right, to see if there are past topics similar to what ever issue or problem you are having. If no past topics match what ever your problem is with the device, start a new topic discussion where others may be able to assist with what ever the problem is. Be as specific as possible with what ever your issue is.
If you don’t know how to use or configure your device, see the WD My Cloud Support website where you can find more information, including the User Manual, for your device.
Every spot on the website that looks like a place to get help is a dead link for me.
What website? What links? As previously indicated, if you are having a specific problem with a single bay My Cloud, start a new topic about it.
OS3 single bay firmware: My Cloud - WD Community
OS5 second gen v2.x firmware: My Cloud - WD Community
You asked if the unit was a small anchor without providing any additional information or detail why you think or assume that. For some of us the single bay My Cloud unit works fine. For others, they start a new topic where seek help from the user community with what ever issue they are experiencing with the device.
I was wondering if anyone has had any luck loading Mycloud firmware or software on a server. I would like to load this on my 6 BAY 2U rack server any ideas on how this can be done?
There are a number of better NAS operating systems out there (free by the way) that one can load to a custom built NAS setup. FreeNAS, OpenMediaVault, XigmaNAS are several popular free OS’s for example. Not sure why in the world anyone would want to use the My Cloud OS, with all of it’s issues and problems, on any other NAS device other than a My Cloud device.
If one really wants to try using the My Cloud OS on a non WD NAS they they could attempt to follow one of the various My Cloud unbrick methods. One would have to partition their hard drive per the unbrick method. Just note that the My Cloud firmware is not standard Linux, WD has customized it to work on their My Cloud hardware. One will have to likely spend A LOT of time and energy trying to figure out why the My Cloud OS won’t work properly (or at all) on hardware it was never designed to run on.
One could spend even more time and effort rolling their own My Cloud firmware by using the GPL source code that WD provides for the My Cloud units on the WD My Cloud Support page on the WD Support website…
One other word of note. If anything in the WD My Cloud OS is proprietary and or third party licensed. one may be violating local/national laws by using it on hardware it was not licensed for.
I have tried FREENAS now called TrueNAS CORE. The problem with that software is it is more complex then it needs to be and It will not run on some equipment. I tied loading it on an old Lonovo thinkserver and it refuses to go and not for lack of trying. Was thinking if WD’s software was OPEN source it would be great to put on that old server to use it. BUT if they do not allow it then I guess that is something that I will not be doing. Thank you all for the help.
