Red X plus invalid parity

[JorgeB]

SASLP works fine for most users but be aware there's also an issue with it and the newer SAS2LP, although it seems they work better than other Marvell controllers like the one you have, it can have similar issues in some cases (they use after all a Marvell chipset also)

[tucansam]

UGH.  Well this was the most stable server I had until I upgraded to 6.x (not blaming unraid at all, just pointing something out).  So far (knock on wood) the other system currently using the SASLP has not had issues and is also running 6.x.....

 

I suppose I'll go over to the controller forum and see if there's a better option.

[JorgeB]

8 minutes ago, tucansam said:

Well this was the most stable server I had until I upgraded to 6.x

 

The Marvell problems are mostly (only?) on the newer kernel/drivers, they are unavoidable if updating to latest unRAID.

[tucansam]

Thanks.  Well, vt-d was already disabled, and I am on the latest BiOS firmware version.  I did disable "Intel Virtualization Support" tho.  

 

And it still boots into Disk 1 being disabled.

[tucansam]

I just picked up an IBM/LSI M1115 flashed to IT mode on fleabay for $79 plus a 3wire breakout cable, will report back if successful.

[JorgeB]

Good choice, LSI are IMO the best option at the moment, AFAIK there are no users with issues specific to those controllers.

[garycase]

There seem to be quite a few issues with Marvell controllers in v6.   I don't recall seeing these in previous versions, so I have to wonder if it's a driver-related issue, but in any event it's likely to not be a problem if you simply avoid Marvell SATA ports.