inside the mind of a linux admin

Moving Array and Virtual Disks from One System to Another

This article applies only to PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, and CERC ATA100/4ch controllers, and specifically for Dell PowerEdge servers. Be VERY careful when making any modifications to any disk array, as data loss is always possible.

After some planning and preparation, it is possible to migrate array and virtual disks from one controller, enclosure or server to another. You can perform array and virtual disk migration on PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, and CERC ATA100/4ch controllers as long as the following conditions are met:

PERC 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, and 4/Di virtual disks cannot be migrated to a PERC 2/SC or PERC 2/DC controller. PERC 2/SC and PERC 2/DC virtual disks can be migrated to a PERC 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, or 4/Di controller.

When moving the array disks from one enclosure to another, the SCSI ID for each disk must remain the same.

When moving the arrays disks from one enclosure to another or when moving an external enclosure from one server to another, the enclosure must be connected to the same channel number on the controller as in the original condition.

In the case where a virtual disk consists of array disks on multiple channels, each array disk must be migrated to an enclosure that is connected to the same channel number that the array disk or enclosure was originally connected to. This also prevents migration of disks on channel 1 of a PERC 2/DC controller to a PERC 2/SC controller because the PERC 2/SC has only the single channel 0.

WARNING: A virtual disk cannot be migrated between the PERC 2, PERC 2/Si, PERC 3/Si, PERC 3/Di, CERC SATA1.5/6ch, and CERC SATA1.5/2s controller family and the PERC 2/SC, 2/DC, 3/SC, 3/DCL, 3/DC, 3/QC, 4/SC, 4/DC, 4e/DC, 4/Di, and CERC ATA100/4ch controller family.

A virtual disk cannot be migrated from one controller to another unless the receiving controller’s configuration has been cleared.

Virtual disks from one controller cannot be merged with virtual disks from another controller.

To migrate virtual disks and volumes from one system to another, do the following:

Shut down the system that the array disks are being moved from.

If the receiving controller has a preexisting virtual disk configuration on attached array disks, use the following procedure for clearing the configuration:

Shut down the receiving server.

Remove all the array disks from the controller.

Start up the receiving server and clear the configuration from the controller BIOS. After making the changes, power down the server when it indicates to reboot the system.

If the receiving controller does not have a preexisting virtual disk configuration, then shut down its server.

Place the array disks into the new enclosure.

Start up the system connected to the receiving controller. When the system connected to the new enclosure comes up, use the BIOS access (Ctrl-M) to update the controller configuration with the information saved on the array disks. Exiting the BIOS access will require one more reboot of the system.

The migration is complete. The virtual disk is now manageable through Storage Management.

Use the following procedure to enter the controller BIOS configuration screens to save the new configuration:

Reboot the PowerEdge server.

Enter the PowerEdge RAID Controller BIOS by pressing Ctrl+M when prompted during the power on self test (POST) of the controller during the bootup sequence.

Select the Configure menu option and press Enter.

Select View/Add Configuration and press Enter.

This will read the data on the array disks to restore the RAID controller’s proprietary configuration information. Press Esc and save the new configuration when prompted.

Press the Esc key and save the new configuration when prompted.

Reboot the system.

Related Posts

How to revert back to X11 / Xorg from Wayland

Wayland is intended as a “simpler replacement for X”, and is getting quite a bit of hype around the Linux community. So much so, that it’s the default in the latest versions of Fedora, GNOME, KDE and others. While Wayland may be the future, it really is in future. At least for Ubuntu 17.10. The […]

Read More

Touchpad stops working after sleep + resume (Fedora 26 on Dell XPS)

After recently upgrading my Dell XPS 13 w/Touchscreen to Fedora 26, the touchpad suddenly stopped working upon resuming from sleep mode. It was reproduced 100% of the time, and required a complete restart in order to get the touchpad working again. There have been several forum posts and bug reports regarding others experiencing these exact […]

Read More

Leave a Reply

Your email address will not be published. Required fields are marked *

Twitter: kireguy

Tweeter button Facebook button Myspace button