Drobo FS won't mount win 10

I have had a Drobo FS dashboard and mounted shares setup on a win 10 machine for some time that still functions normally. I am trying to setup the same dashboard rev and shares on my new computer also a win 10 machine. The dashboard logs in to the drobo, but it can mount the shares and when I try to mount them manually it denies access when I apply the same credentials used to log into the dashboard. It seems like there is a setting in win 10 that is set properly on my old machine that I need to find and change on my new machine for the drobo shares to mount. I have searched and tried many approaches, but I really need some help to find the solution. Please help.

hi jelder,
were you trying to access the drobo fs on the new windows 10 computer (while the first windows 10 computer is already connected to it and accessing it?)

if so, maybe you could power all down, and then just try booting up the drobo-fs, and the new windows 10 computer, and only having the drobo-fs directly connected to the new computer and to try connecting to it again?
(just in case the other computer was somehow locking out the new computer?)

I tried connecting the Ethernet directly between the drobo and the computer and rebooting in both orders with the same result. Can’t mount from dashboard and if i go manually to the shares through the network i see them, but when i try to login with the same credentials that i log into the dashboard with it says access denied like the login is wrong.

thanks for the update jelder,
would you be able to try using notepad to pretend to log in using the details on the problematic instance?

(just to make sure that somehow a keyboard is not stuck or mis-typing, or possibly in ALLCAPS mode for example? - it is probably not that, but just to check)

if you can capture a screenshot of the access denied message and to post it to imgur or similar it could be useful. (but pease remember to rub out any sensitive information before uploading)

by the way, are you using the same network cable that works with the 1st computer, when trying to connect the drobo to the 2nd computer?[hr]
also, are you running the dashboard application with admin rights on the new computer?

I tested the password as you suggested and found no problem. I have provided screen shots at http://dropcanvas.com/cp4z9 of the access denied and Drobo share along with the admin.

I have the same dashboard 2.5.2 [64171] on both win 10 machines and i am logged into the dashboard on the new machine. I have also tried it with the old machine off.

The Ethernet cable i used is the one the machine is connected to the internet with. I just unplugged it from the router and plugged it into the Drobo.

I remember having similar problems getting the drobo mounted on my old machine and don’t remember what finally got it to work. Thanks so much for your help.

thanks for the screens, that seems to be the windows login prompt, so somehow it is not working.
(by the way, have you tried ADMIN in uppercase?)

i think some users needed to slightly rename the share (via dashboard) and to try the new share, (and to then recreate it or change it back) - can you try that to see if it helps?

I did try admin in caps and as you can see in the screen, it is lower case in the Drobo admin screen. I’m a bit concerned about renaming the shares except as a last resort since it might break the connection i have on my old machine which is currently the only way i can access the Drobo. Any less destructive thoughts before i go there?

hi jelder, some of the other users im remembering, may have had slightly different issues though similar, and renaming or setting up the shares again did seem to fix things, but you are right i think the only way to play safe would be to backup the files somewhere else first before trying (especially if there are no other backups currently, as its always a good to have backups in general)

I did a backup and when i went in to edit the name on the share it said time machine not enabled on this share. Is that a problem i need to fix before renaming the share

hi jelder, if you are on windows, and you are not using a mac/time machine then i dont think dashboard needs it to be time machine enabled. (for example, if i was just using windows, i would not enable anything to do with mac time machine) :slight_smile:

Thanks for your help. After resetting the names I was able to map the drives.

cool no worries :slight_smile:

AArrrgh… I just lost all the mounts on my Drobo under Windows 10! ALL of them. And I was panicked, thankfully, I know I did not lose my data. It is not fixed, yet and that is why I need help. Here is what has happened and what I have tried.

My main machine is a Windows 10 Pro machine. It is what I use to keep my iTunes library on, my photos, my music, etc… all Stored on my DroboFS (running firmware 1.2.7). This afternoon, Windows popped up an “Update” window stating it needed to be restarted to apply security updates. I did and went to grab a bit while it rebooted. When I came back up and logged in, the shares were gone, the drives no longer mapped. I tried everything, rebooting the Windows box and the Drobo, even went as far as shutting them down. It still will not map. The Drobo dashboard sees the unit, but Windows does not.

So, I came to the forum. I started searching and saw others having similar issues. “Rename the share, add a letter or number to it…”, I read. I did that and it did not work. It still will not mount. I spun up my MacBook and tried to get to the shares from it. THAT worked (which is how I know I’ve not lost data). I continued to read. One thread said he found that he had to “rebuild his windows 10 machine”. Got news for ya, that ain’t happening! On the main box, I tried rolling back the latest security update. That did not work.

