RE: Long IPL at SRC C600 3915

<<I think this is the first time I have ever treated the IBM i like a
PC. Pulling the power cords and waiting 10 seconds after the lights in
the power supplies went completely out before rebooting seems to be
working. It went by C6003915 in under 5 minutes and came fully
alive in 10.>>

Sounds good. You never had to rap a disk drive with a screwdriver handle to
free it from stiction? Those were the days.

:-))

Paul Nelson
Office 512-392-2577
Cell 708-670-6978
nelsonp@xxxxxxxxxxxxx


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rv-tech@xxxxxxxxxx
Sent: Monday, October 12, 2009 12:47 PM
To: Lukas Beeler
Subject: Re: Long IPL at SRC C600 3915

Quoting Lukas Beeler <lukas.beeler@xxxxxxxxxxxxxxxx>:

On Mon, Oct 12, 2009 at 18:22, Roger Vicker, CCP <rv-tech@xxxxxxxxxx>

wrote:

I had them hit the power button and it seemed to be starting but it has
been sitting at SRC C600 3915 for over an hour. The description is
"Licensed internal code (LIC) has initiated the load source IOP
self-load." so I am thinking this should be a quick step instead. The
customer is not reporting an alert light yet. I hope to get onsite in an
hour.

I've seen a machine stuck on this message before. It was a 250 oder
270. It was a broken disk - resolution was to pull the load source and
have the system IPL from the mirror. Worked fine after replacing the
disk.

Might be something else in your case, though.

Does this still sound like an Oh Frack or the rare Like A PC and reboot
it again?

I'd try to IPL again first. The disk controllers on the Power 520
models are rather flaky, and i've seen at least two machines that
sometimes just wouldn't IPL. A powercycle would help them get back on
track.

Onsite now.

I forgot to mention that this was a 9406-800 model.

I think this is the first time I have ever treated the IBM i like a
PC. Pulling the power cords and waiting 10 seconds after the lights in
the power supplies went completely out before rebooting seems to be
working. It went by C6003915 in under 5 minutes and and came fully
alive in 10.

Thanks.

Roger