On 27.11.2015 21:17, Bruno Friedmann wrote:

On Friday 27 November 2015 15.40:37 DetlevCM wrote:

...

Dear All,

after posting on the OpenSUSE forum ( https://forums.opensuse.org/showthread.php/511116-Sata-card-erratic-behaviou... ) and on Unix Stackexchange ( http://unix.stackexchange.com/questions/244419/marvell-88se9128-9123-sata-ca... ) it was suggested this may be a case for the mailing list.

So a short description (for those not reading the threads at the links - but extensive dmesg output is linked in the two threads): I have a Dell T20 home server with OpenSUSE and use a Marvell 88SE9123 (labelled 88SE9128) chipset based SATA card (2 ports) of which one is used. When a drive is connected to the SATA card and written to (file copy or zero fill) it will drop randomly and vanish from the listed devices, taking a reboot to reappear.

The drive is definitely OK (recertified Seagate) and an alternative drive has also been tested. When using Windows (even installing on the Dell on a spare harddrive), the SATA card tests fine running 5 passes of a 32GB CrystalDisk benchmark - using the same cable as well as the same harddrive (and alternative harddrive has been tested too just in case). But Linux... trouble... - I have now tested a Ubuntu LiveUSB with Kernel 3.13, OpenSUSE 13.2 with Kernel 3.16 - and regularly the server runs on OpenSUSE Leap 42.1 (Kernel 4.1 right now). Whether Native Command Queuing is on or off seems to make no difference whatsoever - be it on the fly via command line or as a Kernel parameter.

My conlusion is therefore that the problem can only be in two locations: 1) the Linux driver OR 2) the card's firmware itself (I cannot chose any kinds of settings on the card - it has the latest available BIOS, it is a StarTech PEXSAT32)

Maybe someone here has any ideas?

Side note: I am happy to collect logs etc. but while I am spending seemingly more and more time with Linux, I do not have any troubleshooting experience and would appreciate precise idiotproof instructions if extra logs/etc. are required.

Many thanks.

I'm not a "guru" kernel ;-)

I guess you best bet with the log you already have is also to fill with those as complementary information in https://bugzilla.kernel.org/show_bug.cgi?id=43160#c15 as suggested in the stackechange discussion.

Now my good sense with my 20 years of sysadmin and hardware things would be to simple discard this damn card. For few bucks you should be able to replace it, with a working chipset under linux.

You will save your time, your data, your nerves.

;-)

Thanks, the only worry I have there is that the server might dislike the card... I have an SiI 3132 (?) card but it isn't recognised, either an issue with the Dell or a dead card... - And before I start collecting hardware... (I have too many hdds already...) Unfortunately Dell also doesn't have a list of compatible cards (though the server was initially sold with the card I have) because in that case it would possibly be a more obvious choice. (Or I need to find owner forums... I stumbled across a German thread on these recently, I guess I bought it at the right time as a home server as it was very affordable. I may buy a new cheap card as a last resort and try that - but which do I pick? Marvell? SiI? Asmedia? - I was thinking of a 30 pounds miniSAS card, but it is a Marvell chip so might have the same problems... Different chipset? Well, will it work with the Dell... (of course it should, but that would be too easy...) (Given I have 3 of 4 drives in my RAID 6 array without the card I'm happy enough for the server to exist as it is for now - I'd be in panic mode otherwise.) I have added a post to the bug entry - brief rundown with links to the openSUSE forum and Stackexchange before I spam their entry with my logs. Maybe someone figures out the bug and fixes it. But yes, a new card would be a last resort option that is on my radar. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org