Feature request: Working with Marvell SATA chipsets

[HellDiverUK]

So, after trying to convert my QNAP to unRAID, I came up against the old Marvell chipset failing issue. Lots of errors on boot, and eventually only 2 SATA bays usable on a 4-port NAS.

 

What, exactly is the issue with unRAID not working with Marvell chipsets?  It's clearly not a Linux issue as the QNAP runs linux by default, and plenty of other version of linux don't crap the bed if Marvell are involved.

 

I understand it's something to do with VMs - is there a way of totally removing/disabling VM stuff if not wanted, to improve compatibility with Marvell?

[saarg]

It's a bug in the Marvell firmware they never cared to correct. Disabling vt-d/iommu in the bios should fix the problem. 

[BobPhoenix]

What linux kernel is the QNAP using?  I know 32 bit unRAID has no problem that I ever saw with Marvel controllers.  But 64 bit unRAID would drop drive on me all the time.

[Squid]

Many users including myself have zero problems with marvel controllers and vt-d, drives dropping, etc.  It is more certain combinations of hardware that cause the issues.

 

[HellDiverUK]

Yeah, I have no problems with the Marvell chipset on my AOC-SAS2LP cards, nor the Marvell on my Supermicro X10SBA.  But, the Marvell in the QNAP doesn't play ball.

 

@BobPhoenix it must be 64-bit, as the NAS can support 8GB RAM, and can run VMs (It has a J3455 chip).