JFS224 change drive order

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.

Did you format the new drive? Formatted size must be the same or bigger than remaining drive.

Hmm,tricky, I think your best bet would be to save old drive and do a complete new programme install hopefully you have the discs, then once setup and running, connect old drive as a backup and transfer data you require, there may be a better way, this is what I would seriously consider.

click start click on your usb drive to open
right click in the drive select new folder and name it lets say for the exercise back up 1 and continue making new folders and naming them they should automatically be arranged by name

however you can change these settings by clicking the view tab in windows explorer it will be at the top of your screen then from the view

drop down list you will see an array of options sort by to name one with sort by name by size by date sort by , ascending , decending ......


if you need more help with this post a reply

hope this helps

You may not be able to boot you drives outside of a RAID array depending on the RAID type (software/hardware) and configuration (RAID0/1/5). Generally a mirrored RAID1 should be bootable off of the RAID array. If you are using software RAID or a RAID0, you best bet is to update the RAID firmware, and if the data is accessible at all, transfer the data to another storage device.

First, buy an external storage device, at least 80GB (although it's currently difficult to find any _smaller_ size!) and make a file-by-file, folder-by-folder, backup of your 73GB of "data".

Second, buy another external storage device, and do a Google-search for "drive image freeware".
Pick one of those applications, and do a "image" backup to this second external storage device.

Third, disconnect the 3 "old" drives, carefully label them, and set them aside.

Fourth, connect the 3 "new" drives, delete the old RAID-5 array definition,
and create a new RAID-5 array definition.

Fifth, do an "image restore" from the second external storage device to the new array.

If you have any problems, all you need to do to "back-out" is to:
* disconnect the "new" drives
* reconnect the "old" drives
* delete the "new" array definition
* redefine the "old" array definition

and you're back to the "old" configuration.

On many systems with RAID1 support built into the mobo chipset, that system includes some RAID management software in BIOS. You won't see it until you turn on RAID capabilities in the BIOS and add a drive. But you might find all the details you need in manuals on the matter from Dell, so look for those. They could have come with your machine, or you may have to search their website and download.

On systems I've seen you create and manage RAID arrays using that built-in software, NOT Windows tools. In fact, some RAID1 management tools would allow you to convert a single stand-along HDD to a RAID1 array by adding a matching HDD unit and then having the system copy all the data to the second drive. This is almost the same as the process to repair a damaged RAID1 array by replacing one faulty drive with a new one and rebuilding the array.

HOWEVER, Windows ALWAYS needs a RAID driver installed in it to use any RAID array. If you are simply booting from a "normal" stand-alone disk into Windows and then using a RAID array as a data storage system, the RAID driver installation can be done any time after Windows is running as you set up the new storage system. BUT Windows in ANY version cannot BOOT from a RAID array unless the RAID driver has been installed at the very beginning of the OS installation. This implies that, if you want to convert your single disk into a RAID1 2-disk array and use ONLY that as the HDD resource in the machine, you will need to re-install Windows, this time including the required RAID driver install at the beginning, in order to boot from that array.

I have read that there may be ways to convert a non-bootable RAID array into bootable by some complicated editing of Windows registry and boot files in order to force it to load the right driver at the right time from the right spot on a HDD, etc. But I am not SURE that would work. It's definitely for the adventurous knowledgeable techie.

So here's a quick guide to installing hardware RAID on a motherboard that features a RAID controller. These steps assume you are performing a clean Windows 7 install rather than an upgrade, and they might differ depending on your system set-up, but the general principles should be the same.

1. Download the RAID drivers for your motherboard from the manufacturer's website and save them to a memory stick.
2. Back up all your important data!
3. Turn your PC off and unplug it.
4. Install 2 hard disks preferably with identically capacity into your PC.
5. Turn on your PC, press the delete key or F2 key when prompted to get to the BIOS menu.
6. Find the option to select the RAID mode, save your settings and exit BIOS.
7. On reboot you should see a new menu option to enter the RAID controller settings. Enter the key combination when prompted to get to the RAID controller menu.
8. Create a new RAID array selecting either RAID 0, or RAID 1.
9. Select the disks that will form the array, save the settings and exit.
10. On reboot press the delete key or F2 key when prompted to get to the BIOS menu.
11. Check the boot sequence of your PC and ensure your optical drive is top of the list.
12. Insert your Windows 7 disk into the optical drive and exit the BIOS.
13. On reboot press any key when prompted to boot from the optical drive.
14. Windows 7 should start installing.
15. Select your localisation settings and click next.
16. Click "repair your computer" and click the "load drivers" button.
17. Insert your memory stick and browse to the correct driver and install.
18. Exit back to the Windows 7 install menu click "Install now" and on the next screen click "Custom (advanced)" to perform a clean install.
19. When you are asked where you want to install Windows 7 you should see that the 2 RAID hard disks are now visible as just 1 drive.
20. Add a partition to the new drive so Windows with be able to recognise it.
21. Continue installing Windows as normal.

Call Dell with your Service Tag.
Lifetime support is included on all Dell servers.
Last time I called them I dialed (800) 945-3355
They can sell you the hardware you need and guarantee it will work with your server. They might even be able to help explain the process of installing the drives.

I recommend that you use Acronis' Imaging software (www.acronis.com) so that you can make an exact copy of your data and apply it to the replacement volumes. If you are using a RAID1 array make sure the new array is completely built before applying your image. Builds can take a long time. I created a RAID1 array with 2-320GB disks and it took 3.5 hours to build the RAID1 array.

I hope this helps.

Please vote for my solution if it helps.

This is a good start:
In order to use it, you will need to have it recognized by your PC/LAPTOP and/or format it by following the steps below: (Your external drive should be automatically recognized by your Windows O/S but in some rare case, you need to tell your PC/Laptop that it has a new drive connected and what drive letter to use it :
CONTROL PANEL -> ADMISTRATIVE TOOLS -> COMPUTER MANAGEMENT -> STORAGE -> DISK MANAGEMENT -> locate your external drive -> right click on the external drive to bring up the context menu -> if required, Create required partition(s) -> if required, Quick FORMAT (NTFS is fine but I suggest FAT32 on some partition for more compatibility on drive/partition of less 32Gb) -> 'change drive letter and path' to assign a drive letter to your partition(s)/external drive(s) .

I am not familiar with the specific model, but my guess is you can setup another separate logical vlume by using a RAID1 for the new disks. You will not be able to add the disks to the existing volume.

If there is no data, and the array supports it you can delete the existing volume and setup a RAID 5 instead, which will use all 4 disks, as long as they have the same capacity.