HellDiverUK Posted November 29, 2017 Share Posted November 29, 2017 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? Quote Link to comment
saarg Posted November 29, 2017 Share Posted November 29, 2017 It's a bug in the Marvell firmware they never cared to correct. Disabling vt-d/iommu in the bios should fix the problem. Quote Link to comment
BobPhoenix Posted November 29, 2017 Share Posted November 29, 2017 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. Quote Link to comment
Squid Posted November 29, 2017 Share Posted November 29, 2017 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. Quote Link to comment
HellDiverUK Posted November 30, 2017 Author Share Posted November 30, 2017 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). Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.