This extends the hard drive carrier handle Press the release button to the right of the hard drive carrier.The unit features hot-swappable hard drives which can be removed without powering down the system The hard drives are mounted in hard drive carriers to simplify their installation and removal from the chassis. To locate the correct drive for replacement, right click the drive's icon and select "Start Locating Drive". Note: If during this process you receive "Alerts", select "Dismiss". This marks an offline/failed drive of a degraded array as missing in order to prepare the drive for replacement Once the drive has been identified, right click the icon and select "Mark Drive as Missing“ While drives are hot swappable, the proper steps to replace a drive are:ġ. From the "Logical" tab menu, the failed drive can be identified by the red dot next to the drive icon.Ģ. I'd not take for granted that clearing config and re-creating would always get your data back, as few people pointed out already.When working with a DIP that is configured for RAID 5, the array itself can sustain a one drive failure and successfully recover with all data intact. After reboot RAID came back up and booted. IMPORTANT! If you want to retain the original data, finish RAID config, but DO NOT perform initialization.ħ. Put LSI card back in, gone into RAID config (Web-bios) clear the existing config (as LSI card still does not like it!) and reconfigure the RAID1 with the same parameters.Ħ. Verify that clone is working and disconnect it.ĥ. Bit-wise copy the original data from the RAID1 onto a 'salvage' HDD.Ĥ. Wonders happened here - HP card detected a RAID1 with all the data intactģ. Booted into bare-metal Unix (FreeBSD in my case, but any Linux should do) system in preparation for cloning. Removed LSI card, and replaced it with an HP P212 that I had lying around.Ģ. I managed to solve it and I thought I'd just post what worked for me which will save someone else some dayĪlthough I was lucky enough this time, I cannot stress how important is to have a fresh backup as I was inches from disaster!Īnd yes it's not a HBA it's a RAID Card, my bad.ġ.
That raid card will write its own proprietary raid "dna" onto the disk, and then you might truly lose the data. Are we talking 10TB drives?Īlso, dont use a different raid card to import a drive. Best to just salvage what you can, then redo the array. I would try to restore configs, and such forth. Back in the day, I kept trying to fix corrupted arrays. IF you keep trying to fix the corrupted config without a clean backup, you might risk data. OP, you mentioned being able to access the data? I would copy out all critical data, then just break everything and redo the config. The moment he breaks any sort of config or removes drives from where its supposed to be, he will lose data. Whatever OP does, he must find a way to transfer the data off the drives. Therefore a new card wont "recognize" the config from the previous setup. It seems that the failed controller corrupted the config. So its technically not pass-through of the drives. Seems like our new member Pete is using LSI branded card, but they are in Megaraid mode. Or have I got this completely wrong and data on disks cannot be read by standard MB SATA controller due to additional metadata that HBAs write on the disk?Īny suggestions welcome, as I am trying to avoid restoring backups and rebuilding a complete virtualization server.Ĭlick to expand.Spot on Jho, you said it correct. Contemplating whether Seagate st1000nm0023 is capable of operating in SATA mode in which case could be a matter of a SAS to SATA converter?Ħ. Can I use a different HBA (HP P212) to 'import' a single disk just to make data visible?ĥ. and attach it directly to the motherboard, however the most important data sits on 2xSAS disks and therefore that's not an option.Ĥ. Create a virtual drive using a single drive and copy the data over before rebuilding RAID. Re-create the RAID1 and force online without initialization?ģ. Can I clear the config WITHOUT losing data?Ģ. My assumption is that data on all drives is still intact (except raid config?).ġ. 2xHDD (7200 NL-SAS) in RAID1 and a single drive (SATA 7200) in RAID0. "Foreign drives cannot be imported as they don't form a complete configuration."
LSI MEGARAID STORAGE MANAGER REPLACE FAILED DRIVE WINDOWS
Nothing unexpected so far, however the problem began when it failed to import that foreign config.īooting into Windows and using MSM, given me the similar error: When booted up it presented me the screen to import a foreign config. After a HBA failure I've replaced it with the identical model I had.
0 kommentar(er)
