Long BCM50 reboot time after long uptime

[linuxsense]

We have a BCM50 that needed to have its power interrupted after a long period of uptime and now the reboot process is taking a very long time (30 minutes as of now). The power LED is solid green and the status LED is solid yellow, the phones are also flashing. The BCM50 is not reachable via LAN. Could this unit be performing a fsck or is this way outside of the norm? Unfortunately I am not local to the BCM50 and the staff that I can use for troubleshooting on-site has limited technical skills so I am hoping this is just due to a long running fsck ;-)

Thanks for any insight.

 

[stsguy]

you need to unplug the bcm for at least 2 minutes, then plug her back in.

 

[foneman1]

FYI - I am assuming that you have 3.0 software. This is a beta patch and available thru Nortel tech support only. I would reboot the system like stsguy said and then get the patch.

BCM50 3.0
======================
PATCH ID: BCM050.R300.UBOOT-214 Category: GEN
-----------------------------------------------------------------

Description:
-----------
The following issue is addressed:

1. BCM may not start after reboot due to some anomaly in u-boot
Systems with Seagate hard drives, intermittently fails to boot.
This was due to some issue with the default setting of SATA controller.
This update resolves the issue.
Q02052788-01

2. Corruption of enigma logs
The enigma log may become corrupted if power is pulled while it is being
written. As the result system fails to boot. This update resolves the issue.
Q01864365-01

 

[linuxsense]

Thanks for the feedback, I'll have someone unplug it for a few minutes and give it another shot.

Thanks again.