- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- 1783 Drive Array Controller Failure after Frimware...
Disk Enclosures
1752710
Members
6029
Online
108789
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
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
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
04-18-2002 04:00 PM
04-18-2002 04:00 PM
1783 Drive Array Controller Failure after Frimware Update
I?ve just built 4 x ML530 Rackmount Servers to the following specification ?
Dual PIII Xeon 1000, 1GB RAM, SMART Array 5304 with 128MB Cache,
Additional Drive Cage, Full Power and Fan Redundancy,
12 x 18.2GB 10K-II Ultra-3 Disks, configured as 2 x Arrays ?
Array A = 2 x Disks RAID 1 + Global Spare
Array B = 9 x Disks RAID ADG + Global Spare
40/80GB Internal DLT
NC3134 Dual Port NIC (replacing the standard NC3123)
Running Windows 2000 Advanced Server
I checked the System ROM was the latest version - V.4.08A (08/04/2001) and updated the Array Controller firmware to V.2.32. After which, the controller reported a 1770 POST error telling me that some of my drives required their firmware updating. I ran the Options ROMPaq for Internal SCSI Attached Drives, V3.02A which updated the drives to firmware revision B010.
Now, intermittently, during Array Controller initialisation, I get the following message ?
1783 ? Slot 8 Drive Array Controller Failure
[command failure (cmd=0h, err=00h, dlu=0f013:1e7fh)]
and the Server cannot continue booting. This happens on all 4 x Servers.
Do I have 4 faulty Array Controllers?
Is the controller and/or disk firmware at fault?
Has anyone else experienced or resolved this problem?
Does anyone from Compaq have a solution?
Dual PIII Xeon 1000, 1GB RAM, SMART Array 5304 with 128MB Cache,
Additional Drive Cage, Full Power and Fan Redundancy,
12 x 18.2GB 10K-II Ultra-3 Disks, configured as 2 x Arrays ?
Array A = 2 x Disks RAID 1 + Global Spare
Array B = 9 x Disks RAID ADG + Global Spare
40/80GB Internal DLT
NC3134 Dual Port NIC (replacing the standard NC3123)
Running Windows 2000 Advanced Server
I checked the System ROM was the latest version - V.4.08A (08/04/2001) and updated the Array Controller firmware to V.2.32. After which, the controller reported a 1770 POST error telling me that some of my drives required their firmware updating. I ran the Options ROMPaq for Internal SCSI Attached Drives, V3.02A which updated the drives to firmware revision B010.
Now, intermittently, during Array Controller initialisation, I get the following message ?
1783 ? Slot 8 Drive Array Controller Failure
[command failure (cmd=0h, err=00h, dlu=0f013:1e7fh)]
and the Server cannot continue booting. This happens on all 4 x Servers.
Do I have 4 faulty Array Controllers?
Is the controller and/or disk firmware at fault?
Has anyone else experienced or resolved this problem?
Does anyone from Compaq have a solution?
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP