Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Serenade limping...

Status
Not open for further replies.

jfrancis1958

Vendor
Oct 5, 2006
38
US
Hi Everyone,

This is a Serenade. Been watching this one for a few weeks now. Stops answering with company greeting intermittently. ports appear idle, but have to power cycle to revive.

Now this morning i'm getting the following output from LOG PR CPT...

I'm suspecting the drive has been failing all along and now getting worse. Any help is appreciated.

btw, nothing noted in hardware error table.

Version is 1.1.0.2

Thanks as always.

here goes:

Procomm Plus Ready!


---------------- SYSTEM SOFTWARE RELEASE S.1.1.0-2 (03/29/96) ----------------

02/12/07 07:29:06 004 INTG_R DIR_EXT DIRECT 515 001
02/12/07 07:29:06 004 PORT OFFHOOK
02/12/07 07:29:10 003 PORT ONHOOK
02/12/07 07:29:12 004 PORT TRANSFER FLASH
02/12/07 07:29:12 004 PORT TRANSFER EXP_DT
02/12/07 07:29:13 004 PORT TRANSFER GOT_DT
02/12/07 07:29:13 004 PORT TRANSFER DELAY
02/12/07 07:29:14 004 PORT DIGIT_OUT 0
02/12/07 07:29:16 004 PORT STATUS FAST_BSY
02/12/07 07:29:17 004 PORT TRANSFER FLASH
02/12/07 07:29:25 004 PORT ONHOOK
@** ERROR IN OPENING FILE: VUSER **, Error: I/O error
** ERROR SAVING CONFIGURATION TABLE VUSER ** , Error: I/O error
** ERROR IN OPENING FILE: SYSDIST **, Error: I/O error
** ERROR SAVING CONFIGURATION TABLE SYSDIST ** , Error: I/O error
** ERROR IN OPENING FILE: SDISFRMS **, Error: I/O error
** ERROR SAVING CONFIGURATION TABLE SDISFRMS ** , Error: I/O error
** ERROR IN OPENING FILE: USTTBL **, Error: I/O error
** ERROR SAVING CONFIGURATION TABLE USTTBL ** , Error: I/O error

@log pr cpt
Specify Print Option(s):
"S"tart <time>, "E"nd <time>, "L"ine <length>, "P"age <length>, "\",
"M"ask <mask (including date and time fields)>, "C"ontinuous
Filters: PR TY EV AU MB MS SL UN LI SO D1 D2 D3 D4 D5
>c


02/12/07 07:45:58 005 PORT OFFHOOK
02/12/07 07:45:58 004 PORT DIGIT_OUT 3
02/12/07 07:45:58 004 PORT DIGIT_OUT 3
02/12/07 07:45:58 004 PORT DIGIT_OUT 8
02/12/07 07:46:01 004 PORT STATUS ANSWER
02/12/07 07:46:01 004 PORT ONHOOK
02/12/07 07:46:09 005 PORT ONHOOK
** ERROR IN OPENING FILE: USTTBL **, Error: I/O error
** ERROR SAVING CONFIGURATION TABLE USTTBL ** , Error: I/O error
02/12/07 07:46:17 006 INTG_R FWD_EXT NO_ANSWR 338 001
02/12/07 07:46:17 006 PORT OFFHOOK
02/12/07 07:46:28 006 PORT ONHOOK
02/12/07 07:46:47 007 INTG_R FWD_EXT DUP_REC 360 004
02/12/07 07:46:52 007 PORT OFFHOOK
02/12/07 07:46:57 007 PORT TRANSFER FLASH
02/12/07 07:46:57 007 PORT TRANSFER EXP_DT


.m sys
Enter system parameter index.
MOD:33
Some PBX systems may require a digit sequence to be dialed so that
system extensions get assigned to the incoming call group.
What digits, if any, should be dialed on all PORTS upon POWER-UP?
(May include: 0-9,*,#, D=DELAY, E=EXPECT DIAL TONE, or F=FLASH,
1-8 chars, empty line = NONE )
MOD:e
Enter system parameter index.
MOD:
.e

EXITING UPDATE.

WAIT... ** ERROR IN OPENING FILE: ADELYT **, Error: I/O error
** ERROR SAVING CONFIGURATION TABLE ADELYT ** , Error: I/O error
** ERROR IN OPENING FILE: DTMFINT **, Error: I/O error
** ERROR SAVING CONFIGURATION TABLE DTMFINT ** , Error: I/O error
** ERROR IN OPENING FILE: SYSP **, Error: I/O error
** ERROR SAVING CONFIGURATION TABLE SYSP ** , Error: I/O error
DONE.

SAVE configuration to a DISKETTE? ( Y/N , empty line = N ).
:y
Insert desired DISKETTE in drive. Press RETURN when ready...
WAIT. Saving configuration to DISKETTE... ** ERROR IN OPENING FILE: USTTBL **,
Error: I/O error
** ERROR SAVING CONFIGURATION TABLE USTTBL ** , Error: I/O error
DONE.



MON 02/12 07:51:44 2007 EDSD112 ID:207117 S/N:207117 PBX:07
 
Hi jfrancis1958

You seem to have a problem with your Floppy Drive and maybe your Harddisk Drive (or VCU).
Please post your alarm logg.
This is the @L H, and also the disk exersizer (@ DEX 1).
It will be easier for me to tell you what the problem is, then. Make shure that the Serenade and the PBX are commonly grounded and that ferrite cores are used on all local lines betwenn the PBX and the Serenade. Also the power cord (110/230 VAC)should have installed 3 ferrite cores. Dont restart this one! It might fail to come up again if the Harddisk is defective.
///doktor.
 
Ohhh. I saw this one now: "nothing noted in hardware error table". Anyway the DEX 1 would be nice to see...
///doktor
 
Do you happen to have captured any of the power cycles on procomm? When the system is booting there should be a few error messages.

Either way it looks like your HD is corrupted or failing, and with it being Serenade1 your options are a little limited.

If it is just corruption and not a failing disk it may be possible to re-install the software.

Jonathan
 
Thanks all.

It's pretty firm that it's the hard drive. Threw a type 40 the other day... they're still limping and i'm on my way down there in a couple of days to replace.

jeff
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top