-> If you do not have SSH enabled, your only solution is to return the product for RMA replacement.
Well, that might not be entirely true. Here is my experience.
A month ago, I updated my MBL 1T, to 2.10.12-124. Soon after that the UI died. I checked with the community here, just to find out that, since I did not have ssh (or auto update) enabled I'm doomed. I had no time to spare, so i did not RMA the product.
Yestrday, the MBL would not show on the network and I could not connect to it or its media server at all, The LEDs on its ethernet port were as usual (one solid and the other blinking).
Without access to the UI to perform a safe reboot, I just disconnected and a 5 - 10 seconds later reconnected the MBL power adapter. The MBL booted (Blue LED followed by Red LED - it "lost" its green "touch" a long time ago) and shortly after, made itself available to the network.
At this point, I decided it would do no harm and tried the UI. Surprise, it WAS working. I checked for an update and got the network connection error. Went to WD's site and found there was a new update (129). By the time the download was complete (and dinner was over), the UI had timed out and it was dead again.
After fiddling with the unplug/5 sec./plug procedure for a few times (performed on the the network cable too, just in case), the UI came back to life. I swiftly did a manual update (from within the UI), which went fine.
I did not encounter the slow UI issue, but there are some funny side effects.
According to the pics below, my MBL is for sure the oldest one on the planet (check the underlined dates).
But my MBL time/date info is correct and here is MBL's message to prove it.
Hey WD, I'm ready to trade it for a new ("bigger") one, and you can put in your museum :smileyvery-happy: .
So, before you RMA your new MBL for a refurbished one, due to the dead UI (with disabled ssh) issue, you might want to try the unplug/plug game of both the power and network cables. I know it doesn't make sense but you never know...