Home | Articles | About | Contact | Forum |
Friday, October 18, 2019

Lunarpages.com Web Hosting

Mailing List

By Joining the mailing list you will be notified of site updates.

Show Your Support For
This Site By Donating:

Audience: System Admins - I.T. Managers
Last Updated: 5/17/2009 3:25:46 PM
Original Creation Date: 5/17/2009 3:25:46 PM
**All times are EST**

IBM Blades: HS20 hard drive missing, won't boot

By Erik Rodriguez

This article provides information on problems booting IBM HS20 blade servers. If your blade server is all the sudden not detecting it's IDE drive, read below.

I've run into a strange problem using IBM HS20 blades. These blades do not support RAID configurations unless you double them up with the optional SCSI add-on. Doing so will occupy 2 blade slots. So, if you wanted to use RAID configurations on all blades you would only be able to use 7 blades in a full chassis.

If use the standard setup, you can deploy 14 blades in a full chassis. That being more attractive, each single blade is able to hold (2) 2.5" IDE drives. They cannot be used in a RAID configuration so use of a single 2.5" drive is common on the HS20 blade servers.

If you have an HS20 that has crashed or is crashing, you may want to try the following.  You should have the ability to see your console remotely.  If your blade is unable to boot it should enter into the BIOS screen.  At this point, it will ask you to confirm changes.  DO NOT ACCEPT!  Accepting the configuration changes stops the blade from further detecting IDE drives.  If you DO NOT accept the changes, and reboot the blade, it should work again.  However, I would suggest moving away from an HS20 showing these symptoms immediately.  If that still does not work for you, try switching IDE channels:

Last, if you still cannot get your blade to boot. Try switching the drive to a different blade. This has worked for me, but there is 1 very important thing to watch out for. The HS20 models (8678, 8832, 1883, 8843) can vary with the network chipsets they use. I swapped an IDE drive in a blade before realizing this and the new network drivers were installed once the server booted. The problem with this is, none of your IP information will be retained once this happens. You will have to re-enter that info on the new network cards. This can be a huge problem if you have a web server with multiple IPs assigned to certain sites. This happened to me when the blade I swapped had broadcom network cards instead of the intel-based chipset.

Juniper SRX anti-spam filtering config
Windows Server 2008 Clustering Configuration
Windows 2008 R2 Network Load Balancing (NLB)
Extreme Networks: Downloading new software image
Juniper SRX save config to USB drive
Juniper SRX logout sessions
Extreme Networks Syslog Configuration
Command line drive mapping
Neoscale vs. Decru
Data Security vs. Data Protection
Juniper SRX Cluster Configuration
HOWTO - Create VLAN on Extreme Switch
Using a Non-local Colocation Facility
Linux Server Administration
IT Chop Shops
Flow Viewers: SFLOW, NetFLOW, and JFLOW
Exchange 2007 Back Pressure
IPtables open port for specific IP
Politics in IT Departments
HOWTO - Block Dropbox
Cisco IOS Cheat Sheet
Subnet Cheat Sheet
Design a DMZ Network
How DNS works
Firewall Configuration
Juniper SSG Firewalls
Server Management
Configuring VLANs
Runlevels in Linux
Server Clustering
SONET Networks
The Red Hat Network
Server Colocation
Complicated Linux Servers
Dark Fiber
Data Center Network Design
Firewall Types
Colocation Bandwidth

Copyright © 2002-2016 Skullbox.Net All Rights Reserved.
A division of Orlando Tech Works, LLC
By using this site you agree to its Terms and Conditions.
Contact Erik Rodriguez