No autoboot after a panic. DU4.0D/Alphaserver 400/233

From: Wigg, David <David.Wigg_at_wang.com>
Date: Wed, 25 Aug 1999 11:36:57 +0200

Hello Managers,
                                        I have a strangeness with an
Alphaserver 400/233 recently upgraded from DU3.2d to DU4.0D patch3
(including the firmware update).

        The system is taken to single user mode once a day to do a backup to
tape. After the backup completes, the system reboots to multiuser. This is
all scripted and runs unattended.

        On 3.2 this worked fine. Since the upgrade though, about once a week
or so, the system panics with a kernel memory fault during the shutdown part
of the reboot to multiuser. I am working on this problem at the moment, but
the real strangeness is that after the crash the system will not auto
reboot, even though I have set boot_osflags A, and set bootdef_dev DKA0(the
bootdisk)

        I really need the system to come back up automatically as this all
takes place overnight and jobs are set to run after it completes. What
happens however, is that the system crashes to the firmware prompt and just
sits there. When the operator turns up, he just types "b" and up it comes
again.

        Am I missing something? Is it possible to have the system come up
again automatically after a crash?

        By the way, the upgrade was performed by way of a fresh install.

Thanks

> Best Regards,
>
> David
>
> David Wigg
> Senior Consultant - Solutions Integration
>
> Getronics
> Phone: +44(0)161 848 4146
> Email : david.wigg_at_getronics.com
>
> mailto:david.wigg_at_wang.com
>
Received on Wed Aug 25 1999 - 09:47:02 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:39 NZDT