This all looks correct, but just to be certain, this shouldn’t wipe or otherwise initialize my existing array, correct? – On the review (last) page, it does indicate that my current settings show Drive Group 1, RAID 5 with a total capacity of 407.918GB (4 drives) and also post modification settings as RAID 5 with a total capacity of 543.891GB (5 drives). Clicking Next, I do see the Unconfigured Good disk that I wish to add to my existing array. I’m allowed to “migrate” to either RAID 0 or RAID 5. I am prompted to back up the configuration data first. – Going to the drive group, I highlight it and Go To -> but I don’t see Adv Opers what I have is Modify Drive Group. I’ve got a dedicated spare to the latter and want to add a single additional disk to the array.įollowing the instructions, I think I’m in the right place, but the instructions are slightly different. IBM server with two arrays (RAID-1 on the system partition, 4 disks in a RAID-5). In a nutshell, I’m in the same boat as Jeremy here. I’m a little hesitant to move forward on this without being certain I’m doing this the right way, particularly after a couple of folks reported issues afterward. Amazing that this is the one place on the web with the answer to this question! If it's from LSI to LSI then it will show up the same way but should let you import the drive properly, except when going SAS to RAID or RAID to SAS.Wow. If you move a drive from say, Adaptec to LSI, it will show up as a foreign device which needs clearing. Most of the time this information would be reported through the monitoring tools (LSI MegaRAID Storage Manager for example). You may be able to get SMART data off of it if the controller supports it in the BIOS - some do, some don't. If you want the RAID controller to see the drive properly it must be cleared of the previous metadata (RAID controllers specifically).
I've touched thousands of servers over the last 15 years and I have never seen "firmware incompatibility" issues preventing you from initializing a drive on any SAS / RAID controller. I am taking about firmware incompatibility wherein I cannot initialize the drive.
Most systems from experience will use one of the LSI-based chipsets for RAID/SAS. There should be an option to "Import foreign configuration" if it's compatible.
Avago initialize drive upgrade#
This is helpful when you upgrade a controller or replace a broken one so you don't lose any data. The exception to this is that (at least with LSI/Avago/Broadcom) you can move drives and RAID sets around controllers from the same manufacturer. When you move drives around different controllers you will need to re-initialize / format the drive using the new controller for it to function properly. For example, if you take a drive from a system using Adaptec controllers, you won't be able to read the data with an LSI controller. You also won't be able to move a hard drive from a system to another if they have different manufacturers of RAID controllers. You can't - in most cases - take a hard drive from a RAID controller and read it on a regular SAS port, and vice versa. The incompatibility you're probably talking about is due to the fact that RAID cards put manufacturer-specific metadata on the drives. The firmware of drive rarely has any issues with the controller it's plugged into. I am constantly running into issues because many RAID cards don't inter-operate with firmware of drive, etc.
0 kommentar(er)
