grizzut

...never ever have seen this behaviour. What unRAID version are you using?...what mobo? Maybe posting this in the general support (or unRAID RC5) section will draw more attention to it. I don't think this is related to the M1015 and its FW. Ok, I tried more testing and it is definitely something related to the M1015 card. Here's what I did: Removed one of my 2TB drives (connected to the Motherboard) from the array and added the 3TB red (and cleared/formatted it). After parity check and multiple restarts, it works fine. Took the 2TB drive that was working and connected it to my M1015. It showed up fine and using initconfig, I added it to the array and did a parity check. It completed successfully. I stopped the array and then unraid successfully saw the disc as 2TB BUT thought it was previously a 3TB disc in that position and wouldn't let me start it back up! So I rebooted the machine and now I have a red light next to the drive and it won't start with the array. I'm using 'unRAID Server Plus version: 5.0-rc1'. My Motherboard is a MSI MS-7613. It was taken from an HP Computer. Everything has worked fine for a year until now. Any thoughts would be much appreciated.

Hi all, Maybe somebody has seen this before? I have a M1015 flashed to IT mode, P15. I hooked up a new WD Red 3TB drive to it. It sees it as 3TB and adds it to the array with no problems. I can write to the drive normally. However, as soon as I stop the array, it thinks my drive is 2TB and will not start the array because it thinks I am replacing my 3tb drive with a smaller 2tb drive. I rebuilt the array and tried adding the drive again and the same thing happened. So I hooked the drive up to my windows machine, ran WD diagnostics on it, and it came back with no errors. Has anybody seen this before or have any ideas? Thanks!