Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
1719 views

NW6.5SP5 Abend

This morning the server was a blue screen of death (netware version) with multiple abends. The only process running at the time was Arcserve backup ver 11 r1. The abend log listed the reason for the abend:

Abend 2 on P00: Server-5.70.05-0: SubAllocFreeSectors given invalid FAT chain end that was already free.

Additional Information:
The NetWare OS detected a problem with the system while executing a process owned by FILESYS.NLM. It may be the source of the problem or there may have been a memory corruption.

Can thoughts on this and a troubleshooting path to find and fix the problem?

Thank you
Labels (1)
Tags (2)
0 Likes
5 Replies
Absent Member.
Absent Member.

Please post your last complet "abend 1" entry from your abend.log file (or simply the whole file if it isn't too big). Note that you are already 3 SP levels behind. You are only at SP5, but currently, we are at SP8 already.
0 Likes
Absent Member.
Absent Member.

Thank you for replying to the thread. I am aware of the issue regarding the SP5 to SP8. I am posting the abend from January 31, the date of the abend: The log was too long so I had to shorten it.

Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.05

Server TREP1 halted Saturday, January 31, 2009 12:09:10.860 am
Abend 1 on P00: Server-5.70.05-0: SubAllocFreeSectors given invalid FAT chain end that was already free.

Registers:
CS = 0060 DS = 007B ES = 007B FS = 007B GS = 007B SS = 0068
EAX = BBAAA000 EBX = 00000002 ECX = BBAB226B EDX = 17510000
ESI = 001D7494 EDI = 831D7494 EBP = 81C0E100 ESP = A6E4DE1C
EIP = BBA72EBC FLAGS = 00000202
BBA72EBC 83C404 ADD ESP, 00000004
EIP in FILESYS.NLM at code start +0006AEBCh

The violation occurred while processing the following instruction:
BBA72EBC 83C404 ADD ESP, 00000004
BBA72EBF 8B1C24 MOV EBX, [ESP]
BBA72EC2 C1E302 SHL EBX, 02
BBA72EC5 01EB ADD EBX, EBP
BBA72EC7 8BBB34040000 MOV EDI, [EBX+00000434]
BBA72ECD 47 INC EDI
BBA72ECE 8B8334060000 MOV EAX, [EBX+00000634]
BBA72ED4 89BB34040000 MOV [EBX+00000434], EDI
BBA72EDA 39C6 CMP ESI, EAX
BBA72EDC 7306 JNB BBA72EE4



Running process: Server 736 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: A6E4DF80
OS Stack limit: A6E46040
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work
Stack: --BBAB226B (FILESYS.NLM|lDOSFirstByteBitMap+85FB)
--00000003 (LOADER.NLM|KernelAddressSpace+3)
--A6E4DE6C ?
--00000016 (LOADER.NLM|KernelAddressSpace+16)
--00000017 (LOADER.NLM|KernelAddressSpace+17)
--831D7494 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000002 (LOADER.NLM|KernelAddressSpace+2)
BBA8FBD0 (FILESYS.NLM|INWRemoveFile+2C8)
--00000002 (LOADER.NLM|KernelAddressSpace+2)
--831D7494 ?
--8D6759A0 ?
-004858FB ?
--9E681BE8 ?
--8C073180 ?
--00000017 (LOADER.NLM|KernelAddressSpace+17)
BBA1E6FB (FILESYS.NLM|CompressBuildPath+27B)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
-004858FB ?
--48AFFDF5 ?
--4C4F563C ?
--4C4F5F31 ?
--412F3A44 ?
--2F535050 ?
--474E564F ?
--2F444952 ?
--41544144 ?
--3157442F ?
--34332D38 ?
--3335302F ?
--2F363030 ?
--54534F42 ?
--534F422F ?
--58465754 ?
--53432E54 ?
--BBEAE456 ?
B866F40D (MM.NLM|MM_CompleteMessage+35)
--C60800EA ?
--00000006 (LOADER.NLM|KernelAddressSpace+6)
B866F41F (MM.NLM|MM_CompleteMessage+47)
--BBEAE4E4 ?
--A6E4DED8 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000002 (LOADER.NLM|KernelAddressSpace+2)
--00000003 (LOADER.NLM|KernelAddressSpace+3)
B867CDA7 (MM.NLM|HotfixCheckCompletion+103)
--00000046 (LOADER.NLM|KernelAddressSpace+46)
00115346 (LOADER.NLM|kSpinUnlockRestore+26)
--00000046 (LOADER.NLM|KernelAddressSpace+46)
0035ED68 (SERVER.NLM|ScheduleInterruptTimeCallBack+6D)
-001484A0 (LOADER.NLM|kIntTimeCallBackSpinLock+0)
--00000046 (LOADER.NLM|KernelAddressSpace+46)
--00000002 (LOADER.NLM|KernelAddressSpace+2)
0025FA04 (SERVER.NLM|AESProcessCleanupProcedure+278)
--00000002 (LOADER.NLM|KernelAddressSpace+2)
-B9D16610 (LSL.NLM|LSLServiceEventsFWTD+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
-813318E8 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
0025F4F3 (SERVER.NLM|ScheduleNoSleepAESProcessEvent+F)
-813318E8 ?
--534E4541 ?
BFA49FF4 (THREADS.NLM|_FillStructure+174)
-813318E8 ?
--00000246 (LOADER.NLM|KernelAddressSpace+246)
--00000046 (LOADER.NLM|KernelAddressSpace+46)
--C07EE500 ?
--BFC2F180 (LSAPI.NLM|NLSGetInternalVersionInfoLSAPI+9BE2)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--C07EEBE0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--5041045E ?
--4F075350 ?
--52474E56 ?
--44044449 ?
--07415441 ?
--38315744 ?
--0634332D ?
--30333530 ?
--42043630 ?
--0C54534F ?
--54534F42 ?
--54584657 ?
--5653432E ?
--8C073180 ?
--9E681BE8 ?
BBA1E6B4 (FILESYS.NLM|CompressBuildPath+234)
0035E622 (SERVER.NLM|StartWorkToDo+23)
--8C073180 ?
--48AFFDF5 ?
--9E681BE8 ?
--FE169F60 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
0021173C (SERVER.NLM|WorkerThread+508)
--8C073180 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8C6AA1E0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8C6AA1E0 ?
0021E6C8 (SERVER.NLM|TcoNewSystemThreadEntryPoint+40)

Additional Information:
The NetWare OS detected a problem with the system while executing a process owned by FILESYS.NLM. It may be the source of the problem or there may have been a memory corruption.

Loaded Modules:
FSTAPE2.NLM BrightStor ARCserve r11.1 SP3 File Server Backup/Restore (Build 991.000 02/06/07)
Version 11.10 February 6, 2007
Code Address: A51FB000h Length: 0004AAEDh
Data Address: A5B95000h Length: 00026810h
TSANDS.NLM TSA for Novell eDirectory 7.x, 8.x
Version 10551.71 July 19, 2005
Code Address: A671E000h Length: 000125DCh
Data Address: 8B5A6000h Length: 00001410h
POLIMGR.NLM NetWare License Policy Manager
Version 6.27 November 3, 2005
Code Address: A5999000h Length: 00013F5Ch
Data Address: A59AD000h Length: 00008E90h
NLSTRAP.NLM NetWare License Server Trap
Version 5.02 February 19, 2004
Code Address: 81BCA000h Length: 0000298Ah
Data Address: 81ADC000h Length: 00000695h
NLSLSP.NLM NLS - License Service Provider
Version 5.02 May 25, 2005
Code Address: 94170000h Length: 0006DF03h
Data Address: A58E0000h Length: 000205DCh
0 Likes
Absent Member.
Absent Member.

From what I can see, the abend occurs during backup. However given you
only a small part of your abend.log, I cannopt see if maybe you have
problematic things loaded on your server.

Overall, I suggest you should proceed as following:

1) Post your server config:
For this, could you download the latest config.nlm from
http://download.novell.com/Download?buildid=C6he4eKewtU~ , install it to
the sys:system directory of your server and then from the server console,
execute the following command:
load config /sma1bjue

Review the resulting config.txt file to remove any passwords and other
security relevant information and then post it here. Use the attachment
option, do not copy and paste the config. If possble, zip the config file
before posting it. That will save a lot of space and time up and
downloading it.

2) Give some history information on your server. How long does this
problem exist? Was there any kind of update or change to the server that
caused it to occur first?

3) The abend suggests that you have at least one traditional volume on
your server. What is the reason for having traditional volumes? Is there
some compatibility restriction, or was your server upgraded from an old
NetWare version? Did you tune your server for the existance of traditional
volumes

4) Of course, you should consider updating to a current support pack
sooner or later. Is there any partitcular reason why you are still on such
an old SP?

--
Marcel Cox
http://support.novell.com/forums
------------------------------------------------------------------------
Marcel Cox's Profile: http://forums.novell.com/member.php?userid=8
0 Likes
Absent Member.
Absent Member.

Aside from Marcel's excellent advice, I'd suggest you run a VRepair with options 2 and 4 ON, against all non-NSS volume son that server.

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
Absent Member.
Absent Member.

That is all good advice. The only thing I would add is to go to SP7 or SP8.

jgray
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.