however, even though i can do this - the drobo dashboard does not see the drobo. The drobo then goes to sleep but i am then also able to reconnect to it and it wakes from sleep. once its connected and mounted i can then disconnect from it in the ATTO software. then whilst its in an awake state, i can go to the ATTO software and then hit CONNECT, then it connects and mounts. i need to manually power it off and on again. I also find that the drobo dashboard does not see the drobo even when i get it all up and running. When i manually go to the ATTO software and try to reconnect to the drobo, it says the targetted cannot be found. even though i have set the ATTO initiator to auto login. when i boot back up, it does not automatically mount and log in. for example, if i power everything off the drobo sleeps. BUT, i can only do that if the b800i is not asleep. Through the ATTO product, i can connect and mount the b800i. after much tweaking a playing around, i managed to configure that so that it can find my drobo b800i. i can't find it anywhere, i have now since paid and downloaded the ATTO iscsi initiator software. I tried to find a copy of the older drobo dashboard i was using. the iMac had an older version of drobo dashboard on it - it had version 2.7.5 on it, which it appears had the iscsi initiator built in. I managed to do this fine and have since gotten rid of my iMac. I managed to get a loaned drobopro chassis, so i could put the drives in my failed drobopro into it - and then connect both the drobopro and the new b800i to my iMac and transfer the data. I was then advised to buy a B800i as it was intended for iscsi. Last year the Drobopro chassis failed and i needed to replace it, but was unable to do so. I used to have a drobopro that i couldn't ever get working using iscsi - in the end I resorted to use it just on firewire and generally it worked fine. Looks like i maybe in a similar situation to many here. I know I am a very small part of your user base but from a customer's perspective this has been beyond frustrating (and still is considering I still don't have a number of machines working). I had no clue what the problem was until I started doing some searches and found this post. It would be best if you updated the support page on as well as the new dashboard to inform users that ISCSI is no longer included. I have already invested a lot of time to just get to the point where I am now. I must say that it is a bit frustrating that you would just now review the contract for this provision. I have had good luck with my Sans Digital unit so I may turn there to replace this thing. It might just be time to buck up and get a new unit that won't run into these obsolescence issues. I have tried installing the old Java, but it is just not working. Now I have one machine connecting using 2.5.4 (which is an older mac) but have been unsuccessful getting the newer Yosemite builds to connect. I was able to find copies of the old dashboards and the old java update online.
0 Comments
Leave a Reply. |