- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: Storageworks 30 Questions, Boot Failure after ...
Disk Enclosures
1753534
Members
5234
Online
108795
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
01-31-2008 09:31 AM
01-31-2008 09:31 AM
Storageworks 30 Questions, Boot Failure after attaching
Ok....
I've got a HP Storageworks 30 Dual Bus Modular Smart Array P/N: 302970-B21.
I installed a HP Smart RAID Array 6402/128 Controller P/N: 273915-B21 in my HP DL380 Windows 2003 R2 SP2 test server and it was recognized and listed in the devices menu. I checked for the latest driver and it was up to date.
I shut down the server, and connected both busses of the Array to the array controller with the suppplied cables. I inserted 4 HP 146GB drives into the array, and powered it on. Then I powered up the server.
Everything worked fine. The array initialized, I used the array management utility to create a RAID 6 array, and successfully managed it as a Windows volume, and gave it a drive letter and wrote some files to it. Then I shut it all down, and powered off the array.
Next, I powered down the production server of the same model, installed an identical array controller card, booted it and checked that it was recognized.
So I shut down the production server, and connected it to the same array as above, with the four drives in it.
I powered the production server on, and it appeared to initialized the array and start the Windows boot process---the black MS Windows screen appeared with the clunky progress bars....and it stayed that way for about 20 minutes, at which time I used the front power switch to shut it down hard.
I powered down the array, disconnected it, and booted the server, and it booted up fine and it back in production, albeit without the array attached.
So what went wrong?
Am I correct in that I should always power off the SCSI bus equipment before connecting and disconnecting it? I haven't worked with SCSI equipment since SCSI2 was the standard.
Is there a problem with attaching the already configured array to the server?
Did I just not wait long enough? This server typically boots up completely within 5 minutes or maybe less. The identical test server booted quite quickly when I originally installed the unconfigured array to it.
Any help is appreciated.
There was a POST error in the HP Management log viewer: 1785-Drive Array not Configured, severity caution. I believe this probably occured when I booted the mahcine with the array attached, but it only got logged after the successful boot without the array attached. It looks like I forgot to check for SCSI array adapter driver updates, on the failed server it is 5.68.0.32 and on the successful server it is 5.78.0.32
I will update that driver but lets assume it isn't the problem, what else should I check?
As an aside, is there a way to set the System Management Homepage password? It claims that it is using host os authentication but I can't get in with my AD account, nor with the local admin password!
I've got a HP Storageworks 30 Dual Bus Modular Smart Array P/N: 302970-B21.
I installed a HP Smart RAID Array 6402/128 Controller P/N: 273915-B21 in my HP DL380 Windows 2003 R2 SP2 test server and it was recognized and listed in the devices menu. I checked for the latest driver and it was up to date.
I shut down the server, and connected both busses of the Array to the array controller with the suppplied cables. I inserted 4 HP 146GB drives into the array, and powered it on. Then I powered up the server.
Everything worked fine. The array initialized, I used the array management utility to create a RAID 6 array, and successfully managed it as a Windows volume, and gave it a drive letter and wrote some files to it. Then I shut it all down, and powered off the array.
Next, I powered down the production server of the same model, installed an identical array controller card, booted it and checked that it was recognized.
So I shut down the production server, and connected it to the same array as above, with the four drives in it.
I powered the production server on, and it appeared to initialized the array and start the Windows boot process---the black MS Windows screen appeared with the clunky progress bars....and it stayed that way for about 20 minutes, at which time I used the front power switch to shut it down hard.
I powered down the array, disconnected it, and booted the server, and it booted up fine and it back in production, albeit without the array attached.
So what went wrong?
Am I correct in that I should always power off the SCSI bus equipment before connecting and disconnecting it? I haven't worked with SCSI equipment since SCSI2 was the standard.
Is there a problem with attaching the already configured array to the server?
Did I just not wait long enough? This server typically boots up completely within 5 minutes or maybe less. The identical test server booted quite quickly when I originally installed the unconfigured array to it.
Any help is appreciated.
There was a POST error in the HP Management log viewer: 1785-Drive Array not Configured, severity caution. I believe this probably occured when I booted the mahcine with the array attached, but it only got logged after the successful boot without the array attached. It looks like I forgot to check for SCSI array adapter driver updates, on the failed server it is 5.68.0.32 and on the successful server it is 5.78.0.32
I will update that driver but lets assume it isn't the problem, what else should I check?
As an aside, is there a way to set the System Management Homepage password? It claims that it is using host os authentication but I can't get in with my AD account, nor with the local admin password!
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2008 09:36 AM
01-31-2008 09:36 AM
Re: Storageworks 30 Questions, Boot Failure after attaching
Ok, please disregard my problems with the system management utility...just a fat finger problem...
Here is version information.
Name Installed Version
HP Insight Management Agents for Windows 2000/Server 2003 7.40.0.0
ATI2MPAD Miniport Driver 5.10.2600.6013
HP Array Configuration Utility 7.40.8.0
HP ProLiant iLO Advanced System Management Controller and Enhanced Management Controller Driver 5.37.0.0
HP iLO Management Channel Interface Driver 1.7.2195.0
HP ProLiant Smart Array Device Manager Extension 5.10.0.32
Smart Array 5x and 6x Controllers SCSI Miniport Driver 5.68.0.32
Compaq Integrated Management Log Viewer Utility 5.2.0.0
HP ProLiant Remote Monitor Service 5.1.2195.0
Network Teaming Intermediate Driver (NTID), 8.10.00.19, NDIS 5.1, x86, (free) 8.10.0.0
HP Array Configuration Utility (CLI) 7.40.7.0
HP Array Diagnostics Utility 7.40.7.0
HP Insight Diagnostics Online Edition for Windows 7.4.0.1570
HP System Management Home Page for Windows 2.1.2.127
HP NC10xx/NC67xx/NC77xx Gigabit Driver NDIS5.1 Driver. 8.39.1.0
HP Version Control Agent 2.1.2.740
HP Smart Array 6i Controller 2.58
HP Smart Array 6400 Controller 2.74
Compaq Remote Insight ROM 1.82
Compaq System ROM 2005.10.10
Here is version information.
Name Installed Version
HP Insight Management Agents for Windows 2000/Server 2003 7.40.0.0
ATI2MPAD Miniport Driver 5.10.2600.6013
HP Array Configuration Utility 7.40.8.0
HP ProLiant iLO Advanced System Management Controller and Enhanced Management Controller Driver 5.37.0.0
HP iLO Management Channel Interface Driver 1.7.2195.0
HP ProLiant Smart Array Device Manager Extension 5.10.0.32
Smart Array 5x and 6x Controllers SCSI Miniport Driver 5.68.0.32
Compaq Integrated Management Log Viewer Utility 5.2.0.0
HP ProLiant Remote Monitor Service 5.1.2195.0
Network Teaming Intermediate Driver (NTID), 8.10.00.19, NDIS 5.1, x86, (free) 8.10.0.0
HP Array Configuration Utility (CLI) 7.40.7.0
HP Array Diagnostics Utility 7.40.7.0
HP Insight Diagnostics Online Edition for Windows 7.4.0.1570
HP System Management Home Page for Windows 2.1.2.127
HP NC10xx/NC67xx/NC77xx Gigabit Driver NDIS5.1 Driver. 8.39.1.0
HP Version Control Agent 2.1.2.740
HP Smart Array 6i Controller 2.58
HP Smart Array 6400 Controller 2.74
Compaq Remote Insight ROM 1.82
Compaq System ROM 2005.10.10
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