It’s been sometime since my original post and I thank all the contributors to the thread.
Well after a successful few weeks with firmware 1.0.3 (as 1.0.4 or 1.0.5 would not get past “…almost there”) - I noticed that a completely new version had arrived (yipee I thought). So after manually updating firmware (CTRL + check for updates then browse for firmware file) - after the firmware required reboot - I return to the same old “almost there…” - but instead of being able to go back to previous firmware - it would appear the new firmware has altered something on the “Volume” in that backward compatibility has become broken.
So I now have no access to my files and am extremely Peased Off - So being from the UK and reading the comments above I have contacted Drobo support in the US and am working my way towards 3rd line support (but not there yet!).
I wonder what it is between 1.0.3 and 1.0.4 (and 1.0.5) that has stopped my drobo from doing a full successful boot and also what has happenend between 1.0.5 and 1.1.0 to the Volume… - Answers on a postage stamp…
If only they had a firmware with SSH built in so that I could try a few things - I feel so helpless being locked out.
As I am a Computer Engineer by trade I have a fair bit of knowledge and could probably identify why the “Samba” (windows file share) service is not able to run (if only I had firmware low level SSH - as dropbear Drobo App does not load in this state.).
God Damn it…
I bought this thing to enable expandability and reliance of my data - but the problems I have had really are starting to make me wonder if I should have built my own “BeyondRAID” system.
I await technical supports further assistance.