![]() System availability and application functionality remain unaffected.įast initialization for quick array setupįast initialization quickly writes zeros to the first and last sectors of the virtual drive. Online RAID Level Migration, which is also known as logical drive migration, can migrate a virtual disk from any RAID level to any other RAID level without requiring a reboot. Online Capacity Expansion (OCE) allows the capacity of a virtual disk to be expanded by adding new physical disks or making use of unused space on existing disks, without requiring a reboot. Applications, such as email and web server, benefit from avoiding downtime during the transition. ![]() The card supports a number of features that can be implemented without rebooting the server. Auto-resume ensures that data integrity is maintained throughout the process. I get nothing at all.The ServeRAID M5210 and M5210e SAS/SATA controllers have the following standard features:Īuto-resume on array rebuild or array reconstruction after the loss of system powerĪuto-resume uses non-volatile RAM (NVRAM) to save the rebuild progress during a host reboot or power failure to automatically resume from the last checkpoint. Now when I boot the server I am no longer getting the BIOS information for the controller card. I found the steps above, and performed them exactly. It was suggested that I flash the controller to the 9260-8i. I was told this was because the HDDs were not IBM and the controller was looking for specific drives. The server has an IBM ServeRAID 8k-l controller - which is like a DIMM (server does not boot without it installed). None of the HDDs were seen in the Web Setup tool, although they all lit up on boot up. ![]() I installed a longer cable from the backplane to the controller, and disabled the ONBOARD SAS - as nothing was attached to it. I have an IBM M5015 controller which was not seeing any HDDs installed in my X3500 (7977) server. Use Megarec or Megacli or MSM to flash to controller, nothing else will be updated only BIOS Megarec -writesbr 0 sbrzzzzz.bin (zzzzz= Card type you are trying to flash to, only really needed with M5014/5015) Megarec -m0flash 0 0xxx_yyy.rom (xxx= version number, yyy= OEM version) ![]() Megarec -cleanflash 0 (0 = if only one LSI card in computer, you'll need to work out which number to flash if more than one) It includes FW from LSI, IBM, Dell, Oracle, SuperMicro, Fujitsu and Intel. Here all the latest LSI SAS2108 based FW can be found. I have followed these steps from this URL: SAS2108 (LSI 9260) based firmware files - Projects, Tools, Utilities & Customized INFs Q4 (which should be probably Q1), please be honest with me and tell me: is there some serious danger I could do something wrong and render the raid-controller completely irreversibely unusable? Did this ever happen to someone? Q3: That "megarec" tool used for cross-flashing, is it a part of standard LSI-tools (MegaCLI or StorCLI)? If not, where can I find/download it? ![]() Q2: what the hell is "SBR" (or is it SRB)? I have read it must be wiped out and new loaded. Q1: which is the last LSI-firmware version working with M5015? I would like to flash the latest LSI-firmware (4.10 p2, 12.13.0-0154), but I have read somewhere on this forum some versions can not be flashed on M5015, they simply do not work (oem-controller is detected, or something like that). I have a few questions, but please be patient with me, because I'm complete noob concerning cross-flashing, never done this, and never heard about it untill now. I just obtained IBM M5015 controller and was scared by terribly long boot-time, so I started looking for some info and found this forum by chance. First, greetings to all forum-members from passer-by! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |