richt

I solved the problem by passing the usb controller on my X9SCM directly through to the unRaid vm. I boot ESXi 5.5 U2 from the usb port on the mb so make sure you pt controller #1 (the ones on the rear I/O). USB Controller #2 is for the internal ports (mb and mb header). UnRaid boots from a vmdk image, so the USB only supplies the config folder. Thanks, Rich

I replaced a failed drive 3 with a new drive. After starting the array, the data rebuild started, but the drive also showed it was unformatted. Thinking it needed to have the file system initialized in order for the data to be rebuilt from parity, I formatted to new drive. The data rebuild then proceeded following the format of drive 3, but now drive stats show no data on drive 3. Prior to the format, drive 3 showed data present, even when starting the array with no drive in slot 3 (due to the parity drive). I stopped the array shortly after the format completed fearing the worse. The array was still in a data rebuild showing it would take over a day to complete. Did I just loose the data on drive 3 by 'formatting' the new drive? Should I re-start the array and let the 'data-rebuild' complete with the new drive 3 showing empty and the data will then appear on drive 3 after it is completed? If I indeed lost the parity information for drive 3 by using the 'format' command, is there any way to recover the data? Drive 3 has an orange ball indicating invalid data content as expected since I did not let the data rebuild complete following the drive format.