richardb Posted January 19, 2016 Share Posted January 19, 2016 Hey all, I am building an Unraid system on a computator built around an Asus Z9PE-D8 motherboard. It is mostly working fine, except I have come across an issue with one of the disk controllers. This is a Marvell controller that has the issue that it fails when Unraid starts up with Vt-d enabled (which I need to run VMs). This bug is described in a few places on this forum, but it isn't clear if this has been fixed or if there is a consistent workaround. Can anyone clarify if there is a good workaround for this, or should I just buy a non-marvell controller? Thanks, Richard Quote Link to comment
saarg Posted January 19, 2016 Share Posted January 19, 2016 You have to add this to your syslinux.conf after append. iommu=pt Should look like this. append iommu=pt initrd=/bzroot I have the same motherboard and its working for me. Quote Link to comment
richardb Posted January 19, 2016 Author Share Posted January 19, 2016 Saarg, that worked perfectly. Thanks for a quick (and easy) fix! Quote Link to comment
kuhnamatata Posted January 20, 2016 Share Posted January 20, 2016 Does this also work for a Addonics - AD4SA6GPX2 6G 4port SATA PCIe card it has a Marvell 88SE9230 I installed the card and it shows in the device list but I am unable to see any attached hard drives If it does where in the syslinux.conf should the added code go? i'm guessing somewhere in this first section default /syslinux/menu.c32 menu title Lime Technology prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append intel_pstate=disable initrd=/bzroot Quote Link to comment
JorgeB Posted January 20, 2016 Share Posted January 20, 2016 Add it after append, it should work, maybe it works even for other marvell chipsets, let us know. Quote Link to comment
kuhnamatata Posted January 20, 2016 Share Posted January 20, 2016 Thanks for the reply, just to be sure you mean like this append iommu=pt intel_pstate=disable initrd=/bzroot I wont be able to try until this evening or tomorrow morning but i'll be sure to update thread, I was pretty sure the card was bad but it would be great if this works Quote Link to comment
JorgeB Posted January 20, 2016 Share Posted January 20, 2016 Thanks for the reply, just to be sure you mean like this append iommu=pt intel_pstate=disable initrd=/bzroot Yep Quote Link to comment
kuhnamatata Posted January 21, 2016 Share Posted January 21, 2016 It worked, I can now see attached hard drives Thanks so much, thought the controller card was bad Quote Link to comment
RobJ Posted January 21, 2016 Share Posted January 21, 2016 You have to add this to your syslinux.conf after append. iommu=pt Should look like this. append iommu=pt initrd=/bzroot I have the same motherboard and its working for me. I didn't realize there was a workaround! Great! I must have missed it. I've added a note in blue to the Marvell bug thread, based on your answer. Can you check whether it's worded correctly, and do you have any further suggestions? Quote Link to comment
saarg Posted January 21, 2016 Share Posted January 21, 2016 You have to add this to your syslinux.conf after append. iommu=pt Should look like this. append iommu=pt initrd=/bzroot I have the same motherboard and its working for me. I didn't realize there was a workaround! Great! I must have missed it. I've added a note in blue to the Marvell bug thread, based on your answer. Can you check whether it's worded correctly, and do you have any further suggestions? That looks good. I don't have anything to add. I just found that suggestion in the kernel bug reporter the marvell issue and thought I'd try it. I thought I posted it here but might have forgotten it. Quote Link to comment
ericave Posted October 16, 2021 Share Posted October 16, 2021 (edited) Hi, I am trying unRAID 6.9.2. I have a Marvell 88SX6081 8 port SATA PCI-X card on a Gigabyte GA-MA78GM-S2H motherboard. I made the modification to /syslinux/syslinux.conf as Community Developer saarg's post. Now, I have 3 HDD. 2 on SATA on motherboard, 1 on Marvell card. They seems working fine. Lucky for me to see the thread before pluging an HDD to Marvell card, so I don't know if Marvell card still work without the modification to /syslinux/syslinux.conf. Just post to tell it's working and thank you. Edited October 16, 2021 by ericave Quote Link to comment
Frank1940 Posted October 16, 2021 Share Posted October 16, 2021 I am going to make a comment here while pinging @JorgeB who is much more of a Guru than I am. The problem with Marvell controllers is that they mostly work. (However, that is like using a parachute that mostly works.) When they don't work (or work right), the problems are varied and differ widely in their symptoms. If you decide to use one, just realize that when you have an array, disk or data problem, switch to another HBA card, preferably one made by LSI. Quote Link to comment
JorgeB Posted October 18, 2021 Share Posted October 18, 2021 On 10/16/2021 at 9:10 AM, ericave said: Marvell 88SX6081 8 port SATA PCI-X That model shouldn't need the iommu workaround. Quote Link to comment
ericave Posted November 24, 2021 Share Posted November 24, 2021 On 10/19/2021 at 12:09 AM, JorgeB said: That model shouldn't need the iommu workaround. You are right. Just now, I did a test and confirmed that this workaround is not needed for Marvell 88SX6081 8 port SATA PCI-X card. 1 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.