We have a ServeRAID-6M on a server

wow posting hard RAID questions here and not on actual
IBM forum,. why do that?
i can do HP or dell but not IBM

on dell R710 it is automatic raid 6 (8 drives) can fail 2 and run.
what raid hardware is it Ibm
What raid card there/
is this RAID 6?????? if not why not.
how big is each drive and now many,? drives
did you read the raid controller manual first, after all no 2 servers on earth work the same unless are EXACTLY the same.
fact key not told.
IF IT CAN DO HOT SWAP NEW DRIVER
IT CAN TAKE DAYS TO SELF REPAIR.
all the time production never ends only a tad slower,
the whole reason for that. no need disable the server.

why not get help here
2012 seems poor support now. 10 years later, IBM is that bad?

https://www.ibm.com/support/pages/installation-and-users-guide-ibm-system-x3400-m3-7378-7379


real help.
this system Base config
has only this.,
x3400 M3 models include an IBM ServeRAID®
-
BR10ilV2 controller???????????


IBM ServeRAID®
-
BR10ilV2 controller, providing RAID-0/1/1E support. The IBM ServeRAID

and best.
-M1015 controller,
providing RAID-0/1/10 with an option to upgrade to RAID 5 is standard on 8-drive 2.5-inch models,
while the ServeRAID-5014 controller, which provides RAID-0/1/10/5/50 support (upgrade-able to
RAID-6/60) and includes 256GB of cache memory, is standard on 16-drive 2.5-inch models.

I have a m1015 here, that it cross loaded LSI rom too..
cheap to buy and easy to convert so know about it.

what you have inside our server is any ones guess.
and recover tools.
WHAT YOU DO find out what raid card is there
then get the IBM manual on it
the ask admin what raid is or run the RAID app and look first
free old manual is here

https://www.manua.ls/ibm/system-x-x3400-m3/manual


read the manual on our raid card first.
read it and now to do recovery.

system load out and CTO not told so answers will be endless.
or even wrong. nobody can see inside your box.

If you can get into the bios, you should be able to tell your system which drive(s) to boot from.

