Anonymous_User Absent Member.
Absent Member.
3119 views

More Netware 6.5 Service Pack 3 woes

I have just SP3'd my fourth server.
The first one went fine.
The second and third installed ok but there were iPrint issues which now
seem to have magically disappeared. Clicking on the printer info link on the
iPrint webpage would abend the server even after applying iPrntNWPCSP12b.exe
but that has now stopped happening. Don't know why.
I just applied SP3 to a fourth server (doesn't run NDPS), rebooted it and
then applied NW65OS3a and then N65NSS3a, rebooted it again and went to the
little boys room. I returned to find the following message on the screen:

ERROR: critical sectioning prevents requested FATFS operation
ERROR: critical sectioning prevents requested FATFS operation

I could do nothing but reset the server.
The server boots up ok now and seems fine but when I load LDNCS.NCF it sits
there trying to join the cluster for about five minutes before giving the
following errors:


2-08-2005 10:37:00 am: COMN-3.22-34 [nmID=60010]
NSS-2.70-5005: Volume PENGUIN/SYS user data write
(20204(zio.c[2201])) to block 205242(file block 0)(ZID 2267100) failed.


2-08-2005 10:37:00 am: COMN-3.22-1092 [nmID=A0025]
NSS-3.00-5001: Pool PENGUIN/SYS is being deactivated.
An I/O error (20204(zio.c[2179])) at block 1617636(file block 6951)(ZID
3)
has compromised pool integrity.


2-08-2005 10:37:00 am: DS-10551.78-266
Bindery close requested by the SERVER


2-08-2005 10:37:02 am: DS-10551.78-263
Directory Services: Local database has been closed


2-08-2005 10:37:03 am: SERVER-5.70-1534 [nmID=B0013]
Device "[V651-A5-D0:0] DELL RAID Device 0:00 rev:1.0" deactivated by
driver due to device failure.


Something has broken my SYS volume. I'll run NSS verifies and so on but I've
done them before so I don't hold out much hope, admittedly that was a long
time ago.
Needless to say that what with this and the experiences of others in the
forums I'll not be service packing any more servers any time soon.
If it aint broke, don't fix it.


Mark


Labels (2)
0 Likes
10 Replies
Anonymous_User Absent Member.
Absent Member.

Re: More Netware 6.5 Service Pack 3 woes

Just ran NSS Poolverify on SYS only for it to tell me that there were no
errors.
I rebooted the server again and was once more presented with:

ERROR: critical sectioning prevents requested FATFS operation
ERROR: critical sectioning prevents requested FATFS operation
ERROR: critical sectioning prevents requested FATFS operation


I am not having a good day.



"Marky" <me@here.com> wrote in message
news:BoHHe.15486$Y_1.12018@prv-forum2.provo.novell.com...
>I have just SP3'd my fourth server.
> The first one went fine.
> The second and third installed ok but there were iPrint issues which now
> seem to have magically disappeared. Clicking on the printer info link on
> the iPrint webpage would abend the server even after applying
> iPrntNWPCSP12b.exe but that has now stopped happening. Don't know why.
> I just applied SP3 to a fourth server (doesn't run NDPS), rebooted it and
> then applied NW65OS3a and then N65NSS3a, rebooted it again and went to the
> little boys room. I returned to find the following message on the screen:
>
> ERROR: critical sectioning prevents requested FATFS operation
> ERROR: critical sectioning prevents requested FATFS operation
>
> I could do nothing but reset the server.
> The server boots up ok now and seems fine but when I load LDNCS.NCF it
> sits there trying to join the cluster for about five minutes before giving
> the following errors:
>
>
> 2-08-2005 10:37:00 am: COMN-3.22-34 [nmID=60010]
> NSS-2.70-5005: Volume PENGUIN/SYS user data write
> (20204(zio.c[2201])) to block 205242(file block 0)(ZID 2267100)
> failed.
>
>
> 2-08-2005 10:37:00 am: COMN-3.22-1092 [nmID=A0025]
> NSS-3.00-5001: Pool PENGUIN/SYS is being deactivated.
> An I/O error (20204(zio.c[2179])) at block 1617636(file block
> 6951)(ZID 3)
> has compromised pool integrity.
>
>
> 2-08-2005 10:37:00 am: DS-10551.78-266
> Bindery close requested by the SERVER
>
>
> 2-08-2005 10:37:02 am: DS-10551.78-263
> Directory Services: Local database has been closed
>
>
> 2-08-2005 10:37:03 am: SERVER-5.70-1534 [nmID=B0013]
> Device "[V651-A5-D0:0] DELL RAID Device 0:00 rev:1.0" deactivated by
> driver due to device failure.
>
>
> Something has broken my SYS volume. I'll run NSS verifies and so on but
> I've done them before so I don't hold out much hope, admittedly that was a
> long time ago.
> Needless to say that what with this and the experiences of others in the
> forums I'll not be service packing any more servers any time soon.
> If it aint broke, don't fix it.
>
>
> Mark
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: More Netware 6.5 Service Pack 3 woes

The errors you have seem to indicate problems with your disk controller
or maybe drivers.
You seem to have some Dell server. Could you please tell us what exact
raid controller you are using, what firmware version you have and what
exact driver you are using (including version)?

--
Marcel Cox
http://support.novell.com/forums
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: More Netware 6.5 Service Pack 3 woes

Marky:

> 2-08-2005 10:37:00 am: COMN-3.22-1092 [nmID=A0025]
> NSS-3.00-5001: Pool PENGUIN/SYS is being deactivated.
> An I/O error (20204(zio.c[2179])) at block 1617636(file block 6951)(ZID
> 3)
> has compromised pool integrity.
>


I would run an nss /poolrebuild on SYS - it looks like you have a bad block on
the disk

Joe Moore
Novell Support Forums SysOp
http://just.fdisk-it.com
http://www.caledonia.net/jmdns.html
http://www.caledonia.net/nesadmin.html
http://www.caledonia.net/jmttb.html


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: More Netware 6.5 Service Pack 3 woes


Mark, I'm right there with you. Ready to jump out the window.

Marky wrote:
> Just ran NSS Poolverify on SYS only for it to tell me that there were no
> errors.
> I rebooted the server again and was once more presented with:
>
> ERROR: critical sectioning prevents requested FATFS operation
> ERROR: critical sectioning prevents requested FATFS operation
> ERROR: critical sectioning prevents requested FATFS operation
>
>
> I am not having a good day.
>
>
>
> "Marky" <me@here.com> wrote in message
> news:BoHHe.15486$Y_1.12018@prv-forum2.provo.novell.com...
>
>>I have just SP3'd my fourth server.
>>The first one went fine.
>>The second and third installed ok but there were iPrint issues which now
>>seem to have magically disappeared. Clicking on the printer info link on
>>the iPrint webpage would abend the server even after applying
>>iPrntNWPCSP12b.exe but that has now stopped happening. Don't know why.
>>I just applied SP3 to a fourth server (doesn't run NDPS), rebooted it and
>>then applied NW65OS3a and then N65NSS3a, rebooted it again and went to the
>>little boys room. I returned to find the following message on the screen:
>>
>>ERROR: critical sectioning prevents requested FATFS operation
>>ERROR: critical sectioning prevents requested FATFS operation
>>
>>I could do nothing but reset the server.
>>The server boots up ok now and seems fine but when I load LDNCS.NCF it
>>sits there trying to join the cluster for about five minutes before giving
>>the following errors:
>>
>>
>>2-08-2005 10:37:00 am: COMN-3.22-34 [nmID=60010]
>> NSS-2.70-5005: Volume PENGUIN/SYS user data write
>> (20204(zio.c[2201])) to block 205242(file block 0)(ZID 2267100)
>>failed.
>>
>>
>>2-08-2005 10:37:00 am: COMN-3.22-1092 [nmID=A0025]
>> NSS-3.00-5001: Pool PENGUIN/SYS is being deactivated.
>> An I/O error (20204(zio.c[2179])) at block 1617636(file block
>>6951)(ZID 3)
>> has compromised pool integrity.
>>
>>
>>2-08-2005 10:37:00 am: DS-10551.78-266
>> Bindery close requested by the SERVER
>>
>>
>>2-08-2005 10:37:02 am: DS-10551.78-263
>> Directory Services: Local database has been closed
>>
>>
>>2-08-2005 10:37:03 am: SERVER-5.70-1534 [nmID=B0013]
>> Device "[V651-A5-D0:0] DELL RAID Device 0:00 rev:1.0" deactivated by
>> driver due to device failure.
>>
>>
>>Something has broken my SYS volume. I'll run NSS verifies and so on but
>>I've done them before so I don't hold out much hope, admittedly that was a
>>long time ago.
>>Needless to say that what with this and the experiences of others in the
>>forums I'll not be service packing any more servers any time soon.
>>If it aint broke, don't fix it.
>>
>>
>>Mark
>>

>
>
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: More Netware 6.5 Service Pack 3 woes

I've run a pool rebuild and it's not made a difference.
But what does 'ERROR: critical sectioning prevents requested FATFS
operation' mean?

Mr Cox, the server in question is an aging Dell PowerEdge 4400. The RAID
controller is a PERC 3/Di bios version 2.1-3 build 2951 using driver
PERC2.HAM version 2.80 dated 1 November 2004. Are you suggesting I try
going back to the previous driver?

I'm thinking of giving up and starting again using a spare Dell 2650 I have.
Fortunately the unwell server is part of a cluster and has no replicas or
data on it so replacing it shouldn't be too much of an issue. I hope.
Fingers crossed.



"Joseph Moore [SysOp]" <joem@*spam*is*evil*fdisk-it.com> wrote in message
news:VA.000018d5.00556027@hostname.not.set.up...
> Marky:
>
>> 2-08-2005 10:37:00 am: COMN-3.22-1092 [nmID=A0025]
>> NSS-3.00-5001: Pool PENGUIN/SYS is being deactivated.
>> An I/O error (20204(zio.c[2179])) at block 1617636(file block
>> 6951)(ZID
>> 3)
>> has compromised pool integrity.
>>

>
> I would run an nss /poolrebuild on SYS - it looks like you have a bad
> block on
> the disk
>
> Joe Moore
> Novell Support Forums SysOp
> http://just.fdisk-it.com
> http://www.caledonia.net/jmdns.html
> http://www.caledonia.net/nesadmin.html
> http://www.caledonia.net/jmttb.html
>
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: More Netware 6.5 Service Pack 3 woes

I'm currently having the same problem with a 2650, so I'm not sure that
may solve yours. I just updated my controller's BIOS to 2.80, so I'll
let you know how that goes.

Marky wrote:
> I've run a pool rebuild and it's not made a difference.
> But what does 'ERROR: critical sectioning prevents requested FATFS
> operation' mean?
>
> Mr Cox, the server in question is an aging Dell PowerEdge 4400. The RAID
> controller is a PERC 3/Di bios version 2.1-3 build 2951 using driver
> PERC2.HAM version 2.80 dated 1 November 2004. Are you suggesting I try
> going back to the previous driver?
>
> I'm thinking of giving up and starting again using a spare Dell 2650 I have.
> Fortunately the unwell server is part of a cluster and has no replicas or
> data on it so replacing it shouldn't be too much of an issue. I hope.
> Fingers crossed.
>
>
>
> "Joseph Moore [SysOp]" <joem@*spam*is*evil*fdisk-it.com> wrote in message
> news:VA.000018d5.00556027@hostname.not.set.up...
>
>>Marky:
>>
>>
>>>2-08-2005 10:37:00 am: COMN-3.22-1092 [nmID=A0025]
>>> NSS-3.00-5001: Pool PENGUIN/SYS is being deactivated.
>>> An I/O error (20204(zio.c[2179])) at block 1617636(file block
>>>6951)(ZID
>>>3)
>>> has compromised pool integrity.
>>>

>>
>>I would run an nss /poolrebuild on SYS - it looks like you have a bad
>>block on
>>the disk
>>
>>Joe Moore
>>Novell Support Forums SysOp
>>http://just.fdisk-it.com
>>http://www.caledonia.net/jmdns.html
>>http://www.caledonia.net/nesadmin.html
>>http://www.caledonia.net/jmttb.html
>>
>>

>
>
>

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: More Netware 6.5 Service Pack 3 woes

Marky wrote:

> Mr Cox, the server in question is an aging Dell PowerEdge 4400. The
> RAID controller is a PERC 3/Di bios version 2.1-3 build 2951 using
> driver PERC2.HAM version 2.80 dated 1 November 2004. Are you
> suggesting I try going back to the previous driver?


1) You must make sure that firmware and driver versions match for PERC
controlelrs using the PERC2.HAM driver

2) There is a serious bug in PERC2.HAM drivers up to an old version
2.80 making it incorrectly see partition bounderies on certain NetWare
versions (I think NW65 SP2 and SP3 for instance is affected). You
absolutely have to upgrade to version 2.80 dated November 2004 or later.
The bug can indeed cause pool deactivations like the one you see.
As Dell did a blind rev on the PREC2.HAM v2.80 driver it is important
that you check the date and not just the version number. Only the new
version fixes the bug.
You seem to be using the correct driver already. Therefor, do
absolutely not downgrade your driver!


--
Marcel Cox
http://support.novell.com/forums
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: More Netware 6.5 Service Pack 3 woes

I'm confused, you say that this error was exhibited by the old driver and
not the new one.
Yet I've not seen this problem before and I'm only seeing it now with the
new driver. Perhaps the issue is not driver related?


Mark


"Marcel Cox" <cimetmc@myrealbox.com> wrote in message
news:6%ZHe.16500$Y_1.12502@prv-forum2.provo.novell.com...
> Marky wrote:
>
>> Mr Cox, the server in question is an aging Dell PowerEdge 4400. The
>> RAID controller is a PERC 3/Di bios version 2.1-3 build 2951 using
>> driver PERC2.HAM version 2.80 dated 1 November 2004. Are you
>> suggesting I try going back to the previous driver?

>
> 1) You must make sure that firmware and driver versions match for PERC
> controlelrs using the PERC2.HAM driver
>
> 2) There is a serious bug in PERC2.HAM drivers up to an old version
> 2.80 making it incorrectly see partition bounderies on certain NetWare
> versions (I think NW65 SP2 and SP3 for instance is affected). You
> absolutely have to upgrade to version 2.80 dated November 2004 or later.
> The bug can indeed cause pool deactivations like the one you see.
> As Dell did a blind rev on the PREC2.HAM v2.80 driver it is important
> that you check the date and not just the version number. Only the new
> version fixes the bug.
> You seem to be using the correct driver already. Therefor, do
> absolutely not downgrade your driver!
>
>
> --
> Marcel Cox
> http://support.novell.com/forums



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: More Netware 6.5 Service Pack 3 woes

