I've been seeing the same problem with my MBWE.
My unit stopped booting - no blue rings, no spinning disk - but the network lights did come on when I plugged in a cable.
I disassembled the unit and removed the drive to try using the tool at fs-driver.org. Windows found four partitions, but still thought they all needed to be formatted. I left them alone because I still need the data from the drive. I placed the drive back in the MBWE case, but I used an external source to power the drive and used another cable to connect the drive to the MBWE controller board. It started booting again - blue lights, spinning disk. However…
I could ping the unit, but I couldn't browse to it in a browser and Windows couldn't see it on the network. I could use ssh, but password authentication failed. I tried to reset the unit using the reset button, but I still can't do anything more than ping the unit.
I disconnected the drive again and I'm currently running SpinRite on it to check for disk errors. The two smallest partitions are clean. The next largest partition (~1G, I think) has hit some errors and we'll see if SpinRite can recover anything. I'll check the last partition (the big one with my data) when the current one completes.
I also plan to use SystemRescueCD to see if I can successfully read the partitions from Linux. I've seen some information about data on MBWE drives being encrypted - not sure if that's the problem.
Could it be that the errors on this third partition are preventing the unit from booting up completely? I'm not sure what's on that partition.