I spun up two other laptops, one on Windows 7 and the other one on Windows 10 (not updated). The Win7 mapped to the Drobo shares just fine as did the Windows 10 laptop.

This leads me to believe that ONE of the updates that MS pushed down is the culprit. I cannot rebuild this machine, so I am going to try rolling back some of the more of the updates.

I DID get the diagnostic files to download through the Dashboard. In case anyone see’s something I am missing, here is the part from the latest attempt:


TM: 000011e4 04\14 17:05:01 Information - Host OS: Microsoft Professional (build 9200), 64-bit
TM: 000011e4 04\14 17:05:01 Information - Version: 2.8.1 [80644]
TM: 000011e4 04\14 17:05:01 Information - Version: 2.8.1 [80644]
TM: 000015e0 04\14 17:05:14 Error - DroboFSAdapter::GetDimming() - Session is NULL
TM: 000015e0 04\14 17:05:14 Error - DNASShareManager::ManageNASDevice - console user is null. Not adding share info for ESA 0db103570747
TM: 000015e0 04\14 17:05:34 Error - DNASShareManager::ManageNASDevice - console user is null. Not adding share info for ESA 0db103570747
TM: 000015e0 04\14 17:06:05 Error - DNASShareManager::ManageNASDevice - console user is null. Not adding share info for ESA 0db103570747
TM: 000015e0 04\14 17:06:37 Error - DNASESAUpdateHelper::getDiskPackID - Failed to get diskpack ID from ESA Update
TM: 000015e0 04\14 17:06:37 Error - DNASShareManager::ManageNASDevice - DiskPackID is 0 or null. Using serial number.
TM: 00002304 04\14 17:35:32 Information - ServiceCmdRouter::RouteCommand - DeviceID = na. CmdID = eCmdIsAutoDiscoveryEnabled
TM: 00002030 04\14 17:35:32 Information - ServiceCmdRouter::RouteCommand - DeviceID = na. CmdID = eCmdGetVersion
TM: 00003b38 04\14 17:35:39 Information - ServiceCmdRouter::RouteCommand - DeviceID = na. CmdID = eCmdIsAutoDiscoveryEnabled
TM: 00001858 04\14 17:35:39 Information - ServiceCmdRouter::RouteCommand - DeviceID = 0db103570747. CmdID = eCmdGetFirmwareInfo
TM: 00003350 04\14 17:35:39 Information - ServiceCmdRouter::RouteCommand - DeviceID = na. CmdID = eCmdIsAutoDiscoveryEnabled
TM: 00002ed0 04\14 17:35:39 Information - ServiceCmdRouter::RouteCommand - DeviceID = na. CmdID = eCmdIsAutoDiscoveryEnabled
TM: 00000eb4 04\14 17:35:39 Information - ServiceCmdRouter::RouteCommand - DeviceID = na. CmdID = eCmdIsAutoDiscoveryEnabled
TM: 0000229c 04\14 17:38:02 Information - ServiceCmdRouter::RouteCommand - DeviceID = na. CmdID = eCmdGetReservedDriveLetters
TM: 00001648 04\14 17:38:05 Information - ServiceCmdRouter::RouteCommand - DeviceID = 0db103570747. CmdID = eCmdMount
TM: 00001648 04\14 17:38:50 Error - NetProcess::TerminateIfActive command line process exit code is : 2
TM: 00001648 04\14 17:38:50 Error - DNASShareMapInfo::MapNetworkShare: Share mapping failed. datacore \datacore\VMs Z: code: 2250
TM: 00001648 04\14 17:39:35 Error - NetProcess::TerminateIfActive command line process exit code is : 2
TM: 00001648 04\14 17:39:35 Error - DNASShareMapInfo::MapNetworkShare: Share mapping failed. datacore \datacore\VMs Y: code: 2250
TM: 00001648 04\14 17:40:20 Error - NetProcess::TerminateIfActive command line process exit code is : 2
TM: 00001648 04\14 17:40:20 Error - DNASShareMapInfo::MapNetworkShare: Share mapping failed. datacore \datacore\VMs X: code: 2250
TM: 00001648 04\14 17:41:05 Error - NetProcess::TerminateIfActive command line process exit code is : 2
TM: 00001648 04\14 17:41:05 Error - DNASShareMapInfo::MapNetworkShare: Share mapping failed. 192.168.1.51 \192.168.1.51\VMs Z: code: 2250
TM: 00001648 04\14 17:41:50 Error - NetProcess::TerminateIfActive command line process exit code is : 2
TM: 00001648 04\14 17:41:50 Error - DNASShareMapInfo::MapNetworkShare: Share mapping failed. 192.168.1.51 \192.168.1.51\VMs Y: code: 2250
TM: 00001648 04\14 17:42:35 Error - NetProcess::TerminateIfActive command line process exit code is : 2
TM: 00001648 04\14 17:42:35 Error - DNASShareMapInfo::MapNetworkShare: Share mapping failed. 192.168.1.51 \192.168.1.51\VMs X: code: 2250
TM: 00001648 04\14 17:42:35 Error - ESANASDevice::Mount() - Failed with error 1
TM: 00003490 04\14 18:40:00 Information - ServiceCmdRouter::RouteCommand - DeviceID = na. CmdID = eCmdGetReservedDriveLetters
TM: 00003718 04\14 18:40:02 Information - ServiceCmdRouter::RouteCommand - DeviceID = 0db103570747. CmdID = eCmdMount
TM: 00003718 04\14 18:40:47 Error - NetProcess::TerminateIfActive command line process exit code is : 2
TM: 00003718 04\14 18:40:47 Error - DNASShareMapInfo::MapNetworkShare: Share mapping failed. datacore \datacore\VMs Z: code: 2250
TM: 00003718 04\14 18:41:32 Error - NetProcess::TerminateIfActive command line process exit code is : 2
TM: 00003718 04\14 18:41:32 Error - DNASShareMapInfo::MapNetworkShare: Share mapping failed. datacore \datacore\VMs Y: code: 2250
TM: 00003718 04\14 18:42:17 Error - NetProcess::TerminateIfActive command line process exit code is : 2
TM: 00003718 04\14 18:42:17 Error - DNASShareMapInfo::MapNetworkShare: Share mapping failed. datacore \datacore\VMs X: code: 2250
TM: 00003718 04\14 18:43:02 Error - NetProcess::TerminateIfActive command line process exit code is : 2
TM: 00003718 04\14 18:43:02 Error - DNASShareMapInfo::MapNetworkShare: Share mapping failed. 192.168.1.51 \192.168.1.51\VMs Z: code: 2250
TM: 00003718 04\14 18:43:47 Error - NetProcess::TerminateIfActive command line process exit code is : 2
TM: 00003718 04\14 18:43:47 Error - DNASShareMapInfo::MapNetworkShare: Share mapping failed. 192.168.1.51 \192.168.1.51\VMs Y: code: 2250
TM: 00003718 04\14 18:44:32 Error - NetProcess::TerminateIfActive command line process exit code is : 2
TM: 00003718 04\14 18:44:32 Error - DNASShareMapInfo::MapNetworkShare: Share mapping failed. 192.168.1.51 \192.168.1.51\VMs X: code: 2250
TM: 00003718 04\14 18:44:32 Error - ESANASDevice::Mount() - Failed with error 1
TM: 00002554 04\14 18:46:15 Information - ServiceCmdRouter::RouteCommand - DeviceID = 0db103570747. CmdID = eCmdUploadDiags
TM: 00002554 04\14 18:46:15 Information -
1 devices detected
Name Serial # Version ConnectionType


datacore tdb103570747 1.2.7 [4.45.10288] Unknown

hi thanks for the info,
if other windows 10 users happen to post back with similar issues, then there might be a general problem with that windows patch, especially if your other machines (and dashboard) can still see and access the data.

btw there were some samba-related updates recently relating to security (though maybe just coincidence), but if you see any of those recently, then maybe rolling those back for the test could help.

seem to be having the exact issue with my drobo-fs . probably started about a week ago.

i’ve tried a few worksation windows 10/7 and can’t mount the shares…

argh…

(just linking to your other thread mbana)
http://www.drobospace.com/forums/showthread.php?tid=146093

thanks paul.

i tried a freshly installed windows 7 laptop with no updates. didn’t work…

think i’m going to get pay for the support incident now.

ok please let us know how things go

hey guys have an update.

after a few weeks of going back and forth with tier 1 i was transferred to a senior tech. he sent me a custom firmware and i was then able to ssh into the drobo and see the files. i’m currently in the process of transferring everything off. Once thats done i’m assuming will probably reset the drobo to factory settings and copy the data back. this time i’ll be backing up the drobo for sure…

thanks for the update mbana,
(once you get to that stage, if you need any tips on windows backup tools please let me know and i can mention what i use in more details for you.)