![mfiutil initialize drive mfiutil initialize drive](https://www.bogotobogo.com/JavaAppletWebStart/images/java/JWS/Beans/UpLoadedFiles.png)
Previous RAID-10 volumes that I've seen MFI BIOSes create used a non-zero The post that made it clear why mfiutil may make this assumption was by John Baldwin I dug a little deeper into the issue and found this thread on the freebsd-current mailing list. According to Common RAID Disk Data Format Specification that is an incorrect assumption. Mfi_raid_level(uint8_t primary_level, uint8_t secondary_level) So why is it still reporting RAID1? Well let’s dive into the source of mfiutil. Mfi0 Configuration (Debug): 3 arrays, 1 volumes, 0 spares Primary RAID level is 1 and secondary RAID level is 0. usr/obj/usr/src/usr.sbin/mfiutil/mfiutil debug
#Mfiutil initialize drive Patch
Alright, let’s get mfiutil to spit out some debug output which requires applying a patch and recompiling. Now this kind of bugs me, since I even followed the MegaRAID SAS User Guide to setup the RAID10 array. Volume mfid0 (408G) RAID-1 64K OPTIMAL spans:Īlright, that looks right but it still says RAID1 as well. Mfi0 Configuration: 3 arrays, 1 volumes, 0 sparesĭrive 8 ( 137G) ONLINE SAS enclosure 1, slot 0ĭrive 9 ( 137G) ONLINE SAS enclosure 1, slot 1ĭrive 10 ( 137G) ONLINE SAS enclosure 1, slot 4ĭrive 11 ( 137G) ONLINE SAS enclosure 1, slot 5ĭrive 12 ( 137G) ONLINE SAS enclosure 1, slot 6ĭrive 13 ( 137G) ONLINE SAS enclosure 1, slot 7 So I ran mfiutil show config to get some more details about my configuration. Say WHAT?! That volume is NOT supposed to be RAID1. However, mfiutil is reporting it as a RAID1 volume.Īfter setting up a RAID10 array using the WebBIOS tool and installing FreeBSD I ran mfiutil show volumes to make sure I was referencing the right virtual drive and to my astonishment I see: Now, I know I setup a RAID10 that spans 3, 2 disk arrays.
![mfiutil initialize drive mfiutil initialize drive](https://s3.manualzz.com/store/data/026287793_1-b0b52b622d7ec2bfc908123119005885-360x466.png)
#Mfiutil initialize drive install
It saves from having to install sysutils/megacli and using its rather complicated arguments (well, at first, after using it for a little while they make sense). As of FreeBSD 8.0, there is a much more friendly tool included called mfiutil. Андрій Вознюк's sysadmin life: FreeNAS 9.Recently I have been setting up a few new boxes that have an LSI MegaRAID controller.Broadcom -> Products -> Storage Adapters, Controllers, and ICs -> RAID Controller Cards -> MEGARAID SAS 9266-8I -> Downloads.Here are some reference articles that gave me all the information I needed: I could go into its config tool and setup my RAIDs. I then decided to flash the latest firmware from the LSI website: The flashing went well, but once rebooted, the card was back in F/W fault state, destroying my ears again. Then I tried flashing the recovery image from the LSI CD: Once rebooted, the card stopped beeping, which was very nice for my ears. The first thing I did was erase the current firmware: Then I could use the megarec commands to flash the card. What I ended up doing was prepare a FreeDOS boot disk including megarec and its dependencies, and boot it. The key to reset the card was to use megarec. I've tried to use the LSI Pre boot CD to flash the card, but it wasn't detected either by any of the tools. I've tried to use storcli on a EFI shell, but the executable didn't work: it froze instantly when I started it. I've tried to use storcli on FreeBSD but it couldn't see the card either. Mfi0: Firmware not in READY state, error 6 I've booted a FreeBSD live CD and tried to inspect the controller using mfiutil, but it couldn't do anything.ĭmesg confirms that the firmware is not ready: This card clearly needed its firmware reconfigured. The following message was displayed during POST:į/W is in Fault State - MFI Register State 0xF001002 When I plugged it in, it woudln't stop beeping and complained that its firmware is in fault state. Issue: I bought a spare SAS-9266-8i on eBay.