I just opened the box, installed four 6TB Red drives and powered up my new DL4100 and the first message on the screen was that a ‘firmware update is available.’
I downloaded the file to my laptop and with both NAS and laptop connected to the same router I initiated a manual firmware update (Ver. 2.11.140) from the settings page/firmware update page in the browser GUI for the NAS.
A very basic white dialogue box popped up that reads: “Importing File…” The status panel on the DL4100 reads “System is in standby mode.” The first attempt at this took about 45 minutes over WiFi but I was logged out and the update never seemed to happen.
I turned off WiFi on my laptop and connected it to the same router as the NAS via Ethernet and started again. Same result and it’s not been about 30-40 minutes with that same status and no obvious way to judge progress.
Firmware updates often seem buggy and problematic and this seems like it might be another case like that. Questions:
– What are the steps/status messages I should be looking for on the Web GUI and on the DL4100 digital display during this process?
– How long (on a wired Gig-E network) should each of those steps take?
– IF I see the same “Importing File…” message for another hour…er…three hours(?) am I correct in assuming that something is wrong? What steps should I take to successfully update this Firmware?
NOTE: I’m thinking that if I see no progress in the next couple hours I will switch the settings to automatically update the Firmware (at least temporarily) and hope that the 3am automated version somehow works better…)
Thanks for any advice or information anyone can offer on this process!
You should have waited until the NAS had set itself up initially, because this process alone can take a while. So, just be patient. Once you load media on the NAS, it also can take a while before it settles in and builds the database… .
I don’t know that I didn’t do that. The manual says it can take a few minutes to set itself up and it had well more than that. It recognized the drives and said they were all healthy, I set-up the basic MyCloud account, etc. but I thought the firmware update was a good idea before I established a RAID level, etc. which I wanted to do before I moved content or set-up a basic directory on the array.
So, here we are an hour+ after my initial post – more than 90 minutes since I started the latest attempt to update the firmware – and the GUI still shows only that “Importing File…” notice. Any more specific suggestion on how long of a while that first step is meant to take? OR has it obviously gotten stuck?
IF I am to complete other basic set-up activities before trying this again…how do I end this firmware update safely?
My only “suggestion” is…Say if I remote to my destop from my lappy and open http://wdmyclouddl4100 sometimes I cannot see the bottom of these popups to click something. Just make sure you can see below the bottom of the popup. Prob not what is happening, just an idea
Well, I am not sure except that I do know my Dashboard returns to Home after 5 minutes (what I have it set to) But if the Updating is still showing, you should be able to get back to the Home screen, and then you should not see the Updating anymore and be able to move through the Dashboard menus. It seems it is just a case of the screen not clearing and going back to Home.view.
Thanks Mike and Gramps. I refreshed the browser and the update screen went away. I’ve gone ahead and successfully set-up a RAID partition, which occurred without issue. My plan now is to get on the phone with WD support to figure out what I’m doing wrong and/or the expected time frame for the various phases of the update.
UPDATE: When I restarted the DL4100 today it listed its firmware as current even though it had not been successfully updated.
With the help of WD support I reset the system to default settings and though it continued to display ‘current firmware’ status, I was able to manually install the new (2.11.140) version of firmware. It took roughly five minutes to complete the process. The system has since performed well and test content, RAID status and shares were not affected by the update.
