So look like the queue depth doesn’t help: None, the status of the bug is updated manually. For a better experience, please enable JavaScript in your browser before proceeding. This bug affects 1 person. There it is, some ideas, suggestions. The problem seems to be a design issue with the Marvell controller.

Uploader: Kigakree
Date Added: 8 March 2012
File Size: 23.53 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 48153
Price: Free* [*Free Regsitration Required]

This problem happened only during burn, intense read access as intense as a DVD can be, that is had no problems. After failing, the drive will not show up in the partitioner in Yast – when querying the SMART data, it will now report a size of PB until the server is rebootet – after which the drive shows again and the SMART data comes back with no problems. Open Source Consulting Domain Registration.

Updates following the suggestions from chanik: I tried various things such as [1] updated the HDD firmware [2] updated the mainboard bios expecting onboard 88SE bios also updated [3] forced SATA link to 3Gbps instead of 6Gbps [4] disabled the VT-d on mainboard bios setting, with lijux luck.

This is in line with the reported speed when looking at an array rebuild on the internal Intel SATA ports in the server.

Only above 91xx chipsets are supported in FreeBSD. The above file locations are wrong! If irrational behaviour occurs, maybe try buying new cables, maybe that will solve the issue. Want to know if that peripheral is compatible with Linux?


[SOLVED] SATA Controller – HDD not showing

Updates following the suggestions from chanik: I won’t know as I don’t really have a good way of testing whether this would resolve the issue. Can I change the location where the initialization script is looking for the vendor, type, etc.

Having a problem logging in? SATA link up 1.

Marvell SATA Linux User Guide

The problem is reproducible! This problem was never truly resolved and the Kernel mailing list didn’t provide any real answers either. So it clearly points to an issue with the Xen system not recognizing the controller see my first remark above.

By clicking “Post Your Answer”, you acknowledge that you have read our updated terms of serviceprivacy policy and cookie policyand that your continued use of the website is subject to these policies. Page 1 of 3 1 2 3 Last Jump to page: Last edited by ardvark71; at No such file or directory.

Because this driver has not reach maturity, do not use it in a production environment. Marvell Technology Group Ltd.

The SMART data for the drive is fine – the drive itself is most definitely fine too recertified return – it also passes a SeaTools test. Select Yes for the driver disk. If you need to reset your password, click here.


Marvell based SATA cards

Windows 7 CrystalDiskMark benchmarks: The community claims it’s safe to just add the correct ID to kinux driver but 1 i’m not going to run untested code and 2 i’m not in the mood of patching and compiling the kernel and run FreeNAS with a custom kernel Joined Dec 1, Messages Thanks Over the time, I noticed that one disk would drop from the array – the disk could sometimes be re-added, sometimes it failed immediately again – erratically, finally having enough I’m trying to figure out where the issue lies By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features.

If you see the messages like the one in this page linkthen you’re still using NCQ. Sign up using Facebook. Andrew Cooks acooks wrote on marvelll It’s definitely a pain to figure out which chipset is crap and which is good.

I attempted to use manual control of NCQ but it seems the parameter does not stick.