Drobo

Resolution to missing shares issue (kind of)

After several back-forth-emails with Drobo support, they say according to one of the logs I uploaded to them there “appears to be an issue with the Admin user name” and I should perform a password reset and/or try changing the Admin username to something else.

Now, when I initially updated my 5N to 3.2.1 when it came up after the reboot the dashboard was able to detect the device but was unable to log in to the Admin account. I tried providing what I THOUGHT was the password, but since it had been so long since I had last used it I couldn’t be sure it was correct. So I went through the password reset process at that time, the dashboard was then able to log in.

Today I tried changing the Admin username to something else, then rebooted the device and lo and behold, the shares came up just like they’re supposed to. Changed the username back to Admin, back to the same old problem. Even if I do another password reset on the Admin account it doesn’t work right.

I guess I’m at a loss as to why the Admin account can be accepted and used by the dashboard to log into the device, and yet it somehow causes a problem with the SMB daemon. This is more of a workaround than a solution, but I fully expect Drobo to tell me this is the best I’m going to get in way of a resolution.

Please let ensure that you are on the latest firmware and dashboard when using the 5N. Both the new firmware and dashboard work in conjunction with one another and are necessary to ensure the best performance and stability.

Drobo Support

Yah this did not work for me.

I now have two drobos5n that got updated and now nether one works even change the admin name form admin to Test did not work for me.

on side note “I sure wish company would support there frimeware and talk to people about it, just because hardware device is out of warranty does not mean they shouldn’t have a ongoing warranty on software you release for free to the units that they push out to every one and tell every one to download.”[hr]
It kinda works kinda does not work

I changed the user name now to gh

and then i changed the device name to drob5n2

and then all of a suddent after reboot device pops up on the workgroup but it pops up as drobo5n

not as drobo5n2 ?

if i change the name back to drobo5n

it disappears - if i leave the name drobo5n2 and then change the user name to admin the device disappears.

o and i can maket his happen over and over with both of my drobo5ns.[hr]
Bingo this is actully is the fix.

I had to change the user name to an older username for admin that I use to use which i dont use any more, also the admin user name can not be same as the user name for any of the shares.

my old user name was i changed out and was using as a share user name

then there issue number to device name

the device name can no longer be drobo or drobo5n

for some reason those device names will not work

I changed it to drobo5n2


issues still

now that i got admin figured out and the domain name changed

it pops up on but it shows it in the workgroup three times

as drobo5n drobo and drobo5n2

if i try to access it as drobo5n or drobo it says cant find device if i double click drobo5n2 it works

so now so its registering with three domain names and only one works ? o and if i change it back to anything of older domain names, that you might have used it disappears off of the network.

Strange usually services are kicked off by root. (and ps confirms that)

davel23 what do your /etc/shadow and /etc/shadow- files look like?
I found a bunch of old usernames that persisted even after the Drobo reset.

cat shadow

Admin:[hidden]:16542:0:99999:7:::

cat shadow-

Admin:!:16542:0:99999:7:::

cat group

root:x:0:root
nobody:x:99::
avahi:x:100:100::
Admin:x:1000:

cat group-

root:x:0:root
nobody:x:99::
avahi:x:100:100::

redmist, do you ssh in as Admin? Have you tried ssh’ing in as root and running those cat commands again? I only ask because mine look quite different (Drobo 5N FW 3.2.1):

[code]# cat /etc/shadow
root:[REMOVED]:10933:0:99999:7:::
bin::10933:0:99999:7:::
daemon:
:10933:0:99999:7:::
adm::10933:0:99999:7:::
lp:
:10933:0:99999:7:::
sync::10933:0:99999:7:::
shutdown:
:10933:0:99999:7:::
halt::10933:0:99999:7:::
uucp:
:10933:0:99999:7:::
operator::10933:0:99999:7:::
ftp:
:10933:0:99999:7:::
nobody:*:10933:0:99999:7:::
default::10933:0:99999:7:::
Admin:[REMOVED]:0:99999:7:::

cat /etc/shadow-

root:[REMOVED]:10933:0:99999:7:::
bin::10933:0:99999:7:::
daemon:
:10933:0:99999:7:::
adm::10933:0:99999:7:::
lp:
:10933:0:99999:7:::
sync::10933:0:99999:7:::
shutdown:
:10933:0:99999:7:::
halt::10933:0:99999:7:::
uucp:
:10933:0:99999:7:::
operator::10933:0:99999:7:::
ftp:
:10933:0:99999:7:::
nobody:*:10933:0:99999:7:::
default::10933:0:99999:7:::
Admin:!:16543:0:99999:7:::[/code]

Yeah, mine look more like nazzaro’s. I SSH as root.

davel: silly question, but since you have access to root still, have you tried running: passwd admin ?

More precisely, it would be these commands:

cat /etc/shadow
# copy down the encrypted password, just in case.
passwd admin
cat /etc/shadow
# the passwords should be different now (in encrypted format)

Oh just I removed the extra lines since we were specifically looking at problems with the Admin account.
Just wanted to make sure your accounts weren’t expired or users assigned to the wrong groups.

How about this for a thread revival! :wink:

I’m having a missing shares issue after updating firmware on my Drobo 5N. Capacity screen on Drobo Dashboard shows the same used/free space as before and the log file says “A File System (Ext4) was found on volume 0.” I have tried changing the Drobo’s name as well as changing the admin name as you all mentioned previously in this thread. I have installed Dropbear in Drobo Apps to have the ability to SSH into the drobo which I successfully did. Not sure where to go from here. Not at all savvy on the commands you all were talking about above like “cat /etc/shadow-” etc.

If anyone who knows how I can work on this issue to get my files back it would be greatly appreciated! Cheers.