Delete a stubborn user directory on a 4500

[FortoReibas]

I got my 4500 reset to defaults and am cleaning out the old user directories on it out via PUTTY and there is a directory at: /shares/SHARE1/user_data/jrc that I can't delete and can't navigate to, either at the command prompt or in Windows browsing. I went to the HTTP admin page and tried the "Reset to default ACLs for volume: VOL0" functionality, but it changed nothing. I'm not entirely new to Linux, but I think I need the root password to reset the permissions. Only problem is, the only user defined in the HTTP admin page is "admin", which I am logged into PUTTY as, and admin's password doesn't work for root. Any ideas?

The permissions on that directory are: drwxrwx---
I tried first the same command I had been using: "rm -r jrc", but no dice.
I tried a "chmod -R 777 jrc" on the directory, but no dice

[bitor]

Did you try putty log in as admin then your password then type "su" then your password again?

1.)Start putty
2.)Enter your user name with admin rights. defualt=admin
3.)Enter your password.
4.)Type su
5.)Enter password same as number 3.)
bitor

[FortoReibas]

I tried that, using the password "admin".

sh-2.04$ su
Password:
su: incorrect password
sh-2.04$

[FortoReibas]

I just created a brand-new admin user: blink/blink and logged in as it. Same results -- can't su using its password.

[blue68f100]

With version 4 you need to use the "os shell" then "su root", PW in order to gain access to the root.

error correction edit: os shell should be "osshell" then "su"

[FortoReibas]

Snapserver manager reports this unit as running 3.2.025. Does that change anything?

Not sure what you mean by "os shell" password?

[blue68f100]

If your not getting the # prompt indicating you have admin rights enter the "os shell" this will grant you access to the system files if you use the root pw.

[FortoReibas]

That sounds great. How do I do it with 3.2.025?

[blue68f100]

Use putty as you were then os shell after your loged in.

[FortoReibas]

Wonderful! How do I do it, though?

[FortoReibas]

I tried issuing the command "os shell" at the command prompt in PUTTY, but that didn't work.

[blue68f100]

I tried that, using the password "admin".

sh-2.04$ su
Password:
su: incorrect password
sh-2.04$

If you do not know the admin password you may need to reset the unit. There is another thread running right now that covers that. My post #2 has the instructions.

[FortoReibas]

That other thread is me too. I did eventually get it reset to defaults via the white reset button and HTTP interface, but that still left me as described in this thread. The admin password is now "admin".

So, to recap:
Log into PuTTY as admin/admin
Navigate to /shares/SHARE1/user_data/
and try to delete subdirectory jrc
with command rm -r jrc
No go.

Try to su as root, but the "admin" password doesn't work for root.

That's where I'm stuck. I need to be clear that I really don't care about root -- it's just a possible method to allow me to delete a subdirectory, which is what I really want.

[blue68f100]

Are you getting the # prompt or $ prompt when you login as admin?

at the > prompt enter
osshell
su
password

see if this works.

[FortoReibas]

Here is what I am getting:

login as: admin
admin@172.16.1.43's password:*****
Last login: Fri Jun 6 18:12:46 2008 from desktop
sh-2.04$
sh-2.04$ osshell
sh: osshell: command not found
sh-2.04$

[blue68f100]

I was thinking the osshell was only good for v4.2 and up.

Does the su root or su drop you into the # prompt.

[FortoReibas]

That's just it. I don't know the password to get past su.

sh-2.04$ su
Password: [I am typing in "admin" here]
su: incorrect password
sh-2.04$

[blue68f100]

Dig out the old null modem cable (115.2kbps N,8,1) and see if you can get into the repair/reset options of the diaster recovery console.

[bitor]

As I understand the default username is the same as the password.
username: admin
password: admin

Try that and see if it works.
You might have to be in the osshell directory in order for it to work.
Do a "find / -name *osshell* " to see it the program is on your system.
bitor

I just saw that you tried that. Never mind.

[FortoReibas]

Well, that was a strange fix. I went into the HTTP admin page and did a real shutdown one more time, then brought it back up, and I was able to SSH in and remove the directory.

It looks like SnapServers don't like to be unplugged when you want them off. I guess that I was treating them too much like appliances and not enough like finicky Windows servers. I'd been just unplugging them when I wanted them off. All is well now.

[blue68f100]

I do not know any pc or server that like the power being removed without being shutdown properly. Particularly anything running a RAID array. Most all will initiate a system file check and array check.

The GuardianOS is on Redhat Enterprise Linux.

[bitor]

Wow, not a good thing to do for Snap Servers of any flavor in general, but glad you got it working. Maybe the next time somebody ask for help they should not only tell us the problem , but what they are doing. Which might be causing the problem.

Just a thought,

bitor

[FortoReibas]

Point well taken.