Freeing up space to upgrade OS on 4500

[Plucky]

Hi guys,

First time poster here. We've just replaced our SNAP 4500 with something newer, so I can finally risk upgrading the OS on the 4500. Per the instructions on adaptec's site, I need 200M free space on the OS partition (I'm assuming) to get the update to work. I have 199M, running V3.0.099

/dev/md100root 529M 330M 199M 63% /

I've cleared out the log files and restarted the server, but I'm still at 199M. Is there any other log files, or a tmp folder that I can purge just to free up a few megs so I can attemp the update?

As a side note, I will not be upgrading as soon as I thought as there is a still data on the 4500. I will need to keep that data on there for a while until we are 100% confident in the new one. Figured I'll poke around to make sure I can upgrade it and ran into this lack of space issue.

Thanks for any help you guys can provide.

[blue68f100]

The main log is under the event log, which has a clear gui below the log screen (what you found). You can disable/un-install snap extensions (AV, backbone, iSCSI, snapshots).

If nothing else works and day has been backed OFF, you can do a clean install with the v4.

[Plucky]

Originally Posted by blue68f100

The main log is under the event log, which has a clear gui below the log screen (what you found). You can disable/un-install snap extensions (AV, backbone, iSCSI, snapshots).

If nothing else works and day has been backed OFF, you can do a clean install with the v4.

I am not sure where you are referring to when you say clear GUI. I am in the GuardianOS web interface, on the monitoring tab, event log, and I just clear the log there by pressing the Clear Log file.

I also checked the snap extensions and they are all disabled, but not uninstalled. I rather not uninstall them if they have been licensed.

Is there any other log file I can kill? I am not a linux guy so commands that don't involve clicking a button would need a step-by-step guide.

I do have a full install of v4 available I got from Adaptec. Will it still install regardless of it not having the 200MB of space required?

Thanks for replying!

[blue68f100]

Disabled is OK, unless you had them enabled and then disabled them. The AV has know to leave files behind. Did you make any of the disaster recovery files, under maintance?

We had another user come through here a while back having the same problem going from v3 to 4. Andy and I got into a discussion as if it was OS Space or data space. But don't recall the resolution. Do search on Guardian, or "clear log" There are not that many threads on the Guardian units. When I get a chance I will see if I can locate the thread.

Once you get the data backed off, the best way would be a clean install. Then the free space is not in play. Due to age of the unit are you going to be installeing new HD's and bring it back online? The OS supports very very large HD's, one users has installed 4 x 750's. I would also open it up and do some cleaning, its amazing how much dust these collect.

edit: Located the other thread, was not a resolution. But here is the link to bring you up to speed on what we discussed http://forums.procooling.com/vbb/sho...light=Guardian

[Plucky]

I have not made any disaster recovery files, so that shouldn't be filling up any space. The machine is probably 3 years old, though I don't know the original purchase date.

I did find that thread you mentioned, but since there wasn't a resolution posted, I decided to post the situation, but I only needed a few MBs, whereas the other guy needed a lot more.

I have not decided on whether or not to invest into some IDE hard drives for the unit, but that is definitely an option. It would be sweet to load it up with some 750GB's though. I figure I'll test out the unit with the latest OS to see how it performs because in it's current state, it's been a slug.

[blue68f100]

You need to boost the ram to a min 1g, and depending on what cpu you have those can me upgraded too. Andy (Phoenix32) has upgraded quite a few of them.

You will like the v4 os it is a lot more polished.

[blue68f100]

You can use putty to ssh into the OS shell. This is the best way to gain access. Once you are in you will need to be made "su -" once you have admin rights the prompt should be "#".
"ls /" will give you a list of directorys located on the snap.
"ls /tmp" will give you a list of files in the tmp directory. adding a -l (ls /tmp -l) should give you long file attributes. adding "|more"

v4 has locked a lot of cmds out.

"cd /tmp" should change you to the /tmp dir (no longer works in v4)

then you need to diside which one you want to remove.

"rm <filename>" should be the cmd to remove the file
or "rm /tmp/<filename>

use "exit" to back out, may need to enter it twice.


NOW I DO NOT KNOW WHAT WILL HAPPEN ONCE YOU REMOVE A FILE. SO USE AT YOU OWN RISK. Maybe someone with better linux skills will be able to add.

[fundoo2008]

FYI. You can call 1-800-959-7274 to see what kind of support you have on your snap server. Friday they were able to help me.

[Plucky]

I actually gave up trying to clean up the data and just went ahead with the full OS reinstall to the latest version and it installed just fine, and all my shares are still I place. I guess the required 200M to run it didn't matter.

After the update, I am now at:

/dev/md100root 529M 320M 208M 61% /