SYS not mounting / partition error SP2 --> SP3

[globalgorrilla]

This is a show stopper, SYS will not mount.

----------------

Partition on device[v371-A2-D0:0] PERCDC
0 RAID5 rev:1.80 is invalid and requires manual repair.

All volumes and pools on this device cannot be seen until fix is made.

----------------

Can I repair this partition? RAID5 array consistency check seems fine.

Server went for restart after SP3 installation and then this.

What do you think?

Thank you very much for your help.

Regards,
--Philip

 

[marvhuffaker]

That's a hardware issue. You're probably better off calling DELL to start with.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[wonsie]

Marvin,

Are you familiar with Netware 6.5 SP3 issues. This is the second server that I have applied SP3 and it has toasted my server. The first server was a Compaq 1600 that had Netware 4.11- upgraded to 6.5 then sp3 and now I took a brand new G4 ML350 and installed Netware 6.5 fresh and then applied SP3. At the end of the SP3 installation it told me to down the server and NOT restart. I downed it and it got hung up and I had no choice but to power it off and now this server is toasted as well (same message as first server). I realize that by not downing it that the Server.exe isn't getting updated, do you know how to get around this. I have 30 servers to do... Help

 

[marvhuffaker]

Gorilla, did you get your problem fixed? I look at that now and don't know why I was so quick to blame it on the hardware. With other problems I've seen, it could have been a botch SP installation.

Wonsie, There is a documented problem in some cases where the SERVER.EXE doesn't get properly applied to the server. There are other problems I've seen with the DOS partition getting hosed (there is a different thread on this).. Best place to start is to check your SERVER.EXE file and make sure it's the same date, time, and size as the one in the Service Pack. Then do a CHKDSK /F or SCANDISK on the C: Parititon and make sure there are no errors.

If you still have problems, do a SERVER -NS and see if you can get to a Server prompt. If you can't, you have corrupt files on C:\NWSERVER.



Marvin Huffaker, MCNE

http://www.redjuju.com

 

[globalgorrilla]

No the problem was not solved. The server was reinstalled and still on SP 2 and data restored from backup.

There was some talk elsewhere of driver issues. (Perhaps not upgrading drivers during the SP install would avoid the problem...not tested.)

I have the feeling it was this last issue, the cause of problems, not a storage partition corruption etc...

I'll note here that Portlock said their Storage Manager could fix the problem (that is, they assumed based on the error messages that making an image of the disk and restoring it back (yeah!) would fix the problem.