I will be watching also. I have two PE2600 servers, the newest runs BackupExec did a similar thing Monday night and Tuesday morning. It is using Pedge3.ham v 7.01.22. The other server is my GroupWise 6.5 server and uses pedge3.ham version 7.01.15 and only runs BackupExec Remote Agent.
What is a mystery is that while only two or three weeks old it has been working fine until this week. I haven't turned it into production yet, thank heavens.
See my posting in support.netware.6x.abends-hangs forum in thread 5213:
Not sure this is an abend or not. Running BackupExec 9.1 on a NW6SP5
w/1GB RAM Dell PE2600 (New) server yesterday the server stopped with:
It's a funny one. I'm running more than a dozen poweredge 2600's, all running arcserve 9.01 and only have had the problem on 5 of them. All of them are production. The servers ran for months before the problem started happening. As far as I can tell the only difference between the bad 5 and the others is that the bad 5 also happen to have the largest amount of data on them.
I can't figure out how to duplicate it. When I reboot the servers the backup run successfully. I've been getting between 1 and 4 hangs every week for the past two months or so. I put a call into novell and they sent me a pedge3.ham 7.01.24 that didn't change anything. Havn't heard from them since. Tried arcserve patches, arcserve settings, sms patches, btrieve settings, replacing arcserve databases, nss rebuilds, and a few things I already forget doing. I even considered an animal sacrifice but decided against it. My boss didn't appreciate the idea of a live chicken in the server room.
I was going to back-rev to arcserve 7 and if that didn't work (which seems likely) I was left with swapping out hardware.
Like I said earlier, my GroupWise server has an older version of the pedge3.ham. I didn't mention it is also NWSP4 rather than SP5. Perhaps something in the SP5 is causing the change since you haven't had a problem until recently. can you roll one back to SP4 and give that a try.
I have "Gold support" on the new one and I am going to call Tech support today to ask, Where is the Beef? Ummmh I mean Drivers?
If they supply 7.01.25 or 26 whatever it is I will let you know.
Later in the day, BackupExec caller the Internal Debugger again. Info i got was this:
P01#? Address in PEDGE3.HAM at code start +00006994h Previous: -000000C4 C8A01D0 PEDGE3.HAM|getHACBandDeviceStatus Current: 00000000 08A01994 Next: +000000FC 08A01A90 PEDG3.HAM|convertEnquiryToEnquiry3
P01#u eip -10 C8A01984 DCB18C378 3C4 qword ptr [ECX-3B&CC874] C8A0198A 0C85 OR AL,85 C8A0198C DB74 ??ESC C8A0198E 05E8D81971 ADD EAX, 7119D8E8 C8A01993 37 AAA C8A01994 5F POP EDI {THIS LINE WAS pINK} C8A01995 5E POP ESI C8A01996 5B POP EBX C8A01997 C3 RET C8A01998 3C14 CMP AL, 14 C8A0199A 7234 JB C8A019D0 C8A0199C 0F8685000000 JBE C8A01A27 C8A019A2 3C22 CMP AL,22 C8A019A4 7221 JB C8A019C7 C8A019A6 0F8699000000 JBE C8A01A45 C8A019AC 3C28 CMP AL, 22
Called Dell Support for the new drivers and he is requesting a delivery date from Engineering.
Peter
Message Edited by pierrejamme on 09-16-2004 03:59 PM
Message Edited by pierrejamme on 09-16-2004 03:59 PM
I updated my two PE2600s, we will see how backup goes tonight. I noticed the older PE2600 had firmware 2.24 while the new one had 2.48. Should I upgrade the older server's firmware also? What do ineed bedsides the LSI Logic Perc 4/DI v.248 Rev 14 floppy?
The latest BIOS revision is A12, so you will want to upgrade that. ESM is Embedded Server Management firmware. You will find a category by that name under downloads for the PE2600. The latest version is a32. The name of the file is PE2600-ESMA32.exe. Download the file to your hard drive. When you run the executable, the file will open in a WinZip self-extractor. Extract the files to a floppy. Boot the server to DOS and run smflsh2.exe.
I have updated my new server's BIOS to 12. I didn't do the EMS because the bootup showed it was Embedded Server Management FM 1.74. I noticed the Primary Backplane FW was 1.01, is that the most current?
Will do the older server when I can, it is our GroupEWise 6.5 server.
pierrejamme
111 Posts
0
September 15th, 2004 17:00
BChick:
I will be watching also. I have two PE2600 servers, the newest runs BackupExec did a similar thing Monday night and Tuesday morning. It is using Pedge3.ham v 7.01.22. The other server is my GroupWise 6.5 server and uses pedge3.ham version 7.01.15 and only runs BackupExec Remote Agent.
What is a mystery is that while only two or three weeks old it has been working fine until this week. I haven't turned it into production yet, thank heavens.
See my posting in support.netware.6x.abends-hangs forum in thread 5213:
Not sure this is an abend or not. Running BackupExec 9.1 on a NW6SP5
w/1GB RAM Dell PE2600 (New) server yesterday the server stopped with:
Novell NetWare Debugger
Break Because Debug procedure was called
current focus processor: P01#
EAX=00000000 EBX=00000001 ECX=C8003F44 EDX=00000002 ESI=C8958F54
EDI=00000000 EBO=390A0BE0 ESP=8958F1C EIP=C8A01994 FLAGS=00000002
C8A0A9945F POP EDI
I could not access debugger, .c just sat there rt&lft shift, alt, esc
nothing. So powered off and restarted. did the same thing last night
when running backup for Monday. No abend.log created either time, NOT
EVEN IN C:\NWSERVER. In fact I do not have any abend.log.
Boot$log.err shows Unable to find dxevent.nlm, this file is not on the
server it is on my SP3 and SP4 servers however. I looked in the
service packs and it isn't in SP4 or SP5. Sp3 has version 10210.42.00
so the SP4 probably had it from there when I updated to sp4.
I don't know where to start looking??
should I replace TSAFS with tsa600? It has been working fine for about
three weeks.
Peter
Bchick
2 Posts
0
September 15th, 2004 19:00
It's a funny one. I'm running more than a dozen poweredge 2600's, all running arcserve 9.01 and only have had the problem on 5 of them. All of them are production. The servers ran for months before the problem started happening. As far as I can tell the only difference between the bad 5 and the others is that the bad 5 also happen to have the largest amount of data on them.
I can't figure out how to duplicate it. When I reboot the servers the backup run successfully. I've been getting between 1 and 4 hangs every week for the past two months or so. I put a call into novell and they sent me a pedge3.ham 7.01.24 that didn't change anything. Havn't heard from them since. Tried arcserve patches, arcserve settings, sms patches, btrieve settings, replacing arcserve databases, nss rebuilds, and a few things I already forget doing. I even considered an animal sacrifice but decided against it. My boss didn't appreciate the idea of a live chicken in the server room.
I was going to back-rev to arcserve 7 and if that didn't work (which seems likely) I was left with swapping out hardware.
pierrejamme
111 Posts
0
September 16th, 2004 14:00
Like I said earlier, my GroupWise server has an older version of the pedge3.ham. I didn't mention it is also NWSP4 rather than SP5. Perhaps something in the SP5 is causing the change since you haven't had a problem until recently. can you roll one back to SP4 and give that a try.
I have "Gold support" on the new one and I am going to call Tech support today to ask, Where is the Beef? Ummmh I mean Drivers?
If they supply 7.01.25 or 26 whatever it is I will let you know.
Later in the day, BackupExec caller the Internal Debugger again. Info i got was this:
P01#?
Address in PEDGE3.HAM at code start +00006994h
Previous: -000000C4 C8A01D0 PEDGE3.HAM|getHACBandDeviceStatus
Current: 00000000 08A01994
Next: +000000FC 08A01A90 PEDG3.HAM|convertEnquiryToEnquiry3
P01#u eip -10
C8A01984 DCB18C378 3C4 qword ptr [ECX-3B&CC874]
C8A0198A 0C85 OR AL,85
C8A0198C DB74 ??ESC
C8A0198E 05E8D81971 ADD EAX, 7119D8E8
C8A01993 37 AAA
C8A01994 5F POP EDI {THIS LINE WAS pINK}
C8A01995 5E POP ESI
C8A01996 5B POP EBX
C8A01997 C3 RET
C8A01998 3C14 CMP AL, 14
C8A0199A 7234 JB C8A019D0
C8A0199C 0F8685000000 JBE C8A01A27
C8A019A2 3C22 CMP AL,22
C8A019A4 7221 JB C8A019C7
C8A019A6 0F8699000000 JBE C8A01A45
C8A019AC 3C28 CMP AL, 22
Called Dell Support for the new drivers and he is requesting a delivery date from Engineering.
Peter
Message Edited by pierrejamme on 09-16-2004 03:59 PM
Message Edited by pierrejamme on 09-16-2004 03:59 PM
Carrie_1
2 Intern
•
188 Posts
0
September 18th, 2004 21:00
This driver has been released. The file name is perc-nw-7.02c-A09.exe. It can be downloaded directly at ftp://ftp.us.dell.com/scsi-raid/perc-nw-7.02c-A09.exe.
You can find the readme at ftp://ftp.us.dell.com/scsi-raid/perc-nw-7.02c-A09.txt.
Message Edited by DELL-Carrie on 09-18-2004 05:13 PM
pierrejamme
111 Posts
0
September 20th, 2004 16:00
Thanks:
I updated my two PE2600s, we will see how backup goes tonight. I noticed the older PE2600 had firmware 2.24 while the new one had 2.48. Should I upgrade the older server's firmware also? What do ineed bedsides the LSI Logic Perc 4/DI v.248 Rev 14 floppy?
Carrie_1
2 Intern
•
188 Posts
0
September 20th, 2004 17:00
pierrejamme
111 Posts
0
September 20th, 2004 18:00
Carrie_1
2 Intern
•
188 Posts
0
September 20th, 2004 19:00
The latest BIOS revision is A12, so you will want to upgrade that. ESM is Embedded Server Management firmware. You will find a category by that name under downloads for the PE2600. The latest version is a32. The name of the file is PE2600-ESMA32.exe. Download the file to your hard drive. When you run the executable, the file will open in a WinZip self-extractor. Extract the files to a floppy. Boot the server to DOS and run smflsh2.exe.
pierrejamme
111 Posts
0
September 21st, 2004 18:00
Carrie:
I have updated my new server's BIOS to 12. I didn't do the EMS because the bootup showed it was Embedded Server Management FM 1.74. I noticed the Primary Backplane FW was 1.01, is that the most current?
Will do the older server when I can, it is our GroupEWise 6.5 server.