Before replacing drives • Be sure that the array has a current, valid backup. • Confirm that the replacement drive is of the same type as the degraded drive (either SAS or SATA and either hard drive or solid state drive). • Use replacement drives that have a capacity equal to or larger than the capacity of the smallest drive in the array. The controller immediately fails drives that have insufficient capacity. In systems that use external data storage, be sure that the server is the first unit to be powered down and the last unit to be powered up. Taking this precaution ensures that the system does not, erroneously, mark the drives as failed when the server is powered up. Replacing drives The most common reason for replacing a drive is that it has failed. However, another reason is to gradually increase the storage capacity of the entire system. NOTE: In fault-tolerant configuration, hot-plug hard drives can be replaced when server is ON, but in case of a Non-hot-plug hard drive, it should be replaced when server is OFF. For systems that support hot-pluggable drives, if user replace a failed drive that belongs to a fault-tolerant configuration while the system power is on, all drive activity in the array pauses for 1 or 2 seconds while the new drive is initializing. When the drive is ready, data recovery to the replacement drive begins automatically. For systems that support non-hot-pluggable drives, if user replace a drive belonging to a fault-tolerant configuration while the system power is off, a POST message appears when the system is next powered up. This message prompts user to press the F1 key to start automatic data recovery. If user do not enable automatic data recovery, the logical volume remains in a ready-to-recover condition and the same POST message appears whenever the system is restarted. Automatic data recovery (rebuild) When user replace a drive in an array, the controller uses the fault-tolerance information on the remaining drives in the array to reconstruct the missing data (the data that was originally on the replaced drive) and then write the data to the replacement drive. This process is called automatic data recovery or rebuild. If fault tolerance is compromised, the controller cannot reconstruct the data, and the data is likely lost permanently. Time required for a rebuild The time required for a rebuild varies, depending on several factors: • The priority that the rebuild is given over normal I/O operations (user can change the priority setting by using HP SSA/ACU) • The amount of I/O activity during the rebuild operation • The average bandwidth capability (MBps) of the drives • The availability of drive cache • The brand, model, and age of the drives • The amount of unused capacity on the drives • For RAID 5 and RAID 6, the number of drives in the array • The strip size of the logical volume • Firmware versions of the Smart Array Controller and Hard Disk Drive • Presence of BBWC/FBWC CAUTION: Because data rebuild time may go upto the rate of 200GB/15 minutes, the system could be unprotected against drive failure for an extended period during data recovery or a drive capacity upgrade. When possible, perform rebuild operations only during periods of minimal system activity. When automatic data recovery has finished, the drive status LED changes from flashing green to solid green. If the drive status LED on the replacement drive changes to flashing or solid amber, the rebuild process has terminated abnormally. If an abnormal termination of a rebuild occurs, identify the cause and appropriate corrective steps. Abnormal termination of a rebuild If the activity LED on the replacement drive permanently ceases to be illuminated even while other drives in the array are active, the rebuild process has terminated abnormally. The following table indicates the three possible causes of abnormal termination of a rebuild. Cause 1: An uncorrectable read error has occurred. 1. Back up as much data as possible from the logical drive. CAUTION: Do not remove the drive that has the media error. Doing so causes the logical drive to fail. 2. Restore data from backup. Writing data to the location of the unreadable sector often eliminates the error. 3. Remove and reinsert the replacement drive. This action restarts the rebuild process. If the rebuild process still terminates abnormally: 1. Delete and recreate the logical drive. 2. Restore data from backup. Cause 2: The replacement drive has failed. Verify that the replacement drive is of the correct capacity and is a supported model. If these factors are not the cause of the problem, use a different drive as the replacement. Cause 3: Another drive in the array has failed. A drive that has recently failed can sometimes be made temporarily operational again by cycling the server power. 1. Power down the server. 2. Remove the replacement physical drive (the one undergoing a rebuild), and reinstall the drive that it is replacing. 3. Power up the server. If the newly failed drive seems to be operational again: 1. Back up any unsaved data. 2. Remove the drive that was originally to be replaced, and reinsert the replacement physical drive. The rebuild process automatically restarts. 3. When the rebuild process has finished, replace the newly failed drive. However, if the newly failed drive has not recovered: 1. Remove the drive that was originally to be replaced, and reinsert the replacement physical drive. 2. Replace the newly failed drive. 3. Restore data from backup. More Resources: • Click here for ProLiant Self Solve. • Click here for Creating and Managing Hard Drive Online Spare Technology. • Click here for 17xx Power-On Self-Test (POST) Errors and fixes. • Click here for HP Dynamic Smart Array RAID Controller User Guide. • Click here for HP Smart Array Controllers for HP ProLiant Servers User Guide. • Click here for HP Smart Array Controllers for HP ProLiant Gen9 Servers User Guide. • Click here for Configuring Arrays on HP Smart Array Controllers Reference Guide. • Click here for Array Configuration, Diagnostic, Storage Administrator and SmartSSD Wear Gauge Utility Software and User Guides.

I am not familiar with your RAID controller card but as long as the controller can see two additional drives, it shouldn't be difficult to add two new drives to your exisiting RAID 5 configuration.

You will probably need to reinitialize the RAID configuration for discs to copy all the parity information so you should refer to the documentation on re-initializing the RAID.

Replace the HDD whose led is blinking in AMBER ( orange ) colour.

Use IBM ServeRaid software to blow the array configuration away then recreate the C partition.

Serveraid is downloadable for IBM Support

Download IBM ServeRaid , this software will allow you to see whats going on and correct issues

if there is a limit this would have been mentioned in the features of the product

please have a check

Hi Nick ,

As of now you can Select "F2" to accept data loss and re-enable logical drive. This Load OS Normally .
It seems that one of the HDD in the RAID 5 has failed , Did you notice any LED indications like red or amber on the HDDs ?? if so get that hdd replaced . Make sure the Failed HDD is replaced .
You can run the Array Diagnostic Utility from HP System tools to check the Failed Drives and also frimware version of the controller . If the frimware is not latest Update it from HP website. DL380 G4 should have Smart Array 6i controller .

Hope This was Helpful
cheers :)

Do you see your new disk in the "Disk Management" window? To get there go to "run", type "compmgmt.msc", then click disk management. If you do see the disks there, then you need to format the disk to a "basic" configuration. If your new disk/volume does not show up there, I would suggest a hard reset on your server whenever possible. I see this issue at times with Windows and newly added storage array logical drives.