4.2.13 ultra 6 not powering up automatically

[PeteCress]

PeteCress this should be an easy issue for tech support to resolve. Contact them about it and work with them.

Last time I called, it was the better part of an hour wasted on the phone with some level-1 guy who I suspect didn't even know what an Ultra-6 was.

In case anybody is listening....I did User Support for over ten years of my life, and now that I'm a developer, I interact with a Help Desk at a major financial concern on a regular basis. Having said that..... NetGear support is bad, bad, bad, BAD.....I mean like REALLY BAD.

First thing I'll try is replying to the note from Level-2 that pointed me at the Bios update.

If that doesn't pan out, I guess there's nothing else but to suck it up and call.... -)

[peterbanks]

PeteCress this should be an easy issue for tech support to resolve. Contact them about it and work with them.

I got a good chuckle out of that too.

[PeteCress]

I think I found something in viewtopic.php?f=64&t=48935&p=281278&hilit=boot+shutdown+loop#p281278

Sounds like a trip to Level-3 is in order.

[PeteCress]

Sounds like a trip to Level-3 is in order.

Which begs a question: How to get to Level-3?

I just spent an hour trying.

If anybody wants a few laughs: viewtopic.php?f=64&t=49899&p=284619#p284619

[beisser]

i fixed your reboot loop.

[PeteCress]

i fixed your reboot loop.

Many thanks again.

BTW: What if this happens a year from now, when the box is off-warranty? Will I need to be on a service agreement to get help?

Where I'm going with this is that maybe even a fool like me could learn to telnet into the box, navigate the the appropriate directory, and delete the offending file. Understood that there may be many causes for a boot loop - but if that file (whatever it's location) is present, deleting it probably has a high probability of resolving the issue.

[beisser]

it wont happen, because im sure the next firmware contains code that will prevent this.

[PeteCress]

it wont happen, because im sure the next firmware contains code that will prevent this.

At the risk of turning into a tar baby on you over this...

What is the current firmware? V1.1 regardless of date? Or are there different v1.1's depending on date?

My box came with 1.1, support emailed me a Bios image that I installed on a USB stick and applied.

After that, the date had changed to a later date, but the version was still 1.1.

I *think* it was different bc I got WOL to work a few times.... but it I would have expected 1.2 or 1.1.something....

OTOH, maybe WOL was working before and I was just doing something wrong.

[mdgm]

The shutdown loop issue is unrelated to the BIOS. The firmware beisser was referring to is RAIDiator firmware e.g. 4.2.15

As for the BIOS, I guess the changes were so minor that they didn't increment the version number. You can tell from the date whether you have the latest version.

[peterbanks]

So I think I'll kick back and wait for an officially-sanctioned and tested fix - along with some instructions and glowing reports from guinea pigs, errr... I mean..... satisfied users....

I'm about at that point. Here's hoping that they actually do come out with a "officially-sanctioned" fix. Or chirpa could just send me the USB key...

We're working on an add-on that doesn't require a USB key. Stay tuned...

Any update on this add-on? I'm still waiting for a fix. Thanks

[chirpa]

Who wants to beta test the add-on?

[peterbanks]

Who wants to beta test the add-on?

Not me, but I'd love to get that USB stick you offered back in November.

[chirpa]

The USB method is no more, this way is more reliable. We've tested it on many machines in-house already, and with a few end users, I would say it is fairly safe to try.

[ahpsi]

I'll give it a go, Ultra 6 @ "05/26/2010 FLAME6-2 V1.1".

[gearvault]

Who wants to beta test the add-on?

I would like to test the add-on
My Ultra 6 is on 05/26/2010 FLAME6-2 V1.1