GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Netservers
- >
- Re: Smart Array 3200 & NetServer LH3 NMI: Memory P...
Netservers
1847203
Members
4506
Online
110263
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-27-2004 11:38 AM
10-27-2004 11:38 AM
Smart Array 3200 & NetServer LH3 NMI: Memory Parity Error
I've installed w2003 server on a netserver lh3.
S.O. is installed in a RAID1 volume attached to the NetRaid controller (C:), and i have 1 storage unit attached to the Smart array 3200 controller, which have 2 volumes (D: y E:) The problem is when i copy and paste or move files from any volume on the storage to volume C: or to the other volume in the storage.
the server stops responding and display a blue screen with the following message:
*** Hardware Malfunction
Call your hardware vendor for support
*** The system has halted ***
NMI: Parity Check / Memory Parity Error
Firmware, Drivers, BIOS, ACU are up to date.
From C: to D: or E: no problems, only from D: to C: or From E: to C:
I also have tried remplacing memory, removing other devices and nothing
Any Suggestions???
Best regards.
S.O. is installed in a RAID1 volume attached to the NetRaid controller (C:), and i have 1 storage unit attached to the Smart array 3200 controller, which have 2 volumes (D: y E:) The problem is when i copy and paste or move files from any volume on the storage to volume C: or to the other volume in the storage.
the server stops responding and display a blue screen with the following message:
*** Hardware Malfunction
Call your hardware vendor for support
*** The system has halted ***
NMI: Parity Check / Memory Parity Error
Firmware, Drivers, BIOS, ACU are up to date.
From C: to D: or E: no problems, only from D: to C: or From E: to C:
I also have tried remplacing memory, removing other devices and nothing
Any Suggestions???
Best regards.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-10-2004 07:45 PM
11-10-2004 07:45 PM
Re: Smart Array 3200 & NetServer LH3 NMI: Memory Parity Error
Hi Samuel,
We've had the same error on a proliant with windows 2003 server. Its happened twice when we rebooted th server without switching on the Quantum tape unit. Its probably coincidence but once the error occurs we have to rebuild/repair windows 2003. I would love to know if you ever discovered the cause of the error
Regards
Huw Godsell
We've had the same error on a proliant with windows 2003 server. Its happened twice when we rebooted th server without switching on the Quantum tape unit. Its probably coincidence but once the error occurs we have to rebuild/repair windows 2003. I would love to know if you ever discovered the cause of the error
Regards
Huw Godsell
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP