Ds3400 manually fail drive

Execute the following command to manually fail a drive in an array: set drive [trayID, slotID] operationalState=failed; it gives the follwoing error "The -n option will not work because either the storage subsystem named storagename; does not exist in the configuration file or its name has changed. Execute.  · ”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 .  · . Messages. 1, IBM DS, dual controller dual fiberchannel port per controller, single enclosure. 11x SAS gb 15krpm drives raid 5, plus one hot spare. Suspect that a drive that failed and was replaced this year triggered some channel errors, and then the controller took a channel offline.

Step 1: Install IBM DS Storage Manager 10 into a VM. The only way to manage the IBM DS I have is through the storage manager. While DNS was down, I did remember the IP addresses of at least one of the controllers. This allowed me to connect to the controller and find the problem. IBM System Storage™ DS series is a family of storage enclosures that support IBM System x™ and BladeCenter ® servers. This family of affordable storage products is designed to be scalable and flexible, with ease of use, and includes the DS SAS (Serial Attached SCSI) controllers, DS Fibre Channel controllers, and an EXP storage expansion enclosure. The problem is solved thankfully the steps required to solve the issue are 1) connect the Console cable to the DS storage controller A Login using the default username / password (shellUsr, wy3oow4) 2)enter the command sysWipe and let it finish the reboot cycle 3)connect the cable to the controller B and repeat step 2 4)Uninstall the IBM storage management software from the machine you are using to manage the storage 5)reinstall the software (during the reinstall process LUN31 will be.

We have IBM AN Storage DS, two ibm servers are booting windows server from Execute the following command to manually fail a drive in an array. 17 Therefore, no action is required on the individual logical drives. Possible causes include: The controller failed a manually initiated. Hot spares are not dedicated to specific volume groups. They can be used for any failed drive in the storage array, as long as the hot spare and the drive share.