- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: Proliant problem
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
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
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- 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
тАО05-24-2006 11:04 AM
тАО05-24-2006 11:04 AM
Hi
I have a proliant 4500 server w/ 4 HD's and 4 PRO cessors.
factory unique driver for cd and array
is there any acid test to know if the C drive is bad
all I did was edit the boot.ini
i don't believe the drive is bad
if the drive is bad, it went bad simultaneously as the boot.ini edit...
Thank You
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-26-2006 01:09 AM
тАО05-26-2006 01:09 AM
SolutionReally old hardware is notoriously finicky after being power cycled.
Try booting to a server diags diskette or an ADU or DAAD (Drive Array Advanced Diagnostics) diskette - you may have to dig around on the hp site to found a really old download to build the diskettes. The ADU/DAAD would better tell you if the drive is bad and what happened.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-26-2006 01:11 AM
тАО05-26-2006 01:11 AM
Re: Proliant problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-26-2006 02:31 AM
тАО05-26-2006 02:31 AM
Re: Proliant problem
Look for Software - System Management
http://h18023.www1.hp.com/support/files/server/us/locate/20_1110.html
http://h18023.www1.hp.com/support/files/server/us/locate/7_1110.html For WNT 4.0
http://h18023.www1.hp.com/support/files/server/us/locate/6_1110.html For WNT 3.51
There you can download the diags and run them on your server.
Best Regards
RaMpaNTe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-26-2006 03:46 AM
тАО05-26-2006 03:46 AM
Re: Proliant problem
Thanks Roy and Rampante, will check out the array diag tool for my platform, I had thought about that...
or do you think with a win98 bootdisk I could just edit the config.sys and autoexec so as to load the storage device drivers..
maybe this is exactly why I can't approach the drive in dos, but with nfts4dos, I can read and write to the other drives, which are ntfs...
Just thinking outloud here...when I get humpty dumpty back together? Im going to drop an image of a working install onto one of the other 3 drives. woulda made this a whole lot easier.
Thanks