Marky wrote:

> I'm confused, you say that this error was exhibited by the old driver
> and not the new one. Yet I've not seen this problem before and I'm
> only seeing it now with the new driver. Perhaps the issue is not
> driver related?


Check part 1) of my reply. It is always a problem for the PERC2.HAM
driver if there is a mismatch between driver and firmware. You should
first update your firmware to v2.80 and see if that makes a difference.
Furthermore, as for the driver problem, it is present in older drivers
as well. It is just uncovered by the newer SCSIHD.CDM in newer support
packs.

--
Marcel Cox
http://support.novell.com/forums
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: More Netware 6.5 Service Pack 3 woes

Ah, I really must read more carefully in future.

I've found the newest version of the PERC bios which is 2.8. My fear is that
I could upgrade the bios and driver to version 2.8 only for the problem not
to go away. Afterall, I have only seen this problem with the 2.8 driver. Is
it possible to regress the BIOS of a PERC controller?
All I know is that this server has been running for almost a year now with
SP2 using the older PERC2 driver. It's one of a pair of 4400s and neither
has ever exhibited this problem. So I've reverted to the previous driver and
the server is now up and in the cluster. If the problem resurfaces at any
point then I shall know what I must do.

I think everyone should go back to pen and paper. Computers are evil. 😉

Thanks for your help

Mark


"Marcel Cox" <cimetmc@myrealbox.com> wrote in message
news:3j_He.16512$Y_1.5119@prv-forum2.provo.novell.com...
> Marky wrote:
>
>> I'm confused, you say that this error was exhibited by the old driver
>> and not the new one. Yet I've not seen this problem before and I'm
>> only seeing it now with the new driver. Perhaps the issue is not
>> driver related?

>
> Check part 1) of my reply. It is always a problem for the PERC2.HAM
> driver if there is a mismatch between driver and firmware. You should
> first update your firmware to v2.80 and see if that makes a difference.
> Furthermore, as for the driver problem, it is present in older drivers
> as well. It is just uncovered by the newer SCSIHD.CDM in newer support
> packs.
>
> --
> Marcel Cox
> http://support.novell.com/forums



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.