Forgotten Settings issues with Guardian OS 4.4.049

[teastman]

We had some weirdness here from a storm this weekend.

Snapserver410 Guardian OS 4.4.049 was attached to a UPS and seemed to power down ok when the rest of our building lost power.

But it's behaving like it crashed. I am able to get to it over the network. But,..

It's not remembering it's own Server name;
It's not remembering that it belongs to a Windows Domain
It's not remembering it's e-mail notification settings
It's not remembering the DNS servername
It seems it's network value settings are whacked.

The Snap Shots are all there,
The Shares are still there but unavailable over the network. It's simply not talking to the network or the main server (which is the Primary Domain Controller Windows 2003 SBS)

There are other issues too but I need to get on top of this first. I made a Disaster Recovery file some time ago which was created last time there was a substantial change on the snapserver.

When I go to restore settings from this file - the process tells me the restore was successful etc. But then at restart again it's asking me for the server name all over again.

When I originally bought the server we had a crash then too and it turned out that a system file in the flash memory (?) got whacked. Most of the lines for setting values were just not there to even write to so all my value inputs never got written back to that file correctly. (Kind of like trying to write values to the old system.ini files.) The tech on the phone at that time had to re-write that file via a nul modem serial cable attached to my personal machine. Command Line Interface stuff.

I also did a snapshot rollback to the last known good state. It still reboots and takes me to the servername screen.

I know that's sketchy but so you guys have ideas I can try?

[blue68f100]

If this was an older unit I was say the cmos battery is dead. Or did Adaptec even put one in the 410 to increase profits by not spending the $1 for the battery.

If you know the proedure and values done by the tech, get the null modem back out.

On your UPS auto shut down, do you shut down on low battery or when ever power is lost for a certain amount of Time. The reason I ask is if the batteries are weak the unit may not be in shutdown when it drops.

Do you have your set for auto restart? If you get another power loss when starting up your batteries may not carry the unit so it can be shut down. always delay my restart till the batteries have at least 25% charge.

Andy may comment since it's a hardware issue.

Did you test after the last failure to see if the unit would retain the settings.

[teastman]

Originally Posted by blue68f100

If this was an older unit I was say the cmos battery is dead. Or did Adaptec even put one in the 410 to increase profits by not spending the $1 for the battery.

If you know the proedure and values done by the tech, get the null modem back out.

On your UPS auto shut down, do you shut down on low battery or when ever power is lost for a certain amount of Time. The reason I ask is if the batteries are weak the unit may not be in shutdown when it drops.

Do you have your set for auto restart? If you get another power loss when starting up your batteries may not carry the unit so it can be shut down. always delay my restart till the batteries have at least 25% charge.

Andy may comment since it's a hardware issue.

Did you test after the last failure to see if the unit would retain the settings.

Yes it was tested after the last failure and it did retain the settings.

Here's what I think happened (from the "Error Logs"); The UPS sent the signal to power down which it did. The screw-up came in because the server (I didn't see this at the time) was set to restart at power. Also there was another piece of equipment on that UPS which completely drained it after the Snap shut down.

The building power did not came back up clean and solid and the power cut out on the Snap before the UPS had enough juice to sustain a proper shutdown. It basically was trying to restart when the power took it out at the knees.

I don't know what the tech did to re-write the file at the CLI level. Sorry.

Looks like I'll have toi bite the bullet and get tech support on the line again.

Thanks
tje

[KOBadmin]

teastman did you ever get this resolved?

The 410 that I have is doing the same thing
Not remembering own Server name
Keeps having some sort of error on the shares requiring a restore of the Share specific settings (twice at last count), the Share have "(E)" behind all of them and we are unble to modify the that at all. Once the restore is complete the shares can be accessed with no problems.

Just woundering how you fix your Server or if I will have to go deal with Tech Support?

Thanks

[teastman]

Originally Posted by KOBadmin

teastman did you ever get this resolved?

The 410 that I have is doing the same thing
Not remembering own Server name
Keeps having some sort of error on the shares requiring a restore of the Share specific settings (twice at last count), the Share have "(E)" behind all of them and we are unble to modify the that at all. Once the restore is complete the shares can be accessed with no problems.

Just woundering how you fix your Server or if I will have to go deal with Tech Support?

Thanks

Yes this was resolved. This gave me some nice error information which I gave to teck support via a Syswrapper. I'm not a brainiac at this stuff but it turned out to be a motherboard issue.

I've since then replaced the 410 via an RMA and the problem has gone away.

I'm afraid this does not help you though.

[KOBadmin]

Thanks for the info.
It does help me decide the next step, looks like I am calling tech support.

How long did it for them to replace the unit?

[teastman]

Originally Posted by KOBadmin

Thanks for the info.
It does help me decide the next step, looks like I am calling tech support.

How long did it for them to replace the unit?

Mind you we have a support agreement with them (now Overland Storage). But once we determined it was a true failure they were right on it with an RMA and I had the RMA unit within a couple days loading it up.

The dealing's I have had with Overland Storage have been good. But then again they probably understood that I was at "ignoramus level" at this stuff.